Discussing Clarity, Ambiguity and Conformance Requirements

In observing the call today, I the conversation about making sure there is no ambiguity in the specifications (apart from what must be determined by implementations), I thought of the Conformance Guidelines.  This is a good test, although it doesn't prevent ambiguity.

I find this document challenging to follow, but very promising in the result it could provide: 

The 4 September 2007 Guidelines to Writing Conformance Clauses
http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html

There are a number of specific instructions about identifying conformance targets and there is an interesting checklist in section 6:
http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html#_Toc170119665

The checklist might be useful to think about.

 - Dennis

Dennis E. Hamilton
------------------
NuovoDoc: Design for Document System Interoperability 
mailto: | gsm:+1-206.779.9430 
http://NuovoDoc.com http://ODMA.info/dev/ http://nfoWorks.org