From: T. O. <tra...@ru...> - 2004-09-09 21:37:51
|
Question / Proposal: - The domain of a tag, after specification, is everything before its last colon or slash, e.g. tag:yaml.org,2002:int # domain = tag:yaml.org,2002 http://mymy.org/int # domain = http://mymy.org - Tags with domains are considered global, and expected to be unique (although it is not in any way enforced). - Tags without domains are local, and need not be unique. Is that about right? / Is that a good proposal? -- T. |
From: Clark C. E. <cc...@cl...> - 2004-09-09 21:49:23
|
T. I'm not sure what you're use case is. If your tag uses prefixes, that is, it uses a %TAG, then it is a URI, and considered global. Otherwise, if you use the !scheme it is local. If your tag is ommitted, it is ?unspecified ;) Cheers, Clark On Thu, Sep 09, 2004 at 05:37:47PM -0400, T. Onoma wrote: | - The domain of a tag, after specification, is everything before its | last colon or slash, e.g. | | tag:yaml.org,2002:int # domain = tag:yaml.org,2002 | http://mymy.org/int # domain = http://mymy.org | | - Tags with domains are considered global, and expected to be unique | (although it is not in any way enforced). | | - Tags without domains are local, and need not be unique. | | Is that about right? / Is that a good proposal? | | -- | T. | | | ------------------------------------------------------- | This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 | Project Admins to receive an Apple iPod Mini FREE for your judgement on | who ports your project to Linux PPC the best. Sponsored by IBM. | Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php | _______________________________________________ | Yaml-core mailing list | Yam...@li... | https://lists.sourceforge.net/lists/listinfo/yaml-core -- Clark C. Evans Prometheus Research, LLC. http://www.prometheusresearch.com/ o office: +1.203.777.2550 ~/ , mobile: +1.203.444.0557 // (( Prometheus Research: Transforming Data Into Knowledge \\ , \/ - Research Exchange Database /\ - Survey & Assessment Technologies ` \ - Software Tools for Researchers ~ * |
From: Sean O'D. <se...@ce...> - 2004-09-09 22:01:13
|
On Thursday 09 September 2004 14:49, Clark C. Evans wrote: > On Thu, Sep 09, 2004 at 05:37:47PM -0400, T. Onoma wrote: > | - The domain of a tag, after specification, is everything before its > | last colon or slash, e.g. > | > | tag:yaml.org,2002:int # domain = tag:yaml.org,2002 > | http://mymy.org/int # domain = http://mymy.org > | > | - Tags with domains are considered global, and expected to be unique > | (although it is not in any way enforced). > | > | - Tags without domains are local, and need not be unique. > | > | Is that about right? / Is that a good proposal? <slaps down Clark's top-posting> > I'm not sure what you're use case is. If your tag uses prefixes, > that is, it uses a %TAG, then it is a URI, and considered global. > Otherwise, if you use the !scheme it is local. If your tag is > ommitted, it is ?unspecified ;) This is sort of how I thought things were playing. Since %TAG is just macro mechanism for creating stored values which are used to resolve prefixes in tags, I don't see any reason to discern a "domain" from it. Sean O'Dell |
From: T. O. <tra...@ru...> - 2004-09-09 22:12:25
|
On Thursday 09 September 2004 05:49 pm, Clark C. Evans wrote: > T. > > I'm not sure what you're use case is. If your tag uses prefixes, > that is, it uses a %TAG, then it is a URI, and considered global. > Otherwise, if you use the !scheme it is local. If your tag is > ommitted, it is ?unspecified ;) So we got rid of being able to directly put --- - !tag:geewiz.net,2000:int 23 or --- - !http://herewe.org/int 23 ? _Have_ to use %TAG for those? I don't have a specific use case, I'm just wondering how one might uniformally differentiate transformations based on domain. -- T. |
From: Clark C. E. <cc...@cl...> - 2004-09-09 22:32:56
|
On Thu, Sep 09, 2004 at 06:12:20PM -0400, T. Onoma wrote: | So we got rid of being able to directly put | | --- | - !tag:geewiz.net,2000:int 23 | - !http://herewe.org/int 23 | | I _Have_ to use %TAG for those? Correct. It actually simplified a great deal of things, including the question you just asked. Of course, there is nothing stopping you from using a URL for your private tag, but that's entirely different... %TAG tag:geewiz.net,2002: gw %TAG http://herwe.org/ --- - !gw|int 23 # global tag:geewiz.net,2002:int - !!int 23 # global http://herwe.org/int - !tag:geewiz.net,2000:int 23 # private !tag:geewiz.net,2002:int - !http://herewe.org/int 23 # private !http://herewe.org/int ... Basically, when you get a tag via the API use these rules: - if it starts with a "!" it was a private tag - if it starts with a "?" the tags was unspecified - if it starts with an alpha, it is a global tag, matching the absolute URI production of RFC 2396 plus # [ ] - else the parser screwed up ;) Clark -- Clark C. Evans Prometheus Research, LLC. http://www.prometheusresearch.com/ o office: +1.203.777.2550 ~/ , mobile: +1.203.444.0557 // (( Prometheus Research: Transforming Data Into Knowledge \\ , \/ - Research Exchange Database /\ - Survey & Assessment Technologies ` \ - Software Tools for Researchers ~ * |
From: T. O. <tra...@ru...> - 2004-09-09 22:41:40
|
On Thursday 09 September 2004 06:32 pm, Clark C. Evans wrote: > Basically, when you get a tag via the API use these rules: > > - if it starts with a "!" it was a private tag > - if it starts with a "?" the tags was unspecified > - if it starts with an alpha, it is a global tag, matching > the absolute URI production of RFC 2396 plus # [ ] > - else the parser screwed up > > ;) Clark Got it. Thanks. -- T. |
From: T. O. <tra...@ru...> - 2004-09-10 00:49:22
|
On Thursday 09 September 2004 06:32 pm, Clark C. Evans wrote: > Correct. It actually simplified a great deal of things, including the > question you just asked. Of course, there is nothing stopping you from > using a URL for your private tag, but that's entirely different... > > %TAG tag:geewiz.net,2002: gw > %TAG http://herwe.org/ > --- > - !gw|int 23 # global tag:geewiz.net,2002:int > - !!int 23 # global http://herwe.org/int > - !tag:geewiz.net,2000:int 23 # private !tag:geewiz.net,2002:int > - !http://herewe.org/int 23 # private !http://herewe.org/int > ... > > Basically, when you get a tag via the API use these rules: > > - if it starts with a "!" it was a private tag > - if it starts with a "?" the tags was unspecified > - if it starts with an alpha, it is a global tag, matching > the absolute URI production of RFC 2396 plus # [ ] > - else the parser screwed up Just thought of something. If global URI's can only be in the %TAG directives, and the %TAG directives are essentially just prefixes, how will emitting work? -- T. |
From: David H. <dav...@bl...> - 2004-09-10 01:17:07
|
T. Onoma wrote: > On Thursday 09 September 2004 06:32 pm, Clark C. Evans wrote: > >>Correct. It actually simplified a great deal of things, including the >>question you just asked. Of course, there is nothing stopping you from >>using a URL for your private tag, but that's entirely different... >> >> %TAG tag:geewiz.net,2002: gw >> %TAG http://herwe.org/ >> --- >> - !gw|int 23 # global tag:geewiz.net,2002:int >> - !!int 23 # global http://herwe.org/int >> - !tag:geewiz.net,2000:int 23 # private !tag:geewiz.net,2002:int >> - !http://herewe.org/int 23 # private !http://herewe.org/int >> ... >> >>Basically, when you get a tag via the API use these rules: >> >> - if it starts with a "!" it was a private tag >> - if it starts with a "?" the tags was unspecified >> - if it starts with an alpha, it is a global tag, matching >> the absolute URI production of RFC 2396 plus # [ ] >> - else the parser screwed up > > Just thought of something. If global URI's can only be in the %TAG directives, > and the %TAG directives are essentially just prefixes, how will emitting > work? Two options, a spec change and a workaround: - change %TAG so that suffix can be empty. Then the emitter can output "%TAG !uri!" and prefix all URIs with !uri!. (In this case the unspecified tags should start with a non-URI character.) - have the emitter output "%TAG !scheme! scheme:" for each URI scheme used in the document. -- David Hopwood <dav...@bl...> |
From: David H. <dav...@bl...> - 2004-09-10 01:19:46
|
David Hopwood wrote: > T. Onoma wrote: >> Just thought of something. If global URI's can only be in the %TAG >> directives, and the %TAG directives are essentially just prefixes, how >> will emitting work? > > Two options, a spec change and a workaround: > > - change %TAG so that suffix can be empty. I meant "so that prefix can be empty". > Then the emitter can output "%TAG !uri!" and prefix all URIs with !uri!. > > (In this case the unspecified tags should start with a non-URI > character.) > > - have the emitter output "%TAG !scheme! scheme:" for each URI scheme used > in the document. -- David Hopwood <dav...@bl...> |
From: David H. <dav...@bl...> - 2004-09-09 23:03:51
|
T. Onoma wrote: > Question / Proposal: > > - The domain of a tag, after specification, is everything before its > last colon or slash, e.g. > > tag:yaml.org,2002:int # domain = tag:yaml.org,2002 > http://mymy.org/int # domain = http://mymy.org > > - Tags with domains are considered global, and expected to be unique > (although it is not in any way enforced). > > - Tags without domains are local, and need not be unique. My assumption was that in #11, the suffix for %TAG must match ("!" | schemec+ ":") (uric | "[" | "]")* Therefore a tag is private iff it begins with "!". -- David Hopwood <dav...@bl...> |