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 Requirement [S4] - p.76


Ah - good point. I should have stated my assumption, which is that
whenever I refer to a "Core Component" I am referring to a Basic Core
Component (BCC). In light of that, does the information below regarding
[S4] make sense?

Sorry for the confusion.

Joe

Diego Ballvé wrote:
> 
> Joe,
> 
> Maybe you've something else in mind but I couldn't follow it.
> IMO you should take Core Components (and its attributes) as
> something abstract, thus you can't simply store a Core Component.
> Instead, you have to decide whether to store a ACC or a BCC.
> Still you can see them both as Core Components.
> 
> Diego
> 
> > -----Original Message-----
> > From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
> > Sent: Monday, June 16, 2003 3:02 AM
> > To: CCRev
> > Subject: [regrep-cc-review] CCTS Requirement [S4] - p.76
> >
> >
> > CCTS Requirement [S4] states:
> >
> > "Aggregate Core Components are a particular category of Core
> > Components.
> > As such, stored Aggregate Core Components shall include all Attributes
> > of Stored Core Components."
> >
> > I know we visited this one earlier this week, and I mentioned an
> > "inheritance" mechanism. I thought my impression was
> > incorrect, but now
> > am revisiting it. What I believe this requirement is saying
> > is that all
> > Core Component attributes listed in [S1] (p.75) apply not just to Core
> > Components, but to Aggregate Core Components as well. Does anyone see
> > this differently?
> >
> > If not: I see the possibility of us having 2 Object Types in the
> > registry (CC and ACC) that both have the exact same set of
> > attributes -
> > except (a) The different ObjectType values, and (b) ACC will have
> > associations to its Core Components (i.e. its Core Component
> > Properties).
> >
> > Having said that: Couldn't we define a "Core Component"
> > ObjectType with
> > the attributes specified in [S1], and an "Aggregate Core Component"
> > Object Type that inherits from the "Core Component"
> > ObjectType? Perhaps
> > we can add a new association "InheritsFrom".
> >
> > Thoughts?
> >
> > Joe
> >
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]