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

[IAML/GENRES] Adding minimal hierachy #39

Open
pasqLisena opened this issue Sep 11, 2017 · 6 comments
Open

[IAML/GENRES] Adding minimal hierachy #39

pasqLisena opened this issue Sep 11, 2017 · 6 comments
Assignees

Comments

@pasqLisena
Copy link
Contributor

pasqLisena commented Sep 11, 2017

Hello,
I would like to add the following relations to the vocabulary and create 2 new concepts.
The reason are more or less the same of the ones of the issue #38 .

<http://data.doremus.org/vocabulary/iaml/genre/lit> skos:narrower <http://data.doremus.org/vocabulary/iaml/genre/vrl> , <http://data.doremus.org/vocabulary/iaml/genre/lid> , <http://data.doremus.org/vocabulary/iaml/genre/lod>, <http://data.doremus.org/vocabulary/iaml/genre/lyh> .

<http://data.doremus.org/vocabulary/iaml/genre/i> a skos:Concept ;
skos:prefLabel "Instrumental music"@en ;
skos:narrower
<http://data.doremus.org/vocabulary/iaml/genre/tri>, <http://data.doremus.org/vocabulary/iaml/genre/aub> , ...

<http://data.doremus.org/vocabulary/iaml/genre/v> a skos:Concept ;
skos:prefLabel "Vocal music"@en ;
skos:narrower
<http://data.doremus.org/vocabulary/iaml/genre/czp>, <http://data.doremus.org/vocabulary/iaml/genre/due> , ...

My points:

  • lit has the note "When any more specific code can’t be used"
  • vrl, lod, lyh have a skos:note "Liturgical", while lid has it in the name
  • lots of concepts have the skos:note "Instrumental" or "Vocal"

I have also to say that we have some concept from other vocabularies that we can reuse:

@rtroncy
Copy link
Contributor

rtroncy commented Sep 11, 2017

I'm not questioning the need for those new skos:Concept. However, I found awkward to define those new terms in the <http://data.doremus.org/vocabulary/iaml/genre/> concept scheme because there are not (yet) defined in IAML.

Should we try first to ask IAML whether they would be interested to add those concepts too? If not, should we not define those concepts in the reconciled concept scheme (pivot graph) that aligns IAML with other genre vocabularies?

@pasqLisena
Copy link
Contributor Author

Should we try first to ask IAML whether they would be interested to add those concepts too?

It would be interesting. It needs a discussion in the modelling group.

If not, should we not define those concepts in the reconciled concept scheme (pivot graph) that aligns IAML with other genre vocabularies?

Yes, but the pivot graph does not exists in this moment :)

@rtroncy
Copy link
Contributor

rtroncy commented Sep 12, 2017

@kgtodorov Can you let us know the status regarding the validation of all alignments between controlled vocabularies, and in particular, for genres and mop? Do we have a chance to have a reconciled graphs before the next general meeting?

@kgtodorov
Copy link
Contributor

Luckily, my student in charge of that is back to work after some hard times. We have now all new alignments (mop and genres), which are of significantly higher coverage than the old ones thanks to the new algorithm using directly SKOS (so no conversion to OWL). However, we need to go again through the validation process before we leverage the final alignments, this would definitely take more time than the couple of weeks before the AG.

@pasqLisena
Copy link
Contributor Author

So I postpone it after #22

@pasqLisena pasqLisena self-assigned this Sep 12, 2017
@pasqLisena
Copy link
Contributor Author

pasqLisena commented Oct 5, 2017

Modeling meeting decisions:

  • add it in the pivot vocabulary
  • propose to IAML the adoption of this hierarchy (I am writing an email with Francoise)

pasqLisena added a commit that referenced this issue Oct 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants