search

buda-base / owl-schema

BDRC Ontology Schema
11 stars 2 forks source link

non-historical agents #102

Closed eroux closed 5 years ago

eroux commented 5 years ago

I'm working with DILA on the migration of their dataset. The property that cannot be migrated is the 'historical' boolean for persons. While we could imagine having such a boolean in the ontology, I think it might be helpful to think a bit more broadly about this. There are many types of agent entities that sometimes overlap:

I'm really unsure how to encode that, mabe having something like:

:Entity
    :Agent          (all agents)
        :Person    (historical)

and then associate different... types ? roles? to agents... wdyt?

eroux commented 5 years ago

There is also some nice and more detailed use cases in

https://docs.google.com/document/d/1cOnfnsarkyFLcEyScJREWy22n7YA9gMAMG4EUkzQb6w/edit

xristy commented 5 years ago

I've added, as you suggest, :Agent and a top-level hierarchy of sub-classes that we can extend downward to accommodate various distinctions such as you've listed above:

:Entity
    :Agent
        :SingleAgent
            :Person 
            :AhistoricalAgent
        :Organization
            :Corporation

I would think that we would want to migrate the various :Topics that represent different sorts of :AhistoricalAgent.

See also #103.

eroux commented 5 years ago

perfect thanks! I agree we want to migrate some topics yes. I'll think of some properties we could use to represent the information recorded in the Jataka database