• Developers willing to access data in LOD formats
• Partners willing to integrate ODM data into their platforms

• How to call the catalog endpoint to obtain a list of datasets
• How to get a particular dataset in various LOD formats

Quoted from linkeddata.org:

Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. More specifically, Wikipedia defines Linked Data as “a term used to describe a recommended best practice for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using URIs and RDF.”

The Resource Description Framework (RDF) is a family of World Wide Web Consortium (W3C) specifications originally designed as a metadata data model. It is used for describing graph-like ( nodes and vertices ) relationships between pieces of information by using RDF Triples.

An RDF triple contains three components:

- the subject, which is an RDF URI reference or a blank node. - the predicate, which is an RDF URI reference. - the object, which is an RDF URI reference, a literal or a blank node.

It is important to distinguish the RDF/XML format from the abstract RDF model itself. Although the RDF/XML format is still in use, other RDF serializations are now preferred by many RDF users, both because they are more human-friendly,[32] and because some RDF graphs are not representable in RDF/XML due to restrictions on the syntax of XML QNames.

From RDF definition on wikipedia

• Turtle: a compact, human-friendly format.
• N-Triples: a very simple, easy-to-parse, line-based format that is not as compact as Turtle.
• N-Quads: a superset of N-Triples, for serializing multiple RDF graphs.
• JSON-LD: a JSON-based serialization.
• N3 or Notation3: a non-standard serialization that is very similar to Turtle, but has some additional features, such as the ability to define inference rules.
• RDF/XML: an XML-based syntax that was the first standard format for serializing RDF.

ODM's CKAN instance exposes this functionality thanks to the great job done by the contributors of https://github.com/ckan/ckanext-dcat, a CKAN extension for exposing data in RDF, and many more things.

RDF representations of a particular dataset can accessed using the following endpoint:

https://data.opendevelopmentmekong.net/dataset/{dataset-id}.{format}

The extension will determine the RDF serialization format returned. The currently supported values are:

The fallback rdf format defaults to RDF/XML.

Here's an example of the different formats available:

• https://data.opendevelopmentmekong.net/dataset/economic-land-concessions.rdf
• https://data.opendevelopmentmekong.net/dataset/economic-land-concessions.ttl
• https://data.opendevelopmentmekong.net/dataset/economic-land-concessions.n3
• https://data.opendevelopmentmekong.net/dataset/economic-land-concessions.jsonld

Additionally to the individual dataset representations, there is a catalog-wide endpoint for retrieving multiple datasets at the same time (the datasets are paginated, see below for details):

https://data.opendevelopmentmekong.net/catalog.{format}?[page={page}]&[modified_date={date}]

As described previously, the extension will determine the RDF serialization format returned.

  http://data.opendevelopmentmekong.net/catalog.rdf
  http://data.opendevelopmentmekong.net/catalog.xml
  http://data.opendevelopmentmekong.net/catalog.ttl

The number of datasets returned is limited. The response will include paging info, serialized using the Hydra vocabulary. The different terms are self-explanatory, and can be used by clients to iterate the catalog:

@prefix hydra: <http://www.w3.org/ns/hydra/core#> .

<http://example.com/catalog.ttl?page=1> a hydra:PagedCollection ;
    hydra:firstPage "http://example.com/catalog.ttl?page=1" ;
    hydra:itemsPerPage 100 ;
    hydra:lastPage "http://example.com/catalog.ttl?page=3" ;
    hydra:nextPage "http://example.com/catalog.ttl?page=2" ;
    hydra:totalItems 283 .

The default number of datasets returned is 100.

The catalog endpoint also supports a modified_date parameter to restrict datasets to those modified from a certain date. The parameter value should be a valid ISO-8601 date:

http://data.opendevelopmentmekong.net/catalog.xml?modified_since=2015-07-24

TBD

Currently, multilingual values are not exposed following RDF standards but as json object.

Instead of using just literals for the object of the different predicates, as is the case now, standard values (such as a country code) should be exposed via an URI.

In case a triple has the value None, it should not be generated.

In order to expose topics using standard terms