Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

* Used in all DiSCOs for required fields

Link Headers and Relations

The following link relations may be returned in response for a DiSCO request:

...

Relation

...

Description

...

predecessor-version

...

The resource indicated by this link represents a DiSCO that is the immediate predecessor of the DiSCO

See: https://tools.ietf.org/html/rfc5829#section-3.5

...

successor-version

...

The resource indicated by this link represents a DiSCO that is the immediate successor of the DiSCO under consideration.

See: https://tools.ietf.org/html/rfc5829#section-3.6

...

latest-version

...

The resource indicated by this link represents the latest version of the DiSCO

See: https://tools.ietf.org/html/rfc5829#section-3.2

...

http://www.w3.org/ns/prov#wasGeneratedBy

...

The resource indicated by this link represents the rmap:Event that generated the DiSCO

...

http://www.w3.org/ns/prov#has_provenance

...

The resource indicated by this link represents a list of rmap:Events that affected the DiSCO

...

http://rmap-project.org/rmap/terms/hasStatus

...

The resource indicated by this link defines the current status of the DiSCO

Example DiSCO

RDF/XML

...

languagexml
themeDJango
firstline1
linenumberstrue

...

Example DiSCO

RDF/XML
Code Block
languagexml
themeDJango
firstline1
linenumberstrue
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:rmap="http://rmap-project.org/rmap/terms/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:ore="http://www.openarchives.org/ore/terms/"
    xmlns:foaf="http://xmlns.com/foaf/0.1/"
    xmlns:prov="http://www.w3.org/1999/02/22-rdf-syntax-ns#"ns/prov#">
    xmlns:rmap="http://rmap-project.org/rmap/terms/" 
    <rdf:Description rdf:about="ark:/00000/03j9uf983h8fh8s">
       <rdf:type xmlnsrdf:dcresource="http://purlrmap-project.org/dcrmap/elements/1.1/"
    xmlns:dctermsterms/DiSCO"/>
	<dcterms:creator rdf:resource="http://purlorcid.org/dc/terms/"0000-0000-0000-0000"/>
       xmlns:ore="http://www.openarchives.org/ore/terms/"<dcterms:description>
          xmlns:foaf="http://xmlns.com/foaf/0.1/"  This is  xmlns:prov="http://www.w3.org/ns/prov#">
    an example DiSCO aggregating different file formats for an
    <rdf:Description rdf:about="ark:/00000/03j9uf983h8fh8s">       article <rdf:type rdf:resource="http://rmap-project.org/rmap/terms/DiSCO"/>
	<dcterms:creator rdf:resource="http://orcid.org/0000-0000-0000-0000"/>
       <dcterms:description>on IEEE Xplore as well as multimedia content related to the
            article.
This is an example DiSCO aggregating different file</dcterms:description>
formats for an     <!-- Optional provenance reference - can also create articlea onprovenance IEEEdocument Xplorein asa wellDiSCO as
multimedia content related to the
            article.
       </dcterms:description>
       <!-- Optional provenance reference - can also create a provenance document in a DiSCO 
       and reference it here-->
       <prov:wasGeneratedBy rdf:resource="ark:/00000/uriOfProvDesc"/>
       <!-- Aggregation section -->
       <ore:aggregates rdf:resource="http://dx.doi.org/10.1109/ACCESS.2014.2332453"/>
       <ore:aggregates rdf:resource="http://ieeexplore.ieee.org/ielx7/123/html/6842585-mm.zip"/>
    </rdf:Description>

    <!-- Statements describing the first ore:aggregates resources-->
    <rdf:Description rdf:about="http://dx.doi.org/10.1109/ACCESS.2014.2332453">
    	<rdf:type rdf:resource="http://purl.org/spar/fabio/JournalArticle"/>
  	<dc:title>Toward Scalable Systems for Big Data Analytics: A Technology Tutorial</dc:title>
  	<dc:creator>Tat-Seng Chua</dc:creator>
 	<dc:creator>Xuelong Li</dc:creator>
 	<dc:creator>Yonggang Wen</dc:creator>
 	<dc:subject>data acquisition</dc:subject>
  	<dc:subject>Big data analytics</dc:subject>
  	<dc:subject>Hadoop</dc:subject>
    </rdf:Description>

    <!-- Statements describing the second ore:aggregates resources-->
    <rdf:Description rdf:about="http://ieeexplore.ieee.org/ielx7/123/html/6842585-mm.zip">
  	<dc:hasPart rdf:resource="http://ieeexplore.ieee.org/123/html/123-mm.zip#README.docx"/>
  	<dc:hasPart rdf:resource="http://ieeexplore.ieee.org/123/html/123-mm.zip#dataintro.avi"/>
  	<dc:format>application/zip</dc:format>
    </rdf:Description>

    <!-- More statements to describe some of the components in the graph-->
    <rdf:Description rdf:about="http://ieeexplore.ieee.org/123/html/123-mm.zip#dataintro.avi">
  	<dc:extent>194KB</dc:extent>
  	<dc:format>video/x-msvideo</dc:format>
    </rdf:Description>
</rdf:RDF>

...


Element Name

Occurrence

Description

rdf:type

1

Required. Will always be rmap:DiSCO

ore:aggregates

1+

Property of a DiSCO. Used to specify an aggregated resource. The aggregated resource MUST have a URI. (revenue model oppty: naming service for resources w/o a URI)

dcterms:creator

0-1

This is distinct from the service/system agent that uses the API to create the DiSCO. This is the individual(s) or organization that assembled the set of relationships and asserted them as a DiSCO. Allows ownership of DiSCOs to be more specific than the system that created them.

dcterms:description

0-1

Optional short description of the DiSCO. Meant for human consumption.

prov:wasGeneratedBy

0-1

Optional link to a document describing the harvester.  This document can be generated in a DiSCO and referenced as provenance information

Additional RDF about each ore:aggregates resource

0*

Additional RDF data about each resource listed in ore:aggregates can be provided.  There are no limitations on what triples are used to describe the aggregated resources, provided it is (1) valid RDF (2) forms a connected graph that has the aggregated resource at its root.


Though not required, it is recommended that each description of the aggregated resource include, where possible, a type, title, and its relationship to the other aggregated resources.

RMap API Usage of This Media Type

Supported Operations


Operation

HTTP Method

Description

Explain

OPTIONS

Describe the capabilities at this path.

Status

HEAD

Returns status of service - essentially the same as OPTIONS without the response body.

Read

GET

Returns a single DiSCO

Create

POST

Creates a new DiSCO

Update

POST

Inactivates existing DiSCO, creates a new DiSCO and generates a version link between them

Inactivate

POST

Inactivates existing DiSCO

Delete

DELETE

Tombstones existing DiSCO (soft delete)

GetStatus

HEAD

Gets status of a DiSCO (Active, Inactive, Tombstoned, Deleted)


Link Headers and Relations

The following link relations may be returned in response for a DiSCO request:


Relation

Description

predecessor-version

The resource indicated by this link represents a DiSCO that is the immediate predecessor of the DiSCO

See: https://tools.ietf.org/html/rfc5829#section-3.5

successor-version

The resource indicated by this link represents a DiSCO that is the immediate successor of the DiSCO under consideration.

See: https://tools.ietf.org/html/rfc5829#section-3.6

latest-version

The resource indicated by this link represents the latest version of the DiSCO

See: https://tools.ietf.org/html/rfc5829#section-3.2

http://www.w3.org/ns/prov#wasGeneratedBy

The resource indicated by this link represents the rmap:Event that generated the DiSCO

http://www.w3.org/ns/prov#has_provenance

The resource indicated by this link represents a list of rmap:Events that affected the DiSCO

http://rmap-project.org/rmap/terms/hasStatus

The resource indicated by this link defines the current status of the DiSCO


Examples

Create a DiSCO via POST HTTP Request

...