Re: [Yaml-core] YAC 19

[Brian I. <in...@tt...>]

On 11/02/02 02:03 -0500, Clark C . Evans wrote:
> | Alas, this doesn't work, because some XML namespaces (as you have
> | pointed out) use fragments! Remember originally we wanted to use
> | '#' to separate the format from the type (the format being a
> | "fragment" of the type). A lovely scheme, except that XML namespaces
> | using '#" killed it. Likewise for this notion.
> |
> | So... what character should we use to separate the XML namespace
> | from the tag name? ';' would work *technically*, but has dubious
> | legality. Our alternative is to choose a character which is a
> | normal URI character but is not allowed in XML tags. Something
> | in the set "$-_.+!*'(),". Since '$' isn't a valid XML tag
> | character. Does that sound reasonable?
> 
> Just beacuse it's not a valid xml tag name, doesn't mean
> that it can't occur in an XML namespace name.  But in any
> case, I don't think this is a use case we should worry 
> about... let's keep our "type" notion specific to the
> YAML scheme...

I leave the XML decisions in your and Oren's capable hands.

> | I must say I'm having a hard time making a decision about this.
> | On the one hand, using normal domain names is much more URI-like.
> | On the other hand, I think using reverse DNS names makes more
> | sense due to it more accurately reflecting the actual hierarchy of
> | things; in fact if I were writing DNS in the first place I'd be using
> | a reverse order *everywhere*. I can't help but feel that having
> | shared prefixes is useful in various small ways...
> 
> Being able to break an "authority" (the stuff to the left
> of the ; in a yaml: scheme) with our ^ trick isn't a big 
> use case.  While it probably is a bigger use case to break
> items in the "type" partition (think Java packages).   Thus,
> for the principle of least suprise, let's go back to regular
> DNS stuff.  Note, this makes sense as Brian pointed out,
> since the real stuff we want to slice and dice is already
> at the end of the URI.

Let's go with forward DNS. I can think of ways to abbreviate the domain name
if it ever became a problem:

    !perl.yaml.org;glob -> !perl;glob
    !perl.clarkevans.com;timesheet
    !python.clarkevans.com;timesheet -> !python.;timesheet

The domain can be relative by ending it with a dot. I don't see this as a use
case, but if it pops up, we're OK.

Cheers, Brian