The purpose of this page is to come to a design for an extension of the ComponentRegistry that will enable versioning and deprecation of components and profiles.

Component versioning

Definitions

• Component refers to both components and profiles as specified by the general component schema that exist in the ComponentRegistry;
• Versioning refers to the precursor/successor relation that may exists between two components. It does not imply a structural or functional extension or inheritance, i.e. the structure of the precursor component does not put any constraints on the structure of the successor relation; no assumptions about the structure of the' one can be made on basis of the structure of the other. Versioning does not imply deprecation (see below) of the precursor.
• Deprecation refers to a state in which a component is no longer 'advertised' by the registry (it will not appear in the list of published components) and will be explicitly marked as such to the client. However it will still be accessible by its URI so that instances based on deprecated components will remain valid. Apart from this, the properties of published components apply. Deprecation can be combined with versioning.

Design

For each component the following will be specified and communicated to the client:

• A flag indicating whether the component is deprecated ('false' by default)
• A (possibly empty) set of direct successors

The ComponentRegistry web service (and as a result this will also apply to the Flex-based component browser) will not display deprecated components in any listing (e.g. ​/registry/profiles). However, they will still be available by their ID (like ​/registry/profiles/clarin.eu:cr1:p_1297242111880).

There will be a call to list all direct (and possibly also recursive) successors

Implementation

The ComponentRegistry web service has a PostgreSQL back-end in which it stores both the component specifications in their verbatim XML formatting and 'component metadata' (referred to as 'descriptions' to avoid ambiguity) containing fields such as 'creator' and 'group'. The 'deprecated' property can be added to this. To accommodate the successor relations, an additional table has to be added simply linking precursors and successors, and optionally storing a comment on each relation.

Discussion

• Should we limit deprecation and versioning to published components?