[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [regrep-cc-review] Friday Conference Call Details and Agenda
Hi All,
Here are call details (copy from Monday's message) and an agenda for our call tomorrow. I've included 2 additional items to help us prepare for our calls in the future:
"Read-Ahead" - a list of things that we can read in advance of all (if we have time, of course)
"Other Resources" - a list of items that we can bring to call (in addition to the Read-Ahead items)
Regarding agenda item #6: I've realized that we probably do not need to store any of the constructs that are associated with the Constraint Language. I'd like to take a few minutes to walk through part of this section, and explain my reasoning to see if we are all in agreement.
Regarding agenda item #7: I'd like to walk through this figure, to discuss each of the individual entities and their relationships with the other entities in the diagram. To make this easier, I created summarized information for each entity (from the bottom up) - please see the "Read-Ahead" section below (if you have time). My hope is that we can use the summarized information to help guide us through the discussion as we look at the figure.
Looking forward to talking with you all then!
Thanks,
Joe
Call Details:
CALL DATE: APR-05-2002 (Friday)
CALL TIME: 02:00 PM EASTERN TIME
DURATION: 1 hr 30 min
USA Toll Free Number: 800-779-6816
PASSCODE: 12136
LEADER: Ms Lisa Carnahan
Agenda:
1. Questions on last meeting's minutes
2. Minutes taker for this call
3. News from eBTWG front
4. Review Functional Points mapping document
5. Review Discussion Topics document
6. Discuss Constraint Language (CC Spec pp.61-66)
7. Discuss Figure 7-1 from CC Spec (p.70) - Metadata
8. Next call - date/time, goals, etc.
Read-Ahead:
Background information for Figure 7-1 (agenda item #7)
<<CC Spec Metadata - Notes on Figure 7-1>>
Other Resources:
CC Spec v1.8 (latest version)
OASIS/ebXML RIM v2.0
Functional Points Mapping Document v0.3 (attached, same as version sent on 3/29/02)
<<CC Spec-Registry Functional Points v0.3.doc>>
Discussion Topics Document v0.1 (attached, same as version sent on 3/29/02)
<<CC Review Discussion Topics v0.1.doc>>
**************************************************************************
Joseph M. Chiusano
Logistics Management Institute
2000 Corporate Ridge
McLean, VA 22102
Email: jchiusano@lmi.org
Tel: 571.633.7722
**************************************************************************
--- Begin Message ---Title: CC Spec Metadata - Notes on Figure 7-1
- From: "CHIUSANO, Joseph" <JCHIUSANO@lmi.org>
- To: "CHIUSANO, Joseph" <JCHIUSANO@lmi.org>
- Date: Thu, 4 Apr 2002 09:05:25 -0500
CC Spec v.1.8 Figure 7-1, p.70 - Notes from Bottom Up:
PLEASE NOTE: The metadata attributes listed below do not contain cardinality (optional/mandatory, repetitive, etc.) - however, these are listed in the CC spec.
Supplementary Component Value:
Page: 73
Description: Defines one possible value of a Supplementary Component.
More info: A Supplementary Component value shall only be stored if all possible values can be defined by an enumeration (e.g. list of quantity units)
Metadata attributes: Value: A possible value of a Supplementary Component
Ex: gram, secondMeaning: The meaning of the Supplementary Component when it has a particular value
Ex: unitExample: None
Content Component Restriction:
Page: 73/74
Description: Allows restrictions on values for a Content Component
More info: A Content Component Restriction shall exist only if the values can be defined by a format restriction such as string pattern, minimum or maximum length, or enumeration
Metadata attributes: Restriction Type: The type of format restriction to be applied to the Content Component
Ex: length, enumerationRestriction Value: The actual value of the Restriction Type
Ex: an integer value for restriction type "length", a list of possible values for restriction type "enumeration"Example: None
Content Component:
Page: 73
Description: Defines the primitive type used to express the content of a Core Component Type
Carries the actual content of a Core Component
More info: Table 8-2, p.87 - list of approved Content and Supplementary Components
Metadata attributes: Name: Name of the Content Component
Definition: A clear, unambiguous and complete explanation of the meaning of a Content Component
Primitive Type: Primitive type to be used for the expression of the value of a BCC based on the associated CCT
Ex: string, decimal, integer, boolean, date, binary
Example: For a CCT of Amount.Type, the Content Component carries the value of "12" and this value has no meaning on its own. But "12 Kilometres" or "12 Euro" (where "Kilometres" and "Euro" are the Supplementary Components) do have meaning.
Supplementary Component:
Page: 72
Description: Gives an essential extra definition to a CCT
More info: Table 8-2, p.87 - list of approved Content and Supplementary Components
Metadata attributes: Name: Name of the Supplementary Component
Definition: A clear, unambiguous and complete explanation of the meaning of a Supplementary Component and its relevance for the related CCT
Primitive Type: Primitive type to be used for the representation of the value of a Supplementary Component
Ex: string, decimal, integer, boolean, date, binary
Example: For a CCT of Amount.Type, the Content Component carries the value of "12" and this value has no meaning on its own. But "12 Kilometres" or "12 Euro" (where "Kilometres" and "Euro" are the Supplementary Components) do have meaning.
Core Component Type (CCT):
Page: 71
Description: A Core Component that consists of one and only one Content Component plus one or more Supplementary Components
More info: There are three difference categories of Core Components: Basic Core Component (BCC), Core Component Type (CCT), and Aggregate Core Component (ACC)
Stored CCT's shall include one Content Component that defines the primitive type and one or more Supplementary Components that give meaning to the Content Component
Metadata attributes: Name: Name of the CCT
Example: For a CCT of Amount.Type, the Content Component carries the value of "12" and this value has no meaning on its own. But "12 Kilometres" or "12 Euro" (where "Kilometres" and "Euro" are the Supplementary Components) do have meaning.
Representation Term:
Page: 72
Description: Defines the type of valid values for an information entity
More info: Part of the Naming Rules defined on p.42 (Object Class, Property Term, Representation Term)
Table 6-1, p.49 - list of permissible Representation Terms
Metadata attributes: Name: Name of the Representation Term
Example: Amount, Code, Date, Graphic, Identifier
Data Type:
Page: 72
Description: Defines the full range of valid values for a particular BCC
More info: See Table 8-2, p.87
Metadata attributes: Name: Name of the Data Type
Example: String, Decimal, Binary
Basic Core Component (BCC):
Page: 71
Description: A Core Component that represents a singular business concept with a unique business semantic definition
More info: A BCC is constructed using a CCT
BCC's are used in developing ACC's
Stored BCC's shall always be based on 3 elements: Object Class, Property Term, Data Type [JMC: Data Type is not listed as a metadata attribute on p.71]
Metadata attributes: Object Class: Basis for the Dictionary Entry Name
Property Term: Basis for the Dictionary Entry Name
Example: Financial Account. Identifier, Financial Account. Name, Financial Account. Country. Code
Core Component:
Page: 71
Description: A building block for the creation of a semantically correct and meaningful exchange "parcel"
Contains only the information pieces necessary to describe a specific concept
More info: There are three difference categories of Core Components: Basic Core Component (BCC), Core Component Type (CCT), and Aggregate Core Component (ACC)
[JMC: These categories are not reflected in the metadata below]
Metadata attributes: Business Term: A synonym term under which the Core Component is commonly known in business. A Core Component may have several Business Terms.
Example: Unit. Charge. Price, Location. Identification. Code
Aggregate Core Component (ACC):
Page: 71/72
Description: A collection of Core Components that convey a distince business meaning
More info: Consists of 2 or more BCC's, or at least one BCC plus one or more ACC's
Metadata attributes: Object Class: Basis for the Dictionary Entry Name
Example: Financial. Account. Details
--- End Message ---
Attachment:
CC Spec-Registry Functional Points v0.3.doc
Description: MS-Word document
Attachment:
CC Review Discussion Topics v0.1.doc
Description: MS-Word document
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC