RE: [wsdm] Naming Conventions - Slight clarification needed

Also, on the same thread but a slightly different issue. Shall we just remove the dates from the URIs for the capabilities but add the “-n” of the current Schema to the “muws” or “mows”?

For example, http://docs.oasis-open.org/wsdm/mows-2/capabilities/OperationalStatus.

Kirk Wilson
Architect, Development

Office of the CTO

802 765-4337

-----Original Message-----
From: Vaughn Bullard [mailto:vbullard@amberpoint.com]
Sent: Thursday, October 27, 2005 3:11 PM
To: Wilson, Kirk D; wsdm@lists.oasis-open.org
Subject: RE: [wsdm] Naming Conventions - Slight clarification needed

Also,

This is in the same thread of the naming conventions, but slightly different issue. If we change the names to reflect WSN and WSRF do we need to also change everything that appears under *.oasis-open.org that we see? For example, WSS, WS-Topics, etc. But only in regards to namespaces, wsdls, etc?

Thanks,

Vaughn

From: Wilson, Kirk D [mailto:Kirk.Wilson@ca.com]
Sent: Thursday, October 27, 2005 2:54 PM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] Naming Conventions

The following revised naming conventions were agreed upon during the conference call. In particular, the team decided to move away from the RF & N convention insofar as namespaces will be resolvable.

XML Schema namespaces and file names:

MUWS Part 1: http://docs.oasis-open.org/wsdm/muws1-2.xsd (see below for explanation of the “-2”)

MUWS Part 2: http://. . ./wsdm/muws2-2.xsd

MOWS: http://. . ./wsdm/mows-2.xsd

MUWS Events: http://. . ./wsdm/muwse-2.xsd

MOWS Events: http://. . ./wsdm/mowse-2.xsd

WSDL namespaces and files names:

MUWS Part 1: http://. . ./wsdm/muws1-2.wsdl

MUWS Part 2: http://. . ./wsdm/muws2-2.wsdl

MOWS: http://. . ./wsdm/mows-2.wsdl

We also agreed that we will make the namespace prefixes uniform throughout the MUWS and MOWS spec by using the muws1, muws2, mows, muwse and mowse portions of the names. However, we will have to add the “w” to the prefixes for the WSDL namespaces, e.g., muws1w, muws2w and mowsw. (ß I don’t think we acknowledged this point after we decided to drop the “w” from the WSDL namespace and file names.)

Based on what you're stating Kirk, is that we'll end up with something like this. I put it diagram form. Helps me figure things out.

An explanation (as best that I can do) for the “-n” at the end of the names: Following the convention establish by RF&N, this number is used to decouple the Schema or WSDL version from the version of the spec. Thus, the spec may change versions (typically a point version change in the case) without changing the version of the Schema or WSDL if no change is involved in those documents. The spec will always point to the version of the Schema or WSDL that it is using. So spec version 1.5 may point to version 2 of the Schema and version 1 of the WSDL assuming that despite changes to the spec from .0 to .5 only one version change was required in the Schema and no version change was required to the WSDL. However, a point change may require a version in these documents, thus version 1.1 of the spec may point to version 2 of Schema and/or WSDL. (As per the decisions made during the conf call, all this will also be better explained on the WSDM homepage and the homepage will contain the references to the “latest” versions of the Schema and WSDL files.)

Justification for the above numbering: We do anticipate issuing a second version of the XML Schema and WSDL files for MUWS and MOWS (if only because of a decision taken at the last F2F to eliminate certain aspects of these files). So the new versions of these files should be designated as “-2”. Also, there will be minor changes in the MUWS Event schema (e.g. elimination of the RelationshipAccessMessage) and changes to the MOWS Event schema because of the addition of new capabilities such as the OperationMetrics and OperationOperationalStatus capabilities. So these also become “-2” versions.

Kirk Wilson
Computer Associates

Architect, Development
Office of the CTO
Tele: + 1 802 765-4337
Fax: + 1 802 765-4339
<mailto:kirk.wilson@ca.com>

wsdm message