-
Notifications
You must be signed in to change notification settings - Fork 6
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
225 235 Add madeBySystem and madeExecution #226
Conversation
…xioms to ssn-* modules Add usedActuatingProcedure usedObservingProcedure usedSamplingProcedure to sosa-* modules, and sub-property axioms to ssn-* modules Add actsOn to sosa-actuation
I don't see technical issues with this implementation (yet), but I would like to think a bit more on this from higher level of abstraction. The ontology is moving towards a set of four very similar graphs, centered on the four main classes:
Those classes are well defined and understood, not only by those of us in the group, but also to users in general that may deal with concerned datasets in this context. However, the semantic nuances between the sub-classes of Procedure and Property are less evident, i.e.:
Are all those classes necessary? Do they all have a well defined and unique semantic definition? Finally coming to the predicates: are they all semantically unique? Or is a single predicate object property between Execution and Procedure enough to convey that relation in all sub-graphs? I would rather have a leaner ontology, with as many elements as possible at the Execution (abstract?) level, only to be specialised in case of objective semantic differences. Thoughts? |
# Conflicts: # ssn/index.html
# Conflicts: # ssn/images/Actuation.png # ssn/images/Observation.png # ssn/images/System.png # ssn/images/System.svg # ssn/index.html # ssn/rdf/ontology/core/sosa-actuation.ttl
Do we need the specializations |
# Conflicts: # ssn/chapters/Actuation.html # ssn/chapters/Common.html # ssn/chapters/Observation.html # ssn/chapters/Sampling.html # ssn/images/Actuation.png # ssn/images/Execution.png # ssn/images/Observation.png # ssn/images/System.png # ssn/index.html # ssn/rdf/ontology/core/sosa-actuation.ttl # ssn/rdf/ontology/core/sosa-common.ttl # ssn/rdf/ontology/core/sosa-observation.ttl # ssn/rdf/ontology/core/sosa-sampling.ttl # ssn/rdf/ontology/core/sosa.ttl # ssn/rdf/ontology/core/ssn-actuation.ttl # ssn/rdf/ontology/core/ssn-observation.ttl # ssn/rdf/ontology/core/ssn-sampling.ttl
I've copied this discussion back to issue #225 - better to have it there rather than on the PR. |
…espace Additional text on Execution and System to emphasize that they are generalized/abstract classes and that individuals in applications should use sub-classes. New diagram in overview establishing the generalized Execution pattern.
Add notes about non-use of abstract properties
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the text clarification should be emphasised as SHOULD NOT
@rob-metalinkage - fixed |
ssn/images/Execution.svg
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still has specialized Procedure Types
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SVG all obsolete. Ignore (removed).
…ysystem # Conflicts: # ssn/chapters/Common.html # ssn/chapters/OMS-alignment.html
Changes implemented as requested
to sosa-common, and sub-property axioms to ssn-* modules
Add usedActuatingProcedure usedObservingProcedure usedSamplingProcedure to sosa-* modules, and sub-property axioms to ssn-* modules
Add actsOn to sosa-actuation
Closes #225