OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: CC/BP Terminology alignment




BP PT Members,

I'm forwarding this message and attachment from Lisa Shreve.  She mentioned on
the StC call today, that her attempt to distribute this to the BP list was
blocked.  Please review the attachment, and we'll include discussion of this on
the 23 Oct. BP call.  Agenda and call-in information to be provided later.

Regards,

Paul Levine
BP PT co-lead




"Lisa M. Shreve" <lms@wwnet.com> on 10/18/2000 10:51:30 AM

To:   ebxml-stc <ebxml-stc@lists.ebxml.org>, "ebxml-core@lists.ebxml.org"
      <ebxml-core@lists.ebxml.org>, ebxml-bp@lists.ebxml.org
cc:    (bcc: Paul R. Levine/Telcordia)
Subject:  CC/BP Terminology alignment




Hi all,

In light of the discussion over the glossary occuring on the steering
committee listserv, and the efforts going on within core components, and
between core components and business process, I wanted to make this
available as soon as possible.

This is a work in progress!  The thing I really like about this matrix
is that it has compiled a set of descriptions/definitions which are
being used in cc and bp along with the set of terms which are being used
for the same description.

Reaching consensus on these terms has been an obstacle to getting the CC
methodology for describing core components updated and out for further
review.  So, I am most anxious to reach concensus.

Regards,

lms

Title: Core Component Terminology

Core Component Terminology

Version 0.1a, 18th October 2000

The following terms are defined in the various models currently proposed for the Core Components group.

NB. The first two terms are taken from the Business Process metamodel to allow core component definitions to be positioned with respect to Business Processes.

Proposed CC Terminology

Description

Original Model Terminology

Component Use Terminology

BusinessContext

Defines a context in which a business has chosen to employ an information entity

EntityApplication

Context/Classification

IndustrySector

Identifies which industry sector the context is being employed within from a predefined set of sector identifiers (or Other if not one of the predefined industry sectors)

Industry

ContextFactor

IndustrySectorQualifier

Subsection of existing industry sector. (If Other  has been selected for the IndustrySector a new industry is proposed for addition to the IndustrySector list.)   

 

ContextFactor

BusinessProcess

Identifies which business process the context applies to. (Taken from a predefined set of generic business processed)

 

ContextFactor

BusinessProcessQualifier

Identifies the generic type of the subprocess that applies to the context (e.g. whether it is part of a request/response sequence, a simple notification, etc)

 

ContextFactor

Region

Identifies the geographical region in which the information entity can validly be used

 

ContextFactor

CountryCodes

Identifies specific countries the information entity is valid within through their 2-alpha ISO 3166 country code.

 

ContextFactor

OfficialRequirements

Identifies which official information requirements the context satisfies.

 

ContextFactor


 

BusinessDocument

The set of functional units that are interchanged as part of a business activity

 

InformationBundle

FunctionalUnit

A set of information entities that can be used within a Business Document to control a business activity

EntityPattern

 

InformationEntity

Generic term that covers both AggregateInformationEntity and BasicInformationEntity.

 

 

 

 

 

 

AggregateInformationEntity

Defines a functional unit representation form that contains embedded information entities.

BusinessEntity

AggregateComponent

Identifier

Character string used to uniquely identify an information entity.

Identification

 

Name

Human-readable string for identification of information entity.

Name

 

Description

Description of function of information entity.

Description

 

SubmittedBy

Unique identifier assigned to organization submitting definition.

Submitter

 

Date

ISO 8601 date on which information entity was documented.

DateSubmitted

 

EmailAddress

Address to be used to request further information about information entity by e-mail.

 

 

MinMax

Indicates the maximum and minimum number of occurrences of the information entity that are permitted within this aggregate information entity. 

 

Cardinality

 

 

 

 

EmbeddedInformationEntity

Rules to be applied when embedding an information entity within an aggregate information entity.

EntityComponent

StructuralCoreComponent

InformationEntityID

Identifier used to uniquely identify embedded information entity

EntityID or RepresentationID

 

ExplanationOfUse

Explanation of function of embedded information entity within the aggregate information entity.

 

 

Order

If the order in which adjacent embedded information entities are entered is significant then all embedded information entities affected by the order should be assigned one of the values of sequence, all or choice.

 

 

BasicInformationEntity

Defines a functional unit representation form which contains data but which does not have embedded information entities.

RepresentationClass

SingleComponent

ControllingAgency

Agency responsible for controlling the content of an information entity

 

 

AgencyAssignedID

Identifier used to recognize the information entity within the specified ControllingAgency.

 

 

RepresentationType

Type of data to be used to represent the content of an information entity. (Must be a member of the set of Representation Types defined for ebXML.)

Format

 

URL

Electronic address used to access details about an externally defined code list.

 

 

PermittedValue

Defines one of the permitted values that has been assigned to a code list associated with a BasicInformationEntity.

CodeValue

 

Value

Form in which a permitted value is to be specified.

 

 

MeaningOfValue

Meaning represented by value.

 

 

Language

Language in which meaning of value is specified, expressed using codes defined in IETF RFC 1766.

 

 

Rule

Rule used to validate correct use of component.

 

Rule

Extension

Extension to information entity definition when applying a component in an Business Message.

 

Extension

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC