Data Web Servers

Example Data Web Servers Created by Koneksys

Data Web Servers called OSLC adapters conforming to Open Services for Lifecycle Collaboration (OSLC) standards.

Data web servers

Mandatory Features

  • Machine-readable representation of resources in RDF (e.g. JSON-LD, RDF/XML, Turtle, etc…)
  • Support for OSLC Core Specification (Self-describing services enabling service discovery)

Possible Optional Features

  • HTML representation of resources
  • Capability to modify, create, delete resources
  • Support for ETags for avoiding conflicts when updating resources information about change events, such as deletion, creation, modification events (according to OSLC Tracked resource Set specification)
  • Provide delegated UIs to provide clients an HTML iframe displaying selection/creation/preview dialogs (according to OSLC Delegated UI spec)
  • Query capabilities similar to GraphQL (using OSLC selective properties according to OSLC Core spec) returning to clients for example a representation of a requirement including only a few selected attributes (and not all 100)
  • Graph query capabilities similar to SPARQL
  • Resource paging to divide large resource representations into smaller chunks which clients can retrieve one by one, similar to Google seach results
  • Support for syncing with Subversion repository
  • Hosting resource shapes and RDF vocabulary
  • Configuration options for syncing adapter with original data source (e.g. periodic, user-driven, etc..)
  • Configuration options for selecting data from original data source to be considered by adapter (e.g. specific data types, or specific data, or specific data containers)
  • Hosting resource shapes and RDF vocabulary

Choices

  • Web application server (e.g. Tomcat, Jetty, and Wildfly (former JBoss), node.js)
  • REST API framework (e.g. Apache Wink, and RESTeasy and Jersey)
  • What data gets exposed through the data Web server?
  • How many links between data get exposed through the data Web server?
Talk To Us