RDS/WIP 2.0 General Use Cases

This is a quick page outlining the general use cases for the RDS/WIP 2.0, as simple sequences of typical events. This is currently far from exhaustive - it should just give a sense of the flavours that are possible.

Add New Yellow Belt Editor

Addition of a new yellow belt editor to the RDS/WIP community.

  • Yellow belt passes accreditation.
  • IDS-ADI personnel use RDS/WIP Administrator UI to create new user credentials and authorize to allowable RDS/WIP ISO 15926 datasets.
  • Credentials are posted to yellow belt.
  • Yellow belt can now login to server (HTTP-based authentication over SSL).

Publish ISO 15926 Definition by SPARQL/SOAP Client

Publish a set of new ISO 15926 conformant definition using a desktop application (or another service).

  • Yellow belt creates definition in SPARQL/SOAP client s/w.
  • Yellow belt posts definition via Web Service to RDS/WIP (authorization required).
  • Content is immediately available to public via SPARQL and via web browser presentation layer.

Publish ISO 15926 Definition by Bulk Upload

Publish a set of new ISO 15926 conformant definitions using the bulk upload user interface.

  • Yellow belt creates definition in OWL/RDF.
  • Yellow belt uploads definition via Submittal UI to RDS/WIP (authorization required).
  • Content is immediately available to public via SPARQL and via web browser presentation layer.

Publish ISO 15926 Definition by Discrete Editor

Publish a set of new ISO 15926 conformant definitions using the Yellow Belt (Discrete) Editor thin client.

  • Yellow belt logs in to RDS/WIP site.
  • Yellow belt creates and edits definition using Yellow Belt (Discrete) Editor in private dataset.
  • Yellow belt may logout and return later, dataset remains valid and private, can continue to edit.
  • Theoretically: could allow a yellow belt to share private dataset with other yellow belts.
  • Yellow belt submits dataset - editor extracts OWL/RDF and adds to WIP using internal bulk submittal process.
  • Private data set is cleared, but left available (would retain permissions if multiple people could edit).
  • Content is immediately available to public via SPARQL and via web browser presentation layer.

Publish and Maintain Ad-Hoc RDF

Publish and maintain an RDF dataset consisting of non-ISO 15926 definitions.

  • Submitter creates RDF as a single document.
  • Submitter passes RDF to IDS-ADI for consideration.
  • IDS-ADI choose to create a dataset and upload using original RDS/WIP 1.0 triplestore manager.
  • Local identifiers in the document will of course reflect the chosen endpoint automatically.
  • IDS-ADI create new user for submitter and give user rights to dataset.
  • User can now alter that data set themselves, and/or assign rights to other users.
  • Note: cannot use discrete editor because its not ISO 15926 format. Can use bulk upload UI and/or API.
  • Theoretically: could form basis for harmonization effort - eg. might set up BIM team RDF repository.

Change Status of Submission

A Yellow Belt Modeler thinks that a submission is "standard" quality and should be elevated in status.

  • Submitter uses Yellow Belt (Discrete) Editor to mark a submission for consideration of new status.
  • Changed submission status is immediately reflected in public data.
  • Yellow Belt notifies Black Belts of changed status (probably by email in 2.0, but automatable later).
  • Black Belts search for submissions and alter status accordingly (might reject or accept).
  • Black Belt notifies Yellow Belt of changed status.
  • Changed status is immediately reflected in public data.
  • Yellow Belt can search for submissions and check returned status.
Home
About PCA
Reference Data Services (RDS)
RDS Operations Support
Meetings and Conferences
ISO 15926
Special Interest Groups
Technical Advisory Board
Norwegian Continental Shelf Std
Projects
Search