No Subject

A Data Type defines the set of valid values that can be used for a =
particular Property of a BBIE or BCC.  It is defined by specifying =
restrictions on the CCT from which the Data Type is derived.  Where =
necessary, a Data Type restricts the set of valid values allowed by the =
CCT on which it is based, by imposing restrictions on the Content =
Component and/or Supplementary Component.

p.76:



7.1.3 Stored Core Component Properties



[S8]

Stored Core Component Properties shall be stored as part of the stored

Aggregate Core Component to which they belong, i.e. they shall never

exist independently of their owning Aggregate Core Component.

 =20

mm1: If you look at the reference above, this can be taken a bit further =
- a BCC is part of an ACC. =20
=20
<Diego>
Then Joe and I got it wrong. We thought you would be able to define BCCs =
and add them to registry as independent parts then compose an ACC
If that is not possible, an ACC with its (B)CCs is the smallest part you =
can store in the registry at once.
Actually it makes sense, if you consider that the specs say that you can =
only reuse ACC through ASCC.. no mentioning on reusing BCC.
</Diego>=20
=20

<!--[if !supportLists]-->From CCSD Primer:
=B7        <!--[endif]-->Basic Core Components (BCC), that represent =
simple properties of Object Classes;


<JMC>

I think we need a clarification on the term "Core Component Property".

Can anyone please tell me the difference between a "Core Component"=20

mm1: Object Class


and

a "Core Component Property"?

</JMC>

mm1: Properties of an Object Class


[S9]

Stored Core Component Properties shall be defined as one of the two

recognized types.Basic Core Component Property or Association Core

Component Property.



<JMC>

We are questioning the need to store Association Core Components

(ASCC's), so this requirement is pending clarification from the CCTS

team.

</JMC>



[S10]

Stored Core Component Properties shall include the following Attributes:

- Property Term

- Cardinality



p.76:



7.1.4 Stored Basic Core Component Properties



[S11]

Basic Core Component Properties are a particular category of Core

Component Properties. As such, stored Basic Core Component Properties

shall include all Attributes of stored Core Component Properties.



[S12]

Stored Basic Core Component Properties shall be linked to the Data Type

that describes the possible values of the Basic Core Component Property.

 =20

mm1: See previous reference.


7.1.5 Stored Association Core Component Properties



[S13]

Association Core Component Properties are a particular category of Core

Component Properties. As such, stored Association Core Component

Properties shall include all Attributes of stored Core Component

Properties.



<JMC>

See note for [S9].

</JMC>



[S14]

Stored Association Core Component Properties shall be linked to the

Aggregate Core Component that describes the structure of the Association

Core Component Property.

 =20

mm1: I've had questions re: this for quite some time, because I think =
those associations in and of themselves imply some type of context.
For example, will a Party be associated with an Address or a Location =
that MAY map to an address?  Does that association imply context - that
thought keeps lingering in my mind.


<JMC>

See note for [S9].

</JMC>



7.1.6 Stored Basic Core Components



[S15]

Basic Core Components are a particular category of Core Components. As

such, stored Basic Core Components shall include all Attributes of

stored Core Components.



<JMC>

We may consider "stored Core Components" to mean "stored Basic Core

Components" by default.

</JMC>



[S16]

Stored Basic Core Components shall represent a Basic Core Component

Property of a particular Aggregate Core Component.

 =20

mm1: I believe this implies that an BCC will always be a part of an ACC.