A class that cannot be directly instantiated. (Contrast: concrete class.) (OMG)
abstract syntax
OMG class diagrams are used to present the OMG metamodel, its concepts (metaclasses), relationships, and constraints. Definitions of the concepts are included. (OMG)
abstraction
(1) The essential characteristics of an entity that distinguish it from all other kinds of entities. (2) An abstraction defines a boundary relative to the perspective of the viewer. ((OMG))
active class
A class whose instances are active objects. (OMG)
activity
A unit of work a worker may be asked to perform (RUP)
activity diagram
Shows behavior with control structure. Can show many objects over many uses, many objects in single use case, or implementation of method. Encourages parallel behavior. (UML Distilled)
actor
Someone or something, outside the system or business that interacts with the system or business. (RUP)
administered item
registry item for which administrative information is recorded in an Administration Record. (ISO/IEC 11179-3:2003, definition 3.3.1)
Administration Manager
Recommended collection of methods that should be defined for managing registry properties such as permissions of Registry Users. (ebRIM Spec)
administrative status
designation of the status in the administrative process of a Registration Authority for handling registration requests (ISO/IEC 11179-3:2003, definition 3.3.7)
agent
An agent is a network component that must implement protocols up to the agent layer of the e-business network application, communications model. (IBM Glossary) (1) In systems management, a user that, for a particular interaction, has assumed an agent role. (2) An entity that represents one or more managed objects by (a) emitting notifications regarding the objects and (b) handling requests from managers for management operations to modify or query the objects. (3) A system that assumes an agent role. (4) Software that acts on behalf of a user as it performs tasks within an application program. An agent may run on both the client and the server.
agent layer
An layer of the e-business network application, communications model in which an agent must implement protocols.
aggregate (class)
A class that represents the "whole" in an aggregation (whole-part) relationship. (OMG)
Aggregate Business Information Entity
ABIE
A collection of related pieces of business information that together convey a distinct business meaning in a specified business context. Expressed in modeling terms, it is the representation of an object class, in a specific business context. (CCTS 2.01)
Aggregate Core Component
ACC
(1) A Collection of Core Components that convey a distinct business meaning, independent of any specific business context. Expressed in modeling terms, it is the representation of an object class, independant of any specific business context. (CCTS 2.01) (2) An Aggregate Core Component will consist of two or more Basic Core Components, or at least one Basic Core Component plus one or more Aggregate Core Components.
aggregation
A special form of association that specifies a whole-part relationship between the aggregate (whole) and a component part. (OMG)
agreement
An arrangement between two partner types that specifies in advance the conditions under which they will trade (terms of shipment, terms of payment, collaboration protocols, etc.) An agreement does not imply specific economic commitments. (BPSS 1.05)
analysis
The part of the software development process whose primary purpose is to formulate a model of the problem area. Analysis focuses on what to do, design focuses on how to do it. See design. (RUP)
analysis class
An abstraction of a role played by a design element in the system, typically within the context of a use-case realization. Analysis classes may provide an abstraction for several roles, representing the common behavior of those roles. Analysis classes typically evolve into one or more design elements (e.g. design classes and/or capsules, or design subsystems). (RUP)
API
API
See Application Programming Interface.
application
Software above the level of the MSH that implements a Service by processing one or more of the Messages in the Document Exchanges associated with the Service.
Application Prgramming Interface
API
A software internface that enables application to communicate with each other. An API is a set of programming language constricts or statements that can be coded in application program to obtain the specific functions on services provide by an underlying operating system of service program. (RUP)
Application Specification
AppSpec
document specifying – ((to be amended)) (UN/CEFACT/TBG 2 and the ISO/TC 154/JWG 2)
Applied Technologies Group
ATG
One of the newly established groups in the UN/CEFACT in May, 2002 Plenary. Work in ATG encompassed four specific technologies, viz. UN/EDIFACT, UN Locode, UNeDocs and ebXML. The reference model used was the basic reference published by the ICG. (UN/CEFACT)
architectural view
A view of the system architecture from a given perspective. It focuses primarily on structure, modularity, essential components, and the main control flows. (RUP)
architecture
The organizational structure of a system. Architecture can be recursively decomposed into parts that interact through interfaces, relationships that connect parts, and constraints for assembling parts. Parts that interact through interfaces include classes, components and subsystems. (RUP)
artefact
See "artifact".
artifact
A piece of information that (1) is produced, modified, or used by a process, (2) defines an area of responsibility, and (3) is subject to version control. An artifact can be a model, a model element, or a document. A document can enclose other documents. (RUP)
Assembly Document
ASDOC
A mechanism for declaring which Core Components will be used to build a Business Message (Core Component Assembly Document) (CCTS 2.01)
Assembly Rules
Assembly Rules group sets of unrefined Business Information Entities into larger structures. Assembly Rules are more fully defined and explained in the Assembly Rules Supplemental Document. (CCTS 2.01)
association
(1) The semantic relationship between two or more classifiers that specifies connections among their instances. (OMG) (2)a semantic relationship between two classes NOTE An association is a type of relationship. (Adapted from ISO/IEC 19501-1:2001, 2.5.2.3)
association class
an association that is also a class. NOTE: It not only connects a set of classes, but also defines a set of features that belong to the relationship itself. (Adapted from ISO/IEC 19501-1:2001, 2.5.2.4)
Association Business Information Entity
ASBIE
A Business Information Entity that represents a complex business characteristic of a specific Object Class in a specific Business Context. It has a unique business semantic definition. An Association Business Information Entity represents an Association Business Information Entity Property and is therefore associated to an Aggregate Business Information Entity, which describes its structure. An Association Business Information Entity is derived from an Association Core Component. (CCTS 2.01)
Association Business Information Entity Property
ASBIE Property
A Business Information Entity Property for which the permissible values are expressed as a complex structure, represented by an Aggregate Business Information Entity. (CCTS 2.01)
Association Core Component
ASCC
A Core Component which constitutes a complex business characteristic of a specific Aggregate Core Component that represents an Object Class. It has a unique business semantic definition. An Association Core Component represents an Association Core Component Property and is associated to an Aggregate Core Component, which describes its structure. (CCTS 2.01)
Association Core Component Property
ASCC Property
A Core Component Property for which the permissible values are expressed as a complex structure, represented by an Aggregate Core Component. (CCTS 2.01)
ATG
ATG
See Applied Technologies Group (UN/CEFACT)
Atomic Transaction
A complete Transaction that follows the atomic rules for every party in the Transaction Tree over space and time, so that all the participants in the transaction will receive instructions that will result in a homogeneous outcome. That is they will be issued instructions to all Confirm (success) or all Cancel (failure / error signal). (Transitively, a set of operations whose effect is capable of counter effect.) (Tony Frecher)
attribute
(1) An attribute defined by a class represents a named property of the class or its objects. An attribute has a type that defines the type of its instances. (RUP) (2) A named value or relationship that exists for some or all instances of some entity and is directly associated with that instance. (CCTS 2.01) (3)a characteristic of an object or entity (ISO/IEC 11179-3).
attribute instance
a specific instance of an attribute. NOTE: Amended from ISO 2382-17:1993 (17.02.13) to distinguish an instance of an attribute from its value. (ISO 11179-3, Second edition)
attribute value
the value associated with an attribute instance. NOTE: Amended from ISO 2382-17:1993 (17.02.13) to distinguish an instance of an attribute from its value. (ISO 11179-3, Second edition)
authorisation process
A procedure for granting authorization. (IFTF RFC 2828)
authorization
A right or a permission that is granted to a system entity to access a system resource. (IFTF RFC 2828)
TERM
ACRONYM
DEFINITION
basic attribute
attribute of a metadata item commonly needed in its specification (ISO 11179-1, Second edition)
Basic Business Information Entity
BBIE
(1) A Core Component used in a specific business context. (2) A Business Information Entity that represents a singular business characteristic of a specific Object Class in a specific Business Context. It has a unique business semantic definition. A Basic Business Information Entity represents a Basic Business Information Entity Property and is therefore linked to a Data Type, which describes it values. A Basic Business Information Entity is derived from a Basic Core Component. (CCTS 2.01)
Basic Business Information Entity Property
A Business Information Entity Property for which the permissible values are expressed by simple values, represented by a Data Type (CCTS 2.01)
Basic Core Component
BCC
(1) A Core Component that represents a singular business concept with a unique business semantic definition. (2) A Core Component which constitutes a singular business characteristic of a specific Aggregate Core Component that represents an Object Class. It has a unique business semantic definition. A Basic Core Component represents a Basic Core Component Property and is therefore of a Data Type, which defines its set of values. Basic Core Components function as the properties of Aggregate Core Components. (CCTS 2.01)
Basic Core Component Property
A Core Component Property for which the permissible values are expressed by simple values, represented by a Data Type. (CCTS 2.01)
BCSS
See Business Collaboration Specification Schema
BDV
See Business Domain View (N093/UMMUG)
behaviour
The observable effects of an operation or event, including its results. (OMG)
binding
a mapping from one framework or specification to another (ISO 11179-3, Second edition)
boundary class
A Boundary is a class that lies on the periphery of a system, but within it. It interacts with actors outside the system as well as objects of all three kinds of analysis classes within the system. (OMG)
Box Completion Guideline
document specifying – ((to be amended)) (UN/CEFACT/TBG 2 and the ISO/TC 154/JWG 2)
BPAWG
See Business Process Analysis Working Group (UN/CEFACT)
BRS
See Business Requirement Specification
BRV
See Business Requirement View (N093/UMMUG)
BSV
See Business Service View (N093/UMMUG)
BTV
See Business Transaction View (N093/UMMUG)
business
A series of processes, each having a clearly understood purpose, involving more than one organization, realized through the exchange of information and directed towards some mutually agreed upon goal, extending over a period of time. (ISO/IEC 14662)
business activity
(1) A business activity is used to represent the state of the business process of one of the partners. (BPSS 1.05) (2) For instance the requester is either in the state of sending the request, in the state of waiting for the response, or in the state of receiving. (CPP 2.0)
business area
An area of knowledge or activity characterized by a family of related systems. (RUP) An area of knowledge or activity characterized by a set of concepts and terminology understood by practitioners in that area.
business collaboration
An activity conducted between two or more parties for the purpose of achieving a specified outcome. (UEBA 0.59)
business collaboration activity
See "business collaboration". (N093/UMMUG)
business collaboration domain
A domain conducted between two or more parties for the purpose of achieving a specified outcome. (N093/UMMUG)
Business Collaboration Framework
BCF
Business Collaboration Framework. A collection of specifications defining electronic business exchange for two or more business partners. (Established experts on process modeling and B2B e-commerce standards development and implementation.) (Edifecs)
Business Collaboration Knowledge
The knowledge involved in a collaboration. (UEBA 0.59)
Business Collaboration Model
A Business Collaboration Model describes in detail how Trading Partners take on roles, relationships and responsibilities to facilitate interaction with other Trading Partners. (CPPA 2.0)
business collaboration pattern
(1) An pattern descrives the way to use of the business collaboration model to be achieved between trading partners. (N093/UMMUG) (2) The Collaboration business pattern, which is also known as the User toUser or U2U pattern, enables interaction and collaboration between users. This pattern can be observed in solutions that support small or extended teams who need to work together in order to achieve a joint goal. (IBM)
Business Collaboration Protocol
BCP
A business collaboration protocol choreographs one or more business transaction activities. (UMM)
Business Collaboration Rules
Rules of Collaboration between Trading Partners. (CPPA 2.0)
Business Collaboration Specification Schema
BCSS
"BCSS is a technical specification (1.) to make CCTS compliant information modelling accessible to a broad user base through standard UML tool support (2.) to support easy interchange of information models between different UML tools and (3.) to support validation of the structure and semantics of information models against the CCTS. These goals are achieved through the development of a formal UML profile for CCTS that includes stereotypes, tagged values and OCL constraints. (BCSS V1.0)"
business commitments
The making or accepting of a right, liability or responsibility by a Person that is capable of enforcement in the jurisdiction in which the commitment is made. (ISO/IEC 15944-1)
business context
(1) Defines a context in which a business has chosen to employ an information entity. (2) The formal description of a specific business circumstance as identified by the values of a set of Context Categories, allowing different business circumstances to be uniquely distinguished. (CCTS 2.01)
business document
The set of information components that are interchanged as part of a business activity. (CCTS 2.01)
Business document flow
A business transaction is realized as Business Document flows between the requesting and responding roles. There is always a requesting Business Document, and optionally a responding Business Document, depending on the desired transaction semantics, e.g. one-way notification vs. two-way conversation. (BPSS 1.05)
Business Domain
An business area of knowledge or activity characterized by a family of related systems. (RUP)
Business Domain View
BDV
The partitioning of business domain into business areas, process areas, and business processes. This view establishes the business context of the process which is a precursor to evaluating the likelihood of finding reusable, previously defined, process descriptions or terminology in the UMM libraries. View aligned with UMM. (UMM, N093/UMMUG)
business entity
Something that is accessed, inspected, manipulated, produced, and worked on in the business. (UMM)
business entity class
Group of Items which are structured in the same way that serves the fundamental missions of the company, that has legal and/or business basis, which may participate in exchanges with partners, which will be implemented into objects (object technology) through a modeling process. For example order is a business entity class. (UMM)
business expert
A person who is knowledgeable about the business area being modeled. (UMM)
business information
Information that two or more Trading Partners agree to use in their exchange of information (BPSS 1.05)
Business Information Entity
BIE
(1) A context specific instantiation of a Core Component that constitutes a piece of business data or a group of pieces of business data with a unique business semantic definition. (2) A Business Information Entity can be a Basic Business Information Entity (BBIE), an Association Business Information Entity (ASBIE), or an Aggregate Business Information Entity (ABIE). (CCTS 2.01)
Business Information Entity Property
A business characteristic belonging to the Object Class in its specific Business Context that is represented by an Aggregate Business Information Entity. (CCTS 2.01)
business information group
A set of basic and/or aggregate information entities that convey a single business function. (CCTS 2.01)
business information model
A model that references all meta-information associated with a specific Business Process. The Business Information Model references Business Entities, Business Information Entities, and Business Information Objects to accomplish that task. (BPSS 1.05)
Business Information Object
BIO
Business Documents are composed from re-useable Business Information Objects. At a lower level, Business Processes can be composed of re-useable Common Business Processes, and Business Information Objects can be composed of re-useable Core Components. (Common Business Processes and Business Information Objects should be stored in a UMM Business Library.) (BPSS 1.05)
business intent
The underlying Business Intent of the Trading Partners (BPSS 1.05)
business interaction
CCMA 0.6a
Business interaction activity
An activity which a specification of how stimuli are sent between instances to perform a specific business. The interaction is defined in the context of a collaboration. (N093/UMMUG)
business library
A collection of approved process models specific to a line of business (e.g., shipping, insurance). (CCTS 2.01)
business message
Any message exchanged between Trading Partners. The Business Process Schema will govern the choreography of business messages and signals.
Business Message Payload
The Assembly Document describes how to construct a Business Message Payload during the Design Phase. (At the time a Trading Partner Agreement is finalized, the Business Message Payloads must also be agreed upon and not subject to change.)
Business Message Type
A Business Message Type is a container of artifacts that describes the information exchanged in a Business Interaction. A Business Interaction synchronizes the knowledge on states of Business Entities at both sides of the interaction, in order to enable the participating Business Partners to continue an intra- and inter-organizational Business Process. A Business Message is not a Business Information Entity (BIE), and does not require a corresponding Aggregate Core Component (ACC). Business Message Types may however be based on more generic Business Message Types, much like Aggregate Business Information Entities are based on Aggregate Core Components. (CCMA 0.6)
Business Modeling Artifact
Modeling artifact from the Business Operational View. Business Modeling Artifacts SHALL be capable of being discovered and shared by other Actors within the infrastructure to facilitate reusability.
Business Object
An unambiguously identified, specified, referenceable, registerable and re-useable scenario or scenario component of a business transaction. The term business object is used in two distinct but related ways, with slightly different meanings for each usage: In a business model, business objects describe a business itself, and its business context. The business objects capture business concepts and express an abstract view of the business's "real world". The term "modeling business object" is used to designate this usage. In a design for a software system or in program code, business objects reflects how business concepts are represented in software. The abstraction here reflects the transformation of business ideas into a software realization. The term "systems business objects" is used to designate this usage. (ISO/IEC 15944-2)
Business Object Type
BOT
Modeling artifact from the Business Operational View (BPSS 1.05)
Business Operational View
BOV
A perspective of business transactions limited to those aspects regarding the making of business decisions and commitments among organizations, which are needed for the description of a business transaction. (ISO/IEC 14662)
Business Operations Map
BOM
"The partitioning of business processes into business areas and business categories first part of Requirements Workflow (UMM)"
business partner
An entity that engages in business transactions with another business partner(s). (BPSS 1.05)
Business Process
BP
(1) The means by which one or more activities are accomplished in operating business practices. (UMM) (2) The Business Process as described using the UN/CEFACT Catalogue of Common Business Processes. (CCTS 2.01)
Business Process activity
See "Business Process". (N093/UMMUG)
Business Process Model
The standard is a model of the business process, not a model of the data, and allows business partners an opportunity to have a dialogue on common ground about business processes that currently are embedded in the applications that perform them. BPML (Business Process Modeling Language) allows these processes to be managed outside the applications, which potentially will foster increased collaboration and innovation between enterprises. In addition, BPML is designed to bridge the gap between legacy IT infrastructures and emerging business-to-business collaboration protocols such as RosettaNet, BizTalk, and ebXML. While those protocols are concerned with the interfact between two companies, BPML deals with the higher-level objectives that move the business forward. (Howard Smith, CSC's) (N093/UMMUG)
Business Process Analysis Working Group
BPAWG
UN/CEFACT Business Process Analysis Working Group. Responsible for analysing and understanding the key elements of international transactions and working for the elimination of constraints. (UN/CEFACT)
Business Process and Information Model
Standard methodology and mechanism for modeling a Business Process and its' associated information models. (UMM)
Business Process Context
The Business Process name(s) as described using the UN/CEFACT Catalogue of Common Business Processes as extended by the user. (CCTS 2.01)
business process interface
The definition of how to interact with one partner role in order to make partner perform a desired service. (BPSS 1.05)
Business Process Role Context
The actors conducting a particular Business Process, as identified in the UN/CEFACT Catalogue of Common Business Processes. (CCTS 2.01)
Business Process Runtime Expression
BPRE
An abstract architectural principle of a runtime expression of a Business Process that is semantic and syntax specific. (BPSS 1.05)
Business Process Specification Schema
BPSS
Defines the necessary set of elements to specify run-time aspects and configuration parameters to drive the partners' systems used in the collaboration. (BPSS 1.05) The goal of the BP Specification Schema is to provide the bridge between the eBusiness process modeling and specification of eBusiness software components. (CPP 2.0)
business profile
Describes a company's ebXML capabilities and constraints, as well as its supported business scenarios.
Business Requirement Specification
BRS
A document that specifies the business requirements for the definition of a specific business process. The business requirements are defined using exclusively business specific terminology with the information requirements expressed in appropriate text, schematics and models that are not influenced by specific harmonised sector neutral terminology. (ICG)
Business Requirements View
BRV
The view of a business process model that captures the business scenarios, inputs, outputs, constraints and boundaries for business processes and their interrelationships within business process collaborations. This view is how the business domain expert sees and describes the process to be modelled. The BRV is expressed in the language and concepts of the business domain expert. (N093/UMMUG)
business role
The Role(s) of Business Partners used in a Business Collaboration and described in the Business Process Model. (BPSS 1.05)
business rule
Rules, regulations and practices for business. (UMM)
business semantic
A precise meaning of words from a business perspective. (CCTS 2.01)
business service
A business service is a network component that responds to business transaction requests initiated by other services.
Business Service Interface
(1) An ebXML collaboration that is conducted by two or more parties each using a human or automated business service that interprets the documents and document envelopes transmitted and decides how to (or whether to) respond. (BPSS 1.05) (2) The Business Service Interface is an abstract architectural component that references the business and technical details of hox to invoke a business service, wheter using a manual or automated interface. (UEBA 0.59)
Business Service View
BSV
"The view of a business process model that specifies the component services and agents and their message (information) exchange as interactions necessary to execute and validate a business collaboration. The BSV is expressed in the language and technical concepts of the software developer. The view of a business process model that specifies the electronic formation of business contracts using an electronic medium Design Workflow. (N093/UMMUG)"
Business stakeholder
An individual who is materially affected by the outcome of the system in a business domain. (N093/UMMUG)
Business Term
This is a synonym under which the Core Component or Business Information Entity is commonly known and used in the business. A Core Component or Business Information Entity may have several business terms or synonyms. (CCTS 2.01)
Business Transaction
BT
(1) A business transaction is a set of business information and business signal exchanges amongst two business partners that must occur in an agreed format, sequence and time period. (UMM) (2) A business transaction is a logical unit of business conducted by two or more parties that generates a computable success or failure state. The community, the partners, and the process, are all in a definable, and self-reliant state prior to the business transaction, and in a new definable, and self-reliant state after the business transaction. In other words if you are still 'waiting' for your business partner's response or reaction, the business transaction has not completed. (CPP 2.0) (3) A Business Transaction is the atomic unit of work in a trading arrangement between two business partners. A Business Transaction is conducted between two parties playing opposite roles in the transaction. (BPSS 1.05) (4) An economic interaction, which may, or may not, be atomic in nature. A set of state changes that occur, or are desired, in computer systems controlled by some set of parties, and these changes are related in some business application defined manner. A Business Transaction is subject to, and a part of, a business relationship. (It is assumed that the parties involved in a Business Transaction have distinct and autonomous Business (Application) Systems, which do not require knowledge of each others' implementation or internal state representations in volatile or persistent storage. Access to such loosely coupled systems is assumed to occur only through service interfaces.) Note: In the UMM the general term 'Business Transaction' is applied very specifically to a single request or single request / response pair with specified optional signals between exactly two parties.(Tony Frecher)
Business Transaction View
BTV
"The view of a business process model that captures the semantics of business information entities and their flow of exchange between roles as they perform business activities. This view is an elaboration on the business requirements view by the business analyst and is how the business analyst sees the process to be modelled. This view uses the language and concepts of the business analyst to convey requirements to the software designer and the business domain expert. The view in a business process model that specifies the contract formation process for various types of business contracts Analysis Workflow (N093/UMMUG)"
Cancel / Roll back
Process a counter effect for the current effect of a set of messages / procedures. There are a number of different ways that this may be achieved in practice.(Tony Frecher)
TERM
ACRONYM
DEFINITION
capsule
A specific design pattern which represents an encapsulated thread of control in the system. A capsule is a stereotyped class with a specific set of required and restricted associations and properties. (RUP)
cardinality
An indication whether a characteristic is optional, mandatory and/or repetitive. (CCTS 2.01)
Catalogue of Business Information Entity
This represents the approved set of Business Information Entities from which to choose when applying the Core Component discovery process. (CCTS 2.01)
Catalogue of Core Component
See Core Component Catalogue. (CCTS 2.01)
CCL
See Core Component Library. (CCTS 2.01)
charasteristic
abstraction of a property of an object or of a set of objects NOTE: Characteristics are used for describing concepts. (ISO 1087-1:2000, 3.2.4).
Child Core Component
A Core Component used as part of a larger aggregate construct. (CCTS 2.01)
choreography
(1) A declaration of the activities within collaboration and the sequencing rules and dependencies between these activities. (2) The Business Transaction Choreography describes the ordering and transitions between business transactions or sub collaborations within a binary collaboration. For example, in a UML tool this could be done using a UML activity diagram. The choreography is described in the ebXML Business Process Specification Schema using activity diagram concepts such as start state, completion state, activities, synchronizations, transitions between activities, and guards on the transitions. (BPSS 1.05)
class
(1) A description of a set of objects that share the same attributes, operations, methods, relationships, and semantics. A class may use a set of interfaces to specify collections of operations it provides to its environment. See interface. (RUP) (2)a description of a set of objects that share the same attributes, operations, methods, relationships, and semantics (ISO/IEC 19501-1:2001, 2.5.2.9).
class diagram
"Shows static structure of concepts, types, and classes. Concepts show how users think about the world types show interfaces of software components classes show implementation of software components. (OMG Distilled) A diagram that shows a collection of declarative (static) model elements, such as classes, types, and their contents and relationships. (RUP)"
classification scheme
(1) This is an officially supported scheme to describe a given Context Category. (CCTS 2.01) (2) arrangement or division of objects into groups based on characteristics that the objects have in common, e.g.,origin, composition, structure, application, and function. (ISO 11179-2, First edition)
classification scheme item
component of content in a classification scheme. NOTE This may be a node in a taxonomy or ontology, a term in a thesaurus, etc. (ISO 11179-2, First edition)
classified component
any component of a data element that may be classified in one or more classification schemes. NOTE The components include the object class, property, representation class, data element concept, value domain, and data element. (ISO 11179-2, First edition)
client
Software that initiates a connection with a Server.
code
A character string (letters, figures or symbols) that for brevity and/or language independency may be used to represent or replace a definitive value or text of an attribute. Codes usually are maintained in code lists per attribute type (e.g. colour). (ebXML CC Dictionary Naming Conventions)
collaboration
"(1) Describes a pattern of interaction among objects it shows the objects participating in the interaction by their links to each other and the messages they send to each other. (RUP) (2) Two or more parties working together under a defined set of rules. (CPP 2.0)"
collaboration diagram
"A collaboration diagram describes a pattern of interaction among objects it shows the objects participating in the interaction by their links to each other and the messages they send to each other. Unlike a sequence diagram, a collaboration diagram shows the relationships among the instances. Sequence diagrams and collaboration diagrams express similar information, but show it in different ways. See sequence diagram. (RUP)"
Collaboration Protocol
The protocol that defines for a Collaborative Process: 1. The sequence, dependencies and semantics of the Documents that are exchanged between Parties in order to carry out that Collaborative Process, and 2. The Messaging Capabilities used when sending documents between those Parties. Note that a Collaborative Process can have more than one Collaboration Protocol by which it can be implemented. (CPPA 2.0)
Collaboration Protocol Agreement
CPA
(1) Information agreed between two (or more) Parties that identifies or describes the specific Collaboration Protocol that they have agreed to use. (CPPA 2.0) (2) A CPA indicates what the involved Parties "will" do when carrying out a Collaborative Process. A CPA is representable by a Document
Collaboration Protocol Profile
CPP
(1) Information about a Party that can be used to describe one or more Collaborative Processes and associated Collaborative Protocols that the Party supports. (CPPA 2.0) (2) A CPP indicates what a Party "can" do in order to carry out a Collaborative Process. A CPP is representable by a Document. While logically, a CPP is a single document, in practice, the CPP might be a set of linked documents that express various aspects of the capabilities. A CPP is not an agreement. It represents the capabilities of a Party. (CCTS 2.01)
Collaborative Process
A shared process by which two Parties work together in order to carry out a process. The Collaborative Process can be defined by an ebXML Collaboration Model.
commitment
An obligation to perform an economic event (that is, transfer ownership of a specified quantity of a specified economic resource type) at some future point in time. Order line items are examples of commitment. (BPSS 1.05)
common attribute
a basic attribute that is applicable to all types of metadata item (ISO 11179-3, Second edition)
Common Business Process
"(1) A business process that is used with reasonable frequency in a business community. (BPSS 1.05) (2) For electronic business-to-business commerce, we are interested in business processes that manifest themselves in an exchange (one way, two way, or n-way) of information in electronic format between parties. Typically, Common Business Processes are defined by standards bodies or business communities that are generally perceived as defining de facto standards for business processes within their domain of specialization. A business process that is not defined as common by a standards body or is only used by a small business community is not a Common Business Process. The phrase ""exchange of information in electronic format"" includes XML messaging, EDI messaging, file transfers, and other forms of electronic data exchange. This could include facsimile, email, and phone conversations. However, it is probably important that any business process that contains a facsimile or phone conversation component also include at least one electronic message, file transfer, or the like."
common facility
common facility (of Metadata Registry) a facility provided by a Metadata Registry that is applicable to all types of Administered Item within the registry. (ISO 11179-3, Second edition)
Communication Protocol Envelope
The outermost envelope of an ebXML Message. For example: HTTP or SMTP. (ebMS Spec)
component
A physical, replaceable part of a system that packages implementation and conforms to and provides the realization of a set of interfaces. A component represents a physical piece of implementation of a system, including software code (source, binary or executable) or equivalents such as scripts or command files. (RUP)
component diagram
A diagram that shows the organizations and dependencies among components. (RUP)
component interface
A named set of operations that characterize the behavior of a component. (OMG)
composite attribute
an attribute whose datatype is non-atomic (ISO 11179-3, Second edition)
composite datatype
a datatype that is also a class. NOTE: A composite datatype is used as a datatype for a composite attribute. (ISO 11179-3, Second edition)
concept
"(1) An abstract idea a general notion:
a plan of intention a conception
an idea or invention to help sell or publicize a commodity
an idea or thought which corresponds to some distinct entity or class of entities, or to its essential features, or determines the application of a term (especially a predicate), and thus plays a part in the use of reason or language. (NOD) (2) unit of knowledge created by a unique combination of characteristics (ISO 1087-1:2000, 3.2.1)."
concept system
set of concepts structured according to the relations among them (ISO 1087-1:2000, 3.2.11)
conceptual domain
set of valid value meanings. NOTE: The value meanings may either be enumerated or expressed via a description. (ISO/IEC 11179-3:2003, 3.3.21)
conceptual model
conceptual model that represents an abstract view of the real world. NOTE: A conceptual model represents the human understanding of a system. (ISO 11179-1, Second edition)
concrete class
A class that can be directly instantiated. (OMG)
conditional
"required under certain specified conditions. NOTE 1: One of three obligation statuses applied to the attributes of metadata items, indicating the conditions under which the attribute is required. See also mandatory (3.2.17) and optional (3.2.28). NOTE 2: Obligation statuses apply to metadata items with a Registration Status of ""recorded"" or higher. (ISO 11179-3, Second edition)"
Confirm
Ensure that the effect of a set of messages / procedures is completed. There are a number of different ways that this may be achieved in practice(Tony Frecher)
conformance
"Fulfilment of a product, process or service of all requirements specified adherence of an implementation to the requirements of one or more specific standards or technical specifications. "
constraint
A semantic condition or restriction. Certain constraints are predefined in the OMG, others may be user defined. Constraints are one of three extensibility mechanisms in OMG. See tagged value, stereotype. (RUP)
constraint language
A formal expression of actions occurring in specific Contexts to assemble, structurally refine, and semantically qualify Core Components. The result of applying the Constraint Language to a set of Core Components in a specific Context is a set of Business Information Entities. (CCTS 2.01)
content component
Defines the primitive type used to express the content of a Core Component Type. (CCTS 2.01)
Content Component Restrictions
The formal definition of a format restriction that applies to the possible values of a Content Component. (CCTS 2.01)
context
(1) Defines the circumstances in which a Business Process may be used. This is specified by a set of Context Categories known as Business Context. (CCTS 2.01) (See Business Context.) (2) A designation or description of the application environment or discipline in which a name is applied or from which it originates (ISO/IEC 11179-3).
context category
A group of one or more related values used to express a characteristic of a business circumstance. (CCTS 2.01)
context driver
Driver information that may be discovered from the Trading Partner Profiles or the Registry Information Model data at the Trading Partner Agreement design time. Eight context categories defined: Business Process, Product Classification, Industry Classification, Geopolitical, Official Constraints, Business Process Role, Supporting Role, System Capabilities. (UABA 0.59)
Context Rules Construct
The overall expression of a single set of rules used to apply Context to Core Components. (CCTS 2.01)
Context Rules Message
CRM
A Context Rules Message can be derived from the context by accessing Context Rules Lookup Tables from the Registry. (UEBA 0.59)
Contract
Any rule, agreement or promise which constrains an Party's behaviour and is known to any other Party, and upon which any other knowing Party may rely.(Tony Frecher)
control class
A class used to model behavior specific to one, or a several use cases. (RUP)
controlled vocabulary.
A supplemental vocabulary used to uniquely define potentially ambiguous words or business terms. This ensures that every word within any of the Core Component names and definitions is used consistently, unambiguously and accurately. (CCTS 2.01)
controlling agency
Agency responsible for controlling the content of a basic information entity. (CCTS 2.01)
Core Component
CC
A building block for the creation of a semantically correct and meaningful information exchange package. It contains only the information pieces necessary to describe a specific concept.(CCTS 2.01) A semantic building block for creating clear and meaningful data models, vocabularies, and information exchange packages. Core Components are used as the basis for creating Business Information Entities. (CCTS 2.x)
Core Component Catalog
The temporary collection of all metadata about each Core Component that has been discovered during the development and initial testing of this Core Component Technical Specification, pending the establishment of a permanent Registry/Repository. (CCTS 2.01)
Core Component Dictionary
An extract from the Core Component Catalogue that provides a ready reference of the Core Component through its Dictionary Entry Name, component parts, and definition. (CCTS 2.01)
Core Component Library
CCL
The Core Component Library is the part of the registry/repository in which Core Components shall be stored as Registry Classes. The Core Component Library will contain all the Core Component Types, Basic Core Components, Aggregate Core Components, Basic Business Information Entities and Aggregate Business Information Entities. (CCTS 2.01)
Core Component Message Library
TBD (CCMA 0.6)
Core Component Property
A business characteristic belonging to the Object Class represented by an Aggregate Core Component. (CCTS 2.01)
Core Component Type
CCT
A Core Component which consists of one and only one Content Component that carries the actual content plus one or more Supplementary Components giving an essential extra definition to the Content Component. Core Component Types do not have business semantics. (CCTS 2.01) (This definition was deleted in CCTS 2.x & move to Example.)
core data type
A Core Component, which consists of one and only one Content Component, that carries the actual content plus one or more Supplementary Components giving an essential extra definition to the Content Component. Core Data Types do not have Business Semantics. Core Data Types define the set of valid values that can be used for a particular Basic Core Component Property or Basic Business Information Entity Property. (CCTS 2.01)
Counter-effect
An appropriate effect intended to counteract a Provisional Effect. (Tony Frecher)
CPA
CPA
See Collaboration Protocol Agreement
CPP
CPP
See Collaboration Protocol Profile
CPP-A
See Collaboration Protocol Profile and Collaboration Protocol Agreement
TERM
ACRONYM
DEFINITION
data
(1) re-interpretable representation of information in a formalized manner suitable for communication, interpretation, or processing. NOTE: Data can be processed by humans or by automatic means. (ISO 2382-1:1993, 01.01.02). (2) representation of facts, concepts, or instructions in a formalized manner suitable for communication, interpretation, or processing by humans or by automatic means (ISO 2382-4)
data element
(1) A unit of data for which the identification, meaning, representation and permissible values are specified by means of a set of attributes (ISO/IEC 11179-3). (2) unit of data for which the definition, identification, representation and permissible values are specified by means of a set of attributes (ISO 11179-2, First edition)
data element concept
A concept which can be represented in the form of a data element, described independently of any particular representation (ISO/IEC 11179-3).
data identifier
An identifier of a data element (a string of characters or other graphic symbols) assigned by a Registration Authority. (ISO/IEC 11179-3)
data model
graphical and/or lexical representation of data, specifying their properties, structure and inter-relationships. (ISO 11179-1, Second edition)
data type
(1) A descriptor of a set of values that lack identity and whose operations do not have side effects. Data types include primitive pre-defined types and user-definable types. Pre-defined types include numbers, string and time. User-definable types include enumerations. (RUP) (2) Defines the set of valid values that can be used for a particular Basic Core Component Property or Basic Business Information Entity Property. It is defined by specifying restrictions on the Core Component Type that forms the basis of the Data Type. (CCTS 2.01) (3) In the CCTS 2.x, "data type" was changed to "core data type).
deliverable
An output from a process that has a value, material or otherwise, to a customer or other stakeholder. (RUP)
deployment diagram
A diagram that shows the configuration of run-time processing nodes and the components, processes, and objects that live on them. Components represent run-time manifestations of code units. See component diagram. (RUP)
design
The part of the software development process whose primary purpose is to decide how the system will be implemented. During design, strategic and tactical decisions are made to meet the required functional and quality requirements of a system. See analysis. (RUP)
design pattern
A specific solution to a particular problem in software design. Design patterns capture solutions that have developed and evolved over time, expressed in a succinct and easily applied form. (RUP)
Design Phase
The design phase SHALL be accomplished by applying object-oriented principles based on the UN/CEFACT Modeling Methodology. (UEBA 0.83)
diagram
A graphical depiction of all or part of a model. (RUP) OMG supports the following diagrams: class diagram, object diagram, use-case diagram, sequence diagram, collaboration diagram, statechart diagram, activity diagram, component diagram, and deployment diagram.
Dictionary Entry Name
This is the unique official name of a Core Component, Business Information Entity, Business Context or Data Type in the dictionary. (CCTS 2.01).
definition
representation of a concept by a descriptive statement which serves to differentiate it from related concepts. (ISO 1087-1:2000, 3.3.1).
digital signature
A digital code that can be attached to an electronically transmitted message that uniquely identifies the sender
Discovery Phase
The Discovery Phase covers all aspects of the discovery of ebXML related resources. A Trading Partner who has implemented an ebXML Business Service Interface can begin the process of discovery. One possible discovery method may be to request the Collaboration Protocol Profile of another Trading Partner. (UEBA 0.83)
distributed registry
Federation of multiple registries that behaves logically as one registry. (UEBA 0.83)
document
A Document is any data that can be represented in a digital form.
document exchange
An exchange of documents between two parties.
Document Type Definition
DTD
DTD is to define the legal building blocks of any SGML-based (SGML = Standard Generalized Markup Language) document. It defines the document structure with a list of legal elements. (W3C)
domain
An area of knowledge or activity characterized by a family of related systems. (RUP)
DTD
DTD
See Document Type Definition
TERM
ACRONYM
DEFINITION
ebXML SOAP Extention
A specification of the structure and composition of the information necessary for an ebXML Message Service to successfully generate or process an ebXML Message (ebMS 1.0)
economic contract
A subtype of agreement between partner types that some actual economic exchanges will occur in the future. Contracts can have recursive relationships with other contracts, for example, yearly contracts with monthly releases and weekly or daily shipping schedules. Contracts are containers for collections of commitments. For example, a purchase order is a contract wherein the line items are commitments. (BPSS 1.05)
economic event
The transfer of control of an economic resource from one party to another party. (BPSS 1.05)
economic resource
A quantity of something of value that is under the control of an enterprise. (BPSS 1.05)
economic resource type
An economic resource type is the abstract classification or definition of an economic resource. For example, in an ERP system, ItemMaster or ProductMaster would represent the Economic Resource Type that abstractly defines an Inventory item or product. Forms of payment are also defined by economic resource types, e.g. currency. (BPSS 1.05)
EDI
See Electronic Data Interchange
EDI message
An approved, published, and maintained formal description of how to structure the data required to perform a specific business function, in such a way as to allow for the transfer and handling of this data by electronic means. (MoU)
EDIFACT messages
A electronic message formats based on UN/EDIFACT standard set developed and maintained by the UN/EDIFACT Working Group which are in UN/TDID directories. (UN/CEFACT)
EDIFACT Working Group
EWG
UN/EDIFACT Working Group. To develop and maintain UN/EDIFACT, the support of harmonised implementations and the use of multi-lingual terminology. (UN/CEFACT)
elaboration
The second phase of the process where the product vision and its architecture are defined. (RUP)
elaboration phase
The second phase of the process where the product vision and its architecture are defined. (RUP)
electronic business
eBusiness
A generic term covering information definition and exchange requirements within and between enterprises, including customers by electronic means. (MoU)
electronic business XML
ebXML
An eBusiness concept based on EDI experience in business processes, XML interchange formats and the Internet technology. ebXML Initiative Project jointly launched by UN/CEFACT and OASIS for 15-18 months work in Nov. 1999 and finished in May 2001. Further work is being made by UN/CEFACT and OASIS separately. (UN/CEFACT)
electronic commerce
Electronic Commerce is doing business electronically. This includes the sharing of standardized unstructured or structured business information by any electronic means (such as electronic mail or messaging, World Wide Web technology, electronic bulletin boards, smart cards, electronic funds transfers, electronic data interchange, and automatic data capture technology) among suppliers, customers, governmental bodies and other partners in order to conduct and execute transactions in business, administrative and consumer activities. (UN/CEFACT- SIMAC)
Electronic Data Interchange
EDI
The automated exchange of any predefined and structured data for business among information systems of two or more organizations.
element
An atomic constituent of a model. (OMG)
encryption
"Cryptographic transformation of data (called ""plaintext"") into a form (called ""ciphertext"") that conceals the data's original meaning to prevent it from being known or used. If the transformation is reversible, the corresponding reversal process is called ""decryption"", which is a transformation that restores encrypted state.data to its original state. "
entity
any concrete or abstract thing that exists, did exist, or might exist, including associations among these things. Example: A person, object, event, idea, process, etc. NOTE: An entity exists whether data about it are available or not. (ISO/IEC 2382-17:1999, 17.02.05).
entity class
A class used to model information that has been stored by the system, and the associated behavior. A generic class reused in many use cases, often with persistent characteristics. An entity class defines a set of entity objects, which participate in several use cases and typically survive those use cases. (RUP)
enumeration
A list of named values used as the range of a particular attribute type. For example, RGBColor = (red, green, blue). Boolean is a predefined enumeration with values from the set (false, true). (RUP)
Error handling
This component handles the reporting of errors encountered during MSH or Application processing of a message. (ebMS 1.0)
essential charactericstic
characteristic which is indispensable to understanding a concept (ISO 1087-1:2000, 3.2.6).
event
The specification of a significant occurrence that has a location in time and space. In the context of state diagrams, an event is an occurrence that can trigger a transition. (RUP)
EWG
EWG
See EDIFACT Working Group (UN/CEFACT)
eXtensible Markup Language
XML
XML is designed to enable the exchange of information (data) between different applications and data sources on the World Wide Web and has been standardized by the W3C. XML is a simplified subset of the Standard Generalized Markup Language (SGML). XML allows construction of structured data (trees), which rely on composition relationships. XML schemas are used to define data models. (W3C)
extension
totality of objects to which a concept corresponds. (ISO 1087-1:2000, 3.2.8).
TERM
ACRONYM
DEFINITION
Final Effect
An appropriate effect intended to complete and finalise a Provisional Effect. (Tony Frecher)
Functional Service View
FSV
A perspective of business transactions limited to those information technology interoperability aspects of IT systems needed to support the execution of open-edi transactions. (ISO/IEC 14662)
functional set
A set of alternative representations for the same semantic concept. (CCTS 2.01)
TERM
ACRONYM
DEFINITION
general concept
concept which corresponds to two or more objects, which form a group by reason of common properties. NOTE: Examples of general concepts are 'planet', 'tower'. (ISO 1087-1:2000, 3.2.3)
generalization
(1) A taxonomic relationship between a more general element and a more specific element. The more specific element is fully consistent with the more general element and contains additional information. An instance of the more specific element may be used where the more general element is allowed. See inheritance. (RUP) (2) that is fully consistent with the first class (i.e. it has all of its attributes and relationships) and that adds additional information. NOTE: A generalization is a type of relationship. (Adapted from ISO/IEC 19501-1:2001, 2.5.2.24)
Geopolitical Context
A specific instance of a context driver covering all aspects of geography and political influences on a business. (CCTS 2.01)
Globally Unique Identifier
GUID
A unique string of characters used to identify a common object. For example, the unique identifier may be computed by adding the time and date to the network adapter's internal serial number.
TERM
ACRONYM
DEFINITION
Header parsing
To extract or transform information from a received SOAP Header or Body element into a form that is suitable for processing by the MSH implementation. (ebMS 1.0)
Header processing
One ebXML Message Service does how report errors it detects to another ebXML Message Service Handler the creation of the SOAP Header elements for the ebXML Message uses input from the application, passed through the Message Service Interface, information from the Collaboration Protocol Agreement (CPA defined in (ebCPP)) that governs the message, and generated information such as digital signature, timestamps and unique identifiers. (ebMS 1.0)
TERM
ACRONYM
DEFINITION
ICG
ICG
See Information Content Management Group (UN/CEFACT)
identifier
(1) See data identifier. (2) (in Metadata Registry) sequence of characters, capable of uniquely identifying that with which it is associated, within a specified context. NOTE: A name should be used as an identifier because it is not linguistically neutral. (ISO 11179-1, Second edition)
IEC
IEC
See International Electrotechnic Commission.
implementation
(1) An implementation is the realization of a specification. (NIST) (2) It can be a software product, system or program. (CCTS 2.01)
Implementation Functional View
IFV
View aligned with UMM. (UMM)
Implementation Phase
The implementation phase deals specifically with the procedures for creating an application of the ebXML infrastructure. (UEBA 0.59)
Inception Phase
The first phase of the Unified Process, in which the seed idea, request for proposal, for the previous generation is brought to the point of being (at least internally) funded to enter the elaboration phase. (RUP)
individual concept
concept which corresponds to only one object. NOTE: Examples of individual concepts are: 'Saturn', 'the Eiffel Tower'. (ISO 1087-1:2000, 3.2.2).
industry classification context
Semantic influences related to the industry or industries of the trading partners (e.g., product identification schemes used in different industries). See Geographical Context. (CCTS 2.01)
industry expert
A person who is knowledgeable about the industry area being modeled.(N093/UMMUG)
information bundle
The formal description of the semantics of the information to be exchanged by Open-edi Parties playing roles in an Open-edi scenario. (ISO 14662)
Information Content Management Group
ICG
One of the newly established groups in the UN/CEFACT in May, 2002 Plenary. Work in ICG covers UN/CEFACT's libraries, code lists and recommendations. (UN/CEFACT)
information entity
A reusable semantic building block for the exchange of business-related information. (CCTS 2.01)
information interchange
process of sending and receiving data in such a manner that the information content, or meaning assigned to the data, is not altered during the transmission. (ISO 11179-6, Second edition)
information model
The information model does not deal with the actual content of the repository. All Elements of the information model represent metadata about the content and not the content itself. The Registry Information Model provides a blueprint or high-level schema for the ebXML Registry. Its primary value is for implementers of ebXML Registries. It provides these implementers with information on the type of metadata that is stored in the Registry as well as the relationships among metadata Classes. (N093/UMMUG, OASIS/ebXML Registry Information Model V2.0)
inheritance
(1) The mechanism by which more specific elements incorporate structure and behavior of more general elements related by behavior. See generalization. (RUP) (2) In object-oriented programming, the ability of a superclass to pass its characteristics (methods and instance variables) on to its subclasses. (techdictionary.com)
instance
An individual entity satisfying the description of a class or type. (RUP)
intention
set of characteristics which makes up the concept. (ISO 1087-1:2000, 3.2.9).
interaction diagram
Shows how several objects collaborate in single use case. (UMM Distilled)
interface
A collection of operations that are used to specify a service of a class or a component. (RUP) A named set of operations that characterize the behavior of an element.
International Code Designator
ICD
identifier of an organization identification scheme. NOTE Based on ISO/IEC 6523-1:1998, definition 3.8. (ISO 11179-6, Second edition)
International Code Designator value
ICD value
identifier allocated to a particular organization identification scheme (ISO/IEC 6523-1:1998, definition 3.9)
International Electrotechnical Commission (The)
IEC
"IEC is the worldwide authority for developing, publishing and promoting voluntary consensus International Standards in the field of electrotechnology that this activity facilitates international exchange of goods and services, and develops cooperation in the spheres of intellectual, scientific, technological, and economic activity and that the IEC currently comprises 58 participating countries representing the full spectrum of electrotechnical interests therein, including suppliers, users, governmental, professional and scientific bodies. (MoU) "
International Organization for Standardization (The)
ISO
"ISO is a worldwide federation of national standards bodies, at present comprising some 120 members (one per country) that the object of ISO is to promote the development of standardization and related activities in the world with a view to facilitating international exchange of goods and services, and to developing cooperation in the spheres of intellectual, scientific, technological and economic activity that the results of ISO work are published in the form of International Standards that international organizations, governmental and non-governmental, participate in the development of ISO International Standards. (MoU) "
international registration data identifier
IRDI
internationally unique identifier for an Administered Item as defined in the framework of ISO/IEC 11179. (ISO 11179-6, Second edition)
International Telecommunication Union (The)
ITU
"ITU is a specialized agency of the United Nations within which governments and the private sector coordinate global telecommunication networks and services that within the ITU, the ITU-T sector mission is efficient, on time production of high quality global standards for telecommunications (except radiocommunications) that, at the time of signature, ITU comprises 189 Member States and ITU-T Sector Members include 160 recognized operating agencies, 189 manufacturers and industrial organizations, 38 international and regional organizations and 3 other entities dealing with telecommunication matters. (MoU) "
International Trade and Business Processes Group
TBG
One of the newly established groups in the UN/CEFACT in May, 2002 Plenary. ICG's works cover business and governmental process analysis, best practices, and international trade procedures using the UN/CEFACT Modeling Methodology to support the development of appropriate trade facilitation and electronic business solutions. (UN/CEFACT)
invariant
"Each Business Message Type may have constraints associated with it. A constraint may be – an Invariant – a Precondition – a Postcondition and – a Transition Condition. Invariants are constraints defined on the information in the Business Message itself. Invariants may affect repetition and cardinality, element values, or a mix (e.g. ""if the Delivery Term=""FOB"", a Delivery Term Location must be present""). Whenever a constraint is totally within the scope of an ABIE, the constraint should be defined on ABIE level as a CCTS Usage Rule. Contraints on the level of the Business Message should have a scope wider thant an ABIE. (CCMA 0.6a)"
ISO
ISO
See International Organization for Standardization. (The)
item identifier
identifier for an item (ISO/IEC 11179-3:2003, definition 3.3.76)
item registration authority identifier
identifier of the Registration Authority registering the item (ISO/IEC 11179-3:2003, definition 3.3.77)
ITU
ITU
See International Telecommunication Union. (The)
language
system of signs for communication, usually consisting of a vocabulary and rules (ISO 5127:2001, 1.1.2.01)
TERM
ACRONYM
DEFINITION
TERM
ACRONYM
DEFINITION
TERM
ACRONYM
DEFINITION
layer
(1) A specific way of grouping packages in a model at the same level of abstraction. (2) The organization of classifiers or packages at the same level of abstraction. A layer represents a horizontal slice through an architecture, whereas a partition represents a vertical slice. Contrast: partition. (RUP)
Legal Group
LG
One of the newly established groups in the UN/CEFACT in May, 2002 Plenary. LG works on legal issued related to ebXML with a particular view to maintaining repositories and contract formation. (UN/CEFACT)
lexicon
The word lexicon used in UN/CEFACT Modeling Methodology express the bridge between the specific business or industry language and the knowledge expressed by the models in a more generalized industry neutral language. The lexicon contains data and process definitions including relationships and cross-references as expressed in business terminology. (UMM)
Life cycle
series of changes in the life of an organism, including reproduction. (POD) (N093/UMMUG)
LG
LG
See Legal Group. (UN/CEFACT)
TERM
ACRONYM
DEFINITION
Managed Object
Metadata referred to in the Registry. Trading Partner Profiles and Trading Partner Agreements SHALL be capable of pointing at other artifacts via a reference to a Registry Managed Object. (UEBA 0.83)
mandatory
"always required. NOTE 1: One of three obligation statuses applied to the attributes of metadata items, indicating the conditions under which the attribute is required. See also conditional (3.2.9) and optional (3.2.28). NOTE 2: Obligation statuses apply to metadata items with a Registration Status of ""recorded"" or higher. (ISO 11179-3, Second edition)"
Memorandum of Understanding
MoU
Memorandum of Understanding between IEC, ISO, ITU and UN/ECE concerning standardization in the field of eBusiness
message
(1) A specification of the conveyance of information from one instance to anoth
Page Operations
Browse Space