Should Tag use uniqueText rather than containedText?

[rjyounes]

Copied from https://github.com/semanticarts/gistHR/issues/134 - it was meant to be added here instead.

Since we are modeling folksonomy terms, tags, and keywords, each should have only one text string.

Relates to PR #989 and issue #372, where tagText was replaced with containedText.

This does not result in an inference change since there is no formal definition related to the predicate. The recommended practice can be added to a scope note.

[rjyounes]

Discussion on https://github.com/semanticarts/gistHR/issues/134:

@Jamie-SA comment:
I'm thinking that this is more of a restriction than necessary and might prevent some valid uses. For instance, what if you want to have several different groups of Tags, you may want them to be unique within the group, but not necessarily globally unique.

@rjyounes response:
This is not what uniqueText means: it doesn't mean the text is unique to the tag, but rather the tag can have only one text string. See the definition: "The unique string value of some content object; i.e., there is no possibility of having more than one value" and the fact that we use it with IDs when we certainly are not claiming the uniqueness of the id string across all ID objects.