Re: [Uri-review] In WG last call review of URI Schemes rtsp, rtsps and rtspu

["Martin J. Dürst" <[e-mail]>]

On 2012/05/11 2:44, Roy T. Fielding wrote:
> On May 9, 2012, at 7:21 AM, Ted Hardie wrote:
>
>> On Tue, May 8, 2012 at 9:28 PM, Roy T. Fielding<[e-mail]>
>> wrote, quoting Graham Klyne:
>>
>>>>    Note that this specification, like any URI scheme specification, does
>>>>    not define syntax or meaning of a fragment identifier (see [STD66]),
>>>>    because these depend on the type of a retrieved representation.  In
>>>>    the currently known usage scenarios, a 'mailto' URI cannot be used to
>>>>    retrieve such representations.  Therefore, fragment identifiers are
>>>>    meaningless, SHOULD NOT be used on 'mailto' URIs, and SHOULD be
>>>>    ignored upon resolution.  The character "#" in<hfvalue>s MUST be
>>>>    escaped as %23.
>>>>
>>>> This seems to be fully in line with the discussion up to here, including Roy's comment above, but if anybody thinks it needs to be changed, please send some new proposed wording.
>>>
>>> The second to last sentence is wrong.  That spec cannot make
>>> normative requirements about something that is out of scope;
>>> any fragment is completely outside the scope of a URI scheme
>>> specification.  Just remove the "Therefore, ... resolution."
>>> sentence -- it serves no useful purpose.

>> Would you still object if it simply said "Therefor fragment
>> identifiers are meaningless in current email contexts."?  I think this
>> remains useful and it eliminates the normative language.
>
> I wouldn't object, but I personally don't like talking about
> "current contexts" in a spec that will live for decades.
> I don't see why it matters -- if it is meaningless, nobody
> will use them; if they use them, they won't be meaningless.

I agree that "current contexts" is the wrong wording. What about 
something like:
"Therefore, at the time of publication of this document, fragment 
identifiers are meaningless in current email contexts."

Regards,   Martin.