Hi Allessandro,
I like that. It is neat and fits well with the existing specialisation
dot notation. It is something we might be able to make use of in
templates as well.
Ian
On 20 November 2013 06:18, Alessandro Torrisi <alessandro at code24.nl> wrote:
> Bert,
>
> I was not clear, but this is is my suggestion
>
> /items[at0008,1]/value/value = Jan
> /items[at0008,2]/value/value = Peter
> /items[at0009]/value/value = Balkenende
>
> Alessandro
>
>
>
> On 19 November 2013 21:08, Bert Verhees <bert.verhees at rosa.nl> wrote:
>>
>> Hi Alessandro,
>>
>> I think you propose this?
>>
>>
>> /items[at0008,1]/value/value = Mark
>> /items[at0009,2]/value/value = Rutte
>>
>> regards
>> Bert Verhees
>>
>>
>> Alessandro Torrisi schreef op 19-11-2013 20:19:
>>
>> i would say
>>
>> /items[at0008,1]/value/value = Mark
>> /items[at0008,2]/value/value = Rutte
>>
>> Alessandro
>>
>>
>>
>> On 19 November 2013 13:57, Diego Bosc? <yampeku at gmail.com> wrote:
>>>
>>> Hi Bert,
>>>
>>> Personally I would use:
>>>
>>> /items[at0008]/value[1]/value = Jan
>>> /items[at0008]/value[2]/value = Peter
>>> /items[at0009]/value/value = Balkenende
>>>
>>> Regards
>>>
>>> 2013/11/19 Bert Verhees <bert.verhees at rosa.nl>:
>>> > Hi all,
>>> >
>>> > I had following interesting discussion.
>>> >
>>> > Suppose we have a cluster containing name of a person.
>>> >
>>> > There is a field called firstname, and a field called lastname.
>>> >
>>> > The problem is concerning the ADL-path, what should be used.
>>> >
>>> > This is a part of the archetype:
>>> >
>>> > CLUSTER[at0007] occurrences matches {0..1} matches { -- voornamen
>>> > items cardinality matches {0..*; ordered}
>>> > matches {
>>> > ELEMENT[at0008] occurrences matches {0..*}
>>> > matches { -- firstname
>>> > value matches {
>>> > DV_TEXT matches {*}
>>> > }
>>> > }
>>> > ELEMENT[at0009] occurrences matches {0..1}
>>> > matches { -- lastname
>>> > value matches {
>>> > DV_TEXT matches {*}
>>> > }
>>> > }
>>> > }
>>> >
>>> >
>>> > This is a hypothecical example, only to explain:
>>> >
>>> > Because at0008 has upper-occurrences of more then 1 ( a person can have
>>> > more
>>> > then one firstnames)
>>> > And at0009 has upper-occurrences of 1 (people only have one last-name
>>> > (in
>>> > this hypothetical country))
>>> >
>>> > If we want to express data in a path/value combination, what would be
>>> > the
>>> > best solution?
>>> >
>>> > /items[at0008][1]/value/value = Jan
>>> > /items[at0008][2]/value/value = Peter
>>> > /items[at0009]/value/value = Balkenende
>>> >
>>> > /items[at0008][1]/value/value = Jan
>>> > /items[at0008][2]/value/value = Peter
>>> > /items[at0009][1]/value/value = Balkenende
>>> >
>>> > /items[at0008][1]/value/value = Jan
>>> > /items[at0008][2]/value/value = Peter
>>> > /items[at0009][3]/value/value = Balkenende
>>> >
>>> > Or would another solution be better?
>>> > Thanks in advance for suggestions.
>>> >
>>> > Kind regards
>>> > Bert Verhees
>>> >
>>> > _______________________________________________
>>> > openEHR-technical mailing list
>>> > openEHR-technical at lists.openehr.org
>>> >
>>> > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>>>
>>> _______________________________________________
>>> openEHR-technical mailing list
>>> openEHR-technical at lists.openehr.org
>>>
>>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>>
>>
>>
>>
>> --
>> Alessandro Torrisi
>>
>>
>> _______________________________________________
>> openEHR-technical mailing list
>> openEHR-technical at lists.openehr.org
>>
>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>>
>>
>>
>> _______________________________________________
>> openEHR-technical mailing list
>> openEHR-technical at lists.openehr.org
>>
>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
>
>
>
> --
> Alessandro Torrisi
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
--
Dr Ian McNicoll
office +44 (0)1536 414 994
fax +44 (0)1536 516317
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com
Clinical Modelling Consultant, Ocean Informatics, UK
Director openEHR Foundation www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL
SCIMP Working Group, NHS Scotland
BCS Primary Health Care www.phcsg.org
