W3C home > Mailing lists > Public > public-lod@w3.org > February 2012

Metadata about single triples

From: Carsten Keßler <carsten.kessler@uni-muenster.de>
Date: Wed, 22 Feb 2012 12:02:27 +0100
Message-ID: <CANqMnYOhPpEu1x4x_pZ8nvbzx8fbjt_CdqQ-JpEdrq62iD_6DA@mail.gmail.com>
To: public-lod@w3.org
Cc: Chad Hendrix <hendrix@un.org>
Dear LODers,

we are currently working on a project for the United Nations Office
for the Coordination of Humanitarian Affairs (OCHA) in Geneva to
develop a Humanitarian Exchange Language (HXL). Some information about
the project is available at https://sites.google.com/site/hxlproject/.

One of the core components of HXL will be an RDF vocabulary to
annotate the data that are exchanged between humanitarian
organizations. The current draft is available at
http://hxl.humanitarianresponse.info. It is far from complete, but I
think it already shows where we want to go with this. Any feedback on
the vocabulary draft is very welcome, of course.

The aspect we are currently working on is a metadata section that will
include classes and properties to state who has reported a certain
piece of information, when it was reported, whether it was approved
(and at which level), and so forth. The current idea is to create
named graphs that can be described by these metadata elements. I'd
like to hear your comments on this approach, since this will lead to a
situation where we can have the same triple in several named graphs
For example, graph A with all data reported on Januar 20, 2012 by an
OCHA information officer in Suda, graph B with all data approved by
the OCHA regional office on January 21, and graph C with all data
approved by OCHA in Geneva on January 22. The rationale is  to be able
to query based on these metadata elements via SPARQL, e.g., "give me
all figure about refugess in Sudan from January 2012 approved by OCHA
Geneva". Note that the regional office may only approve some of the
triples originally reported, and OCHA Geneva may only approve a subset
of those approved by the regional office. So basically we need to be
able to attach those metadata elements to every single triple.

We will probably run into a situation where we can have the same
triple in 10–20 graphs at the same time. Likewise, we will have a
pretty large number of named graphs in our store, and I'd like to know
whether you think this approach is problematic (e.g. in terms of query
performance), and whether you see an alternative approach?

Thanks,
Carsten

---
Dr. Carsten Keßler
http://carsten.io

+49 (0) 251 83 39764

Linked Open Data University of Münster → http://lodum.de
Münster Semantic Interoperability Lab → http://musil.uni-muenster.de
Institute for Geoinformatics → http://ifgi.uni-muenster.de
University of Münster → http://www.uni-muenster.de
Received on Wednesday, 22 February 2012 11:03:35 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:37 UTC