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. |