[OASIS Issue Tracker] Created: (CAMP-115) 4.3.2.3 artifacts - semantically significant?

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

 4.3.2.3 artifacts - semantically significant?
----------------------------------------------

                 Key: CAMP-115
                 URL: http://tools.oasis-open.org/issues/browse/CAMP-115
             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
          Issue Type: Bug
          Components: Public Review
            Reporter: Martin Chapman 


From https://tools.oasis-open.org/issues/browse/TAB-90

The phrase "semantically significant" occurs four (4) times in the main text and again in the appendix that summarizes requirements. Here, 4.3.2.4 Services, 4.3.3.3 requirements and 4.3.4.2 characteristics.

Unfortunately, I can't find a definition for "semantically significant" in the spec.

Does this means nodes maybe unordered? Or something else that we can specify sufficiently to require conformance?

As a general comment, all requirements should be swept with a view towards pointing to where sufficient information has been specified to enable conformance. The pointing doesn't have to be hyperlinks but as a reader encounters requirements, they should be able to understand what is being asked of an implementation that conforms to the spec.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira