[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency-comment] codes
Jacob, If you use a CAM template - then you will be able to directly key off the <code> and select the appropriate enumeration values you want to use for the validation. i.e. <constraint condition="//parameter/code='NAS=1.3'" action="restrictValues(//parameter/value,'A'|'B'|'C')"/> <constraint condition="//parameter/code='HPP=1.0'" action="restrictValues((//parameter/value,'1'|'2'|'3'|'4')"/> and so on. If you want to use external codelist values - then the lookup(uri) function can be used instead of restrictValues() function. The Java implementation of jCAM is available from sourceforge - http://www.jcam.org.uk/ and we have a lightweight xslt version to that's currently in beta that works with Saxon 9 if that is of interest. Thanks, DW -------- Original Message -------- Subject: [emergency-comment] codes From: Jacob Westfall <jake@jpw.biz> Date: Tue, August 12, 2008 5:07 pm To: emergency-comment@lists.oasis-open.org Hi, The code element in the alert block could be enhanced by using the valueListUrn and value format to better present any special handling values. Currently we use the code element to show what Profiles/Layers are in use for the message so that the receiving system can load its Layer validators before parsing info blocks. For example, <code>NAS=1.3</code> <code>HPP=1.0</code> Is there perhaps a better way of denoting what Profiles/Layers are in use for a message? Maybe an element like profile or layer or something instead of code. The layer would match the valueListUrn's used for the optional elements. <layer>urn:cap:profile:NAS1.1</layer> ... <parameter> <valueListUrn>urn:cap:profile:NAS1.1</valueListUrn> <value>A</value> </parameter> -- jake@jpw.biz -- -- This publicly archived list offers a means to provide input to the OASIS Emergency Management TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: emergency-comment-subscribe@lists.oasis-open.org Unsubscribe: emergency-comment-unsubscribe@lists.oasis-open.org List help: emergency-comment-help@lists.oasis-open.org List archive: http://lists.oasis-open.org/archives/emergency-comment/ Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: http://www.oasis-open.org/maillists/guidelines.php Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]