Introduction

The information, mapped to ISO 15926-7 templates in ISO 15926-8 format, shall be stored in a triple store or quad store.

An API is required so that such a store handles the files in a way that warrants an optimum information quality, and to warrant that all ISO 15926 triple stores behave identically.

This topic lists the requirements for such an API.

API Functionalities

• Part 8 file import - rules for:
  • validation (well-formedness and other validation (duplicates, cardinalities, etc.));
  • the form of responses of success and failure) of imported Turtle files that conform to Part 8 of this standard;
  • logging of import transactions.
• Data caching - rules for:
  • managing information in Part 8 format that is “cached” (copied into a store that doesn’t “own” it),
  • support for a ‘subscription’ service to enable a caching store to obtain relevant updates from the owning store, including actual data changes and the beginning of a new temporal part with new data values. NOTE: Part 9 is not about how to do caching, but the rules in data updating to facilitate better caching.
• Deprecation of updated information - in cases where information is updated by storing a newer template instance, the template with older information shall be deprecated by adding a deprecation triple.
• Part 8 file export - rules for:
  • selection of data to be exported to another store;
  • generation of a corresponding transfer file that conforms to Part 8;
  • transfer of the file to the target recipient, or to a file system;
  • logging of export transactions.
• Data hand-over - rules for:
  • activation of the Part 8 file export function in the source store for the data to be handed over;
  • invoking the Part 8 file import function in the target store;
  • sending transfer file and confirming successful completion of transaction;
  • logging and production of contractual transmittals of handover transactions.
• SPARQL query processing – rules for the acceptance, processing and response to SPARQL queries against the information maintained by the store or a federation of stores.
• Federation - rules for:
  • support for creation of federations of stores;
  • distribution architecture;
  • data sharing;
  • central security services. NOTE: look into the work of http://tscp.org.
• URI Dereferencing - rules for:
  • online availability of resources associated with URIs (dereferenceability);
  • allocation of responsibility for de-referencing URIs in a federation of participating stores. NOTE: see http://www.w3.org/TR/cooluris/ for the requirement and solutions.
• Security - rules for:
  • authentication of store service clients;
  • control of access to information maintained by the store, according to client privileges, including import, correction, query, and export;
  • support for encryption of information during query, import and export transfers;
  • selective access rights per template instance.