Just tested it with the xml you provided. The second one works, first one doesn't. It's weird because in the sample data I created they did in fact work. I generated it modifying another instance you put on this thread.
2013/11/21 Thomas Beale <thomas.beale at oceaninformatics.com> > On 20/11/2013 11:28, Diego Bosc? wrote: > >> It is right in XPath, maybe is less intuitive, but I would say these >> are even less intuitive and still work >> /cluster[@archetype_id='openEHR-EHR-CLUSTER.bert.v1']/ >> items/value[3]/value=Balkenende >> /cluster[@archetype_id='openEHR-EHR-CLUSTER.bert.v1']/ >> items[3]/value/value=Balkenende >> > > Diego, > do you mean you tested this? Could you provide the XML source content you > did this on? > > > I think we should decide why is this for: >> >> Is this for ADL paths? then use ADL path syntax. >> Is this for XML query? then use XPath >> > > well what we want I believe, is for the ADL paths to be easily mappable > (i.e. simple algorithm) to convert to the correct Xpaths. I'm not yet > convinced we have the answers right here. Happy to be corrected though. > > - thomas > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20131122/bde01007/attachment-0001.html>
