Issue 12106

Rework the Tag API (API, services, persistence clients etc)

Reporter: trobertson
Type: Task
Summary: Rework the Tag API (API, services, persistence clients etc)
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2012-10-25 17:02:28.626
Updated: 2013-08-29 14:45:07.887
Resolved: 2013-02-26 18:38:46.422
Description: Following the group discussion on the tagging, the following were decided upon through a democratic voting process:

i) We will have Tag and Machine Tag, 2 interfaces and 2 resource URLs
ii) Machine Tag will always have:

  - namespace (String with guidelines on sensible ones like "dwc")
  - name (String)
  - value

iii) Both tag and machine tag will have a creator (type?), and a created (Date)
iv) All fields of tags will be be treated as case sensitive and NOT modified, with a plan to review this once in use

It was not decided on how a tag should be serialized and the implementor of this issue should open that discussion for a decision. is a hastily prepared start to this issue, capturing most of the decisions, but is incomplete.

Comment: This is being done in the Registry V2 work
Created: 2013-02-26 18:38:46.449
Updated: 2013-02-26 18:38:46.449