Re: [Yaml-core] #9a - No More Warts

[Oren Ben-K. <or...@be...>]

On Sunday 05 September 2004 09:24, Clark C. Evans wrote:
>    This is draft 9a, based on the 9th pass draft.  I think with this
>    draft I finally 'grok' what Brian is saying:

This completely ignores my use case. There's just one extra point I _must_=
=20
make:

> The most important impact of this change is that tag 'resolution'
>  need not be detailed in the specification 'proper' -- in fact, it
>  is completely up to the application, as Brian has been insisting.
>  Resolution is no longer special, it is simply a transformation of
>  the input graph to produce another graph, where the target graph is
>  the one that is actual loaded into native data structures. =A0While
>  this should be explained in the specification; the only "limits"
>  placed on the transformation is that serialization and presentation
>  features should not be used during this process.

So, in effect, tags now mean "whatever the current piece of code says they=
=20
mean"?

=46or example, my application can now convert all !foo.com,2003:bar/baz=20
to !baz.com,2004/foo/bar in sequence entries with prime indices, and the wo=
rd=20
"chaos" doesn't appear in the document an even number of times.

Lovely. I now understand how Brian feels when he thinks both of us went=20
completely ethereal. I have no idea at all what you are trying to achieve,=
=20
and why. Reading your proposal, I see something like that:

1. If a tag isn't specified, its converted to=20
"unspecified-mapping/sequence/scalar/plain". Fine.

2. The YAML specification intentionally does not say anything about how tag=
s=20
are to be used. Specifically, issues of uniqueness, mix-and-matching schema=
s,=20
migrating "private" documents to "public" documents and so on are beyond th=
e=20
scope of the specification.

3. Oh, BTW, here's something nice: You can use %TAG to have a prefixing=20
shorthand for some arbitrary set of tags. Since apps can do anything they=20
want with tags, there's no guarantee that using this means anything in=20
particular - for example, two nodes with the same %TAG based tag may have=20
completely different types - but hey, its neat, and you _can_ use it for go=
od=20
deeds if you feel like it. Or you can just ignore it (most people do).

All I can say is: -1000.

Could someone please tell me again what's wrong with #7? Ah, the extra "!",=
=20
right. Well, using proposal #9 to solve this is like nuking your home to ge=
t=20
rid of a fly.

Have fun,

	Oren Ben-Kiki