headers
Graham Klyne | 4 Apr 2000 11:57

draft-ietf-conneg-feature-hash-04.txt

Folks,

I've just submitted <draft-ietf-conneg-feature-hash-04.txt> for publication 
as a revised Internet Draft.

As agreed at the RESCAP WG meeting in Adelaide, all mention of URI 
references to feature sets has been removed.  (I am planning to try and 
document the issues with these separately.)

As this is getting close to final form, some review would be good.  I think 
that critical review of section 3.1.1 (it's only half a page) would be 
particularly welcome when the draft is issued.

Subject to review comments, the substantive content of this draft is pretty 
much in final form.  I still wish to review the example sections:  (a) 
contributions of meaningful examples would be welcome, and (b) I plan to 
implement the hash algorithm described and substitute some _real_ MD5 hash 
values in the examples.

#g
------------
Graham Klyne
(GK <at> ACM.ORG)
Permalink | Reply | 15 comments |
headers
Graham Klyne | 6 Apr 2000 12:05

Feature expression syntax; quoted strings

Folks,

In looking through RFC 2533, I note that a string value for a feature may 
not contain a double quote character, there being no escape mechanism 
within a string.  (This was lifted from RFC 2234, which has alternative 
mechanisms for describing specific individual characters.)  On reflection, 
it seems that assuming that a feature value can never contain a double 
quote character could cause problems in the future.

I am thinking that there should probably be an escape mechanism defined so 
that a quote character can be included in a string -- using a backslash 
escape character is the technique that strings to mind, so that special 
constructs '\\' and '\"' within a string are introduced.

I am not aware of any current use of RFC2533 which would be impacted by 
such a change.

If this change is felt to be a Good Thing, it will have some impact on the 
feature-hash draft (section 3.1.1: description of normalization logic).

Process question:  in view of the CONNEG WG being wound up, what is the 
process for moving the work to draft standard, as and when implementations 
are created?

#g

------------
Graham Klyne
(GK <at> ACM.ORG)
(Continue reading)

Permalink | Reply | 2 comments |
headers
Internet-Drafts | 10 Apr 2000 13:35
Picon
Favicon

I-D ACTION:draft-ietf-conneg-feature-hash-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Content Negotiation Working Group of the IETF.

	Title		: Identifying composite media features
	Author(s)	: G. Klyne, L. Masinter
	Filename	: draft-ietf-conneg-feature-hash-04.txt
	Pages		: 16
	Date		: 07-Apr-00
	
In RFC 2533 [1], an expression format is presented for describing
media feature capabilities as a combination of simple media feature
tags [2].
This document describes an abbreviated format for a composite media
feature set, based upon a hash of the feature expression describing
that composite.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-conneg-feature-hash-04.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-conneg-feature-hash-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.
(Continue reading)

Permalink | Reply | 0 comments |
headers
hardie | 10 Apr 2000 19:34
Favicon

Re: Feature expression syntax; quoted strings

Am I getting old?  I seem to remember going through this in
several times in previous lives.  

First, are you sure that anyone really wants to use a double quote
inside a string?  It is fairly common to disallow it when it is the
delimiter, which is the case here?  Second, are these use cases places
where a different method for encoding the double quote (such as
URL-encoding) already exists?  Third, since this definition of
string has been in place from the beginning, is it unreasonable
to presume that those designing the values to be used with this
system have been taking it into account and taking appropriate
action to avoid the problem?

Last, please realize that we will not modify "string" at this point.
If we absolutely must have a representation that allows double quotes,
we will need to introduce a new value type.  That will cause a need to
update the syntax and registration docs, which recycles everything at
proposed.   It also seems to cause problems for our ITU friends,
and may cause a serious deployment delay.

To answer your other process question, anyone who has evidence that
the requirements of Draft standard have been met by a standard currently
at Proposed may submit that evidence to the relevant ADs for consideration.
If they are satisified, they request that the IESG consider changing
the document from Proposed to Draft.  If new, non-normative language
is added or two documents combined (as would be the case for us), a
new document would be submitted at the same time as the evidence and
it would be given a new RFC number.

				regards,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Patrik Fältström | 10 Apr 2000 19:43
Favicon

Re: Last Call: Indicating media features for MIME content to (fwd)

At 12.00 +0000 2000-02-15, Graham Klyne wrote:
>I think there are some useful comments here.  I think a revision 
>would be good, but I'd like to clarify with Ned some of the points 
>raised before proceeding.

Can you give me a status on where you are with this update?

   paf
Permalink | Reply | 0 comments |
headers
Graham Klyne | 11 Apr 2000 11:10

Re: Feature expression syntax; quoted strings

At 10:34 AM 4/10/00 -0700, hardie <at> equinix.com wrote:
>Am I getting old?  I seem to remember going through this in
>several times in previous lives.

Oops, sorry.  If we, did, I forgot.  (I suspect it's I who am getting old :-)

>First, are you sure that anyone really wants to use a double quote
>inside a string?

No I'm not.  That's why I ask.

>   It is fairly common to disallow it when it is the
>delimiter, which is the case here?

It is common, I believe, when there are alternative ways of expressing the 
same value (e.g. alternative quotes).

>   Second, are these use cases places
>where a different method for encoding the double quote (such as
>URL-encoding) already exists?

I am thinking specifically of string *values* for features, for which there 
is no alternative.

>   Third, since this definition of
>string has been in place from the beginning, is it unreasonable
>to presume that those designing the values to be used with this
>system have been taking it into account and taking appropriate
>action to avoid the problem?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Graham Klyne | 11 Apr 2000 10:44

Re: Last Call: Indicating media features for MIME content to (fwd)

At 03:13 AM 4/11/00 +0930, Patrik Fältström wrote:
>At 12.00 +0000 2000-02-15, Graham Klyne wrote:
>>I think there are some useful comments here.  I think a revision would be 
>>good, but I'd like to clarify with Ned some of the points raised before 
>>proceeding.
>
>Can you give me a status on where you are with this update?

I've summarized to the list updates arising from Ned's comments.  Apart 
from that I've not done anything, per our previous exchange, awaiting other 
comments (of which none).

For convenience, I attach a summary of the proposed changes below.

#g

>I think we are in agreement.  To summarize the proposed changes (mainly 
>for the benefit of others following this):
>
>draft-ietf-conneg-feature-type-02.txt:
>
>(a) restrict content of type to content-type only, without parameters.
>
>(b) add text explaining how to deal with content-type parameters.
>
>draft-ietf-conneg-content-features-xx.txt:
>
>(c) clarification of interpretation of Content-feature headers on outer 
>multipart.  Specifically, MUST NOT assume relationship between outer 
>header and any specific inner part.  Also explain that content-feature can
(Continue reading)

Permalink | Reply | 3 comments |
headers
Patrik Fältström | 11 Apr 2000 13:21
Favicon

Re: Last Call: Indicating media features for MIME content to (fwd)

At 9:44 AM +0100 4/11/00, Graham Klyne wrote:
>For convenience, I attach a summary of the proposed changes below.

As far as I understand, new versions are needed of the documents. So, 
please create those, send them to the Internet-Draft archive, and let 
me know when you see the announcement.

    Patrik
Permalink | Reply | 0 comments |
headers
steve | 12 Apr 2000 14:24

Looking to work with you


I came upon your web site as a result of a metacrawler search. I am the Business Development Officer for
DigitalMen.com.  I am looking to create relationships with web sites with similar demographics as ours. 
My goal is to create e-commerce and banner ad exchanges. Our site is http://www.digitalmen.com . I did a
search using the key word "Men" and your site came up.  I would appreciate it if you could review our site and
let me know if you feel there would synergy between our sites.

Our site was conceived and developed as a comprehensive Internet destination site for one of the largest
and most lucrative target markets online - men aged 18 - 50. Intending to be the ultimate Internet resource
for men, DM provides an "edgy" environment, graphically rich and bold in design in accordance with
current tastes of the 18 to 50 demographic. 

We are looking to do our grand opening the end of this month (the 24th). With a combination of a national radio
advertisement campaign and recent signing of a celebrity spokesman, I believe the traffic and exposure
from the site will be extraordinary.  With the timing of the opening I would like to create any
relationships before the grand opening

The DigitalMen.com web site is comprised of twelve "channels", each representing a general subject
popular among men. These channels are: Toys, Women, Style, Money, Debauchery, Health, Sports, News,
Entertainment, Travel, and the Digital Men Marketplace.  If there is an area that most fits your site we
could place your banner on a specific channel.

Inside each channel, men find an assortment of articles, surveys, and editorials-- consistent with the
enduring themes of men's interest. These concisely written product reviews and lifestyle features
serve as quick reference for the male consumer, delivering pertinent information with wry humor, at the
same time providing links to more in-depth resources and valuable online shopping opportunities. 

After reviewing our site please e-mail me if we can work together.  I there is an individual that you feel I
should speak to at your organization please forward the name to me and I will respond at once. I am available
9-6 pacific time.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 13 Apr 2000 12:52
Picon
Favicon

I-D ACTION:draft-ietf-conneg-content-features-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Content Negotiation Working Group of the IETF.

	Title		: Indicating media features for MIME content
	Author(s)	: G. Klyne
	Filename	: draft-ietf-conneg-content-features-03.txt
	Pages		: 13
	Date		: 12-Apr-00
	
In 'A syntax for describing media feature sets', an expression
format is presented for describing media feature capabilities using
simple media feature tags.

This memo defines a MIME 'Content-features:' header that can be
used to annotate a MIME message part using this expression format,
and indicates some ways it might be used.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-conneg-content-features-03.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-conneg-content-features-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane