[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
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 From: Tim Turner [mailto:tjt@lsc.co.uk]
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, NB
- I believe that there is already a definition of Notes in a separate
developer's owl file which could then be harmoized with descriptor (sub-class)
in this context. ************************************************************************* 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 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]