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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-architecture message

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

Subject: Re:Conformance and naming

The approved ebXML Requirements Specification clearly identifies naming
conventions as a responsibility of technical architecture (Section 3.4, bullet
8) to wit - "In coordination with BP process specification and core components
identification, provide for naming conventions for technical and business
content in the technical architecture".

The approved specification also states that the TA team is responsible to
"Provide design guidelines for ebXML compliant messages". (Section 3.4, bullet
9).  In the candidate requirements document submitted to the Plenary on 7 May,
the requirements team originally included a requirement for the technical
coordination and support project team to provide "A clear definition of ebXML
compliance."  However, this requirement was dropped at the insistance of the TCS
Project Team lead.  If memory serves me correctly, the TCS project team lead
stated a conformance definition was the responsibility of  Technical

Mark Crawford
Research Fellow
E-business Strategies
LMI Logistics Management Institute
2000 Corporate Ridge, McLean, VA 22102-7805
(703) 917-7177   Fax (703) 917-7518
"Opportunity is what you make of it"

____________________Reply Separator____________________
Subject:    Conformance and naming 
Author: "agrangard@nycall.com" <anders.grangard@edifrance.org>
Date:       10/16/00 5:42 PM

The TechArch team has been working hard and late hours to take the received
comments of our specification into account and we will shortly circulate an
updated version that I hope will impress you as it has me. In the process
there are two important issues that have surfaced which need immediate
attention from the steering committee. Conformance rules and naming
conventions are being worked on by our team as they affect all or most of
the other teams. We need to resolve quickly whether these are in or out of
scope. If they are in-scope, which I certainly think, we need to allocate
them to the appropriate group.

Kind regards
Anders Grangard

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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC