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

epo:ResultNotice is defined in restrictions but not in the core #114

Closed
dachafra opened this issue Oct 7, 2022 · 3 comments
Closed

epo:ResultNotice is defined in restrictions but not in the core #114

dachafra opened this issue Oct 7, 2022 · 3 comments
Assignees
Labels
type: bug Something implemented incorrectly in a release
Milestone

Comments

@dachafra
Copy link

dachafra commented Oct 7, 2022

The class epo:ResultNotice is defined in the restrictions file but not in the core.

@costezki
Copy link
Collaborator

costezki commented Oct 25, 2022

  1. When the Notice is generated (this is a TED-SWS issue to be implemented), import the core ontology and notice extension.
  2. Fix the wrong namespace "http://unknown.domain/for/prefix#ResultNotice" in the generated module. This is done by augmenting the list of known/defined prefixes in the configurations file.

@costezki costezki transferred this issue from OP-TED/ePO Oct 25, 2022
@costezki costezki added the type: bug Something implemented incorrectly in a release label Oct 25, 2022
@andreea-pasare
Copy link
Contributor

In the prefixes configuration file (https://github.com/OP-TED/model2owl/blob/master/config/ePO-default/namespaces.xml):

Please let me know if there are other unknown prefixes so we can handle those as well.

@costezki
Copy link
Collaborator

costezki commented Nov 4, 2022

The prefix issue is fixed. The update will be reflected in the next delivery.
The definition of epo:ResultNotice has been clarified with David.

@costezki costezki added this to the 2022-Q4 milestone Nov 4, 2022
@costezki costezki closed this as completed Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something implemented incorrectly in a release
Projects
None yet
Development

No branches or pull requests

4 participants