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

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-cc-review message

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


Subject: Re: [regrep-cc-review] Conformance to CCTS



Agreed - on all points... especially number 3.




> 4.3 Conformance
> 
> Applications will be considered to be in full conformance with this
> technical specification if they comply with the content of normative
> sections, rules and definitions.
> 
> [A1] Conformance shall be determined through adherence to the content of
> normative sections, rules and definitions.
> 
> As per our analysis of the CCTS spec against our registry architecture,
> we will not be in full conformance with the CCTS spec. This leaves
> several options:
> 
> (1) Notify the CCTS Team of those places where we will not be in
> conformance (we will do this), and have the CCTS Team update their spec
> accordingly;
> 
> MY THOUGHTS: The CCTS Team is under no obligation to do so, any more
> than we are under an obligation to be 100% conformant with their spec.
> 
> (2) Notify the CCTS Team of those places where we will not be in
> conformance, and assume that they may/may not update their spec
> accordingly; we will call our Technical Note "Implementing UN/CEFACT
> ebXML Core Components in an ebXML Registry";
> 
> MY THOUGHTS: Since the CCTS spec is copywritten, can we call our 
> Technical Note "Implementing UN/CEFACT ebXML Core Components in an ebXML
> Registry" if we are not in 100% conformance?
> 
> (3) Notify the CCTS Team of those places where we will not be in
> conformance, and assume that they may/may not update their spec
> accordingly; we will not use the term "UN/CEFACT ebXML Core Components"
> in the title of our Technical Note, but will instead call something like
> "Component-Level Registration and Reuse in an ebXML Registry". We will
> state that our work is *based on* the UN/CEFACT ebXML Core Components
> specification.
> 
> MY THOUGHTS: Not sure of the legal ramifications of this, since the CCTS
> spec is copywritten.



carl
Carl Mattocks
CEO CHECKMi
e-mail: CarlMattocks@checkmi.com
*******************************************
Business Agent Software that
Secures Knowledge for Reputation:Protection
*******************************************
CHECKMi Compendium the shortcut to Valued & Trusted Knowledge
******************************************* 
www.checkmi.com
(usa)1-908-322-8715
CarlCheckMi (I M)



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