|
|
|
|
|
|
Definitions for computer,
Internet and RosettaNet-specific terminology.
|
|
|
 |
Definitions for RosettaNet Monolithic PIPs (DTD). |
| |
|
Term |
Definition |
|
|
|
|
Message Guidelines
|
Human readable structure definitions of the business messages for discussion and design. Message Guidelines include fields and codes for PIPing companies to build Business Documents, which outline cardinality of Business Properties and Business Data Entities (BDEs), and provide Code Lists and definitions of Business Properties, BDEs, Fundamental BDEs, and Quantitative Fundamental BDEs. |
|
|
|
|
|
Message Schemas
|
Machine readable structure definitions of the business messages for validation, mapping and PIP oeperations. In addition to the .dtd syntax, more will be available that include .sml Schema and Microsoftâ„¢ .xdr. |
|
|
|
|
|
|
Definitions for RosettaNet Modular PIPs (XML Schema) |
| |
|
Term |
Definition |
|
|
|
|
Main type
|
A reusable type that is used to define the root element of the XML instance document (PIP Action Message). In case when Schema contains only one reusable type definition than that type is by default the Schema main type. |
|
|
|
|
|
MAY
|
This word, or the adjective "OPTIONAL", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation, which does not include a particular option, MUST be prepared to interoperate with another implementation, which does include the option, though perhaps with reduced functionality. In the same vein an implementation, which does include a particular option, MUST be prepared to interoperate with another implementation, which does not include the option (except, of course, for the feature the option provides). |
|
|
|
|
|
Mixed Content
|
A combination of child elements and character data nested within an element. |
|
|
|
|
|
Modular PIP
|
Describes the PIP Service Content using W3C XML Schema, and PIP Choreography described using ebXML BPSS. |
|
|
|
|
|
Monolithic PIP
|
Describes the PIP Service Content using message guidelines and DTD. |
|
|
|
|
|
MUST
|
This word, or the terms "REQUIRED" or "SHALL", means that the definition is an absolute requirement of the specification. |
|
|
|
|
|
MUST NOT
|
This phrase, or the phrase "SHALL NOT", means that the definition is an absolute prohibition of the specification. |
|
|
|
|
|
|
|
