Re: [regrep-cc-review] Re: Mapping Patterns

["Chiusano Joseph" <chiusano_joseph@bah.com>]

<Quote>
mm1: Note, there has been discussion in the CCSD team that a controlled 
vocabulary may be required when it come to context.  See this 
***draft*** extract from the primer:
</Quote>

Just to clarify Monica's excellent point here: The controlled vocabulary
would be used in Data Element names - specifically the Qualifier
portions. In terms of ISO/IEC 11179, there are the following Data
Element name parts:

- Object Class
- Property Term
- Representation Term
- Object Class Qualifier
- Property Term Qualifier

The final 2 parts are what Monica is referring to. For example, one may
have the following 11179-compliant Data Element name (please don't
analyze the name itself too finely - it's just to get an idea across):

EmployeeTelephoneNumber 

- Object Class: Employee
- Property Term: Telephone
- Representation Term: Number

If qualifiers are required to make the Data Element names more specific
and distinct, one could add 2 qualifiers to the name above:

ContractorEmployeeHomeTelephoneNumber 

- Object Class Qualifier: Contractor (vs. Permanent)
- Object Class: Employee
- Property Term Qualifier: Home (vs. Work)
- Property Term: Telephone
- Representation Term: Number

So in the e-mail below, when it says "A qualifier should be 
used consistently across the library of core components.  The qualifier 
context category, semantic, and control vocabulary source should be 
noted.", that is more of a usage note. Our job is to ensure that the
Registry can store and maintain the above Data Element name parts, as
per the CCTS spec.

Joe

"Monica J. Martin" wrote:
> 
> >
> >
> ><Quote4>
> >[3] Not present in my implementation but I see the need for it now.
> >For instance, to store localized enumeration/regexps. BIEs have
> >Contexts (Classifications) that could define the region where they
> >should be used.. Same CC, different BIE for different region,
> >different DataType, but still same CCT.
> ></Quote4>
> >
> >Joe: Glad you brought this up - the issue of whether or not Data Types should
> >be stored as Registered Objects or be represented as metadata attributes
> >for Registered Objects will be a big one for us.
> >
> mm1: I would ask the OAG-CC group about their work in this arena as they
> have been modeling the XML schema of their CC.  See Garret Minakawa,
> garret.minakawa@oracle.com.
> 
> >
> ><Quote5>
> >And what about Contexts? Do they need a pattern too? I've used RIM's
> >Classification mechanism for Contexts so that each Context Category
> >has it's own ClassificationScheme.
> ></Quote5>
> >
> mm1: Note, there has been discussion in the CCSD team that a controlled
> vocabulary may be required when it come to context.  See this
> ***draft*** extract from the primer:
> 
> <<4.5.1Use of Context in Core Component Normalization
> 
> Qualifiers that are used in the naming of Business Information Entities
> associate a context specific semantic with the Core Component.   These
> qualifiers make up a controlled vocabulary that can have unique semantic
> within a specific context.  For instance, "reserved" used as a qualifier
> has an order process context semantic, as well as a travel industry
> context semantic. Rigor in the construction of the controlled
> vocabularies for qualifiers is as important as rigor in the construction
> of the controlled vocabulary for core components.  A qualifier should be
> used consistently across the library of core components.  The qualifier
> context category, semantic, and control vocabulary source should be
> noted.  >>
> 
> Thanks.
> Monica
begin:vcard 
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard