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

Add 2 new properties for fuzzy positions #38

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ljgarcia
Copy link

It is currently not straight forward to model possible positions for OneOfPosition, see #37. The new property possiblePositions makes it simpler.
The second new property for FuzzyPosition, probability, cover cases as those of PTMs in IntAct where a probability is assigned to a fuzzy position.

It is currently not straight forward to model possible positions for OneOfPosition, see OBF#37. The new property possiblePositions makes it simpler.
The second new property for FuzzyPosition, probability, cover cases as those of PTMs in IntAct where a probability is assigned to a fuzzy position.

:possiblePosition
rdf:type owl:ObjectProperty ;
rdfs:comment "One of the possible positions listed for a OneOfPosition element."^^xsd:string ; ;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line ends with ; ; instead of just one. could lead to issues.

rdfs:domain :OneOfPosition ;
rdfs:range :Position .

:probability
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the probability part should come in a different pull request. I think for clean modelling it should be inverted and should not be attached to :FuzzyPosition as even an :ExactPosition can have a probability funcion associated with it.

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

Successfully merging this pull request may close these issues.

2 participants