[Crm-sig] Ordering of elements

Vladimir Alexiev vladimir.alexiev at ontotext.com
Tue Nov 20 14:39:18 EET 2012

> Sent: Tuesday, November 20, 2012 12:58 PM
> Subject: Preferred Identifier vs Appellation vs Image
> ... a property such as "P200 is preferred" on E1

A scope note could be something like this:
"Whether this entity should be preferred amongst all other entities falling in a given set (e.g. the Identifiers, Appellations or Image representations of some Man-Made Object).
Such naïve global notion of preference may be useful in scenarios where an object needs to be represented by one of its related Appellations and/or Images (e.g. search result lists).
You can use Attribute Assignment in order to express who and when expressed this preference."

The above is motivated by the need to use a particular image of an object as its thumbnail.
Joshan added the following:
> the sequence (order) of images is also important, particularly for objects with lots of images

This could be added as a property P201_sort_order from E1 to Number with scope note 
"Sort ordering of this entity amongst all other entities falling in a given set" ... (then similar to the above)


RDF naturally represents multi-valuedness: if you have a statement <S,P,O1> you can always add <S,P,On>, e.g.
  <obj> P138i_has_representation <obj/image/1>,<obj/image/2>.
But RDF doesn't naturally represent order amongst these values. E.g. if you say
  <obj> P138X_has_representations (<obj/image/1> <obj/image/2>).
that means an rdf:List 
   [ rdf:first (<obj/image/1>; rdf:rest [ rdf:first (<obj/image/2>; rdf:rest rdf:nil ] ]
and totally changes the data representation.

(Luckily, OWLIM returns results in the same order as inserted, but that's not guaratneed).

More information about the Crm-sig mailing list