Wikidata:Requests for comment/List of properties
An editor has requested the community to provide input on "List of properties" via the Requests for comment (RFC) process. This is the discussion page regarding the issue.
If you have an opinion regarding this issue, feel free to comment below. Thank you! |
THIS RFC IS CLOSED. Please do NOT vote nor add comments.
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- some new property lists were created, for an overview see
{{Property lists}}
- some new property lists were created, for an overview see
Proposal for a bot maintained List of properties that use direct links instead of templates to avoid script errors. Initial columns could:
- Name
- Data type - e.g. most properties that use "string" are identifiers so one could have them in one place by sorting after that column
- Description
- Usage - like on Wikidata:Database reports/Popular properties
Benefits:
- allows tracking of creation and deletion of properties
- allows tracking of usage
- allows to see all description in one list and detect inconsistencies, e.g. Identifer, ID, id, identifier
Current situation: Of the subpages of Wikidata:List of properties some have script errors:
and as User:John F. Lewis wrote [1] this seems to have been mentioned several times already. Other subpages seem to be not updated when new properties are created, I myself recently added several identifiers for geographical features at the corresponding subpage. Additionally there is Wikidata:Database reports/Popular properties, but it does not include data type, nor does it list all properties. A very helpful table for all properties was created by User:Snipre, it is temporarily located at Wikidata:List of properties/all in one table.
Tamawashi (talk) 23:32, 11 July 2014 (UTC)[reply]
- Support Tamawashi (talk) 17:07, 13 July 2014 (UTC)[reply]
I (for myself) don't really care about this page. How do users use this page, actually ? properties sorted by class, like in this {{Item documentation}}
example seems more useful, or properties by projects.
- {{Item documentation|Q16521}}
- https://www.wikidata.org/w/index.php?title=Talk:Q16521&oldid=88810134 (template disabled and link added to page where the template already displays the same content, Tamawashi (talk) 16:53, 13 July 2014 (UTC))[reply]
A combo Category:Property plus an opt-out gadget to display more informations about properties than just their name can also do the trick. Or on a special page that lists pages on a namespace. A gadget can then extract for each of those properties the relevant informations. It is also more fitted to the job as such pages have a configurable limit and split the list naturally.
TomT0m (talk) 16:34, 12 July 2014 (UTC)[reply]
- If you don't care about that page, then you probably do not oppose to others improving it for their needs? Your template does not show usage count, nor will one see new or removed properties. IT does also not show all properties that have a specific data type, as described above. Tamawashi (talk) 16:55, 13 July 2014 (UTC)[reply]
- When you say that the list of properties should be maintained by bot, do you mean that you are willing to write and mantain a bot doing that task?
- Do you plan to add manually the categories to the property talk pages to create the structure for generating the lists automatically?
- If the list doesn't rely on scripts, what about multilingual support? Can the bot maintain the list in several languages?
--Micru (talk) 17:13, 13 July 2014 (UTC)[reply]
- I can answer partially the above questions:
- I have a personal script for extracting the parameters of the properties and theoretically you can do that for the different languages (label, descritption). I think a bot is not necessary because properties creation will decrease after some time and the implementation of all datatypes. Categories will be added in the properties data structure when statement for properties will be added.
- So as conclusions I think we have to do nothing new until we have statements in property items. Snipre (talk) 09:53, 15 July 2014 (UTC)[reply]
- "Properties creation will decrease after some time", nobody knows. Perhaps it will, perhaps it will not, it all depends on how much we develop the uses, and how many people there are using them, and how much we want to achieve.
- It is not bad to have the structure as categories because later on it can be converted easily into statements. It all depends on how long we have to wait before being able to use statements on property pages...--Micru (talk) 11:07, 15 July 2014 (UTC)[reply]
@Micru: @1 - if I would be able to, I would never ever have started this RfC, I would just have done it. @2 - I do not plan to manually "add categories" to talk pages. @3 - the Q-templates are broken already, i.e. no description nor label is shown for them in any human language. So, to have a label in English (probably the most widely understood among wikidata users) may help a lot of users. Many or most Wikidata:Database reports are monolingual. Since so far no one except me supports a bot maintained basic list in one language in this RfC, it could be that it is useless to talk about additional languages before that changes. Tamawashi (talk) 23:06, 17 July 2014 (UTC)[reply]
@Tamawashi, TomT0m, Snipre, Underlying lk: Now that we have template has topic (P1423) and topic's main template (P1424) we can know which infoboxes belong to each topic. On each item linked to a infobox or template, we could have a property "may use property" with datatype string containing the property number. Example: <Template:Taxonomy/Syngnathiformes (Q14464882)> may use property <P171> With that we could automate:
{{ExternalUse}}
info- a list of properties classified by infobox/template that uses them
- Wikidata:Infobox mappings (by having a monolingual text qualifier to store the name of the template field)
What do you think of the idea?--Micru (talk) 14:19, 17 July 2014 (UTC)[reply]
- @Micru: At first I would start with a bot maintained list. Then data such as you mention can be added to the table, if a bot could collect it. E.g. in the complete list a column "is used by an infobox" could be added, with a link to a WDQ that shows the related infobox-items. But since no one except me supports a bot maintained basic list in this RfC, it could be that it is useless to talk about additional features. Tamawashi (talk) 20:31, 17 July 2014 (UTC)[reply]
I created for myself a list of properties which is similar to the one User:Tamawashi requested. It will be updated daily and I can add more languages if requested. You find the list at User:Pasleim/List of properties.--Pasleim (talk) 14:26, 14 September 2014 (UTC)[reply]