OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [ebxml-msg] proposed conformance clause text


All,

As agreed during today's call, I have taken a stab of
drafting proposed text for the conformance clause.

Flame away;-)

Cheers,

Chris
----------------------------------------------------------

X.X Implementation Conformance

An implementation of this specification MUST satisfy
ALL of the following conditions to be considered
a conforming implementation:

a) It supports all of the mandatory syntax, features and behavior
(as identified by the [RFC2119] key words MUST, MUST NOT, REQUIRED,
SHALL and SHALL NOT) defined in Part I - Core Functionality[ref].

b) It supports all of the mandatory syntax, features and behavior
defined for each of the optional module(s) defined in
Part II - Additional Features[ref] that it has chosen to implement.

c) If it has implemented optional syntax, features and/or behavior
defined in this specification, it MUST be capable of
interoperating with another implementation that has not implemented
the optional syntax, features and/or behavior. It MUST be
capable of processing the prescribed failure mechanism
for those optional features that it has chosen to implement.

d) It is capable of interoperating with another implementation
that has chosen to implement optional syntax, features and/or
behavior defined in this specification that it has not
chosen to implement. Handling of unsupported features SHALL
be implemented in accordance with the prescribed failure
mechanism defined for that feature.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC