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 - [S44] to [S52]


Team,

Picking up where we left off on our RIM mappings:

Here is the next set of CCTS requirements for us to cover - please see
my comments marked with <JMC>. 

Comments are welcome and appreciated.

Thanks,
Joe

[S44] Business Information Entities are a particular category of
Registry Classes. As such, all stored Business Information Entities
shall include the following Attributes:

- Unique Identifier
- Version
- Dictionary Entry Name
- Definition
- Usage Rule

<JMC>
BIEs will be represented in the registry as ExtrinsicObjects. For RIM
mappings of the above attributes, reference requirement [S1].
</JMC>

[S45] Stored Business Information Entities shall be based on a stored
Business Context.

<JMC>
BIEs are created by taking existing Core Components and classifying them
according to one of the 8 Context Categories.
</JMC>

[S46] Stored Business Information Entities shall be based on a stored
Aggregate Core Component, Basic Core Component or Association Core
Component. They shall never be based on a Core Component Type.

<JMC>
Since we are not planning to represent ASCCs as entities in the registry
(but rather as Associations), this requirement is a bit different for
us. It would be:

"Stored Business Information Entities shall be based on a stored
Aggregate Core Component, or Basic Core Component. They shall never be
based on a Core Component Type."

This is handled by the fact that a BBIE is created using a Basic Core
Component as its basis, and an ABIE is created using an Aggregate Core
Component as its basis. This means that a CCT will never be used as the
basic for a BIE.
</JMC>

[S47] Stored Business Information Entities shall be defined as one of
the three recognized types: Basic Business Information Entity,
Association Business Information Entity or Aggregate Business
Information Entity. The type of Business Information Entity shall be the
same as the type of its related Core Component:

 An Aggregate Business Information Entity is based on an Aggregate Core
Component.
 A Basic Business Information Entity is based on a Basic Core
Component.
 An Association Business Information Entity is based on an Association
Core Component.

<JMC>
Since we are not planning to represent ASCCs as entities in the registry
(but rather as Associations), this requirement is a bit different for
us. It would be:

Stored Business Information Entities shall be defined as one of the two
recognized types: Basic Business Information Entity or Aggregate
Business Information Entity. The type of Business Information Entity
shall be the same as the type of its related Core Component:

 An Aggregate Business Information Entity is based on an Aggregate Core
Component.
 A Basic Business Information Entity is based on a Basic Core
Component.

This is covered in our handling for [S46] above.
</JMC>

[S48] Stored Business Information Entities shall include the following
attributes:

 Constraint Language
 Business Term

<JMC>
Constraint Language: Part of Assembly mechanism, which is out of our
scope. This attribute will be ignored in our initiative.

Business Term: Use Slot mechanism
</JMC>

[S49] Aggregate Business Information Entities are a particular category
of Business Information Entities. As such, stored Aggregate Business
Information Entities shall include all Attributes of stored Business
Information Entities.

<JMC>
Covered by [S44].
</JMC>

[S50] Stored Aggregate Business Information Entities shall contain one
or more Business Information Entity Properties.

<JMC>
Since we are not storing Properties as entities, this requirement would
read:

"Stored Aggregate Business Information Entities shall contain one or
more Business Information Entities."

We will represent the link between ABIEs and the BBIEs that they contain
using Associations.
</JMC>

[S51] Stored Aggregate Business Information Entities can be referenced
by one or more Association Business Information Entity Properties of
other Aggregate Business Information Entities.

<JMC>
Since we are not storing Properties as entities, this requirement would
read:

"Stored Aggregate Business Information Entities can be referenced by one
or more Association Business Information Entities of other Aggregate
Business Information Entities."

Furthermore, we are not representing ASBIEs as entities. So now this
requirement becomes:

"Stored Aggregate Business Information Entities can be referenced by
other Aggregate Business Information Entities."

That is, an ABIE can contain another ABIE. We will represent the link
between ABIEs and the ABIEs that they contain using Associations.
</JMC>

[S52] Stored Aggregate Business Information Entities shall include the
following Attribute:

 Qualifier Term (mandatory): Qualifies the Object Class Term of the
associated Aggregate Core Component.

<JMC>
We will represent the Object Class Qualifier Term as a Slot for ABIE.
</JMC>
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


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