Wikidata:Property proposal/nimi.li id

‎nimi.li id edit

Originally proposed at Wikidata:Property proposal/Lexemes

   Done: ‎nimi.li ID (P12513) (Talk and documentation)
Descriptionnimi.li id
Representsnimi.li (Q122958648)
Data typeExternal identifier
Domainlexeme
Example 1kijetesantakalu (L641772)kijetesantakalu
Example 2nimi (L220728)nimi
Example 3waso (L220807)waso
Example 4tenpo lete (L1235761)compounds#tenpo lete
Example 5ala (L220623)ala (identifier shared with lexeme (P9531))
Example 6ala (L220624)ala (identifier shared with lexeme (P9531))
Sourcehttps://nimi.li/
Number of IDs in source246
Formatter URLhttps://nimi.li/$1
Single-value constraintyes
Distinct-values constraintno

Motivation edit

The id can be aquired by clicking the more link on the upper right corner of a lexeme on the front page. –Shisma (talk) 09:02, 28 January 2024 (UTC)[reply]

I proposed to the developers to allow deep links to make this property truely Distinct-value. –Shisma (talk) 16:52, 28 January 2024 (UTC)[reply]

issue was rejected. So there goes our distinct value constraint 💩 –Shisma (talk) 08:36, 29 January 2024 (UTC)[reply]

Discussion edit

@Ookap, Blahma, Spenĉjo, Theki, Venca24: @Aleks Andre, Binarycat32, Robin van der Vliet: speakers of Toki Pona –Shisma (talk) 09:07, 28 January 2024 (UTC)[reply]

toki a! I'd definitely support this being added as a property. nimi.li is a great website that is used by many within the toki pona community, and its addition to Wikidata would be welcomed, at least by me! jan Osuka (talk) 22:07, 28 January 2024 (UTC)[reply]
I suppose I should ping more tokiponists to add to the discussion: @Tbodt, Tamzin. jan Osuka (talk) 22:30, 28 January 2024 (UTC)[reply]
  Support this! nimi.li, as well as Linku, are great resources and well respected in the community. JnpoJuwan (talk) 22:35, 28 January 2024 (UTC)[reply]
of note is that nimi.li internally uses the sona Linku dataset, but adds 8 marginal words (which Linku will probably have too when the "sandbox" rolls out) and compounds from the ku surveys (which aren't planned for Linku to my knowledge) ~Sobsz aka hecko (talk) 23:15, 28 January 2024 (UTC)[reply]
  Support, i don't think we have an external id for toki pona words, and this is the best tp dictionary i am aware of.
however, i'm not sure about the distinct-values constraint, most toki pona words i've seen have a seperate lexeme for noun, verb, and adjective definitions. perhaps each word should have only a single lexeme, calling these homoglyphs is kind of a strange way of modeling toki pona. has anyone made a lexeme guide for toki pona yet? Binarycat32 (talk) 03:32, 29 January 2024 (UTC)[reply]
I would say that using a parts of speech analysis for toki pona is a little odd. Any word can really be any part of speech, and can mean really whatever you interpret it as in each of these spots (as long as it fits in the semantic space of the word). jan Osuka (talk) 04:22, 29 January 2024 (UTC)[reply]
I updated the proposal to reflect that –Shisma (talk) 08:36, 29 January 2024 (UTC)[reply]
@Binarycat32: which grammatical category would you add to these lexemes? – Shisma (talk) 08:42, 29 January 2024 (UTC)[reply]
I would use content word (Q789016), this is what most toki pona speakers would describe non-particle words as, and I believe it already is a superclass of noun, adjective, etc
If other toki pona speakers here agree, I could perhaps write up a simple guide toki pona lexemes under Wikidata:Lexicographical_data/Documentation/Languages. Binarycat32 (talk) 23:01, 30 January 2024 (UTC)[reply]
@jan Osuka thoughts on categorizing all toki pona words into either grammatical particle (Q184943) or content word (Q789016)?
of course we would also need to decide what to use for loanwords, or if those should be included at all. Binarycat32 (talk) 23:06, 30 January 2024 (UTC)[reply]
I do like that classification. Perhaps we could also have second lexemes for preverb and preposition definitions? Also, nanpa may be in both categories, so I suppose we'd need to have two lexemes for that too. jan Osuka (talk) 23:43, 30 January 2024 (UTC)[reply]