Every status a technical issue can be in, and the steps the workflow allows between them. The status this tissue is in now is the box drawn in bold.

Hide the workflow

TissueDB status workflow back to Discussion Batch Triage Accepted Discussion Drafting Implementation Verify Draft Implementation Analysis Of Compatibility Conformance Test Preparation Conformance Test Verification Ballot Period Solution Accepted Must Implement In Force Approval (N/A) Approval (Duplicate) Approval (Editorial) Approval (Future Improvement) Not Applicable Duplicate Future Improvement Editorial Must Implement (Editorial) In Force (Editorial) Legend normal route of a technical solution accepted or released → in force classification branch (working group approval) back to Discussion for rework (lines are bundled) reaching the final state
The route a technical solution takes from Triage to In Force, the working group approvals that close an issue instead, and the ways back to Discussion for rework. Opens full size in a new tab.

914 spelling of enum sboClass

Created
04 Sep 2012
Status
Not ApplicableClosed: the issue falls outside the scope of the standard. No further comments are taken. Hide the workflow
Part
Part 6 (2009-12; Edition 2)
Links
None
Page
Clause
Paragraph
Category
No impact on this part

Issue

The enum "sboClass" in part 6 is spelled "SboClasses" in part 7-3, (while the attribute name in part 7-3 is sboClass)

See also tissue #769 for enum "ctlModel" versus "CtlModels"

Proposal

Please clarify/correct

DiscussionCreated
Not Applicable See the clarification at Tissue 769. As this definition is now available in 7-3, it will be removed from part 6. 04 Sep 12