Hi Robin, thanks for the early feedback. We will address.
Thanks,
Paul (from mobile - please excuse typos and brevity)
Paul Lipton
CA Technologies
VP, CA Industry Standards and Open Source Program
Member, CA Council for Technical Excellence
Phone (preferred): +1 609 583-9718
Mobile: +1 267 987-6887
----- Original Message -----
From: Robin Cover [mailto:]
Sent: Wednesday, January 25, 2012 06:39 AM
To: TOSCA TC List <>
Cc: Lipton, Paul C; Thomas Spatzier <>; Robin Cover <>; Chet Ensign <>; Paul Knight <>
Subject: construction of URIs identifying XML namespace names
TOSCA TC members,
It's great to see a high level of TC participation and early progress
on the TOSCA TC deliverables. Congratulations!
I took a peek at the Working Draft 01, and spotted one item
for early feedback. The draft spec uses a default namespace
pattern (and derived URIs as identifiers for plan types
and DeploymentArtifact type values) using the substring
pattern "/ns/tosca/" where we expect "/tosca/ns/".
This was an understandable point of confusion because the
Naming Directives document was under revision recently.
We attempted to flag the change in the JIRA comment [1] and
in the boilerplate Starter Template sent by Paul Knight
in December [2], but the detail got lost in the weeds.
It should not be a big deal, since URIs identifying XML
namespace names and derived properties are just strings,
but for internal/operational reasons, we are asking that
the new construction pattern documented in the updated
Naming Directives [3] be followed:
http://docs.oasis-open.org/[tc-shortname]/ns/xxxx
[thus]
http://docs.oasis-open.org/tosca/ns/xxxx
I spotted these instances in the WD01 draft spec:
======================================================================
I. Declared XML namespace
for: http://docs.oasis-open.org/ns/tosca/2011/12
want: http://docs.oasis-open.org/tosca/ns/2011/12
II. plan type URIs
for: http://docs.oasis-open.org/ns/tosca/2011/12/PlanTypes/BuildPlan
want: http://docs.oasis-open.org/tosca/ns/2011/12/PlanTypes/BuildPlan
for: http://docs.oasis-open.org/ns/tosca/2011/12/PlanTypes/TerminationPlan
want: http://docs.oasis-open.org/tosca/ns/2011/12/PlanTypes/TerminationPlan
III. DeploymentArtifact type value (example)
for: http://docs.oasis-open.org/ns/tosca/2011/12/deploymentArtifacts/ovfRef
want: http://docs.oasis-open.org/tosca/2011/12/ns/deploymentArtifacts/ovfRef
Similarly for any named properties, functions, type values, etc where
these TOSCA-spec URIs are based upon the HTTP scheme URI starting
with http://docs.oasis-open.org/ (http://docs.oasis-open.org/tosca/ns/xxxx )
======================================================================
Let me know if there are any questions.
Cheers,
- Robin
Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email:
Staff bio: http://www.oasis-open.org/who/staff.php#cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783
======== References
[1] JIRA comment:
http://tools.oasis-open.org/issues/browse/TCADMIN-796?focusedCommentId=29102&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_29102
The XML namespace names, if HTTP scheme URIs, need to be formed
using the official tc-shortname, and respecting lower-case
thus... e.g.,
http://docs.oasis-open.org/tosca/ns/2011/12
[2] Starter Template
Starter Document for Topology and Specification for Cloud Applications Version
1.0 (attached)
http://lists.oasis-open.org/archives/tosca/201112/msg00028.html
http://lists.oasis-open.org/archives/tosca/201112/msg00028/TOSCA-v1.0-wd01.doc
= TOSCA-v1.0-wd01.doc
Includes on the cover page:
Declared XML namespaces:
http://docs.oasis-open.org/tosca/ns/2011/12
[3] Naming Directives (v1.2)
XML Namespace Identifiers and Namespace Documents
http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#xml-namespaces
http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#ns-URI-string-rules
