[FoRK] Seagate Kinetic

Ken Meltsner meltsner at alum.mit.edu
Fri Oct 25 14:17:55 PDT 2013

Just received an Oasis technical committee proposal to set up a standard
interface for key-value databases.  I'd assume this would allow the devices
like Seagate's to become commodities within a year or two.... There're
still value-added possibilities in that the committee specifically excluded
the messy details of dealing with "authentication, authorization, and
access control mechanisms and protocols."

The full proposal should be in the archives at :

(1)(a) Name of the TC

OASIS Key-Value Database Application Interface (KVDB) Technical Committee

(1)(b) Statement of purpose

The purpose of the Key-Value Database Application Interface (KVDB)
Technical Committee (TC) is to define an open application programming
interface for managing and accessing data from database systems based on
key-value model.

The work will focus on:

* Defining an abstract model and requirements of a key-value based database

* Managing data in key-value based database systems using a REST-ful
application programming interface.

(1)(c) Scope of work

The TC will accept as input the KVDB V1.0 Specification published on
September 23, 2013:

The TC will refine this initial contribution to produce OASIS standard
specifications, including necessary supporting documentation.

Other contributions will be accepted for consideration without any
prejudice or restrictions and evaluated based on technical merit in so far
as they conform to this charter. Members with extensive experience and
knowledge in these areas are particularly invited to participate.

The scope of the TC's work is limited to technical refinements to the
feature set defined in the input contribution and the following features
and capabilities.

The features in scope for the TC have been divided into the following

1. Abstract models of key-value based database systems

2. Requirements

Description of requirements for key-value based database systems include

  * Protocols

  * Authentication

  * Data consistency

  * Naming

  * Status messages

  * Error codes and error messages

  * Request headers

  * Response headers

  * Other requirements

3. Application programming interface (API)

   Mechanisms to

    * Retrieve tables

    * Create tables

    * Delete tables

    * Retrieve metadata

    * Insert/update metadata

    * Insert/update data

    * Delete data

    * Retrieve data

    * Query data


More information about the FoRK mailing list