Reference Data

["Barker, Sean (UK)" <sean.barker@baesystems.com>]

Folks

In support of DEX 3, I have started a list of reference data which is relevant to Task_specification. The list covers all the assignments to or from task entities except Language, String and Classification itself, and those assignments to Activity_method and other Activity* supertypes not defined in Ap239_task_specification_resourced.

It does not include reference data which does not apply to an assignment, such as the list of lifecycle states.

In the Task_assignment and Task_method_assignment, items to which the same reference data will apply have been abbreviated to <*list>

I have started the process of filling this in on the basis of the Representing_task capability. However, I need to know what other classifications will be required. This particularly affects members of DEX team 3, but I expect it will also impact DEX team 4. Note that there are some 130 odd opportunities to define reference data. That is, there is over 10 times as many semantic modifiers as there are entities in the schema.

Where more than one reference data value is required, duplicate the line. Where a line ends up with no reference data, it will be explicitly excluded as valid for a DEX.
It would be useful to have responses by the 1st July, in order to consolidate for any reference data discussions at the Bath SC4 meeting, and to develop a suitable class hierarchy.

Sean Barker
ATC Filton
0117 302 8184


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

RefData1.xls