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: (Final Set!) CCTS Spec RIM Mappings - [S53] to [S64]


Team,

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

Please pay particular attention to [S58], which is the most complex
requirement we have. Comments are welcome and appreciated.

Thanks,
Joe

[S53] Stored Business Information Entity Properties shall be stored as
part of the stored Aggregate Business Information Entity to which they
belong, i.e. they shall never exist independently of their owning
Aggregate Business Information Entity.

<JMC>
Since we are not storing Properties as entities, this requirement can be
ignored for our purposes.
</JMC>

[S54] Stored Business Information Entity Properties shall be based on a
Core Component Property that is stored as part of the Aggregate Core
Component on which the owning Aggregate Business Information Entity is
based.

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

"Stored Business Information Entities shall be based on a Core Component
that is stored as part of the Aggregate Core Component on which the
owning Aggregate Business Information Entity is based."

Suppose we have an ACC called "AddressDetails" that contains a BCC
called "TelephoneNumber". We then create a BBIE from the BCC, called
"US_TelephoneNumber". This means that the "AddressDetails" ACC is no
longer an ACC - it is now an ABIE (well, another entity is derived from
it and that entity is an ABIE) called "US_AddressDetails". So, an ACC
cannot contain any BBIEs - if it does, it is an ABIE rather than an ACC,
and must be named as such.

Bottom line: I interpret this as mostly informational to implementers,
so that they can include the proper controls/validations in their
implementations.
</JMC>

[S55] Stored Business Information Entity Properties shall be defined as
one of the two recognized types.Basic Business Information Entity
Property or Association Business Information Entity Property. The type
of Business Information Entity Property shall be the same as the type of
its related Core Component Property:

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

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

"Stored Business Information Entities shall be defined as one of the two
recognized types- Basic Business Information Entity or Association
Business Information Entity . The type of Business Information Entity
shall be the same as the type of its related 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"

We are also not planning to represent ASCCs/ASBIEs as entities in the
registry, but rather as Associations. Additionally, this requirement
does not mention Aggregate Business Information Entities, and it should
(i.e. I believe the requirement is incorrect). So this requirement now
becomes:

"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:

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

This is covered by [S47], so we can ignore this requirement for our
purposes.
</JMC>

[S56] Stored Business Information Entity Properties shall include the
following Attributes:

- Qualifier Term
- Cardinality

<JMC>
The Qualifier Term will be an attribute (using a Slot) on BIE's. More
specifically:

- BBIEs will have a Property Term Qualifier Term (ex:
HomeTelephoneNumber, where "Home" is a Property Term Qualifier Term);
- ABIEs will have an Object Class Qualifier Term (ex: ShippingAddress
Details, where "Shipping" is an Object Class Qualifier Term);

Cardinality will be specified as a Slot on the Association that links a
BBIE to an ABIE, and an ABIE to another ABIE.
</JMC>

[S57] Basic Business Information Entity Properties are a particular
category of Business Information Entity Properties. As such, stored
Basic Business Information Entity Properties shall include all
Attributes of stored Business Information Entity Properties.

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

"Basic Business Information Entities are a particular category of
Business Information Entities. As such, stored Basic Business
Information Entities shall include all Attributes of stored Business
Information Entities.

But since we don't store BIEs (rather, we store BBIEs and ABIEs), this
requirement can be ignored for our purposes.
</JMC>

[S58] Stored Basic Business Information Entity Properties shall be
linked to the Data Type that describes the possible values of the Basic
Business Information Entity Property. This Data Type shall either be the
same as the Data Type that is linked to the corresponding Basic Core
Component Property or it shall be a more restricted Data Type (i.e.
additional and/or more restrictive Content Component Restrictions and/or
additional and/or more restrictive Supplementary Component
Restrictions).

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

"Stored Basic Business Information Entities shall be linked to the Data
Type that describes the possible values of the Basic Business
Information Entity. This Data Type shall either be the same as the Data
Type that is linked to the corresponding Basic Core Component or it
shall be a more restricted Data Type (i.e. additional and/or more
restrictive Content Component Restrictions and/or additional and/or more
restrictive Supplementary Component Restrictions)."

For us, this would mean:

- We link a BBIE to its corresponding Data Type through an Association;

- That Data Type MAY be the same as the the Data Type to which the BCC
from which the BBIE is derived is linked;

- Else, it may be a different Data Type that is more "restricted" than
the BCC Data Type;

- If it is a different Data Type, the Supplementary Component
Restriction and Content Component Restriction (which we call "Core
Component Content Restriction") entities must be linked to the BCC Data
Type's Supplementary Component Restriction and Core Component Content
Restriction;

- The BBIE's Supplementary Component Restriction and Core Component
Content Restriction must list for its "Restriction Value" attribute
values a subset of the BCC's Supplementary Component Restriction and
Core Component Content Restriction "Restriction Value" attribute values;
</JMC>

[S59] Association Business Information Entity Properties are a
particular category of Business Information Entity Properties. As such,
stored Association Business Information Entity Properties shall include
all Attributes of stored Business Information Entity Properties.

<JMC>
Since we are not planning to represent ASCCs/ASBIEs as entities in the
registry - but rather as Associations - this requirement can be ignored
for our purposes.
</JMC>

[S60] Stored Association Business Information Entity Properties shall be
linked to the Aggregate Business Information Entity that describes the
structure. This Aggregate Business Information Entity shall be based on
the Aggregate Core Component that describes the structure of the
corresponding Association Core Component Property.

<JMC>
Since we are not planning to represent ASBIEs as entities in the
registry - but rather as Associations - this requirement can be ignored
for our purposes.
</JMC>

[S61] Stored Business Information Entities are a particular category of
Business Information Entities. As such, stored Basic Business
Information Entities shall include all Attributes of stored Business
Information Entities.

<JMC>
This is covered by our interpretation of [S57]. This requirement can be
ignored for our purposes.
</JMC>

[S62] Stored Basic Business Information Entities shall represent a Basic
Business Information Entity Property of a particular Aggregate Business
Information Entity.

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

"A Basic Business Information Entity shall be contained within an
Aggregate Business Information Entity."

We will represent the link between BBIEs and ABIEs through Associations.
</JMC>

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

<JMC>
Since we are not planning to represent ASBIEs as entities in the
registry - but rather as Associations - this requirement can be ignored
for our purposes.
</JMC>

[S64] Stored Association Business Information Entities shall represent
an Association Business Information Entity Property of a particular
Aggregate Business Information Entity.

<JMC>
Since we are not planning to represent ASBIEs as entities in the
registry - but rather as Associations - this requirement can be ignored
for our purposes.
</JMC>

THE END!!!
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]