gist:containedText and gist:uniqueText proposals

[rjyounes]

Proposals:

• Make gist:uniqueText a subproperty of gist:containedText [Done in 13.0.0]
• Add gist:Content and gist:ContentExpression to the domainIncludes assertion.
  • Or probably better: replace gist:Text and gist:ID with gist:Content: I'm not sure if it's useful to include subclasses of a class that's the object of domainIncludes. It is redundant, but perhaps there's a value to being explicit.
• Add a scope note indicating that a content object may have multiple containedText assertions, and that whether to do so or not is an implementation-specific choice.
• Definition is poor. Current:

skos:definition "A string that is closely associated with an individual."

This sounds like any resource could have contained text. E.g., do I contain my name? Obviously not.

[rjyounes]

As of gist 13.0.0:

• containedText has subproperties uniqueText and encryptedText.
• ID and MediaType have some uniqueText
• Tag, Text have some containedText. Should Tag instead have uniqueText? See #1003.
• Address does not require containedText. Should it? See #1128.

gist:containedText
    a owl:DatatypeProperty ;
    rdfs:range xsd:string ;
    skos:definition "A string that is closely associated with an individual."^^xsd:string ;
    skos:example
        "The string associated with a tag."^^xsd:string ,
        "The string associated with text content."^^xsd:string
        ;
    skos:prefLabel "contained text"^^xsd:string ;
    gist:domainIncludes
        gist:Tag ,
        gist:Text
        ;
    .

gist:uniqueText
    a
        owl:DatatypeProperty ,
        owl:FunctionalProperty
        ;
    rdfs:subPropertyOf gist:containedText ;
    rdfs:range xsd:string ;
    skos:definition "The unique string value of some content object, to be used when there is no possibility of having more than one value."^^xsd:string ;
    skos:example "The unique string for a vehicle identification number."^^xsd:string ;
    skos:prefLabel "unique text"^^xsd:string ;
    skos:scopeNote "Note that the uniqueness only goes in one direction: a product catalog number might also be an employee ID."^^xsd:string ;
    gist:domainIncludes
        gist:ID ,
        gist:MediaType ,
        gist:Tag ,
        gist:Text
        ;
    .