Glossary C

Cardinality specifies how many instances of one class may be associated with a single instance of another class. Cardinality can be indicated for both classes and relationships.

Application of a cardinality adornment to a class indicates the number of instances allowed for that class.
Application of a cardinality adornment to a relationship indicates the number of links allowed between one instance of a class and the instances of another class.

Valid Values
The following cardinality values apply to both classes and relationships. Values are presented in lower-bound..upper bound format. Literals stand for any number and must be typed in using the appropriate specification.

Value	Description
0..1	Zero or one (Optional and one)
0..n	Zero or more (Optional and many)
1	One (Mandatory and one)
1..n	One or more (Mandatory and many)
n	Unlimited number

Cluster

A Cluster is a group of high-level business processes. The Clusters that are addressed by the RosettaNet Initiative represent the core business processes or the backbone of a supply chain.

The Clusters listed below were identified through interviews with RosettaNet Board Member companies, and through the RosettaNet Business Research Teamâ€™s knowledge of common and emerging business practices. This provides only a guideline for RosettaNet's focus and may be changed by the Cluster Workshop Teams.

Cluster 1: Partner and Product/Service Review
Cluster 2: Product Introduction
Cluster 3: Order Management
Cluster 4: Inventory Management
Cluster 5: Marketing Information Management
Cluster 6: Service and Support

Compliance

An implementation that meets all requirements of the RNIF specification. All transactions, actions, or data elements must be valid as defined in the term, â€œValidation.â€

Compliance Testing

Comparing an implementation operation against specified requirements to determine compliance or noncompliance.

Conformance

The ability to demonstrate in an unambiguous way that a given implementation is correct with respect to the formal model.

Constraint

The conditional constraints that specify the mandatory composition of the business document in certain contexts.

Control Information

Information that is appended to content from an upper network layer.

Glossary - Modular

Definitions for RosettaNet Modular PIPs (XML Schema)

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | None

	Term	Definition
	Class Diagram	A grouping of related information.

	Complex Type	An XML element type that allows nested elements in their content and may carry attributes.

	Complex Type Definition	A complex type definition is a set of attribute declarations and a content type, applicable to the attributes and children of an element information item respectively. The content type may require the children to contain neither element nor character information items (that is, to be empty), to be a string that belongs to a particular simple type or to contain a sequence of element information items that conforms to a particular model group, with or without character information items as well.

	Complex type extension	Extension adds attributes, and adds elements to the end of the content model of the base type.

	Complex type restriction	Restriction limits a base type to a more restrictive set of valid values.

	Component	Component means a basic building block of the Schema like named type, named element, named group, etc.

Privacy

IP Policy