A group of logically related data elements in a defined sequence. Within the EDI format, segments are grouped into a transaction set.
Each RosettaNet Cluster is comprised of several Segments that are cross-enterprise processes involving more than one Partner Type in the supply chain (rather than internal company processes).
Service
Work performed by a software component. Components that do work in computing environments have names such as print server or file server. Components that do work in business environments have names such as catalog service or order management service, requisition management service.
SI
International System of Units
SKU
Stock Keeping Unit
SMTP
Simple Mail Transfer Protocol
Source Business Data Entity
The source of the business data entity compositional association.
Specification
A detailed formulation, in document form, which provides a definitive description of a system for the purpose of developing or validating the system.
Standard
A set of clearly defined and agreed-upon conventions for specific programming interfaces.
Structure
Something composed of organized or interrelated elements; the manner in which the elements of something are organized or interrelated.
Substantive Response
Includes data from the initiating message as well as data included by the responding partner (e.g., disposition of a product such as quantity and ship date that a supplier can fulfill on a Purchase Order).
Syntax
The patterns of formation of sentences and phrases from words and the rules for the formation of grammatical sentences in a language.
Glossary - Modular
Definitions for RosettaNet Modular PIPs (XML Schema)
A business scenario describes a specific instance of a specific process within the business process. Scenarios are specific instances of use cases.
Schema
Refers to XML Schema document compliant with W3C XML Schema Recommendations.
Schema Component
Refers to the building blocks of the Schema like elements, types, content models, model groups, annotation etc.
SHOULD
This word, or the adjective "RECOMMENDED", means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
SHOULD NOT
This phrase, or the phrase "NOT RECOMMENDED", means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
Simple Structure (Type)
A special case of data type that is constrained to a specific representation of the value.
Simple Type
Simple types cannot have element content and cannot carry attributes.
Simple Type Definition
A simple type definition is a set of constraints on strings and information about the values they encode, applicable to the normalized value of an attribute information item or of an element information item with no element children. Informally, it applies to the values of attributes and the text-only content of elements.
Specification Requirements Document (SRD)
A deliverable from a Milestone Program that contains the requirements for a PIP(s).
Standard Document Header
Adopted from UNCEFACT.
Substitution groups
An element can be declared to be a substitute for another element, the "head" element, allowing the new element to appear anywhere the head element may appear.
System Structure
The Standard Document Header and any other components of a PIP message that are used for integration with RNIF and/or other middleware.
