[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (CAMP-129) C.1 Mandatory Statements RE-01
C.1 Mandatory Statements RE-01
------------------------------
Key: CAMP-129
URL: http://tools.oasis-open.org/issues/browse/CAMP-129
Project: OASIS Cloud Application Management for Platforms (CAMP) TC
Issue Type: Bug
Components: Public Review
Reporter: Gilbert Pilz
From the comment list: https://lists.oasis-open.org/archives/camp-comment/201309/msg00078.html
TAB issue: https://tools.oasis-open.org/issues/browse/TAB-104
*****
The following attributes SHALL be present in a Link.
*****
I appreciate the TCs diligence in trying to marshal all the things a conforming implementation needs to conform to, but in so doing, it has deprived a conforming implementation of the context in which to judge its conformance. RE-01 being only one of several examples in the current draft.
That is further aggravated by the conformance clauses using these non-contextual statements as the basis for judging conformance.
In re-consideration of the conformance clause, be mindful that conformance isn't judged solely by meeting an enumeration of "SHALL" statements. Yes, that is part of conformance but no more so than following "statements" that are made in normative part of the text, along with "definitions," as well. Together, keywords (indicating what is needed for interoperability), statements, which are normative descriptions that don't use keywords, and definitions, all contribute to a normative text, to which a conforming implementation conforms.
--
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]