RE: [plcs-dex] Representing_parts C002 Issue RBN-15

I agree with Tim

I think that it is critical that all issues that we have with existing capabilities are recorded as issues in the issue logs (issues.xml) and that the resolution of those issues is also recorded there.

That stops us going around in circles.

Regards
Rob

-----Original Message-----
From: Tim Turner [mailto:tjt@lsc.co.uk]
Sent: 16 August 2005 18:08
To: 'Gyllström Leif'; Tim Turner; DEXS-PLCS-OASIS (E-mail)
Subject: RE: [plcs-dex] Representing_parts C002 Issue RBN-15

No you didn't miss anything Leif,

I'm just going through the issues that have arisen & getting these decisions explicitly documented so that we & others can trace the impacts.

Some issues impact capabilities across the board & include editors who may not have kept up-to-date with all minutes of all meetings & decisions taken at different times.

In my mind this type of communication is crucial in this project & was one of the reasons we decided to open up our discussions to the Dex exploder.

kind regards,

Tim

-----Original Message-----
From: Gyllström Leif [mailto:leif.gyllstrom@aerotechtelub.se]
Sent: 16 August 2005 12:22
To: Tim Turner; DEXS-PLCS-OASIS (E-mail)
Subject: SV: [plcs-dex] Representing_parts C002 Issue RBN-15

All

I thought that we once and for all decided that ALL names should be assigned using Identification_assignment.

Are we going round in circles, or did I miss anything during my vacation ?

Leif

-----Ursprungligt meddelande-----
Från: Tim Turner [mailto:tjt@lsc.co.uk]
Skickat: den 11 augusti 2005 21:37
Till: DEXS-PLCS-OASIS (E-mail)
Ämne: [plcs-dex] Representing_parts C002 Issue RBN-15

In the interest of visibility My response & comments to the issue are provided below;

Issue: RBN-15 by Rob Bodington (05-07-27) minor_technical issue

Should assigning_identification be used to assign the name to a part?

TJT Response: just as an identifier may change over time, so might the name.

The name can be specified through C001 - assigning_identification where the identification_assignment.name carries the product name, and the corresponding external_class_library.class_name should be set to "Name_identification".

Questions for consistency purposes:

1. Is the Organization specifying the name required to be identified (according to current C001 template, the Organization assigning the name is also required to be specified)?

2. Should ALL other types of products in PLCS (i.e. attachment_slot, breakdown, breakdown_element, document, interface_connector, interface_specification, part, product_as_individual, requirement) also conform to this rule regarding names?

3. Any feedback?

regards,
Tim

*************************************************************************
*
* Mr. Timothy J. Turner BSC(Hons) MSc, MBCS
* Executive Consultant, Enterprise Integration Technologies
* LSC Group, Lincoln House, Wellington Crescent, Fradley Park, LICHFIELD, Staffordshire WS13 8RZ, ENGLAND
* UK Switchboard: +44-1543 446800 Fax: +44-1543 446900
* US Direct telephone: +1-803-327 2829 (Rock Hill)
* Mobile (US) telephone: +1-843-4759179
* Mobile (UK) telephone: +44-7885-393225
* e-mail: tjt@lsc.co.uk <mailto:tjt@lsc.co.uk> Internet: <http://www.lsc.co.uk/>
*
*************************************************************************

DISCLAIMER: ***SECURITY LABEL: NOT PROTECTIVELY MARKED*** The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This e-mail originates from LSC Group. Registered in England & Wales No 2275471 Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1 4SG

DISCLAIMER: ***SECURITY LABEL: NOT PROTECTIVELY MARKED*** The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This e-mail originates from LSC Group. Registered in England & Wales No 2275471 Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1 4SG

plcs-dex message