Meta tags:

Headings (most frequently used words):

property, translation, and, talk, p5972, contents, documentation, as, query, kept, automatically, fill, language, of, work, or, name, p407, large, networks, p5137,

Text of the page (most frequently used words):
the (87), this (41), with (29), #property (26), and (26), for (25), p5137 (18), p5972 (17), sense (17), that (17), items (16), all (15), item (14), other (13), translation (13), constraint (12), language (11), senses (11), talk (10), statements (10), properties (10), data (9), was (9), have (9), reply (9), most (9), comment (9), utc (8), are (8), discussion (8), wikidata (7), from (7), main (7), lexeme (7), some (7), connections (7), which (7), these (7), there (7), not (7), one (7), list (7), create (7), violations (7), search (6), may (6), used (6), number (6), help (6), had (6), them (6), value (6), between (6), translations (6), only (6), can (6), edit (6), label (6), using (5), use (5), page (5), january (5), would (5), graph (5), network (5), same (5), query (5), latest (5), years (5), ago (5), 2018 (5), uses (5), add (4), topic (4), view (4), statement (4), documentation (4), constraints (4), entity (4), values (4), see (4), what (4), should (4), graphs (4), based (4), english (4), still (4), possible (4), following (4), connection (4), could (4), nodes (4), languages (4), another (4), networks (4), links (4), large (4), comments (4), automatically (4), november (4), changes (4), database (4), reports (4), history (4), sitelinks (4), hide (4), move (4), sidebar (4), contents (3), statistics (3), agree (3), 2022 (3), example (3), conflicts (3), scope (3), type (3), such (3), dog (3), resulting (3), get (3), any (3), connected (3), linked (3), meaning (3), added (3), qualifier (3), work (3), name (3), p407 (3), kept (3), more (3), seems (3), exactly (3), random (3), chart (3), claims (3), count (3), tools (3), toggle (2), table (2), privacy (2), policy (2), namespaces (2), available (2), under (2), terms (2), creative (2), commons (2), license (2), last (2), categories (2), lists (2), moved (2), declaration (2), wikibase (2), datatype (2), need (2), corresponding (2), just (2), recently (2), think (2), has (2), been (2), andreasmperu (2), complete (2), then (2), reorganizations (2), fewer (2), overall (2), lost (2), either (2), those (2), fact (2), really (2), semantic (2), might (2), otherwise (2), equivalent (2), liquid (2), water (2), mother (2), wiktionary (2), dutch (2), word (2), does (2), also (2), already (2), lexemes (2), given (2), rather (2), than (2), special (2), long (2), service (2), leads (2), point (2), people (2), way (2), please (2), ping (2), person (2), fill (2), deletion (2), don (2), translatable (2), method (2), better (2), when (2), problematic (2), interwiki (2), preferably (2), make (2), denny (2), but (2), tubezlob (2), kaman (2), vigneron (2), difference (2), lyyy (2), qzzz (2), lxxx (2), projects (2), sparql (2), p279 (2), exceptions (2), specified (2), must (2), hourly (2), updated (2), report (2), types (2), here (2), 136 (2), total (2), current (2), proposal (2), usage (2), fewest (2), link (2), wikipedia (2), lexicographical (2), according (2), chien (2), appearance (2), read (2), log (2), account (2), donate (2), recent (2), new (2), menu (2), access, mobile, cookie, developers, code, conduct, legal, safety, contacts, disclaimers, about, structured, entityschema, text, additional, apply, site, you, attribution, sharealike, cc0, edited, hidden, duplicated, errors, 100000, retrieved, https, www, org, index, php, title, property_talk, oldid, 1570150349, going, limit, guidelines, verbs, adverbs, adjectives, prepositions, tend, háblame, andreasm, part, reorganization, concept, thus, like, others, done, whether, principles, guided, persist, mahir256, reverted, address, latter, two, points, above, respect, reorganized, instead, single, focus, sort, logic, were, chosen, first, genealogical, relationship, paiwan, malay, latin, sicilian, geographical, proximity, german, polish, malayalam, sinhala, relevant, historico, linguistic, relationships, british, sign, danish, kalaallisut, during, connectedness, maintained, finnish, talo, occitan, ostal, through, paths, yet, achieved, direct, got, detriment, three, within, never, removed, principle, rest, someone, wanted, remove, both, lacked, distinguish, change, exists, identify, house, node, none, directly, each, borrowed, practice, non, placing, completely, neglect, power, maintain, without, exhaustive, enumeration, end, promoting, idea, lexicographic, centers, emanates, something, constricted, diversity, simply, scalable, edges, forced, scale, quadratically, involved, linearly, moreover, since, features, preserved, follow, path, predicate, wdt, q45715, merely, redundant, question, across, different, argument, maintaining, revising, removing, aforementioned, situation, occured, quite, few, while, upper, bound, around, now, considerably, larger, pertaining, concepts, often, happens, alongside, things, however, doesn, show, needs, display, 2020, demondays64, nominated, 2019, multichill, assumption, necessarily, transitive, they, always, form, mutually, perfect, group, case, star, off, problems, maintenance, previously, say, explicit, wikipedias, furthermore, hard, obviously, gui, development, jura, depends, how, experiments, good, variants, pair, interested, personally, gloss, field, users, who, requested, duesentrieb, sintakso, true, parts, speech, similar, wikidata_talk, lexicographical_data, archive, cheers, jura1, infovarius, mfilot, blank, second, store, anyway, very, least, maybe, equivalence, notify, before, big, renaming, merge, etc, being, error, applicable, symmetric, q21510862, rare, exist, exception, p2303, listed, subclass, q54828448, certain, allowed, q54285715, included, 138, 141, map, creation, date, deprecated, unknown, novalue, created, identifier, wikis, sample, welsh, cywiki, stored, l3080, l2120, l41496, l87, l189, l3302, template, note, domain, q7553, represents, corresponds, qualifiers, class, start, printable, version, download, pdf, print, export, shortened, url, information, permanent, related, general, actions, beginning, personal, pages, nearby, project, chat, community, portal, navigation, jump, content,

Text of the page (random words):
property talk p5972 wikidata jump to content main menu main menu move to sidebar hide navigation main page community portal project chat create a new item recent changes random item query service nearby help special pages lexicographical data create a new lexeme recent changes random lexeme search search english appearance donate create account log in personal tools donate create account log in contents move to sidebar hide beginning 1 documentation 2 translation as property and query 4 comments 3 kept 1 comment 4 automatically fill language of work or name p407 1 comment 5 large translation networks and p5137 2 comments toggle the table of contents property talk p5972 add topic property discussion english read edit view history tools tools move to sidebar hide actions read edit add topic view history general what links here related changes permanent link page information get shortened url print export download as pdf printable version in other projects appearance move to sidebar hide from wikidata latest comment 4 years ago by andreasmperu in topic large translation networks and p5137 documentation start a query current uses statistics by class list of qualifiers count translation sense meaning of a lexeme in another language that corresponds exactly to this sense meaning of the lexeme represents translation q7553 data type sense domain sense note this should be moved to the property statements example according to this template dog en chien fr chien fr dog en according to statements in the property no label l3302 s1 no label l189 s1 no label l87 s1 no label l41496 s1 no label l2120 s1 no label l3080 s1 when possible data should only be stored as statements see also item for this sense p5137 lists wikidata lexicographical data statistics translations items with the most statements of this property count of items by number of statements chart items with the most statements items with the fewest statements count of items by number of sitelinks chart items with the most sitelinks items with the most sitelinks but no link to one wikipedia sample welsh wikipedia cywiki items with the fewest sitelinks most linked wikis items with the most identifier properties items with no other statements most recently created items items with novalue claims items with unknown value claims items with deprecated claims usage history total usage history main statement chart by item creation date database reports constraint violations p5972 map random list proposal discussion proposal discussion current uses total 136 141 main statement 136 138 99 9 of uses qualifier 3 0 1 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 sense q54285715 the property may only be used on a certain entity type help list of violations of this constraint database reports constraint violations p5972 entity types hourly updated report scope is as main value q54828448 the property must be used by specified way only help list of violations of this constraint database reports constraint violations p5972 scope hourly updated report sparql conflicts with subclass of p279 this property must not be used with the listed properties and values 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 p5972 conflicts with p279 search sparql constraint symmetric constraint q21510862 declaration error the constraint is not applicable to datatype sense this property is being used by please notify projects that use this property before big changes renaming deletion merge with another property etc translation as property and query edit latest comment 7 years ago 4 comments 4 people in discussion hi do we really a property for translation more exactly what is the difference between lxxx p5972 lyyy and lxxx p5137 qzzz lyyy p5137 qzzz point blank i don t see a difference this seems exactly equivalent to me and the second method seems better to me as we need to store item for this sense p5137 anyway at the very least maybe we can add some constraints based on this equivalence tubezlob mfilot infovarius kaman jura1 cheers vigneron talk 07 53 8 november 2018 utc reply vigneron that s true as long as we agree to create items for all parts of speech there seems similar discussion at wikidata_talk lexicographical_data archive 2018 11 translations kaman talk 08 05 8 november 2018 utc reply ping tubezlob denny sintakso duesentrieb as users who requested it i think it all depends on how one uses it for experiments it can be good to list all translations for january but overall 3 variants between the same language pair could be more interested personally i rather see a statement than a translation in the gloss field furthermore p5137 statements make it hard to view the other lexeme obviously the gui on all these could use some more development jura 08 15 8 november 2018 utc reply the assumption is that translations are not necessarily transitive and that they don t always form a mutually translatable perfect group of lexemes in which case the star based method off item for this sense p5137 would be better i do agree that using translation p5972 when we already have item for this sense p5137 is problematic and leads to all the problems that interwiki maintenance had previously i would preferably say to use translation p5972 only if item for this sense p5137 is problematic just as we can still can have explicit interwiki links in the wikipedias does this make sense denny talk 15 28 8 november 2018 utc reply kept edit latest comment 7 years ago 1 comment 1 person in discussion this property was nominated for deletion and kept multichill talk 20 32 27 may 2019 utc reply automatically fill language of work or name p407 edit latest comment 6 years ago 1 comment 1 person in discussion all of the things that use this item should have a language however it doesn t automatically show the language of the translation and it needs to be added as a qualifier is there any way that the qualifier language of work or name p407 could automatically be added to this property and display the language of the other item demondays64 talk to me 23 55 9 january 2020 utc please ping on reply reply large translation networks and p5137 edit latest comment 4 years ago 2 comments 2 people in discussion there are a number of lexeme senses with quite a few translations on them while this upper bound is around 20 now at one point it was considerably larger for some senses most pertaining to the concepts of liquid water and mother this often happens alongside one of the following all nodes in the resulting network have the same item for this sense p5137 value this is merely redundant given that the connection to the wikidata item in question is the same across all senses in the network if the connection was different for some of the senses that might be an argument for maintaining this property on those senses only and either revising or removing the corresponding p5137 links in the aforementioned large sense graphs this situation had occured with the following all nodes in the resulting network are connected to one another i e it is a complete graph q45715 this is simply not scalable given that the number of edges in the network would be forced to scale quadratically in the number of languages involved rather than linearly moreover since most of the senses in such networks do not have any other special semantic features the connections between language senses can be preserved with fewer p5972 links so long as it is possible to follow a p5972 path between them to get from one language to another the wdt p5972 predicate in the wikidata query service this leads then to the following there is one node to which all other nodes are connected and none of these other nodes are otherwise directly connected to each other this may have been borrowed from the practice on the non linked data based wiktionary of for example placing a list of translations in other languages for a dutch word on the dutch wiktionary page for that word not only does this completely neglect the power of linked data to maintain these translation connections without such exhaustive enumeration it may also end up promoting the idea that there are lexicographic centers from which meaning in other languages emanates something which has already constricted the diversity of the lexemes added for some languages to address the latter two points above with respect to the graphs for mother liquid water and house i had reorganized these graphs so that instead of a single focus or a complete graph the connections using this property had some sort of logic to them the connections were chosen based first on genealogical relationship paiwan malay latin sicilian then on geographical proximity german polish malayalam sinhala and last on other relevant historico linguistic relationships english british sign language danish kalaallisut during these reorganizations the connectedness of the resulting graph was maintained it is still possible to get from the finnish talo to the occitan ostal through following p5972 paths in the network and yet this is achieved with fewer direct connections in the overall graph if there was a sense that got lost in these reorganizations this was no detriment either for all three of these graphs all senses within them had the same p5137 value and this p5137 value was never removed so in principle there is still a connection between those lost senses and the rest of the p5972 graph in fact if someone really wanted to remove all p5972 connections between senses which both 1 had the same p5137 value and 2 lacked any other semantic properties which might otherwise distinguish them this would not change the fact that the p5137 connection still exists and could be used to identify equivalent senses for them recently part of such a reorganization for the concept of dog was reverted by andreasmperu i would thus like to see what others think of what has been done and whether the principles which have guided it should persist mahir256 talk 05 20 30 january 2022 utc reply if this property is going to have a limit on the number of values we ll need some guidelines verbs adverbs adjectives prepositions tend to have no corresponding item so no item for this sense p5137 to help with the connections andreasm háblame just talk to me 05 46 30 january 2022 utc reply retrieved from https www wikidata org w index php title property_talk p5972 oldid 1570150349 categories all properties properties with wikibase sense datatype properties used on 100000 items properties with entity type constraints properties with scope constraints properties with conflicts with constraints properties with constraint declaration errors hidden categories property documentation with data to be moved to statements property with duplicated example property documentation using lists this page was last edited on 30 january 2022 at 05 46 all structured data from the main property lexeme and entityschema namespaces is available under the creative commons cc0 license text in the other namespaces is available under the creative commons attribution sharealike license additional terms may apply by using this site you agree to the terms of use and privacy policy privacy policy about wikidata disclaimers legal safety contacts code of conduct developers statistics cookie statement mobile view data access search search toggle the table of contents property talk p5972 add topic