[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Membership and Public Review of OASIS Artifact StandardIdentification Scheme for Metadata
WS-TX TC Members,
Normally I would not express an interest in this TC's
design choices, as I only monitor the technical activity
from a distance. Indeed, in this case, the concern expressed
operates at the meta-level, relating to OASIS IT support and
Web Architecture best practices.
In summary, I would urge the TC to consider the arguments
posted by Chris Ferris [1] [2] about NOT rushing to
implement the design for "Persistent URIs" suggested
in ASIS [5] Normative Section 8, which locates a
required "Technical Committee Tree" at the URI
"docs.oasis-open.org/[tcShortName]" -- where "tcShortName"
is defined as "the short name assigned by the TC Administrator
to the Technical Committee, with any hyphens eliminated." [8]
Similarly, I would recommend that the WS-TX TC NOT craft any
new HTTP scheme URI namespace names based upon a hyphenless
variant (wstx), rooted at http://docs.oasis-open.org/wstx/,
per current discussions and the issues list [3] [4]. At least,
not until any such rule/policy is mandated by the OASIS Board.
Considerations:
a) your TC already has a TC Root on the new document server
being used for predictable (and persistent) URIs:
http://docs.oasis-open.org/ws-tx/
b) the new document server, as announced in November 2005 by
OASIS Staff members Scott McGrath and Peter Roden, has been
authorized as the canonical location for TC specs: the OASIS
TC Administration announced its plans to "exclusively to
use the [Internet] domain "docs.oasis-open.org" for public
access to approved work product of its technical committees..."
http://lists.oasis-open.org/archives/chairs/200511/msg00002.html
c) the official short name for your TC contains a hyphen, and
this canonical spelling is used in numerous official
contexts; for example:
TC Name: OASIS Web Services Transaction (WS-TX) TC
Chartered name: OASIS Web Services Transaction (WS-TX) Technical Committee
http://lists.oasis-open.org/archives/ws-tx/200510/msg00000.html
TC URI: http://www.oasis-open.org/committees/ws-tx/
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-tx
Charter: http://www.oasis-open.org/committees/ws-tx/charter.php
Document Repository (OOLibrary): http://docs.oasis-open.org/ws-tx/
TC List: http://lists.oasis-open.org/archives/ws-tx/
d) The design contemplated in ASIS which removes the hyphen is,
as far as I can tell, unmotivated. It also conflicts with
current OASIS practice, and with direct instructions given to TCs
about how to construct persistent URIs using the document server
at http://docs.oasis-open.org/
e) The original motivation for a hyphenless tcShortName was
apparently [9] justified by a design -- now abandoned --
in which the TC Short Name was required in the construction
of an artifact identifier string: "owner" would have been
literal "oasis" or any canonical tcShortName with hyphen
changed to underscore. That old design for the string was:
owner-product-version-part-artifacttype-stage-revision-language.form
Later, the TAB's design changed to "eliminate" the hyphen in the
tcShortName so that no component would contain a hyphen internally.
However, since ASIS no longer uses any "owner" or "tcShortName"
as a component in an OASISdefinedName -- itself an option for
constructing an ArtifactIdentifier -- there is IMO no motivation
for a grammar production which defines (and universally applies)
tcShortName as hyphenless. The new ASIS (optional) format is as
follows:
product-productVersion-artifactType-stage-revision[-language].form
f) We have enough opportunities for confusion without introducing
a new hyphenless variant of WS-TX: that would pointlessly
compound the QA problems associated with URIs (e.g., moving
spec publication from Kavi and from www.oasis-open.org to
http://docs.oasis-open.org/ is already enough of a challenge).
Apart from this: I do urge members of the WS-TX TC to carefully
review the ASIS specification, out for review until March 1, 2006,
as announced [6].
The draft ASIS document and the memo describing its review
sent on February 6, 2006 declared that use of the ASIS document
would be:
"recommended and not mandated"
The characterization "recommended and not mandated" has been
clarified in a memo sent to the (not generally open) OASIS
Chairs list [7]:
"Our Board of Directors plans to consider in March
whether to make it [ASIS], or portions of it,
mandatory policy after the current review is completed."
Respectfully
Robin Cover
================= Notes:
[1] Ferris 2006-02-21
Subject: Re: [ws-tx] Issue 015: Replace namespace and action URIs
From: Christopher B Ferris <chrisfer@us.ibm.com>
To: Ian Robinson <ian_robinson@uk.ibm.com>
Date: Tue, 21 Feb 2006 10:50:34 -0500
http://lists.oasis-open.org/archives/ws-tx/200602/msg00028.html
"I have submitted comments on the ASIS related to this issue
of: "to wstx or ws-tx". Given that the WS-RX TC has already
begun using the persistent URI space assigned by the OASIS
staff at http://docs.oasis-open.org/ws-rx/, and that this is
inconsistent with the current draft of the ASIS, I have asked
that they reconsider the prohibition of the hyphen character
at least in the context of the non-terminal path component
segment of a URI.
I have yet to have my comments acknowledged, but I expect that
Jamie will respond in due course.
Cheers,
Christopher Ferris
STSM, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440
phone: +1 508 377 9295
[2] Ferris 2006-02-21-Review
http://lists.oasis-open.org/archives/oasis-member-discuss/200602/msg00002.html
Also:
http://lists.oasis-open.org/archives/oasis-member-discuss/200602/msg00001.html
[3] Robinson 2006-02-21
http://lists.oasis-open.org/archives/ws-tx/200602/msg00027.html
Subject: Re: [ws-tx] Issue 015: Replace namespace and action URIs
From: Ian Robinson <ian_robinson@uk.ibm.com>
To: "Colleen Evans" <coevans@microsoft.com>
Date: Tue, 21 Feb 2006 15:29:32 +0000
"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..."
See also:
http://lists.oasis-open.org/archives/ws-tx/200512/msg00068.html
http://lists.oasis-open.org/archives/ws-tx/200512/msg00075.html
http://docs.oasis-open.org/ws-tx/issues/WSTransactionIssues.xml#i015
i015 Replace namespace and action URIs
[4] Evans 2006-02-08
http://www.oasis-open.org/archives/ws-tx/200602/msg00007.html
Subject: Issue 015: Replace namespace and action URIs
From: "Colleen Evans" <coevans@microsoft.com>
To: <ws-tx@lists.oasis-open.org>
Date: Wed, 8 Feb 2006 15:00:17 -0800
{...} "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]..."
[5] ASIS January 30, 2006
Artifact Standard Identification Scheme for Metadata 1.0
Approved TAB Document 30 January 2006 Artifact Identifier:
ArtifactStandardIdentificationSchemeForMetadata-1.0.1-req-approved
http://www.oasis-open.org/committees/download.php/16546/ArtifactStandardIdentificationSchemeForMetadata-1.0.1.pdf
[6] February 6, 2006 Review notice posted to mailing lists
Membership and Public Review of OASIS Artifact Standard
Identification Scheme for Metadata
Posted to lists for: members, tc-announce, oasis-member-discuss
http://lists.oasis-open.org/archives/members/200602/msg00007.html
http://lists.oasis-open.org/archives/tc-announce/200602/msg00005.html
http://lists.oasis-open.org/archives/oasis-member-discuss/200602/msg00000.html
[7] ASIS - mandatory policy
"Draft ASIS under review: mandatory policy? Please review and comment
by 1 March"
From James Bryce Clark <jamie.clark@oasis-open.org> on 18 Feb 2006
07:30:34 -0000
http://lists.oasis-open.org/archives/chairs/200602/msg00037.html
Posted to the Chairs list
[8] TC Short Name (tcShortName) according to ASIS
TC Short Name: The short name assigned by the TC Administrator
to the Technical Committee, with any hyphens eliminated.
This is typically done at TC initiation. [334-336]
EBNF [726]
TCshortName = NAMECHAR, {NAMECHARPLUSUNDERSCORE | NAMECHAR};
[9] Why does it say "with any hyphens eliminated"?
This statement in ASIS [335-336] appears to reflect an earlier stage
of design in which the format of an artifact identifier included
an "owner", which was either the string "oasis" or a de-hyphenated
variant of the TC's abbreviation/acronym:
owner-product-version-part-artifacttype-stage-revision-language.form
Artifact Identifiers (normative): OASIS artifacts MUST contain
their artifact identifier within the required OASIS metadata
for or in the artifact. The following format SHALL be used for
artifact identifiers:
owner-product-version-part-artifacttype-stage-revision-language.form
The owner component SHALL be either 'oasis' in the case of an
OASIS Standard or the 'short form' acronym for the OASIS TC that
manages the artifact with any hyphens changed to underscores."
[OASIS - Artifact Naming Guidelines, October 25, 2004]
see also "Section 5.1 Artifact Identifiers (normative)
OASIS - Artifact Naming Guidelines
Working Draft 08, 4 October 2004
http://lists.oasis-open.org/archives/ebxml-cppa/200410/pdf00000.pdf
There *may* be a need to define a kind of hyphenless TC Short Name
(string) for use in URNs, but that requirement, if necessary, should
not motivate a broad application of a tcShortName component that
(as hyphenless) needs to be enforced everywhere.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]