Template:— referencing_resource_as_realized (ref_res_as_rlzd)
Capability:representing_resource_as_realized
[warning:]The use of this template is deprecated. (2007-10-19) 		Date: 2008/01/14 08:43:55
Revision: 1.11
CoverContentsDescriptionModel diags.Input params.Ref. params.Instantiation pathInstance diags.CharacterizationsIssuesin situ

Issue raised against: referencing_resource_as_realized

GENERAL issues

Open issue Issue: GYL-1 by Leif Gyllstrom (2007-05-04) major_technical issue
Resolution: Accept. Status: open

The introduction says: "used to represent tokens of resources that are actually used or consumed or that are intended for use or consumption." The intention of the Resorce_as_realized module was to RECORD what resources WAS used or consumed during an Activity_actual. A Resource_as_realized is never planned or intended. Intended/planned use/consuption shall be described using Required_resource.

Open issue Issue: GYL-2 by Leif Gyllstrom (2007-05-04) major_technical issue
Resolution: Accept. Status: open

We should avoid the attribute quantity. Use Resource_property_assignment instead. This would allow for more than one quantity to be recorded, e.g. qualifications such as preliminary or final consumption.

Open issue Issue: GYL-3 by Leif Gyllstrom (2007-05-04) major_technical issue
Resolution: Accept. Status: open

I think that we need to be explicit about that reference parameters within reference templates shall be private to the template. If the entiry needs further characterization, that should be done using its representing counterpart.

GENERAL issues

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

I'm not sure that a referencing_resource_as_realized template is needed. It would be enough to have either an assigning or representing template. I would prefer an assigning_resource_as_realized.
Comment: (Rob Bodington 07-10-19)
Created assigning_realized_resource and deprecated referencing_resource_as_realized