Property talk:P11130

Latest comment: 1 year ago by Infrastruktur in topic The # symbol in identifiers is causing links to fail

Documentation

Merriam-Webster online dictionary entry
identifier for an entry for a word in the Merriam-Webster online dictionary
Associated itemMerriam-Webster (Q585329), Merriam-Webster (Q585329)
Applicable "stated in" valueMerriam-Webster online dictionary (Q52055677)
Data typeExternal identifier
Allowed values[A-Za-zÀ-ž0-9-\/\,\.\' \-\#]+
Exampleno label (L4177)let
no label (L3674)spoon#dictionary-entry-1
no label (L474913)Greek
no label (L337067)germane
no label (L44134)24/7
Sourcehttps://www.merriam-webster.com/dictionary
Formatter URLhttps://wikidata-externalid-url.toolforge.org/?url=https%3A%2F%2Fwww.merriam-webster.com%2Fdictionary%2F%251&exp=%28.%2A%29&id=$1
https://www.merriam-webster.com/dictionary/$1
Related to country  United States of America (Q30) (See 762 others)
See alsoOxford English Dictionary entry ID (pre-July 2023) (P5275), Collins Online English Dictionary entry (P11230), Dictionary.com entry (P11228), The Britannica Dictionary entry (P11263), Cambridge Dictionary entry (American English) (P11423), Cambridge Dictionary entry (British English) (P11422)
Lists
Proposal discussionProposal discussion
Current uses
Total1,922
Main statement1,69988.4% of uses
Qualifier50.3% of uses
Reference21811.3% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Allowed entity types are Wikibase lexeme (Q51885771), Wikibase sense (Q54285715), Wikibase item (Q29934200), Wikibase form (Q54285143): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P11130#Entity types
Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P11130#Scope, SPARQL
Format “[A-Za-zÀ-ž0-9\/\,\.\' \-\#]+: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P11130#Format, SPARQL
Lexeme language: English (Q1860): this property should only be applied to lexemes with these languages (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P11130#language

Words with only one entry (e.g., germane) edit

I'm not sure how to form the identifier for words in the dictionary that don't have more than one entry. For example: germane. The URL for this is https://www.merriam-webster.com/dictionary/germane. https://www.merriam-webster.com/dictionary/germane#dictionary-entry resolves to the same page, and https://www.merriam-webster.com/dictionary/germane#dictionary-entry-1 does as well, but puts you slightly lower on the page. Should the identifier for this be just "germane" or "germane#dictionary-entry"? UWashPrincipalCataloger (talk) 18:28, 25 October 2022 (UTC)Reply

yes, I think it should just be 'germane'. Also, even in cases of multiple entries under the same page-level URL, as in 'let', I think it would be simpler for most Wikidatans to just type 'let' into the property value, even if it would not bring the reader exactly to the entry we wanted to link to, but require some scrolling.
Alternatively, trying to balance both needs, we might keep 'let' as the property value, but add a qualifier to the claim with the fragment (#) value. Then the URL formatter can construct a correct URL for both types of cases. Asaf Bartov (talk) 23:45, 26 October 2022 (UTC)Reply

The # symbol in identifiers is causing links to fail edit

When you click on this identifier in the Lexeme items, the link fails. I think the # is causing this problem. UWashPrincipalCataloger (talk) 15:05, 26 October 2022 (UTC)Reply

I looked into this. The identifier is stored with the raw hash-sign, but the links you get have url-coding. Some webservers or scripts don't handle this properly and causes problems. The hash-symbol is actually an HTML anchor, it points to the location of a paragraph on a webpage. I would suggest just ditching the hash-sign and everything after it, as it is not needed. But this is a major change so it will need support from the community. An alternative would be to use ArthurPSmith's tool to handle the redirection, this would be a drop-in replacement, but personally I prefer getting rid of the anchors, as they are used for navigation and probably can't be relied upon to be very stable. Infrastruktur (talk) 21:14, 26 October 2022 (UTC)Reply

@Ijon, CristianCantoro, Infrastruktur, The-erinaceous-one, ArthurPSmith: Do you agree with Infrastruktur to just stop using the anchors, or should the redirection tool be employed to solve this issue? UWashPrincipalCataloger (talk) 21:27, 26 October 2022 (UTC)Reply

See above. I think status quo is of course broken, and should be unbroken ASAP. I think expecting editors to figure out this technicality when filling values in would be frustrated by reality, so I point your attention to one of the two alternatives I proposed above. Asaf Bartov (talk) 23:47, 26 October 2022 (UTC)Reply
It has been over a week now. Time to conclude? A "format as regex" statement should be added. Assuming we go with just the word, which characters are allowed? I'm going to add a preliminary one, feel free to update it as needed, or ask me to do it. Infrastruktur (talk) 18:31, 3 November 2022 (UTC)Reply
Return to "P11130" page.