-
Notifications
You must be signed in to change notification settings - Fork 18
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
feat: Extend the model of Segment
with additional properties (DEV-3505)
#3193
feat: Extend the model of Segment
with additional properties (DEV-3505)
#3193
Conversation
owl:maxCardinality "1"^^xsd:nonNegativeInteger ] , | ||
[ rdf:type owl:Restriction ; | ||
owl:onProperty :hasDescription ; | ||
owl:minCardinality "0"^^xsd:nonNegativeInteger ] , |
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.
question: A Segment
may have more than one description?
I would have expected a single description to be optional.
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.
That was my first assumption too, but turns out that projects may want to be able to describe different aspects of a Segment as different descriptions. I'd have been happy either way, but this aligns with how EKWS modelled their Sequences, which I found reason enough to go that way.
…o-segment-in-knora-base
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.
Should this be merged w/o added documentation, knowing that Friday the release will happen?
looks like this is approved, so I can write documentation for it right away |
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.
schema.org – interesting.
Pull Request Checklist
Task Description/Number
Issue Number: DEV-3505
This PR adds a number of properties to
knora-base:Segment
in hopes that most projects will find their needs satisfied by this, rather than needing subclasses of Segment with custom properties.For all of them, mappings to popular external ontologies have been added, in hope that this will be a step towards making data more interoperable; furthermore this backs up the claim that this is supposed to be a reasonable set of properties for the concept of segments.
PR Type
Basic requirements for bug fixes and features
Does this PR introduce a breaking change?
Does this PR change client-test-data?