ubl — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Re: [ubl] Groups - draft-9.1.zip uploaded
MHonArc v2.5.0b2 -->ubl message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl] Groups - draft-9.1.zip uploaded
- From: Tim McGrath <[email protected]>
- To: "CRAWFORD, Mark" <[email protected]>
- Date: Tue, 23 Mar 2004 08:05:07 +0800
|
i am not sure if you are saying we don't need a Core Component
Parameters schema or that we are not putting documentation with every
type definition. we have always had a Core Component Parameters schema. it is used to define the documentation elements. what we have done for draft 9.1 is update this schema to have the same/correct names for things (they had gone out of synch.). but the larger question is, if we don't use a parameters schema then how do we ensure we use consistent documentation components across all modules? CRAWFORD, Mark wrote: The documentation is to be with every type definition where occuring. The modularity model never called for or supported the parameters module - nor should it. Mark Crawford Research Fellow - LMI XML Lead W3C Advisory Committee, OASIS, RosettaNet Representative Vice Chair - OASIS UBL TC & Chair Naming and Design Rules Subcommittee Chair - UN/CEFACT XML Syntax Working Group Editor - UN/CEFACT Core Components ______ Logistics Management Institute 2000 Corporate Ridge, McLean, VA 22102-7805 (703) 917-7177 Fax (703) 917-7481 Wireless (703) 655-4810 [email protected] http://www.lmi.org "Opportunity is what you make of it" |