Another alternative is PROV-DICTIONARY:
http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/
Lists are a special case of mappings, especially if you've already conceded
the use of explicit indices. Two possible benefits here are that a) it's
already part of an accepted standard (but is itself
Property paths help for some queries, but it is still hard to query all
items in a list (of unknown length) and get them back *in order*. See
the explanation here:
http://goo.gl/8PNuAG#heading=h.r5k2cm3j5iua
David Booth
On 05/06/2015 04:27 PM, Jim McCusker wrote:
Lists aren't that bad anymor
Lists aren't that bad anymore in SPARQL, now that property paths are
available: http://www.snee.com/bobdc.blog/2014/04/rdf-lists-and-sparql.html
Jim
On Wed, May 6, 2015 at 4:25 PM David Booth wrote:
> In defining the RDF representation of FHIR data, we need to maintain
> element ordering in som
In defining the RDF representation of FHIR data, we need to maintain
element ordering in some cases, both because ordering can be
semantically relevant (such as listing someone's preferred mailing
address first in a list of addresses), and to support round-tripping of
FHIR RDF data back to FHIR
