Re: Tag URIs

Hmmm. There is a reason we recommend using the tag: URI scheme, as it
properly addresses all these issues directly. Comparing URIs for
equality, in general, is pretty much impossible to do in a
scheme-independent way...

How about adding a paragraph to the equality section saying:

... Different URI schemes may define different rules for testing the
equality of tags. Since a YAML processor cannot be reasonably expected
to be aware of them all, it "must" resort to a simple
character-by-character comparison. This also happens to be the
comparison method defined by the tag: URI scheme. Tags in a YAML stream
"must" therefore be written in a canonical way so that such comparison
would yield the correct results.

And also add a sentence at production 39: , paragraph 2:

The YAML processor must not expand such escaped characters. Tag
characters are preserved and compared exactly as written in the YAML
stream, without any processing.

cce, ingy: What do you think?

BlueGM: Thanks for reviewing the spec!

	Oren Ben-Kiki

On Mon, 2009-04-20 at 12:13 -0400, BlueGM wrote:
> One other recommendation:
> ...
> Add a statement to section 3.2.1.2 Tags of the 1.2 specification that
> states that URIs are always to be treated as case-sensitive,
> regardless of the scheme used, and that this includes the scheme name
> (the part before the first colon). If this can not be made a "MUST"
> statement because of existing implementations, then perhaps use a
> "SHOULD" statement instead.
> 
> Thanks again,
> 
> Blue G




------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p