[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
-----Original Message----- From: Rob Bodington [mailto:rob.bodington@eurostep.com] Sent: 29 July 2004 08:14 To: plcs-dex@lists.oasis-open.org Subject: [plcs-dex] Identification of properties Hi I was wondering whether we should use identification_assignment to identify properties. The justification being: 1) We have tried to use identification_assignment rather than id attributes consistently throughout. 2) We use identification_assignment because that allows us to have multiple identifiers on things. Question - does it makes sense to have multiple identifiers on properties? The reason for not using identification_assignment is that the PDM schema does not. Is there really a business requirement to allow multiple identifiers on properties? Regards Rob ------------------------------------------- Rob Bodington Eurostep Limited Web Page: <http://www.eurostep.com> http://www.eurostep.com <http://www.share-a-space.com> http://www.share-a-space.com Email: Rob.Bodington@eurostep.com Phone: +44 (0)1454 270030 Mobile: +44 (0)7796 176 401 ------=_NextPart_000_0182_01C4754C.03A3B080 Content-Type: text/html; charset="us-ascii" 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=3Dus-ascii"> <TITLE>Message</TITLE> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR> <STYLE>@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt = 72.0pt 90.0pt; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } A:link { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline } A:visited { COLOR: purple; TEXT-DECORATION: underline } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline } P { FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: = "Times New Roman" } SPAN.EmailStyle17 { FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; = FONT-FAMILY: Arial; TEXT-DECORATION: none } DIV.Section1 { page: Section1 } OL { MARGIN-BOTTOM: 0cm } UL { MARGIN-BOTTOM: 0cm } </STYLE> </HEAD> <BODY lang=3DEN-GB vLink=3Dpurple link=3Dblue> <DIV><SPAN class=3D862455407-29072004><FONT face=3DArial color=3D#0000ff = size=3D2>Hi=20 Rob,</FONT></SPAN></DIV> <DIV><SPAN class=3D862455407-29072004><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D862455407-29072004><FONT face=3DArial color=3D#0000ff = size=3D2>From a=20 systems integrator's point of view, I've never encountered the need to = do this.=20 Usually, the name of the property in context of the=20 part/document/requirement/etc. it describes is enough to identify it. I = would be=20 relucant to force identification of properties when there will be no = source data=20 available to populate the identifier when you export = data.</FONT></SPAN></DIV> <DIV><SPAN class=3D862455407-29072004><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D862455407-29072004><FONT face=3DArial color=3D#0000ff = size=3D2>There=20 obviously is a need to identify the property class, but this will be = taken care=20 of with external_class.</FONT></SPAN></DIV> <DIV><SPAN class=3D862455407-29072004><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D862455407-29072004><FONT face=3DArial color=3D#0000ff = size=3D2>Cheers</FONT></SPAN></DIV> <DIV><SPAN class=3D862455407-29072004><FONT face=3DArial color=3D#0000ff = size=3D2>--</FONT></SPAN></DIV> <DIV><SPAN class=3D862455407-29072004><FONT face=3DArial color=3D#0000ff = size=3D2>Ian</FONT></SPAN></DIV> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"> <DIV></DIV> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr = align=3Dleft><FONT=20 face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> Rob = Bodington=20 [mailto:rob.bodington@eurostep.com] <BR><B>Sent:</B> 29 July 2004=20 08:14<BR><B>To:</B> plcs-dex@lists.oasis-open.org<BR><B>Subject:</B>=20 [plcs-dex] Identification of properties<BR><BR></FONT></DIV> <DIV class=3DSection1> <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20 style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">Hi</SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20 style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">I was wondering whether = we should=20 use identification_assignment to identify = properties.</SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20 style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial"></SPAN></FONT> </P> <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20 style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">The justification=20 being:</SPAN></FONT></P> <P class=3DMsoNormal style=3D"MARGIN-LEFT: 36pt; TEXT-INDENT: = -18pt"><FONT=20 face=3DArial size=3D1><SPAN style=3D"FONT-SIZE: 9pt; FONT-FAMILY: = Arial">1)<FONT=20 face=3D"Times New Roman" size=3D1><SPAN=20 style=3D"FONT: 7pt 'Times New = Roman'"> =20 </SPAN></FONT></SPAN></FONT><FONT face=3DArial size=3D1><SPAN=20 style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">We have tried to use=20 identification_assignment rather than id attributes consistently=20 throughout.</SPAN></FONT></P> <P class=3DMsoNormal style=3D"MARGIN-LEFT: 36pt; TEXT-INDENT: = -18pt"><FONT=20 face=3DArial size=3D1><SPAN style=3D"FONT-SIZE: 9pt; FONT-FAMILY: = Arial">2)<FONT=20 face=3D"Times New Roman" size=3D1><SPAN=20 style=3D"FONT: 7pt 'Times New = Roman'"> =20 </SPAN></FONT></SPAN></FONT><FONT face=3DArial size=3D1><SPAN=20 style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">We use = identification_assignment=20 because that allows us to have multiple identifiers on things. = Question – does=20 it makes sense to have multiple identifiers on = properties?</SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20 style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial"></SPAN></FONT> </P> <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20 style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial"></SPAN></FONT> </P> <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20 style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">The reason for not using=20 identification_assignment is that the PDM schema does not. = </SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN=20 style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial">Is there really a = business=20 requirement to allow multiple identifiers on = properties?</SPAN></FONT></P> <P><FONT face=3DArial size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: = Arial">Regards<BR>Rob</SPAN></FONT></P> <P><FONT face=3DArial size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: = Arial">------------------------------------------- <BR><= /SPAN></FONT><FONT=20 face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: = Arial">Rob=20 Bodington</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><BR>Eurostep = Limited<BR>Web Page:=20 </SPAN></FONT><A href=3D"http://www.eurostep.com"><FONT face=3DArial = size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: = Arial">http://www.eurostep.com</SPAN></FONT></A><FONT=20 face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: = Arial">=20 </SPAN></FONT><A href=3D"http://www.share-a-space.com"><FONT = face=3DArial=20 size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: = Arial">http://www.share-a-space.com</SPAN></FONT></A><BR><FONT=20 face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: = Arial">Email:=20 Rob.Bodington@eurostep.com<BR>Phone: +44 (0)1454 = 270030<BR></SPAN></FONT><FONT=20 face=3DArial size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: = Arial">Mobile</SPAN></FONT><FONT=20 face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: = Arial">: +44=20 (0)7796 176 401</SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20 style=3D"FONT-SIZE: = 12pt"></SPAN></FONT> </P></DIV></BLOCKQUOTE></BODY></HTML> ------=_NextPart_000_0182_01C4754C.03A3B080--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]