sca-c-cpp message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Fw: [sca-c-cpp] NEW ISSUE: Define C Conformance Targets
- From: Bryan Aupperle <aupperle@us.ibm.com>
- To: sca-c-cpp@lists.oasis-open.org
- Date: Thu, 8 Nov 2007 13:17:06 -0500
Based on discussion in the Bindings
TC, this issue can be combined with the corresponding one for C++ (i.e.
the targets will probably be the same for both C and C++) so the title
for the single issue should be: Define Conformance Targets.
Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
Master Inventor
Research Triangle Park, NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com
----- Forwarded by Bryan
Aupperle/Raleigh/IBM on 11/08/2007 01:14 PM -----
Bryan Aupperle/Raleigh/IBM@IBMUS
11/08/2007 12:05 PM
|
To
| sca-c-cpp@lists.oasis-open.org
|
cc
|
|
Subject
| [sca-c-cpp] NEW ISSUE: Define C Conformance
Targets |
|
TARGET: C C&I Spec
DESCRIPTION: In order to write a normative statement or conformance clause
using RFC2119 language, the target or subject of the rule needs to be included.
Some of these are obvious, as we have rules governing components, composites,
services, references etc. Other targets are less so, especially when it
comes to conformance, as we need to identify artefacts that vendors can
claim they handle according to the rules of the spec. We should enumerate
a list of conformance targets early on, so that every time we use a MUST,
MAY, or SHOULD, we know to what the rule applies to.
PROPOSAL: none
Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
Master Inventor
Research Triangle Park, NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]