Database Reference
In-Depth Information
can be acquired from technology-specific forums that are related to business functional
areas such as telecommunication, transportation, and healthcare. However, you must be
quite skeptical about the amount of data presented on these resources; these specifications
are some sort of all-weather cases that are oversized and over-bloated with elements you
could never use in your business. By following them blindly, you can end up with a
simple purchase order with two or three order lines of 3 Meg size. Another problem is that
these models are quite illogically partitioned, mixing together all essential building
blocks:
•
Qualified data types
(
QDT
)
•
Qualified data object
(
QDO
)
• Message header and process header elements
• Message tracking data
Amazingly, through some international projects, we also witnessed the implementation of
regional data models using local languages. Yes, you won't believe it. An entire local mes-
saging hierarchy (XML elements, attributes, documentation, and constraints) has been im-
plemented in one Scandinavian language—so much for discoverability and composability,
without mentioning the encoding issues.
The foundation for the XML framework has been well set by the
UN/CEFACT Document
XML Naming and Design Rules
draft version published in August 2004. Please acquire
the latest version and follow the design rules section (see
Appendix C
,
Naming and
Designing the Rules List
). They are all important, from
[R 1]
to
[R 185]
; we just would
like to quote the most important part from our point of view.
The following table lists the implementation techniques, service models, and some selec-
ted design rules using the contract-first approach, as follows:
Implementation tech-
nique
Service models
Selected Design rules (out of 185)
All: Utility Services,
Entity Services, and
Task Services
[R 4] ELEMENT, ATTRIBUTE AND TYPE NAMES MUST BE IN THE ENGLISH
LANGUAGE, USING THE PRIMARY ENGLISH SPELLINGS PROVIDED IN THE
OXFORD ENGLISH DICTIONARY.
Avoid XSD generation
from DB model
Identify all EBO/EBM
elements
[R 5] LOWER-CAMEL-CASE (LCC) MUST BE USED FOR NAMING
ATTRIBUTES.
Follow Naming and
Design Rules List
[R 6] UPPER-CAMEL-CASE (UCC) MUST BE USED FOR NAMING ELEMENTS
AND TYPES.
Search WWH ::
Custom Search