[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ws-tx] Issue 015: Replace namespace and action URIs
"wstx" or "ws-tx" - a question to tax the finest minds. Given the following proposed format for namespace URIs: http://docs.oasis-open.org/[TC short name]/[product]/yyyy/mm/[element name], we should consider the member review draft of the new ASIS guidelines for artifact naming [i], in which the definition of "TC Short Name" is: "The short name assigned by the TC Administrator to the Technical Committee, with any hyphens eliminated." The ASIS guidelines may change - many TCs (including TX) already use a hyphen in the [TC short name] of existing TC product. As a path of least resistance, I suggest the TX TC uses "wstx" as the [TC short name] in our namespace URIs. [i] http://www.oasis-open.org/committees/download.php/16546/ArtifactStandardIdentificationSchemeForMetadata-1.0.1.pdf Regards, Ian Robinson STSM, WebSphere Messaging and Transactions Architect IBM Hursley Lab, UK ian_robinson@uk.ibm.com "Colleen Evans" <coevans@microsof t.com> To <ws-tx@lists.oasis-open.org> 08/02/2006 23:00 cc Subject [ws-tx] Issue 015: Replace namespace and action URIs There are three considerations related to this issue [1]: 1. The action and namespace URIs need to be updated to adhere to the OASIS guidelines. 2. The TC needs to determine when URIs should change (e.g., between committee drafts). 3. The TC should have a namespace document to point to various resources. Related to consideration 1, Ian's proposal lists the URIs that should be updated and suggests a format: replace http://schemas.xmlsoap.org/ws/2004/10/... with http://docs.oasis-open.org/wstx/2005/11/... Based on the OASIS guidelines and the WS-RX TC's experience, I propose we add a '-' (ws-tx) which is the TC short name (not wstx) and switch the date and product order: http://docs.oasis-open.org/ws-tx/[product]/yyyy/mm/[element name], or yyyymm without the '/' using 2006 rather than 2005 for the year. For example: http://docs.oasis-open.org/ws-tx/wscoor/2006/04/Register Also, there are elements missing from the list of URIs in the issue (e.g., CreateCoordination context). The editors should review the list and ensure all action and namespace URIs are identified. Related to considerations 2 and 3, the TC needs to determine when the NS should change. The submitted issue also touches on this: "....when an incompatible schema change is made so that the XML namespace of the schema needs to be changed." The WS-RX TC has resolved an issue on versioning policy that covers this same territory [2]. I suggest that the WS-TX TC should consider a similar direction. Best regards, Colleen [1] http://lists.oasis-open.org/archives/ws-tx/200512/msg00075.html [2] http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml#i088
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]