Terminologies EU

This site is to support a proof of concept of how we think the process of terminology development and maintenance should be supported. The key objective is to create a coherent, open and transparant approach for a wide user community, to allow for timely and effective feedback based on fact rather than authority.

Process Desiderata

To achieve this key objective, the following requirements must be met: (not exhaustive)

Transparant and well documented decision making

Coherent adaptable working environment for multiple terminologies

Immediate availability of, and access to relevant data for all at all times

Close involvement of prospective user community

Clear roles and reponsibilities of different actors

Open, simple, flexible, but robust interfaces to interconnect subprocesses

Agreed standards to best capture format and meaning of resources

Precise identification of different instantiations of schemes, and access to it

Which pieces are available

At this point a small set of coherent services is available. Some still in rudimentary form, but sufficient to realistically support this proof of concept. Ultimately we foresee a Service Oriented Architecture, where system integrators re-use separate Web Services in their tools, to enable sharing in the collaboration.

A simple http-call to submit comments directly from your tool (SNOB example)

A simple http-call to Cast a Vote on comments submitted by peers

A simple http-call to retrieve all available comments on a specific class

A customised comment-submission form

Simple WEB services for toolbuilders (All classes that have comments, Classification details)

For users a call that lists all their comments on a specific classification

Appropriate communication modalities for different users

Agreed standard for representing classification schemes (ClaML)

A public Registry for Coding Schemes

Central public browser(s) where organisations can publish their latest products