Assume name/value pairs of Strings (UTF-8)? Value optional.
Consider whether annotations is something separate (probably not - just use value field).
Need to optionally refer to specific path & version, or default to latest version, whole object etc.
Target can be any VERSIONED object. Reference is an OBJECT_VERSION_ID [+ path]
Need to consider some core set of standard tag names - mod to terminology ?? (Not necessary for this CR)
As we agreed on the in-person SEC meeting, let’s document existing approaches first and then we can try to extract the least common denominator into a specification. I’m asking CDR implementors that have a notion of tags within their systems to document them here:
To the extent of my knowledge this request targets and .
, can you also fill in that wiki-doc above?
To add tagging to the demographic spec, we need to get a better idea of how it might be used. First question is: what are the tags attached to? To answer this, we probably need to return to the question of a logical ‘repository' or ‘system’ holding PARTY instances.
This version is probably still too minimal - but putting it into review to obtain feedback.
I missed the earlier discussions on this topic. I see that many vendors support this, so this obviously has many use cases. However, for me it is quite hard to see what to use this for and what not to use this for. For example, for some of the things solved by tags, one could also use folders or links. This adds another option to that choice.
Do we need some explanation about the reason for the existence of tags, plus perhaps guidelines as for when to use tags and when to use folders or links?