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


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-cc-review message

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

Subject: CCTS Spec RIM Mappings - Requirements [S19] and [S20]


I'm trying a new approach to the latest set of requirements - offering
them in smaller chunks. This might make them a bit more manageable for
us. So...

Below please find requirements [S19] and [S20], with my comments marked
with <JMC>. Please provide feedback as soon as possible.


Core Component Types are a particular category of Core Components. As
such, stored Core Component Types shall include all Attributes of stored
Core Components.

I believe we should represent Core Component Types (CCTs) as
RegistryObjects, with all attributes of Core Components.

Stored Core Component Types shall include one Content Component that
defines the Primitive Type and one or more Supplementary Components that
give meaning to the Content Component.

Regarding Content Components: The CCTS lists the following attributes
(jumping ahead to [S26]):

- Name: 	  Name of Content Core Component
- Definition:	  Definition of Content Core Component
- Primitive Type: Primitive Type to be used for the expression of the
value of an instance of a Basic Core Component based on the associated
Core Component Type

Regarding "Primitive Type" above: The CCTS lists the Primitive Types for
the various Content Components on p.97, Table 8-2. For example:

- Content Component "Amount. Content" has Primitive Type "decimal";
- Content Component "Binary Object. Content" has Primitive Type

My thought is: If these Primitive Type values are fixed, why should they
be specified as attributes of the Content Core Component? In other
words, I believe we can simply refer to (or reproduce) this table in our
Technical Note to tell implementers that:

- "When you are capturing a value for a Core Component that is based on
Core Component Type of Amount. Type, it must be a decimal value", or

- "When you are capturing a value for a Core Component that is based on
Core Component Type of Binary Object. Type, it must be a binary value"

Because of this, I really don't see a need to represent Content Core
Components in the registry. I believe that in an XML serialization of a
Business Information Entity (noting that according to UN/CEFACT ATG 2, 
only BIEs will appear in XML documents), the tag name will be taken from
the "Dictionary Entry Name" for the BIE, so this will take care of what
CCTS says the Content Core Component is required for.

Any thoughts?
tel;work:(703) 902-6923
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
title:Senior Consultant
fn:Joseph M. Chiusano

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