[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: No Subject
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> ------_=_NextPart_001_01C3359E.BB6B257C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <TITLE></TITLE> <META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD> <BODY> <DIV> <P><FONT size=3D2>Hi Monica,</FONT></P> <P><FONT size=3D2>Thanks for joining this discussion.<SPAN=20 class=3D104192213-18062003> I've added 2 comments = inline.</SPAN></FONT></P></DIV> <BLOCKQUOTE cite=3Dmid3EEDC660.F247FEEB@bah.com type=3D"cite"><PRE = wrap=3D"">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). </PRE></BLOCKQUOTE> <DIV>mm1: Properties are like attributes on a object, which can be = restricted by=20 Data Types. For example, properties on Person could be Person ID, First = Name,=20 etc.<BR>From draft CCSD primer on data types: <EM>Note: This is only a = draft in=20 work primer so take that into consideration when reviewing my=20 comments.</EM><SPAN class=3D104192213-18062003><FONT face=3DArial = color=3D#0000ff=20 size=3D2> </FONT></SPAN></DIV> <DIV><SPAN class=3D104192213-18062003></SPAN> </DIV> <DIV><SPAN class=3D104192213-18062003><FONT=20 size=3D2><Diego></FONT></SPAN></DIV> <DIV><SPAN class=3D104192213-18062003><FONT size=3D2>"Can" be restricted = by a=20 datatype? So figure 7.1 is wrong since it does not show that DataType = can be=20 missing and Properties/BCCs can directly be based on a CCT (BTW, = UBL takes=20 this assumption, right?)</FONT></SPAN></DIV> <DIV><SPAN class=3D104192213-18062003><FONT=20 size=3D2></Diego></FONT> </SPAN><BR></DIV> <BLOCKQUOTE> <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 6pt">A Data Type defines = the set of=20 valid values that can be used for a particular Property of a BBIE or=20 BCC.<SPAN> </SPAN>It is defined by specifying restrictions on = the CCT=20 from which the Data Type is derived.<SPAN> </SPAN>Where = necessary, a=20 Data Type restricts the set of valid values allowed by the CCT on = which it is=20 based, by imposing restrictions on the Content Component and/or = Supplementary=20 Component.<O:P></O:P></P></BLOCKQUOTE> <BLOCKQUOTE cite=3Dmid3EEDC660.F247FEEB@bah.com type=3D"cite"><PRE = wrap=3D"">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. </PRE></BLOCKQUOTE> <DIV>mm1: If you look at the reference above, this can be taken a bit = further -=20 a BCC is part of an ACC. <SPAN class=3D104192213-18062003><FONT = face=3DArial=20 color=3D#0000ff size=3D2> </FONT></SPAN></DIV> <DIV><SPAN class=3D104192213-18062003></SPAN> </DIV> <DIV><SPAN class=3D104192213-18062003> <DIV><SPAN class=3D104192213-18062003><FONT=20 size=3D2><Diego></FONT></SPAN></DIV> <DIV><SPAN class=3D104192213-18062003><FONT size=3D2>Then Joe and I got = it wrong. We=20 thought you would be able to define BCCs and add them to registry as = independent=20 parts then compose an ACC</FONT></SPAN></DIV> <DIV><SPAN class=3D104192213-18062003><FONT size=3D2>If that is not = possible, an ACC=20 with its (B)CCs is the smallest part you can store in the registry = at=20 once.</FONT></SPAN></DIV> <DIV><SPAN class=3D104192213-18062003><FONT size=3D2>Actually it makes = sense, if you=20 consider that the specs say that you can only reuse ACC through ASCC.. = no=20 mentioning on reusing BCC.</FONT></SPAN></DIV> <DIV><SPAN class=3D104192213-18062003><FONT=20 size=3D2></Diego></FONT> </SPAN><BR> </SPAN></DIV></DIV> <BLOCKQUOTE> <P class=3DMsoNormal=20 style=3D"MARGIN: 0in 0in 6pt 0.25in; TEXT-INDENT: -0.25in"><!--[if=20 !supportLists]--><SPAN lang=3DEN-GB=20 style=3D"FONT-SIZE: 11.5pt; FONT-FAMILY: Symbol">From CCSD = Primer:<BR>=B7<SPAN=20 style=3D"FONT: 7pt 'Times New Roman'; font-stretch: normal; = font-size-adjust: = none"> </SPAN></SPAN><!= --[endif]--><SPAN=20 lang=3DEN-GB style=3D"FONT-SIZE: 11.5pt; FONT-FAMILY: = TimesNewRoman">Basic Core=20 Components (BCC), that represent simple properties of Object=20 Classes;<O:P></O:P></SPAN><BR></P></BLOCKQUOTE> <BLOCKQUOTE cite=3Dmid3EEDC660.F247FEEB@bah.com type=3D"cite"><PRE = wrap=3D""><JMC> I think we need a clarification on the term "Core Component Property". Can anyone please tell me the difference between a "Core Component" = </PRE></BLOCKQUOTE>mm1:=20 Object Class<BR> <BLOCKQUOTE cite=3Dmid3EEDC660.F247FEEB@bah.com type=3D"cite"><PRE = wrap=3D"">and a "Core Component Property"? </JMC></PRE></BLOCKQUOTE>mm1: Properties of an Object Class<BR> <BLOCKQUOTE cite=3Dmid3EEDC660.F247FEEB@bah.com type=3D"cite"><PRE = wrap=3D"">[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. </PRE></BLOCKQUOTE>mm1: See previous reference.<BR> <BLOCKQUOTE cite=3Dmid3EEDC660.F247FEEB@bah.com type=3D"cite"><PRE = wrap=3D"">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. </PRE></BLOCKQUOTE>mm1: I've had questions re: this for quite some = time,=20 because I think those associations in and of themselves imply some type = of=20 context.<BR>For example, will a Party be associated with an Address or a = Location that MAY map to an address? Does that association imply = context -=20 that<BR>thought keeps lingering in my mind.<BR> <BLOCKQUOTE cite=3Dmid3EEDC660.F247FEEB@bah.com type=3D"cite"><PRE = wrap=3D""><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. </PRE></BLOCKQUOTE>mm1: I believe this implies that an BCC will always = be a=20 part of an ACC.<BR> <BLOCKQUOTE> <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 6pt"><SPAN lang=3DEN-GB=20 style=3D"FONT-SIZE: 11.5pt; FONT-FAMILY: TimesNewRoman">From CCSD = Draft Primer:=20 Each Basic Core Component is of a Core Component Type.=20 <O:P></O:P></SPAN><BR></P></BLOCKQUOTE> <BLOCKQUOTE cite=3Dmid3EEDC660.F247FEEB@bah.com type=3D"cite"><PRE = wrap=3D"">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></PRE></BLOCKQUOTE><BR><BR></BODY></HTML> ------_=_NextPart_001_01C3359E.BB6B257C--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]