Hello, > On 19 févr. 2015, at 11:31, Uldis Bojars <[email protected]> wrote: > > It would make sense to define UI element order at a higher level than > individual triples. Defining the position for every triple separately would > lead to chaos. > > A more sensible approach 'd be to define the order of statements [about > something] at the property level. > > E.g. display the most important properties first, then have an ordered list > of other properties that we know are frequently used for this type of objects > and, as fallback, list all other (unknown) properties at the end.
The Fresnel RDF vocabulary was designed to let you specify this sort of things. It lets you specify different “lenses” that apply to specific types of RDF resources (e.g. those that are instances of a given class, or those that match a particular SPARQL query) and then gives the RDF browse that applies a lens to a resource indications about which properties should be displayed, in what order, what properties can be used as fallbacks for others, etc. Plus some high-level indication about how property values should be formatted. [1] http://www.w3.org/2005/04/fresnel-info/ [2] http://dx.doi.org/10.1007/11926078_12 (ISWC paper) -- Emmanuel Pietriga INRIA & INRIA Chile http://pages.saclay.inria.fr/emmanuel.pietriga
