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

feat: Extend the model of Segment with additional properties (DEV-3505) #3193

Conversation

BalduinLandolt
Copy link
Collaborator

@BalduinLandolt BalduinLandolt commented Apr 16, 2024

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

  • build/chore: maintenance tasks (no production code change)
  • docs: documentation changes (no production code change)
  • feat: represents new features
  • fix: represents bug fixes
  • perf: performance improvements
  • refactor: represents production code refactoring
  • test: adding or refactoring tests (no production code change)
  • deprecated: Deprecation warning (ideally referencing a migration guide)

Basic requirements for bug fixes and features

  • Tests for the changes have been added
  • Docs have been added / updated

Does this PR introduce a breaking change?

  • Yes

Does this PR change client-test-data?

  • Yes

@BalduinLandolt BalduinLandolt self-assigned this Apr 16, 2024
Copy link

linear bot commented Apr 16, 2024

@BalduinLandolt BalduinLandolt marked this pull request as ready for review April 16, 2024 14:58
owl:maxCardinality "1"^^xsd:nonNegativeInteger ] ,
[ rdf:type owl:Restriction ;
owl:onProperty :hasDescription ;
owl:minCardinality "0"^^xsd:nonNegativeInteger ] ,
Copy link
Collaborator

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.

Copy link
Collaborator Author

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.

Copy link
Collaborator

@mpro7 mpro7 left a 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?

@BalduinLandolt
Copy link
Collaborator Author

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

Copy link
Contributor

@siers siers left a comment

Choose a reason for hiding this comment

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

schema.org – interesting.

@BalduinLandolt BalduinLandolt merged commit 54a439c into main Apr 17, 2024
11 checks passed
@BalduinLandolt BalduinLandolt deleted the feature/dev-3505-add-additional-properties-to-segment-in-knora-base branch April 17, 2024 08:21
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.

None yet

4 participants