[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [tag] namespace issues still
Many thanks Mary, that's great. Best regards Steve --- Stephen D Green 2010/1/7 Mary McRae <mary.mcrae@oasis-open.org>: > Hi Stephen, > > I believe that other TCs have done so, so you're in the clear. > > Mary > > > > On Jan 7, 2010, at 10:10 AM, Stephen Green wrote: > >> Thanks for helping us out Mary. >> >> The namespace we have at present is >> >> "http://docs.oasis-open.org/ns/tag/taml/201001"; >> >> If this would meet with your approval (I was thinking >> that the slash in "taml/201001" might be regarded >> as unconventional with respect to the ns guidelines) >> this would save me a whole lot of trouble by letting >> us ballot the existing specs and schema. >> >> Best regards >> >> Steve >> --- >> Stephen D Green >> >> >> >> >> 2010/1/7 Mary McRae <mary.mcrae@oasis-open.org>: >>> Hi Stephen, >>> >>> Here's a couple of factoids that might help. >>> >>> 1. The date string typically has nothing to do with the approval date in practice. It seems that TCs decide at some point to include a number, pick an arbitrary date, and stick with it. So don't worry that whatever date you use has to match with the actual approval date at any particular stage of the specification. >>> >>> 2. The TC is free to name the namespace. If you want to use taml that's perfectly acceptable since 'tag' is already in the path. >>> >>> Regards, >>> >>> Mary >>> >>> >>> Mary P McRae >>> Director, Standards Development >>> Technical Committee Administrator >>> OASIS: Advancing open standards for the information society >>> email: mary.mcrae@oasis-open.org >>> web: www.oasis-open.org >>> twitter: @fiberartisan #oasisopen >>> phone: 1.603.232.9090 >>> >>> Standards are like parachutes: they work best when they're open. >>> >>> >>> >>> On Jan 7, 2010, at 6:37 AM, Stephen Green wrote: >>> >>>> Quoting http://docs.oasis-open.org/specGuidelines/namingGuidelines/resourceNaming.html#NamespaceDesign >>>> >>>> "HTTP scheme namespace URIs must be rooted at the >>>> "docs.oasis-open.org" Internet domain using one of the following two >>>> patterns with the /ns/ path element, unless an alternative URI is >>>> approved by the TC Administration: (1) >>>> http://docs.oasis-open.org/ns/<ShortName>/<Versioned-NS-String> OR (2) >>>> http://docs.oasis-open.org/<ShortName>/ns/<Versioned-NS-String>. >>>> ShortName is the approved short name for the TC or Member Section; >>>> Versioned-NS-String is a short string identifying a namespace using a >>>> versioning subcomponent. For example, given an imaginary TC short name >>>> 'ws-xx' and a versioned namespace string element 'WS-XX-20080115', a >>>> NS URI would be: http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115 OR >>>> http://docs.oasis-open.org/ws-xx/ns/WS-XX-20080115."; >>>> >>>> I note "unless an alternative URI is approved by the TC >>>> Administration" and by 'TC Administration' I take it it >>>> means the OASIS staff, rather than TAG TC. >>>> >>>> The pattern which for us would therefore be >>>> >>>> http://docs.oasis-open.org/ns/tag/<Versioned-NS-String> >>>> >>>> (where there are no slashes in '<Versioned-NS-String>' >>>> so that seems to make our existing namespace one >>>> requiring special TC Admin approval). >>>> >>>> This would mean we need something like >>>> >>>> http://docs.oasis-open.org/ns/tag/tag-20100129 >>>> >>>> The trouble is, to change the namespace I need to change >>>> the guidelines too (since they include the example markup). >>>> I don't know if we can assume the approval date will be >>>> 20100129 and it seems likely it could be sometime in Feb. >>>> On one hand the date needs to be able to reflect the precise >>>> committee draft (in case there is a further committee draft >>>> for version 1.0 requiring a change of namespace). On the other, >>>> I can't leave the namespace to the last minute after approval >>>> because the namespace needs to be changed in various >>>> places besides the titles (e.g. in the example in the guidelines >>>> and in the schema embedded in the markup spec). So my >>>> preference, which I think is within our scope of TC discretion, >>>> is to use a less precise date, just enough to pinpoint a >>>> uniques comittee draft. Because we might approve in Feb >>>> (could we time it to do so) more easily than limiting it to Jan >>>> I'd prefer Feb as a month of approval in case we need a >>>> second ballot or the ballot is delayed. >>>> >>>> i.e. >>>> http://docs.oasis-open.org/ns/tag/tag-201002 >>>> >>>> I'd kind of prefer to replace the second 'tag' with 'taml' but >>>> I'm not sure how much scope the TC has to do this so, unless >>>> assured by Admin http://docs.oasis-open.org/ns/tag/taml-201002 >>>> would be OK, I'll use >>>> >>>> http://docs.oasis-open.org/ns/tag/tag-201002 >>>> >>>> just to be on the safe side. >>>> >>>> It looks like I'll need to create a new set of documents. Sorry. >>>> >>>> Best regards >>>> >>>> Steve >>>> --- >>>> Stephen D Green >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this mail list, you must leave the OASIS TC that >>>> generates this mail. Follow this link to all your TCs in OASIS at: >>>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >>>> >>> >>> > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]