ubl message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: [ubl] Position Paper: Modularity, Namespaces and Versioning version 3
- From: "Burcham, Bill" <Bill_Burcham@stercomm.com>
- To: 'ubl-ndrsc@lists.oasis-open.org'
- Date: Fri, 15 Mar 2002 22:02:10 -0600
Please find
attached version 3 of the Naming and Design Rules Subcommittee Position
Paper on Modularity, Namespaces and Versioning.
Changes from version
2:
- Added options and
recommendation on Namespace identification (OASIS URN namespace versus
"namespace name = namespace location")
- Added
recommendation on schemaLocation
- In section 7.3
Option 3: Core Plus "Functional" Namespaces, I filled in the table of
namespace names for each of the namespaces we've identified thus
far.
Pleas find also
attached, a .zip file contianing a nascent example. It consists of tiny
schemas for (the XSD realization of) the Core Components CCT's
(cc-core-component-types.xsd), a UBL core (core.xsd), a UBL order schema module
(order.xsd), a schema defining the UBL order message element (order-message.xsd)
and a minimal document instance (Order-1.xsd).
Some notes on the
example:
- While some of the
type and tag names may remind you of UBL type and tag names, the resemblance
is purely coincidental. We need to keep the example
short.
- The example is not
yet mentioned in the position paper itself. Next steps are to mention it
from the position paper and also to annotate the XML documents themselves so
as to make the somewhat self-describing.
- For the example to
be truly worthwhile, we'll have to add: invoice schema modules and document
instance. Also we'll need to show an example of a root schema comprised
of more than one schema module.
That's all.
See you in Barcelona!
Regards,
Bill
Burcham
draft-burcham-modnamver-03.pdf
Example.zip
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC