[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-rx] proposed resolution to i017
I disagree. We should not assign a final namespace now, we should simply define the convention to use. Anytime a spec changes that may affect conformance or adds a new feature the namespace should change. We can not make the determination now that this will be true for the work of this TC from now until we reach the point of producing an OASIS Standard. It is a virtual certainty that products will ship that have support for intermediary versions of the spec. If the namespace is constant across all of these it will make interoperability in the field much more difficult. Each published version of the spec should have its own unique namespace. The churn required in code to do this is far less painful than the pain customers will feel trying to plug together implementations that unbeknownst to them conform to two (or more) different versions of the spec. Having a distinct uri for each published version of the spec, and subsequently used in products that ship with support for those versions, helps greatly in preventing this. I do agree we do not need to resolve i015 before determining the form of the namespace on the same grounds that you do below. I propose the following resolution to i017[1]: The namespace URI used for our specs should follow the draft AIR Guidelines as follows: http://docs.oasis-open.org/yyyy/mm/[productname] Where [productname] is the name from the resolution of issue i015 [2] for the respective specs and yyyy/mm is the date of the published version of the specification. [1] http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/13809/Re liableMessagingIssues.xml#i017 [2] http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/13809/Re liableMessagingIssues.xml#i015 -----Original Message----- From: Christopher B Ferris [mailto:chrisfer@us.ibm.com] Sent: Wednesday, August 03, 2005 7:52 AM To: ws-rx@lists.oasis-open.org Subject: [ws-rx] proposed resolution to i017 All, I propose that we resolve issue i017 [1] as follows: The namespace URI used for our specs should follow the draft AIR guidelines. e.g. http://docs.oasis-open.org/[productname]1 where [productname] is whatever we conclude for issue i015 [2] for the respective specs. The trailing '1' signifies the "version" of the *namespace* but is NOT in any way tied to the version/revision of the corresponding schema for that namespace (see my previous rants on this subject). This will allow us to assign a final namespace URI for the specifications that we are chartered to produce (rather than having to either guess at a date, or worse yet, change the namespace name with each successive published draft -- BLECH!) I would also assert that we do not need to resolve i015 before resolving that the form of the namespace URI will be as above... we just fill in the blank once we have settled on a [productname] for our specs. Benefits: this yields a nice SHORT namespace URI (see my previous rants) it allows us to assign a final URI now, rather than waiting until we are essentially done (good for implementation as it reduces unnecessary churn to tweak the namespace URI in code). [1] http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/13809/Re liableMessagingIssues.xml#i017 [2] http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/13809/Re liableMessagingIssues.xml#i015 Cheers, Christopher Ferris STSM, Emerging e-business Industry Architecture email: chrisfer@us.ibm.com blog: http://webpages.charter.net/chrisfer/blog.html phone: +1 508 377 9295
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]