[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [plcs-dex] Error in path for template representing_count
|
Tim, Thanks for the comments, really good
feedback! 1) the si_unit is not defined in representing_count, but in
representing_value_with_unit, and it is already a Boolean. The reason for the ‘false’
string is the P28 notation – that’s how a Boolean false is recorded
in P28. But the parameter has a note that discusses the differences in encoding
format of Boolean datatypes, so it should be clear that .F. in P21 is the same
(and a valid) encoding. 2) The type of unit was missing, as you pointed out, and still is in
representing_value_with_unit. Until the XML DTD for templates give me some
other possibility, this is handled by encoding the value input parameter as
e.g. “ANY_NUMBER_VALUE(5.)” in P21, or as “<ap239:Any_number_value-wrapper>5</ap239:Any_number_value-wrapper>”
in P28. I can’t say if this good enough, but I have no other solution at
the moment. Any input welcome… 3) I have updated the template representing_count, both regarding the
parameter definitions and the figures 3 and 4. I will go through the other templates I
have made to see if the problem needs to be handled elsewhere too. Peter From: Tim Turner
[mailto:tjt@lsc.co.uk] Peter, I just raised the following issues while validating
one of our business templates. in representing_count the instantiation path is incorrect, This did not get picked up by the ESL tools - so you might
want to log that too. The si_unit refered to below must be of type boolean not
string
i.e. either; Unit.si_unit
= .F. The resulting instances of this template include; #6 = UNIT('/IGNORE', 'false'); However, the type of unit is missing. Given the select type
options of any_number_value, any_string_value, plane_angle_measure or
length_measure, one of these should be populated in the template to produce a
valid instantiation. For example, #6 = UNIT('/IGNORE',.F.); Also, the templates figure 3 is misleading - there is no
indication of the representation or need for the type of unit to be used. If one is not to be specified, then it needs to be part of
the instantiation path. regards, Tim NB Maybe you could also check your other templates that make
use of si_units and correct where necessary? ************************************************************************* This message contains information that may be privileged or confidential and is the property of Eurostep Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. 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 England & Wales No 2275471 Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1 4SG |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]