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

[Function] Move parts from IAML MoP vocabulary #44

Open
4 tasks
pasqLisena opened this issue Mar 11, 2018 · 3 comments
Open
4 tasks

[Function] Move parts from IAML MoP vocabulary #44

pasqLisena opened this issue Mar 11, 2018 · 3 comments
Assignees
Labels

Comments

@pasqLisena
Copy link
Contributor

Parts of IAML MoP vocabulary describe indeed functions:

Most of them are already in the function vocabulary (table), so I suppose that the modelling group already spotted this. Anyway we should put an effort for mantaining all the languages and notes.

Roadmap

  • Make sure that all the concepts in MoP are in Function
  • Add a column in the table for the other languages and move them
  • Add a column in the table for the skos:exactMatch and move them
  • Remove the concepts from MoP

We can avoid to keep that skos:editorialNote "English term is preferred globally." that is repeated for each concept. While is useful for instrument (see traditional ones), it is weird for functions.


Related comment:

@ccecconi
Copy link
Contributor

ccecconi commented Mar 12, 2018

Make sure that all the concepts in MoP are in Function

We chose to keep only the terms that could be used in our data --> IAML is a different vocabulary.
Why should we keep the same functions ?

Add a column in the table for the other languages and move them

ok. We'll do that

Add a column in the table for the skos:exactMatch

ok. We'll do that

Remove the concept from MOP"

what do you want to say here ? We'll never use these terms as MOPs in our data but they are part of the IAML vocabulary. Do we really have to remove them ? In that case, what's the point of linking them with our functions ?

"Chef éclairagiste" / "éclairagiste"

The term in our vocabulary is more generic and contains the two terms of IAML

We can avoid to keep that skos:editorialNote "English term is preferred globally."

OK

@pasqLisena
Copy link
Contributor Author

I will refer here to "MoPs that are actually functions" as "bad MoPs".

We chose to keep only the terms that could be used in our data --> IAML is a different vocabulary.
Why should we keep the same functions ?

Not clear the question to me, but I interpret it as "The function vocabulary is autonomous, it follows different rules. So it is normal that some bad MoPs do not appears as function".

This is fair enough BUT there is a practical issue:
what will happen to concepts used so far as bad MoPs that have not a correspondance in functions?

Stupid example. Suppose that you decide about not transferring the conductor to function.
Should we continuing declaring it in real data as MoP?

Remove the concept from MOP

what do you want to say here ? We'll never use these terms as MOPs in our data ...

Consider that BnF normally refers with codes to that vocabulary. Normally for casting, but what about BIB records?

... but they are part of the IAML vocabulary.

Our IAML vocabulary is not an "hard copy" of the IFLA official one. It is an export that we autonomously generated from our sources (tables, online resources) and we have the full control on it (infact we use OUR namespace http://data.doremus.org/something). The 2 vocabularies (IFLA one and our one) are not the same (our one is more rich ✌️ ).
("Hard copy" is how we imported MIMO, Rameau, we use them "as is", without any improvement from our side)

SO, if we consider them bad MoPs, we should remove them from MoPs (on my opinion).

In that case, what's the point of linking them with our functions ?

I was not speaking about an interconnection between DOREMUS-IAML-MOP and DOREMUS-FUNCTION, but between IFLA-MOP and DOREMUS-FUNCTION.
We link them with IFLA one anyway (interconnection is always good).

"Chef éclairagiste" / "éclairagiste"

The term in our vocabulary is more generic and contains the two terms of IAML

Good. I suppose that the labels in other languages of éclairagiste will be transferred to the function vocabulary.
What about the labels of Chef éclairagiste? Should them be transferred as altLabel?

@ccecconi
Copy link
Contributor

ccecconi commented Jun 13, 2018

Consider that BnF normally refers with codes to that vocabulary. Normally for casting, but what about BIB records?

The BnF doesn't use these codes in the bibliographic records.

SO, if we consider them bad MoPs, we should remove them from MoPs (on my opinion).

We agree. We should remove :

What about the labels of Chef éclairagiste? Should they be transferred as altLabel?

No

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants