From: Oren Ben-K. <or...@be...> - 2004-09-03 16:09:06
|
On Friday 03 September 2004 18:11, T. Onoma wrote: > Quick note to add to this. It is almost as if we have the default prefix > just so we can get to yaml's typing with, > > --- %TAG:yaml.org,2002: > > Like I said before, that _will_ be far and away the most common YAML line > of the future if that's the case. Yes, and I'm trying to get rid of it :-) > Even so it forces you to be somewhat > "padantic" becuase you'll still have to put the !int, right? I mean > > --- > - 4 > > Won't come back as integer will it. Two points. First, in any reasonable implementation, it will. Again, that's part of what makes yaml.org types special. You can reasonably expect that any implementation will give you an easy way to say: "please use implicit typing to automatically detect the following yaml.org types: !int, !bool, ...". Note, it is _still_ an application/schema choice whether to use these as "implicit" types. Its just that they are "common" enough to most schemas that support for them is "universal". Second, you are mixing up two completely separate steps. "Globalization" converts the tag-as-written-in-the file into a "globally unique tag" or, at the very least, "a tag unique within the current application/schema". In contrast, a completely seperate step is "tag resolution" - computing the tag for nodes that have _no_ tag specified in the file in the first place. There's absolutely no connection between these steps, except that a schema describes both how to "globalize" private tags _and_ how to "resolve" missing ones. So, trying to solve the "tag resolution" problem using mechanisms for "tag globalization" only muddies the waters and is doomed to lead to all sort of nastiness. Have fun, Oren Ben-Kiki |