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
Is an appellation unique to its bearer? #25
Comments
I think from a social standpoint we do share names. For example, even though parents individually name their children, first names have trends and are linked to socio-historical elements such as celebrities or rulers naming their own children, beloved characters in works of fiction being used as inspiration, etc. As such, humans are assigning names en masse in a way and this act is closely tied to their place in society. Cognitively speaking, we use names uniquely I believe. We might know many Johns, but if we do not specify which one we are talking about what comes to mind is an aggregation of all the Johns we know, not a class of Johns with the single characteristic of sharing a name. So generally speaking both conceptualizations are accurate with the individualized URI being closer to cognitive reality and the shared one closer to social reality. I am not sure what would be the implications of each pattern from an efficiency point of view, however? All this is to give the background to my view of this: if linking people by their name is mostly a social evaluation of trends and patterns, it seems more statistical in nature than semantic. Moreover, the semantics are more closely resembling cognition than social patterns I believe (from a functional standpoint). As such, and I have very limited knowledge on this, it would seem to me that using individualized URIs would be closer to how we function in everyday life. In other words, the absence of a link between two Johns illustrates how they do not put forth an "intentional sharing" of their name but an incidental one. |
By discussing with Ludovic, we realized that the |
interesting discussion. The correct pattern is 2. There would be no point to generate an appellation node if you did not say that one name was one name. The point of an appellation node is to identify the name in itself independent of the entity it names. If you land on a name appellation node/record then you want to know the things that it names. You would lose that functionality by making my 'George Bruseker' different than that of the other 'George Bruseker'. It is true that you put a preferred identifier type on a name sometimes. Since the data will be loaded in a named graph you can see whose preference via the named graph. To be even more specific you should even create an attribution node so that you can say who says it is preferred. If you are not interested in the name itself then you can just put an rdfs label on the actor/object itself and save yourself trouble (though I wouldn't recommend it). |
@Habennin indeed you are quite right, having a separate appellation for each actor is anti-lod logic. We would still need to be careful, as some names could have different parts. In the case of @KarineLeonardBrouillet "Léonard Brouillet" is her last name, but another Karine Léonard Brouillet could have "Léonard" as a middle name, which means it would be two separate appellations. |
I think you'll find that in a lot of data about names and identifiers you have specific documentation of who said it within your source data. In that case it is a case of 'quoted speech', so you would most easily use E13 |
From the discussion during the meeting of the 20th of December, we've decided to chose the proposition 1 for the TM 2.0, where the appellation of an actor is unique to it bearer, as it seems easier to manage at first. |
I read the thread once again more carefully and I would like to clarify something. For the moment, we keep option 1 because it was easier to implement according to our delay. That said, I highly recommend to go with option 2 for the next version. Some reasons:
|
So I think option 1 is better for CIC |
Thanks @VladimirAlexiev, For the moment, our model allows to breakdown an appellation in different parts. However, the part type is managed using a vocabulary. Thank you for the advice about first/last name, we will take care of recommending a proper set of terms. For the moment we will go with option 1. I don't think we are going against the scope note of |
I also think option 1 doesn't make I believe E13 and Named graphs are a distraction in this case because often preferred/non-preferred is "universal knowledge" and you don't know or need to record who expressed that preference. And just because a museum recorded it, doesn't necessarily mean they prefer it. To record more details about an Appellation, you can use frbroo's Name Use class. |
By reading this issue again prior to the Semantic Committee meeting, it seems that the shared appellation is the most semantic. But two issues seems of importance: What to do with the Preference Type?As stated above, some appellations are preferred to some actors, and some are non preferred. The preference of an appellation is directly linked to the appellation in the TM 2.0. If the appellations are shared by actors, that mean that some appellations would have multiple preference types. How to differenciate to which actor the preference type is linked to? Let's take an example to illustrate that. Actor number 64862 is called John Doe. This appellation is therefore the preferred appellation for that person. Actor number 11603 is called John William Doe, but can some times be refered to as John Doe. Therefore, the appellation John Doe is a non-preferred one for that other person. In this example, the appellation John Doe will have two The question is: How to specify that the Preferred Type is for the Person 64862 and the Non-Preferred Type is for Person 11603? I see two solutions for that:
Another solution, of course, would be to NOT share the appellations between actors. Link the Name Use Activity to the ActorIn the TM 2.0, the If we use shared appellation between actors, there is nothing that links the
|
After discussing this with members of CHIN's semantic committee, we have come to the conclusion that there is no immediate and foreseeable use to the use of a "shared appellation" approach to the application of the appellation. That said, it might be relevant in the future for certain disciplines such as genealogy. For the moment, CHIN will continue implementing the "individual appellation" approach, although this position might be reassessed if relevant use cases establish the need to do so. |
@KarineLeonardBrouillet glad you took that decision! |
There is two way of understanding appellations of actors:
To exemplify this, we could have two homonyms, Person A, called John Doe and born in Montreal and Person B, also called John Doe and born in Ottawa. In the first conceptualization, the appellation of person A is unique to him, and therefore the URI of each appellation John Doe is unique (mic.ca/uri/appellation/1234 and mic.ca/uri/appellation/6573). In the second conceptualization, because person A and B are being called with the same first and last name, they both share the same appellation that has just one URI (mic.ca/uri/appellation/john_doe).
What are the benefits of linking people by their name? I'm afraid that it would create meaningless links?
What are the benefits of not linking people by their name?
The text was updated successfully, but these errors were encountered: