Dataset: Read

The Dataset: Read Web service is used to get information (title, description, creator, contributor(s), creation date and last modification date) for a dataset belonging to the WSF (Web Services Framework).

Developers communicate with the Dataset: Read Web service using the HTTP GET method. You may request one of the following mime types: (1) text/xml, (2) application/rdf+xml, (3) application/rdf+n3 or (4) application/json. The content returned by the Web service will be serialized using the mime type requested and the data returned will depend on the parameters selected.

Version
This documentation page is used for the version 3 of this endpoint. Check at the top of this page to see the documentation pages for the other versions of this endpoint.

Usage
This Web service is intended to be used by any user that wants to get some information about a dataset registered to a WSF (Web Service Framework) for querying or other purposes.

Web Service Endpoint Information
This section describes all you permissions you need in the WSF (Web Service Framework) to send a query to this Web service endpoint, and it describes how to access it.

To access this Web service endpoint you need the proper CRUD (Create, Read, Update and Delete) permissions on a specific graph (dataset) of the WSF. Without the proper permissions on this graph you won't be able to send any queries to the endpoint.

Needed registered CRUD permission:


 * Create: False
 * Read: True
 * Update: False
 * Delete: False

As shown on the graph URI:


 * http://[...]/wsf/dataset/

Here is the information needed to communicate with this Web service's endpoint. Descriptions of the parameters are included below.

''Note: if a parameter has a default value, the requester can omit it and the default value will be used. Also, some baseline Web services may not offer other values than the default.''

HTTP Method:


 * GET

Possible "Accept:" HTTP header field value:


 * text/xml (structXML)
 * application/json (structJSON)
 * application/rdf+xml (RDF+XML)
 * application/rdf+n3 (N3/Turtle)
 * application/iron+json (irJSON)
 * application/iron+csv (commON)

URI:


 * http://[...]/ws/dataset/read/?uri=&interface=&version=

URI dynamic parameters description:

Note: All parameters have to be URL-encoded


 * uri. Unique identifier used to refer to this new dataset
 * Optionally, the user can specify "all" for the URI to get the description of all datasets accessible to him.
 * interface. Source interface used for this web service query. The interface is a different way to process a query (different algorithms, different data management system, etc. The default interface is 'default'
 * version. (default: 3.0) Version of the interface to query

Available Sources Interfaces
A source interface is a way to process a web service query. Different sources interfaces can be implemented for the same OSF Web Service endpoint. Each interface will process the query differently, but all the queries to the web service endpoint will be the same, at the exception of the  parameter. Each interface shares the same API (the one defined by the web service endpoint), but their processing may differ (like using different algorithms, using different data management systems, etc.)

This is a list of the core interfaces for this endpoint. Organizations that hosts a OSF Web Service network could create their own interface and make it available to the users. However such private source interface won't be part of this list, but should be publicized by the organization.

Example of Returned XML Document
This is an example of the XML document returned by this Web service endpoint for a given dataset URI.

This example returns the description of a dataset registered to a WSF.

Query:


 * http://[...]/ws/dataset/read/?uri=http://[...]/wsf/datasets/237/

"Accept:" HTTP header field value:


 * text/xml

Result:

DTD of the XML Document
Descriptions of the Types of XML Elements

Here are descriptions of the types of XML elements that might be returned from from this Web service. Please read the XML data structure documentation to understand how the data is structured within these XML documents.

Example of Returned RDF/XML Document
 * 'void:Dataset' (subject/object). A dataset registered/available in the WSF
 * 'sioc:User' (subject/object). A user of a system (like the user of a CMS)
 * 'dcterms:title' (predicate). Title of the dataset
 * 'dcterms:description' (predicate). Description of the dataset
 * 'dcterms:creator' (predicate). Creator of the dataset
 * 'dcterms:contributor' (predicate). Contributor of the dataset
 * 'dcterms:created' (predicate). Creation date of the dataset
 * 'dcterms:modified' (predicate). Last modification date of the dataset

Here is an example of a RDF/XML document returned by this Web service endpoint for a given URI.

Query:


 * http://[...]/ws/dataset/read/?uri=http://[...]/wsf/datasets/237/

"Accept:" HTTP header field value:


 * application/rdf+xml

Result:

Example of Returned RDF/N3 Document
Here is an example of a RDF/N3 document returned by this Web service endpoint for a given URI.

Query:


 * http://[...]/ws/dataset/read/?uri=http://[...]/wsf/datasets/237/

"Accept:" HTTP header field value:


 * application/rdf+n3

Result:

HTTP Status Codes
Here are the possible HTTP status (error) codes returned by this Web service endpoint.

On error code and the specific error, a different message description can be issued (meaning a different error has been returned).