[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [plcs-dex] RE: Capability property value ranges
|
Hi Tim, Now I have looked at your templates, and
the way you use them, and I have a few questions: In your template
representing_numerical_value_with_unit you have included the Property_value_representation
entity, but as far as I understand from Cap Representing_location you are not
using it. The inclusion appears to have been a copy-paste mistake. If so, I
think I understand your requirements (i.e. everything but Property_value_representation. I can see two resolutions here: 1) I change the Representing_numerical_value
in cap Representing_properties_numerically to include a reference parameter ^item,
in which case you would get exactly what you have now, or 2) I edit your
representing_numerical_value_with_unit by deleting the
Property_value_representation entity, and use that in Representing_numerical_value.
It would then have a reference parameter ^item, and it would be located in Cap Representing_value_with_unit. The first choice is the easiest for me,
but kind of cludgy, so I think I go for the second choice. I’m however not sure that I will
include the representing_value_with_unit template in Cap Representing_value_with_unit.
To me, I can’t see the difference between a value with unit and a
numerical value with unit, and it seem to me that it will only confuse issues (‘which
one is applicable where?’). Can you or someone else enlighten me
regarding their difference? Comments? Cheers, Peter From: Tim Turner
[mailto:tjt@lsc.co.uk] Hi Peter,
For your
info, I have just managed to get my sourcefoge account operational again &
have uploaded some work from last week during the outage. Inside
representing_location, you will see that there are 7 templates - 2 of which are
additional templates that were done during development of this capability.
These are; representing_value_with_unit (- the previous one in C00 - version
1.6 had many errors) & representing_numerical_value_with_unit. The first
should be moved to the appropriate place while the second was found not to be
necessary - but I have left it since it works & may serve a purpose
sometime. Kind
regards, NB - all
work without error in GI -----Original
Message----- Peter,
Regards,
Tom
Thomas E.
Hendrix -----Original
Message----- Tom,
I'm
editing the property capabilities in DEXlib now, and need three templates in
cap representing_property_value_ranges, one for range, one for limit and one
for value with tolerance. Can I
take over the editorship temporarily, or will you do it? Peter
Bergström 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]