Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't create subClassOf Task, but rather narrower concepts of GSBPM subProcesses #119

Open
tfrancart opened this issue Oct 13, 2023 · 0 comments

Comments

@tfrancart
Copy link
Collaborator

The spec reads as follow:

In certain cases however, it could be useful to define standard sub-classes of Task for some widely used and specific types of tasks, for example record linkage or hot-deck imputation

While it is not impossible of course to declare subClassOf Task, in practice it is easier to extend the loose-typing typing, here GSBPM, with new Concepts, that would be declared skos:broader to some more generic GSBPM concepts.

The additionnal information to be captured (e.g. methodology, or relevant GSIM input/output) is then declared on that new Concept.

Declaring a new OWL class only make sense if that new class can hold additionnal information in addition to what can be expressed on the superclass.
For this reason, I even question the utility to introduce the class "Task", while using the class "StatisticalActivity" is enough, at any level of granularity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant