Thomas Beale wrote:
> Adam Flinton wrote:
>>
>>
>> I reserve my views wrt attributes vs text() however that would do on 
>> the proviso of a bit of testing with many tools as it used to be 
>> patchily supported by different tools.
>>
>> I accept that was a few years back & things may well have improved.
>>
>> So then next question then is when will the tools support this?
>>   
> looks like we have arrived at a useful point - first thing we need is 
> an analysis of changes to the XML-schemas. If Lisa's change is all 
> that is needed and someone wants to update the current schemas to make 
> thi work, we can put it on the main TRUNK so that everyone can have 
> access to it.
>
> Further analysis will be needed for the tools, but I would not expect 
> big problems. Generally they are using orthodox XML parsers whcih I 
> assume respect the whitespace settings in an XML schema...
>
> - thomas
>
>

I would like though to enquire wrt the rationale of containing _id info 
in a separate <value/> element.

If you are being consistent
instead of :

       <terminology_id>
           <value>ISO_639-1</value>
       </terminology_id>

it should be simply:

       <terminology_id>ISO_639-1</terminology_id>


or <terminology_id value="ISO_639-1"/>

Adam



**********************************************************************
This message  may  contain  confidential  and  privileged information.
If you are not  the intended  recipient please  accept our  apologies.
Please do not disclose, copy or distribute  information in this e-mail
or take any  action in reliance on its  contents: to do so is strictly
prohibited and may be unlawful. Please inform us that this message has
gone  astray  before  deleting it.  Thank  you for  your co-operation.

NHSmail is used daily by over 100,000 staff in the NHS. Over a million
messages  are sent every day by the system.  To find  out why more and
more NHS personnel are  switching to  this NHS  Connecting  for Health
system please visit www.connectingforhealth.nhs.uk/nhsmail
**********************************************************************


Reply via email to