gist:allocatedBy

[DougalW]

In our enterprise ontology we often want to use this Object Property to link a source system to an ID for provenance reasons. It would be good if the GIST System class was also part of the range of this object property i.e. 'Intellectual Property' or Organization or Person or System

[uscholdm]

This is a good point, we have struggled with the idea of 'something that has the capacity to perform an action", which as you point out should include computers and other (but not all) kinds of system.

[rjyounes]

I advocate for a class Agent with subclasses (perhaps not exhaustive) Person, Organization, and SoftwareAgent, which would allow us to define Agent as the range of allocatedBy. See #132.

Addendum: I don't recommend this anymore.

[DougalW]

Agent as you describe it would work.

[uscholdm]

I think the most central idea behind the notion of 'agent' is the capacity to carry out a task. There are a lot of other dimensions, like autonomy and intention etc. But the core is about 'doing'. Because the term 'agent' is so overloaded, I once had a class for this idea called "Doer". A terrible name, but at least is was fairly accurate.

[uscholdm]

@rjyounes

I advocate for a class Agent with subclasses (perhaps not exhaustive) Person, Organization, and SoftwareAgent, which would allow us to define Agent as the range of allocatedBy. See #132.

I recommend against attempting an exhaustive definition. In my experience its ends up being a fools errand - something new tends to show up.

[rjyounes]

Agreed.

[rjyounes]

DEFERRED: until gist software ontology is released.

[uscholdm]

@rjyounes DECISION: Close. AllocatedBy had been updated to take this into account.

gist:isAllocatedBy
    a owl:ObjectProperty ;
    rdfs:isDefinedBy <https://w3id.org/semanticarts/ontology/gistCore> ;
    rdfs:range [
        a owl:Class ;
        owl:unionOf (
            gist:IntellectualProperty
            gist:Organization
            gist:Person
        ) ;
    ] ;
    skos:definition "Relates the subject to whomever or whatever assigns or distributes it."^^xsd:string ;
    skos:example "A U.S. Social Security number is allocated by the U.S. Social Security Administration. The media type https://www.iana.org/assignments/media-types/text/csv is allocated by the Internet Assigned Numbers Authority (IANA)."^^xsd:string ;
    skos:prefLabel "is allocated by"^^xsd:string ;
    skos:scopeNote "The allocator may be a person, organization, or automated process."^^xsd:string ;
    gist:domainIncludes
        gist:Category ,
        gist:ID
        ;
    .

[uscholdm]

@rjyounes On second thought, should we add gist:System to the union defining the range, and all the restrictions using gist:allocatedBy?

[rjyounes]

I think the range should remain open as a generally useful predicate. I tend to use it for a wide variety of things.

[uscholdm]

I think the range should remain open as a generally useful predicate. I tend to use it for a wide variety of things.

That is a separate question, we already have a limited range. Given it is limited, the question for this issue is whether System should be added. The broader question of fixing the range of predicates might be better in a separate issue.

[uscholdm]

See also: #339 and #517