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: Re: [regrep-cc-review] CCTS Spec RIM Mappings (7.1.3-7.1.7)


See inline.
Monica

>The biggest question I have is the meaning of a "Core Component
>Property" vs. a "Core Component". We are also questioning the need to
>stored Association Core Components (ASCC's), so some requirements cannot
>be handled until that issue is cleared with the CCTS team (they are
>marked accordingly).
>  
>
mm1: Properties are like attributes on a object, which can be restricted 
by Data Types. For example, properties on Person could be Person ID, 
First Name, etc.
 From draft CCSD primer on data types: /Note: This is only a draft in 
work primer so take that into consideration when reviewing my comments./

    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.
>  
>
mm1: If you look at the reference above, this can be taken a bit further 
- a BCC is part of an ACC.

     From CCSD Primer:
            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" 
>
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.
>  
>
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.
>  
>
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.
>  
>
mm1: I believe this implies that an BCC will always be a part of an ACC.

     From CCSD Draft Primer: Each Basic Core Component is of a Core
    Component Type.

>7.1.7 Stored Association Core Components
>
>[S17]
>Association Core Components are a particular category of Core
>Components. As such, stored Association Core Components shall include
>all Attributes of stored Core Components.
>
><JMC>
>See note for [S9].
></JMC>
>
>[S18]
>Stored Association Core Components shall represent an Association Core
>Component Property of a particular Aggregate Core Component.
>
><JMC>
>See note for [S9].
></JMC>
>




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