----- Original Message -----
Sent: Friday, September 14, 2001 5:25
AM
Subject: RE: One potential XML mapping
for ebXML Core Components
Brian,
These components look good. I do have some
reservations as to what is mandatory. Using the usual horrible example -
Party, I can see that the Address details are mandatory but in some cases
where the transactions are part of an existing set, repeating all this
information seems heavy. Is there a plan to allow people to apply their
own rules on these items.
Martin Roberts
xml designer,
BTexact Technologies
e-mail: martin.me.roberts@bt.com
tel: +44(0) 1473 643775
fax:
+44(0) 1473 646668
pp Columba House Rm123, Adastral
Park, Martlesham, Ipswich IP5 3RE, UK
BTexact Technologies is a trademark
of British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no. 1800000
This electronic message contains
information from British Telecommunications plc which may be privileged or
confidential. The information is intended to be for the use of the
individual(s) or entity named above. If you are not the intended recipient
be aware that any disclosure, copying, distribution or use of the contents
of this information is prohibited. If you have received this electronic
message in error, please notify us by telephone or email (to the numbers or
address above) immediately.
ebXML Community,
For one of our clients we developed XML Schemas
for business documents based on the ebXML Core Components. Of course,
this required us to create a mapping of the Core Components Data Dictionary
into a Core Components XML Schema. With the encouragement of our
client (who enthusiastically supports public standards efforts), we are
contributing both "attribute rich" and "attribute free" variants of these
Core Components XML Schemas for consideration by the ebXML and ebTWG
community.
We are looking forward to suggestions for
improvements, debate over style of mapping, comments on our embedded
comments, etc.
Brian Handspicker
N.B. To satisfy UN/CEFACT's goal of
openness, Foliage agrees to remove any IPR
constraints or
restrictions associated with this contribution. Foliage offers this
contribution for evaluation and standards development purposes only, with no
implied or explicit warrantee.
--
Brian D. Handspicker
Engineering
Director
Foliage Software Systems, Inc.