#25 owl classes for id codes should be consistently named

[Mike Ward]

Every SysML block that can be assigned an identifier should have a corresponding owl class that is a sub-class of "Identifier" and that can be used to classify the relevant Identifier and the name of that class should be derived directly from the name of the original block. For example GlobalLocationRepresentation has an attribute called "id" (inherited from LocationRepresentation) which allows for the assignment of one or many Identifiers. Each Identifier can in turn be assigned a Classification that may be an Owl class (or some other type of class). If an Owl class is to be used, it should be called "Global_location_representation_identification_code" (or similar - the "identification_code" suffix is something that requires a separate discussion). It is currently called "Geographic_location_identification_code" - something that cannot be reliably inferred from the relevant block.

[Mike Ward]

plcslib/data/contexts/OASIS/refdata/plcs-rdl-en.owl revision: 1.4

[Mike Ward]

all identifier code classes made ready for review: plcslib/data/contexts/OASIS/refdata/plcs-rdl-en.owl revision: 1.6

[Rob Bodington]

CCB 2012-10-15
Accepted

[Rob Bodington]

The labels should be identifiers not identification code
E.g.
part identification code should be part identifier

[Rob Bodington]

Change preflabel f of identifcation_code class from "*identification code" to "*identifier"
/cvsroot/plcslib/plcslib/data/contexts/OASIS/refdata/plcs-rdl-en.owl,v <-- plcs-rdl-en.owl
new revision: 1.49; previous revision: 1.48