Re: p3-payload proofreading

Anthony Bryan wrote:
> ...
>> Well, if there was a type called "type", it would be valid.
>>
>> It seems to me that
>>
>>        "...and "type/*" indicating all subtypes of that type"
>>
>> is sufficiently clear. Do you think something like
>>
>>        "...and "X/*" indicating all subtypes of type X"
>>
>> would make things clearer (this would be easier if IETF specs allowed font
>> changes...).
> 
> Yes, that would be easier...
> 
> What about going from smaller to larger?
> 
> The asterisk "*" character is used to group media types into ranges,
> with "X/*" indicating all subtypes of type X and "*/*" indicating all
> media types.
> ...

I have to say that I'm not sure that there's a problem here.

What do others think?

Best regards, Julian

Received on Monday, 8 February 2010 16:12:01 UTC