Property talk:P2561
Documentation
- Start a query
- Current uses
- Statistics by class
- String length
- Language of strings
- List of qualifiers
- Count
name the subject is known by. If a more specific property is available, use that
List of violations of this constraint: Database reports/Constraint violations/P2561#Entity types
List of violations of this constraint: Database reports/Constraint violations/P2561#Scope, SPARQL
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
| ||||||||||||||||||||||||||
alias?[edit]
How is this different from adding an alias? --Laboramus (talk) 01:29, 1 March 2016 (UTC)
- one difference is that with a Property you can also attach qualifiers — e.g. to give the dates when a name was used --Oravrattas (talk) 07:10, 9 March 2016 (UTC)
Language (mandatory)[edit]
@Joshbaumgartner, Micru: Why is language mandatory? If my name is Kolja Garibaldi and I was born in France, do I have a "French" or "Russian-Italian" name? --Kolja21 (talk) 22:10, 11 June 2018 (UTC)
- It is a monolingual text datatype, which forces a language to be applied. I'm not convinced it wouldn't have been better to be a simple string. Josh Baumgartner (talk) 22:18, 11 June 2018 (UTC)
- If you are not convinced, you should be able to answer my question. --Kolja21 (talk) 22:27, 11 June 2018 (UTC)
- @Kolja21: The language of the name depends on the context it is used. For instance when you speak in French and you say "Kolja", then your name is in French. When you speak in Italian and you say "Kolja" then your name is in Italian. When you speak French and you say your name as you would say it in Italian, then your name is in Italian. The language of the name doesn't say anything about the origin of the name, but still is interesting to record it as names mutate when they are imported from one language into another.--Micru (talk) 07:43, 12 June 2018 (UTC)
- If you are not convinced, you should be able to answer my question. --Kolja21 (talk) 22:27, 11 June 2018 (UTC)
- Language is mandatory because a name always has at least one language. For the record, if a specific languages is not appropriate, there is always the code mul for multilingual or und for undetermined. Cheers, VIGNERON (talk) 07:58, 11 March 2019 (UTC)
For person names only?[edit]
Not stated, but it seems to me that this property is limited to persons. Is that correct? I would like to use it on items like places in Ggreenland, have had an earlier Danish name. Aliases will not be usefull for many purposes and queries. Pmt (talk) 14:47, 13 July 2018 (UTC)
- No, you can add it to places as well. Even if you do, I think you should add it as alias too, otherwise internal search wont find it. Not sure if adding them only as Lexemes would be a good idea.
--- Jura 15:18, 13 July 2018 (UTC) - Not for person names only in the original proposal it was stated that this would be a super-property for all the name type properties:
User:Joshbaumgartner, https://www.wikidata.org/wiki/Wikidata:Property_proposal/Archive/45#P2561
So I think this is indeed a super-property and probably should have a statement of title (P1476) subproperty of (P1647) name (P2561) --Thadguidry (talk) 18:34, 23 July 2022 (UTC)
conflicts-with constraint[edit]
@Ivan_A._Krestinin: name (P2561) is used for a special nameforms used in the Swedish parlament used in Swedish PM (Q110382440) see example Q6022267#P2561 or query --> the new restrictions gives us warnings
- Error: conflicts-with constraint "An entity should not have statements for both name and given name"
- Q6026789#P2561
- Salgo60 (talk) 03:37, 5 February 2022 (UTC)
name as qualifier[edit]
Why shouldn't name be used as a qualifier, eg. with different uses of an object in different periods? Lutzto (talk) 10:25, 27 February 2022 (UTC)