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: ASCC Name (Was Re: [Fwd: [regrep-cc-review] Core Components Issue: Representation of Aggregate Core Components])


Revisiting the following comment below (by me) regarding ASCCs (citing
CCTS p.12 example):

<Quote>
- Person. Residence. Address - A stored ASCC, that can be represented in
the registry as an Association. The Association would carry the ASCC
name in its attributes (which would be Slots).
</Quote>

My question is: Should the ASCC Association carry the name in its
attibutes (as Slots)? Or, should the name of the ASCC be "constructed"
by the Assembly mechanism (not yet existing) that creates an XML
serialization from the entities?

Seems that there are advantages and disadvantages to each approach. If
we carry the ASCC name in the Association, any changes to the entity
names (ex: change "Person. Details" ACC to "Individual. Details") would
have to be reflected also in the Association Slots (potential
disadvantage: extra maintenance, prone to error). If we don't, this
additional maintenance would not be necessary, and the Assembly
mechanism would be required to construct the name as defined in the CCTS
spec.

Thoughts?

Joe

Chiusano Joseph wrote:
> 
> Yes - that makes sense.
> 
> Using parts of the CCTS p.12 example, I'm seeing this as follows:
> 
> - Person. Details: A stored ACC
> 
> - Address. Details: A stored ACC
> 
> - ResidenceAddress. Details: A stored [name pending - is this an ABIE,
> another ACC, or some other type of entity?]
> 
> - Person. Residence. Address - A stored ASCC, that can be represented in
> the registry as an Association. The Association would carry the ASCC
> name in its attributes (which would be Slots).
> 
> And if there is a need to create another ASCC using "Address. Details"
> "joined" to a different ACC (which there most likely would be), this
> could simply be another Association.
> 
> Joe
> 
> "CRAWFORD, Mark" wrote:
> >
> > I wrote -
> >
> > > I am not sure I agree with the notion that an ASCC can stand
> > > on its own in the registry.  I believe it must always be
> > > associated with at least one ACC.
> >
> > One slight correction to the following - I don't mean to imply that the ASCC should not be a separate entry in the registry, only that it must have a direct correlation with its associated ACC that describes its properties.
> >
> > Mark
> >
> >
> > You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/regrep-cc-review/members/leave_workgroup.php
> 
>   ------------------------------------------------------------------------
> You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/regrep-cc-review/members/leave_workgroup.php
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]