Capability (C095):— assigning_descriptor Date: 2007/06/22 12:22:09
Revision: 1.10
CoverContentsIntro.Overview Info. modelTemplatesCapabilities.Ref. dataIssues

Issue raised against: assigning_descriptor

GENERAL issues

Open issue Issue: RBN-5 by Rob Bodington (06-01-11) minor_technical issue
Resolution: Accept. Status: open

The express-g diagram should indicate that the text of the description should be held in the document description attribute.

OTHER issues

Closed issue Issue: TJT-1 by Tim Turner (04-20-06) minor_technical issue
Resolution: Accept. Status: closed

Add an optional input parameter to allow for sub-classes of 'descriptor' to be passed into the template. The default value of the parameter should be 'descriptor'.
Comment: (Tim Turner 20 april 2006 17:51)
From: Tim Turner [mailto:tjt@lsc.co.uk] Sent: den 20 april 2006 17:51 To: 'plcs-dex@lists.oasis-open.org' Subject: [plcs-dex] Assigning_descriptor I would like to be able to specialize the descriptor classification for use with assigning_descriptor. However, the template fixes the class_name assigned to the document to be 'descriptor', rather than making this the type associated with an optional input parameter. With an optional parameter of type class 'descriptor', we would be able to characterize the descriptor into appropriate sub-classifications (mentioned in the capability), such as notes, remarks, comments etc.,. Any application will still know that any of the above are of type 'descriptor' through the class hierarchy. Would there be any objection to making this minor modification to the template definition, before I submit an unworthy issue? Kind regards, Tim
Comment: (Peter Bergström [mailto:peter.bergstrom@eurostep.com] 20 April 2006 17:46)
-----Original Message----- From: Peter Bergström [mailto:peter.bergstrom@eurostep.com] Sent: 20 April 2006 17:46 To: 'Tim Turner'; plcs-dex@lists.oasis-open.org Subject: RE: [plcs-dex] Assigning_descriptor I think this is fine, especially if you supply a default value ‘descriptor’ for the new parameter. Then nothing will change for existing usages… Peter --------------------------------------------------------------------------------
Comment: (Rob Bodington [mailto:rob.bodington@eurostep.com] 20 April 2006 12:59)
From: Rob Bodington [mailto:rob.bodington@eurostep.com] Sent: 20 April 2006 12:59 To: peter.bergstrom@eurostep.com; 'Tim Turner'; plcs-dex@lists.oasis-open.org Subject: RE: [plcs-dex] Assigning_descriptor I agree with Peter – it should be fine so long as you add the default. Regards Rob
Comment: (Leif Gyllstrom 2007-05-02)
Defining the type of descriptor being assigned is done by classification of Document_assignment. There is no need for specializing the classification of Document as well. Therefore is the issue rejected.

Closed issue Issue: GYL-1 by Leif Gyllstrom (05-10-04) minor_technical issue
Resolution: Accept. Status: closed

Add a remark that states why we are using Document to realize this capability, and that we will raise a SEDS against AP239 for the development of a new module.
Comment: (Leif Gyllstrom 05-10-06)
Note added to the introduction.

Closed issue Issue: GYL-2 by Leif Gyllstrom (05-10-04) minor_technical issue
Resolution: Accept. Status: closed

The ExpressG diadram in the Information Model Overview section shall contain default attribute values.
Comment: (Leif Gyllstrom 05-10-04)
Added

Closed issue Issue: GYL-3 by Leif Gyllstrom (05-10-04) minor_technical issue
Resolution: Accept. Status: closed

Add an example to the descriptive text next to the template for assigning_reference_data assigned to Document_assignment (e.g. decription, note). Figures 1 and 5.
Comment: (Leif Gyllstrom 05-10-04)
Text added.

Closed issue Issue: GYL-4 by Leif Gyllstrom (05-10-04) minor_technical issue
Resolution: Accept. Status: closed

Remove the usage of Document_version to contain the textual representation. Use the Document.description attribute. Make sure to delete Document_version from the usage section.
Comment: (Leif Gyllstrom 05-10-04)
Changed.

Closed issue Issue: GYL-5 by Leif Gyllstrom (05-10-04) minor_technical issue
Resolution: Accept. Status: closed

Add a note under a additional usage section that states that decriptions, remarks, notes etc shall not be represented as String properties.
Comment: (Leif Gyllstrom 05-10-06)
Section added.

Closed issue Issue: GYL-6 by Leif Gyllstrom (05-10-04) minor_technical issue
Resolution: Accept. Status: closed

Change Capability number to #95.
Comment: (Leif Gyllstrom 05-10-04)
Done

Closed issue Issue: GYL-7 by Leif Gyllstrom (05-10-03) minor_technical issue
Resolution: Accept. Status: closed

Add dependent and related capabilities.
Comment: (Leif Gyllstrom 05-10-06)
Done.

Closed issue Issue: GYL-7 by Leif Gyllstrom (05-10-20) minor_technical issue
Resolution: Accept. Status: closed

Product_category and Product_category_assignment are missing in the Figures 2, 3, 4 and 7.
Comment: (Leif Gyllstrom 05-11-06)
Product_category isn't required. This is a missunderstanding. Se Issue RBN-1 below.

Closed issue Issue: GYL-7 by Leif Gyllstrom (05-10-20) minor_technical issue
Resolution: Accept. Status: closed

A "populating arrow" is missing in Figure 5.
Comment: (Leif Gyllstrom 05-11-06)
Added.

Closed issue Issue: RBN-1 by Rob Bodington (05-11-02) minor_technical issue
Resolution: Accept. Status: closed

There is no need to include the Product_category and assignment - it serves no purpose and is not mandated by any rule in the EXPRESS. The only place where Product_category is mandated is in Part (unfortunately).
Comment: (Leif Gyllstrom 05-11-06)
OK

Closed issue Issue: RBN-2 by Rob Bodington (05-11-02) minor_technical issue
Resolution: Accept. Status: closed

There are no reference parameters in the template. There should be a reference parameter against: Document and Document_assignment. Otherwise you can not characterize the document with data time etc.
Comment: (Leif Gyllstrom 05-11-06)
Added.

Closed issue Issue: RBN-3 by Rob Bodington (05-11-02) minor_technical issue
Resolution: Accept. Status: closed

Is there a requirement to be able to represent descriptions in multiple languages? If so the entities in the module "Multi linguism" should be used.
Comment: (Leif Gyllstrom 05-11-06)
An issue against all capabilities, and not explicitly assigning_descriptor.

Closed issue Issue: RBN-4 by Rob Bodington (05-11-02) minor_technical issue
Resolution: Accept. Status: closed

In the template, the parameter that carries 'item' to which the descriptor is attached should be named 'is_assigned_to' to make it easy to understand that it is the target of the attribute Document_assignment.is_assigned_to
Comment: (Leif Gyllstrom 05-11-06)
Corrected.