Hi Ted,
At 10:02 24-01-11, Ted Hardie wrote:
I think the key question is whether this qualifies as well-defined
(section 2.3).
The draft declares some tokens/strings to be "reserved", and names one such
string. It also declares that other strings may be reserved by other
specifications,
but it provides no way to discover them. This leads someone who
wishes to mint
a new "about" uri with no way of discovering whether a specification
has reserved
it. To me, that means "reserved" is not currently well-defined.
Yes.
I would not personally propose HTML5 be the canonical source for
reserving these
strings, because I have some serious reservations about that spec's
tendency to
fork other specs. But the conversation thus far leads to believe that the two
probably ways forward are to
1) have a registry and populate it with blank and those
from the HTML5 spec as initial values
2)make HTML5 the only spec which can reserve these strings, an move
blank into it.
Agreed.
Regards,
-sm
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf