Wikidata:Property proposal/Plants of the World online
Plants of the World online ID[edit]
Originally proposed at Wikidata:Property proposal/Natural science
Description | identifier of a (vascular) plant name in the Plants of the World online database |
---|---|
Represents | Plants of the World Online (Q47542613) |
Data type | External identifier |
Domain | plant (Q756) |
Example | |
External links | Use in sister projects: [ar] • [de] • [en] • [es] • [fr] • [he] • [it] • [ja] • [ko] • [nl] • [pl] • [pt] • [ru] • [sv] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt]. |
Planned use | upon request |
Formatter URL | http://www.plantsoftheworldonline.org/taxon/$1 |
Robot and gadget jobs | yes |
See also | for a different use of IPNI numbers, see IPNI plant ID (P961), which uses a different subset |
Motivation
Upon request. Should be useful. Can't hurt: respected database, with substantial content. - Brya (talk) 12:01, 30 January 2018 (UTC)
WikiProject Taxonomy has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
Discussion
- Oppose If these values are those in IPNI plant ID (P961), simply add the above formatter URL to that property, using third-party formatter URL (P3303). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:15, 30 January 2018 (UTC)
- And indeed that is already the case, so marked as "not done". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:17, 30 January 2018 (UTC)
- Do you have any evidence that your assumption is indeed true? - Brya (talk) 12:25, 30 January 2018 (UTC)
- There is no assumption. The situation I described can be viewed at Property:P961#P3303. I've again marked this as "not done". Please do not reverse that again. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:28, 30 January 2018 (UTC)
- There is a huge assumption, in your "If ...". - Brya (talk) 17:31, 30 January 2018 (UTC)
- Do you have any evidence that your assumption is indeed true? - Brya (talk) 12:25, 30 January 2018 (UTC)
- And indeed that is already the case, so marked as "not done". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:17, 30 January 2018 (UTC)
Three times now, Brya has reverted my closing this as "not done". Such behaviour is highly disruptive. There is not a snowball-in-hell's chance of us creating a duplicate property proposed as holding the same values as another. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:33, 31 January 2018 (UTC)
- Twice now Andy Mabbett has refused to answer a basic question, making it a near certainty that he is deliberately misrepresenting the facts. - Brya (talk) 11:46, 31 January 2018 (UTC)
- Which question? (Your indenting was again broken, BTW). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:52, 31 January 2018 (UTC)
- Twice now Andy Mabbett has refused to answer a basic question, making it a near certainty that he is deliberately misrepresenting the facts. - Brya (talk) 11:46, 31 January 2018 (UTC)
- That question (although since that time there was a shift from an assumption to an assertion). I can't say I find Andy Mabbett's attitude of "ignorant and proud of it" amusing. - Brya (talk) 17:37, 31 January 2018 (UTC)
- That question was answered in the subsequent edit; as you know, since you replied it it. So stop posting falsehoods. And knock of the ad hominem attacks. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:42, 31 January 2018 (UTC)
-
- Andy Mabbett can play ignorant all he wants, but he did present an assumption ("If ..."), and when asked to substantiate this, he shifted this to an assertion, apparently based on the presumption that if one does not know what one is talking about, and being called out on that, it is a good idea to start shouting. - Brya (talk) 04:31, 1 February 2018 (UTC)
- There was, as stated, no assumption. What you wrote in the original proposal (regarding $1 in the formatter URL) was "$1 is an IPNI number (P961)". And you, too, need to stop your abusive ad hominem attacks. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:30, 1 February 2018 (UTC)
- Andy Mabbett can play ignorant all he wants, but he did present an assumption ("If ..."), and when asked to substantiate this, he shifted this to an assertion, apparently based on the presumption that if one does not know what one is talking about, and being called out on that, it is a good idea to start shouting. - Brya (talk) 04:31, 1 February 2018 (UTC)
- As Andy Mabbett note I wrote "is an IPNI number" and Andy Mabbett wrote down the assumption "If these values are those in IPNI plant ID (P961), ", and later went even further, shifting to an assertion. Andy Mabbett apparently really likes acting the part of being an ignorant loudmouthed bully. - Brya (talk) 11:37, 1 February 2018 (UTC)
-
- That question was answered in the subsequent edit; as you know, since you replied it it. So stop posting falsehoods. And knock of the ad hominem attacks. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:42, 31 January 2018 (UTC)
- Support David (talk) 15:27, 31 January 2018 (UTC)
- Support The external identifier used by POWO is an URN, so I changed the formatter URL accordingly. --Succu (talk) 18:32, 31 January 2018 (UTC)
- The new identifier is still the IPNI plant ID (P961) value, just with a common prefix, lifted from the original proposal's formatter URL. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:42, 31 January 2018 (UTC)
- No. This approach is more flexible. And you gave no reference for your assumption. --Succu (talk) 18:45, 31 January 2018 (UTC)
- I make no assumption; and the original and current versions of the proposal are available for anyone to compare. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:50, 31 January 2018 (UTC)
- „The new identifier is still the IPNI plant ID (P961) value“. This needs some proof. --Succu (talk) 19:02, 31 January 2018 (UTC)
- See my previous post. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:10, 31 January 2018 (UTC)
- Good to know that your Contra is based on no grounds. --Succu (talk) 20:53, 31 January 2018 (UTC)
- See my previous post. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:10, 31 January 2018 (UTC)
- „The new identifier is still the IPNI plant ID (P961) value“. This needs some proof. --Succu (talk) 19:02, 31 January 2018 (UTC)
- I make no assumption; and the original and current versions of the proposal are available for anyone to compare. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:50, 31 January 2018 (UTC)
- No. This approach is more flexible. And you gave no reference for your assumption. --Succu (talk) 18:45, 31 January 2018 (UTC)
- The new identifier is still the IPNI plant ID (P961) value, just with a common prefix, lifted from the original proposal's formatter URL. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:42, 31 January 2018 (UTC)
- Oppose this is not an independent ID, at least for the examples provided so far. The original request regarding Malva acerifolia (Q47519412) has IPNI plant id "561509-1", and when you use the plantsoftheworld 3rd party formatter URL for this you get this link which seems correct. As to the original requestors intent @Peter coxhead: seemed to be looking more for a supporting reference than an ID, so that direct URL to plantsoftheworldonline.org can be used as is via reference URL (P854), there's no need for a new property for this. ArthurPSmith (talk) 18:39, 1 February 2018 (UTC)
- So how do you know that all URNs used by POWO as an identifier can substituted that way, ArthurPSmith? --Succu (talk) 18:45, 1 February 2018 (UTC)
- I don't, however all examples presented so far do. If you find a counterexample I would be happy to change my opinion here. Also note that the URN format explicitly includes "ipni.org", which suggests they are relying on IPNI. If there are URN's on the site that use a different format that would be another story. ArthurPSmith (talk) 18:50, 1 February 2018 (UTC)
- I don't know why do you think inductive reasoning (2 out of more than 800,000) applies here. As far as I know there exists no documentation of POWO. This URN is an Life Science Identifier (Q6459954). LSIDs includes a authority part. In this case ipni.org. --Succu (talk) 20:29, 1 February 2018 (UTC)
- because we have nothing better to go on. However, I did browse the POWO site looking for counterexamples, and among hundreds I looked at, every single one was using IPNI. If you actually do find a counterexample please present it here. Also, IPNI is referred to throughout the POWO site as a reference source. ArthurPSmith (talk) 21:07, 1 February 2018 (UTC)
- „because we have nothing better to go on“?! Really? Maybe creating a separate property for more than 800,000 entries, if we are not sure? Why not using the URN as POWO does? --Succu (talk) 21:24, 1 February 2018 (UTC)
- because we have nothing better to go on. However, I did browse the POWO site looking for counterexamples, and among hundreds I looked at, every single one was using IPNI. If you actually do find a counterexample please present it here. Also, IPNI is referred to throughout the POWO site as a reference source. ArthurPSmith (talk) 21:07, 1 February 2018 (UTC)
- I don't know why do you think inductive reasoning (2 out of more than 800,000) applies here. As far as I know there exists no documentation of POWO. This URN is an Life Science Identifier (Q6459954). LSIDs includes a authority part. In this case ipni.org. --Succu (talk) 20:29, 1 February 2018 (UTC)
- As anybody who has basic familiarity with taxonomy should know, IPNI is a nomenclatural database. It contain entries for all kinds of things ("names" sensu lato) with each entry having a number that can be used as an external identifier in P961. PotWo is a taxonomic database, presenting "correct names" according to a particular taxonomic point of view: it uses a subset of these IPNI numbers, which, conversely, means that many IPNI numbers do not have a PotWo entry. Wikidata also holds a subset of these IPNI numbers in statements using P961. Given the size of IPNI, a detailed breakdown of numbers will not be easy to come by, but clearly many of the entries in PotWo can not be reached through Wikidata statements, and many IPNI numbers in Wikidata statements will not lead to PotWo entries. - Brya (talk) 05:17, 2 February 2018 (UTC)
- "it uses a subset of these IPNI numbers" QED. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:47, 2 February 2018 (UTC)
-
- Indeed, QED. These two subsets are different and will remain different. - Brya (talk) 11:53, 2 February 2018 (UTC)
-
- "it uses a subset of these IPNI numbers" QED. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:47, 2 February 2018 (UTC)
- I don't, however all examples presented so far do. If you find a counterexample I would be happy to change my opinion here. Also note that the URN format explicitly includes "ipni.org", which suggests they are relying on IPNI. If there are URN's on the site that use a different format that would be another story. ArthurPSmith (talk) 18:50, 1 February 2018 (UTC)
- So how do you know that all URNs used by POWO as an identifier can substituted that way, ArthurPSmith? --Succu (talk) 18:45, 1 February 2018 (UTC)
- Comment My reason for raising the issue in the first place was so that a POWO link was picked up by en:Template:Taxonbar, e.g. at en:Malva acerifolia. Although the identifiers are the same, the information is most certainly not; so far in the last week, for example, I've had four authorities in IPNI corrected to match POWO, which does seem to be more up-to-date. Precisely how the link to POWO from the Wikidata entry and hence Taxonbar is implemented in Wikidata isn't my concern; I leave that to you guys. It does seem that, at present, only IPNI identifiers are used, but as Brya notes there are many IPNI entries that don't appear in POWO, and as POWO expands, they will encounter taxa that don't have names in IPNI. Maybe they will ensure that IPNI is updated. I've tried e-mailing POWO at the address given, but haven't had a reply to date. Peter coxhead (talk) 10:24, 2 February 2018 (UTC)
- Support The POWO database contains valuable information. The identifier to POWO is not the same as the identifier to IPNI as they point to different information, even though the identifier uses the same ID. The important item is the data, not the ID ((hence WikiData, not WikiID). Jts1882 (talk) 16:20, 3 February 2018 (UTC)
- Thank you for confirming that these are "the same ID". However, you appear to have posted support here after being canvassed on en.Wikipedia [1]. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:39, 3 February 2018 (UTC)
- Not at all. As you have read my comment you know I said I had found this page and added support. @Peter coxhead:'s original comment neither requested support or stated where to add it. I found it myself before I saw his subsequent comment.
- Further, you have not addressed my point. An identifier for POWO would provide two pieces of information, the fact that the POWO contains a corresponding data item (the important thing) and an ID to access it. The IPNI property says nothing about whether a POWO entry exists. Jts1882 (talk) 17:08, 3 February 2018 (UTC)
- As I understand the issue now, the key piece of information is the first one: the Wikidata item needs to indicate that a POWO entry exists. Then so long as the identifiers remain the same (which we don't know they will, but they may) the link to the database can be picked up using the IPNI property value. Peter coxhead (talk) 17:27, 3 February 2018 (UTC)
- @Peter coxhead: "the Wikidata item needs to indicate that a POWO entry exists" That is easily achievable like this (albeit the reference URL is superfluous to your requirement), using existing properties. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:49, 3 February 2018 (UTC)
- @Pigsonthewing: so why did Succu immediately remove your addition? How will that help us move forward? Peter coxhead (talk) 09:16, 4 February 2018 (UTC)
- @Peter coxhead: You'd have to ask them that - since they failed to leave an edit summary, a talk page comment or a comment here - but I suspect for the reasons described at en:WP:POINT. Absent such an explanation, I've restored it. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:28, 4 February 2018 (UTC)
- I simply removed your wrong experimental reference. As you should know it's not possible to add a comment while removing a refenence or statement. --Succu (talk) 15:49, 4 February 2018 (UTC)
- @Peter coxhead: You'd have to ask them that - since they failed to leave an edit summary, a talk page comment or a comment here - but I suspect for the reasons described at en:WP:POINT. Absent such an explanation, I've restored it. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:28, 4 February 2018 (UTC)
- @Pigsonthewing: so why did Succu immediately remove your addition? How will that help us move forward? Peter coxhead (talk) 09:16, 4 February 2018 (UTC)
- @Peter coxhead: "the Wikidata item needs to indicate that a POWO entry exists" That is easily achievable like this (albeit the reference URL is superfluous to your requirement), using existing properties. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:49, 3 February 2018 (UTC)
- As I understand the issue now, the key piece of information is the first one: the Wikidata item needs to indicate that a POWO entry exists. Then so long as the identifiers remain the same (which we don't know they will, but they may) the link to the database can be picked up using the IPNI property value. Peter coxhead (talk) 17:27, 3 February 2018 (UTC)
- Thank you for confirming that these are "the same ID". However, you appear to have posted support here after being canvassed on en.Wikipedia [1]. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:39, 3 February 2018 (UTC)
- Support Assuming that Veronica chamaedrys (Q157343) is the model solution, w:Veronica chamaedrys's {{w:Taxonbar}} fails to show any POTWO information. The desired behavior is to display both an IPNI and a POTWO entry/link. Since the current "solution" is inadequate, the POTWO property needs to be created. Tom.Reding (talk) 14:14, 5 February 2018 (UTC)
- Further support, since all IPNI IDs do not map perfectly to available POTWO IDs, and that POTWO has the potential to fork/expand beyond IPNI. — Tom.Reding (talk) 16:03, 5 February 2018 (UTC)
- The statement "the current solution is inadequate" is false. You appear to have been mislead by this edit on en.Wikipedia. It is clear from that discussion and the one on this project's "chat" that the desired behaviour is to display both an IPNI and a POTWO entry/link in an en.Wikipedia template. It currently fails to do so, because that template has not yet had the necessary (but perefectly feasible) code added. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:31, 5 February 2018 (UTC)
- Isn't the point of Wikidata to avoid wiki-specific work-arounds? How is editing en-wiki's template a better solution than adding this parameter? — Tom.Reding (talk) 15:40, 5 February 2018 (UTC)
- You have that wrong; the point of Wikidata is to hold and make available data. Even if the proposed property were created, the template would have to be updated to make use of it. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:51, 5 February 2018 (UTC)
- Adding this new property to {{en:Module:Taxonbar/conf}} is a trivial task one can do without any Lua coding experience. Would a similarly trivial change be needed to display POTWO on w:Veronica chamaedrys with the current configuration? — Tom.Reding (talk) 16:12, 5 February 2018 (UTC)
- Probably not; but - especially as plenty of en.Wikipedia editors have the necessary skills - that's immaterial to the discussion at hand. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:33, 5 February 2018 (UTC)
- Actually it is material if it makes maintenance of this highly used template unnecessarily complicated.
- People looking for this sub-property would be required to know a priori to look under IPNI, which is unreasonable.
- POTWO is a separate effort from IPNI, and doesn't belong as a reference, as all other property references are related real-world entities or aliases.
- There's the possibility of POTWO forking from/expanding beyond IPNI, which, by itself, is enough to warrant its own property. 'nuff said. — Tom.Reding (talk) 17:10, 5 February 2018 (UTC)
- It doesn't make maintenance of the template unnecessarily complex. Who would be looking for this property? We have other cases where third parties use an existing identifier, and have third-party formatter URL (P3303) specifically for such cases, where it is used without fuss. PotW uses, as as been clearly demonstrated, IPNI identifiers, Not one PotW page without an IPNI identifier has been shown. We don't create properties based on a hypothetical "possibility". Come back when - if that happens. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:32, 5 February 2018 (UTC)
- Adding this new property to {{en:Module:Taxonbar/conf}} is a trivial task one can do without any Lua coding experience. Would a similarly trivial change be needed to display POTWO on w:Veronica chamaedrys with the current configuration? — Tom.Reding (talk) 16:12, 5 February 2018 (UTC)
- You have that wrong; the point of Wikidata is to hold and make available data. Even if the proposed property were created, the template would have to be updated to make use of it. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:51, 5 February 2018 (UTC)
- Isn't the point of Wikidata to avoid wiki-specific work-arounds? How is editing en-wiki's template a better solution than adding this parameter? — Tom.Reding (talk) 15:40, 5 February 2018 (UTC)
- Support some way of getting POWO incorporated into Wikidata. It is a valuable resource. I don't really care how it is done. I must say, I don't understand the issue causing objections here when Wikidata has Flora of China ID (P1747) and Flora of North America taxon ID (P1727). As far as I can see, FoC and FNA use identical IDs when a taxon is in both sources. They're really eFlora IDs, with FNA representing one subset of the eFlora IDs and FoC representing another subset. And eFlora is a single domain. At least POWO is a different domain from IPNI. Plantdrew (talk) 21:25, 7 February 2018 (UTC)
- The nature of those shared IDs was not declared when the second property was proposed. We should probably combine them. A suitable formatter URL would seem to be
http://www.efloras.org/browse.aspx?name_str=$1
(example: [2]) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:30, 7 February 2018 (UTC)- No, it was noted at the time that the FNA property was proposed that eFlora IDs were reused in different floras (Wikidata:Property_proposal/Archive/29#Flora_of_North_America). FoC property was created subsequently, reusing the ID. Again, I don't really care how POWO gets implemented here. Due to the subset problem, regardless of whether you go with a formatter URL or a property, each taxon item will need to have a statement added. Plantdrew (talk) 22:09, 7 February 2018 (UTC)
- Yes; FNA was the first of these property proposed (and it was not noted until late in that proposal); I referred to the second, FoC, property proposal. But as you say, there are other - better - ways of doing this for PotW. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:19, 7 February 2018 (UTC)
- Plantdrew's comment 'And eFlora is a single domain. At least POWO is a different domain from IPNI.' supports my point #TR3 above. All of the references I see under Veronica chamaedrys (Q157343)'s Identifiers are related real-world entities of their parent, and all of them share a name or expand the acronym of their parent. Putting POTWO under 'IPNI plant ID' breaks this logic and structure. — Tom.Reding (talk) 13:21, 8 February 2018 (UTC)
- We're not discussing references, but a property. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:52, 8 February 2018 (UTC)
- Plantdrew's comment 'And eFlora is a single domain. At least POWO is a different domain from IPNI.' supports my point #TR3 above. All of the references I see under Veronica chamaedrys (Q157343)'s Identifiers are related real-world entities of their parent, and all of them share a name or expand the acronym of their parent. Putting POTWO under 'IPNI plant ID' breaks this logic and structure. — Tom.Reding (talk) 13:21, 8 February 2018 (UTC)
- Yes; FNA was the first of these property proposed (and it was not noted until late in that proposal); I referred to the second, FoC, property proposal. But as you say, there are other - better - ways of doing this for PotW. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:19, 7 February 2018 (UTC)
- No, it was noted at the time that the FNA property was proposed that eFlora IDs were reused in different floras (Wikidata:Property_proposal/Archive/29#Flora_of_North_America). FoC property was created subsequently, reusing the ID. Again, I don't really care how POWO gets implemented here. Due to the subset problem, regardless of whether you go with a formatter URL or a property, each taxon item will need to have a statement added. Plantdrew (talk) 22:09, 7 February 2018 (UTC)
- The nature of those shared IDs was not declared when the second property was proposed. We should probably combine them. A suitable formatter URL would seem to be
- Note to closer: discussion spilled over to Wikidata:Project chat/Archive/2018/03#Plants of the World Online database; please take the points there into account, not least the absence of the requested examples. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:18, 17 February 2018 (UTC)
- The discussion started over there. It was shown that
- The proposed formatter URL can result in HTTP 404 (Q208219) because the IPNI id is not part of POWO
- The domain of POWO is much broader than that of IPNI (fungi and algae are not the subject of IPNI)
- --Succu (talk) 21:31, 17 February 2018 (UTC)
- Still not one single example of a case where the model I proposed does not work. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:09, 17 February 2018 (UTC)
- Succu missed the following arguments by me Mr. Mabbett
- ?
- ?
- --Succu (talk)
- Still only hot air... --Succu (talk) 21:44, 28 February 2018 (UTC)
- Succu missed the following arguments by me Mr. Mabbett
- Still not one single example of a case where the model I proposed does not work. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:09, 17 February 2018 (UTC)
- The discussion started over there. It was shown that
General purpose of wikidata properties[edit]
- Comment The above discussion suggests to me that there are differing understandings of the purpose of wikidata properties. In general for structured databases it's preferable to avoid redundancy in the storage of information - we generally discourage creation of inverse properties, for example, as the information only needs to be entered once to be available for anybody to use (via SPARQL query at least). And similarly we discourage creation of properties that record the same piece of data as an existing property. The reason to avoid redundancy is that it multiplies the required effort in maintenance of data - the same data needs to be entered 2 or more times, instead of just once - and it can also lead to inconsistencies that are difficult to resolve, when for example the two different properties are maintained by separate people or groups with different standards or approaches. However, we do also want wikidata information to be useful to people accessing it via standard systems of one sort or another (particularly wikipedia templates with LUA etc). So maybe this is a case for an exception along those lines. But I think the case needs to be much more clearly made on why a separate property is needed here. Why is the third party formatter URL approach not sufficient? ArthurPSmith (talk) 16:53, 8 February 2018 (UTC)
- Third party formatter URL doesn't really solve "same data needs to be entered 2 or more times". There are IPNI IDs that don't have records in POWO, so something has to be entered for each item with a POWO record to indicate that the POWO record exists. And like Tom.Reding says, I would find it counterintuitive to have to look for POWO under IPNI when every other botanical database has it's own section on Wikidata. Plantdrew (talk) 17:22, 8 February 2018 (UTC)
- @Plantdrew: so your argument is that this property would be not so much to provide the ID, but to provide an indication that POWO has a page for it. Do we have an example of an IPNI that is not covered in POWO? ArthurPSmith (talk) 16:49, 9 February 2018 (UTC)
- This is of no relevance (see my remark below). But: 128853-1 and urn:lsid:ipni.org:names:128853-1. --Succu (talk) 18:30, 9 February 2018 (UTC)
- @ArthurPSmith: I gave a solution for this use-case, requiring no new property, and usable today, above (timestamp: 17:49, 3 February). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:42, 9 February 2018 (UTC)
- If these values are those in IPNI plant ID (P961). No, Mr. Mabbett --Succu (talk) 21:17, 9 February 2018 (UTC)
- Random, out of context quotes, relating to a different proposal to the one at hand. Not helpful. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:22, 9 February 2018 (UTC)
- Then make it helpful Mr. Mabbett. What's you point now. --Succu (talk) 21:34, 9 February 2018 (UTC)
- Thanks, Mr. Mabbett for your housekeeping --Succu (talk) 22:55, 9 February 2018 (UTC)
- Random, out of context quotes, relating to a different proposal to the one at hand. Not helpful. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:22, 9 February 2018 (UTC)
- If these values are those in IPNI plant ID (P961). No, Mr. Mabbett --Succu (talk) 21:17, 9 February 2018 (UTC)
- @Plantdrew: so your argument is that this property would be not so much to provide the ID, but to provide an indication that POWO has a page for it. Do we have an example of an IPNI that is not covered in POWO? ArthurPSmith (talk) 16:49, 9 February 2018 (UTC)
- The domain of POWO and IPNI and the range of possible values are different. If an POWO-URN is based on an IPNI id it link's not to the „same piece of data“. --Succu (talk) 18:45, 8 February 2018 (UTC)
- Furthermore, although the identifiers stored in a wikidata item can be made the same, they wouldn't necessarily be so because IPNI has more than one identifier for the same name. Thus Lotus rubriflorus H.Sharsm. is at both 144018-2 and 503872-1. However, WOFO only has an entry at 144018-2. Peter coxhead (talk) 10:22, 10 February 2018 (UTC)
Done[edit]
@Brya, Pigsonthewing, Succu, ديفيد عادل وهبة خليل 2, ArthurPSmith: @Jts1882, Peter coxhead, Tom.Reding, Plantdrew: Done Micru (talk) 11:07, 11 April 2018 (UTC)
- @Micru: there were different suggestions above as how to handle the POWO database, but as I understand it, you have created a property Plants of the World Online ID (P5037) to be used on items that are instances of taxon (Q16521), just like other databases. That is certainly a help to us over at enwiki. Peter coxhead (talk) 16:55, 11 April 2018 (UTC)
Just for the record: Byttneriaceae in POWO has no entry in IPNI. --Succu (talk) 14:04, 12 April 2018 (UTC)
- Encouraging to see that this straightforward proposal for a useful property won through, in spite of all the obstructionism (based on fact-free logic). - Brya (talk) 05:03, 14 April 2018 (UTC)