Wikidata:Property proposal/Pending

From Wikidata
Jump to: navigation, search

Awaiting multilingual text type[edit]

Sandbox-Multilingual texts (en)[edit]

Agreed to be created; waiting for multilingual text datatype
   On hold
Description A sandbox type per available data type
Data type Multilingual text (not available yet)
Domain any
Example MISSING
Proposed by GZWDer (talk) 09:37, 6 June 2013 (UTC)
Discussion

IUPAC name[edit]

Agreed to be created; waiting for multilingual text datatype
   On hold
Description en:IUPAC name
Data type Multilingual text (not available yet)
Domain chemistry
Example see Wikidata:Chemistry_task_force/Properties.
Source en:PubChem
Proposed by GZWDer (talk) 03:07, 7 June 2013 (UTC)
Discussion
Symbol support vote.svg Support Snipre (talk) 21:41, 10 June 2013 (UTC)
Symbol support vote.svg Support --Kaligula (talk) 07:06, 19 June 2013 (UTC)
Hmm, this is for some compounds still a disputed property .. --Beetstra (talk) 13:05, 24 June 2013 (UTC)
There is always one IUAPC and most of the time you can put more than one. And as IUAPC is going to publish some rules to select the preferred name when several possibilities exist (see here, we can define one name for that property. Snipre (talk) 12:49, 26 June 2013 (UTC)
I have noticed French language using alternative characters with accents for the names, which does not quite match use in English. So is the non accented use correct? Graeme Bartlett (talk) 08:15, 29 June 2013 (UTC)
In French non accented names are not correct. That's why a multilingual property is proposed: each language will have its own name, so the value of this property will be a list of chemical names associated with a language. Snipre (talk) 08:32, 29 June 2013 (UTC)
Symbol support vote.svg Support, though the domain should probably be refined to "chemical compounds". Otherwise perhaps I'll finally get to see the IUPAC name for titin! It would also help to have an example, if only for documentation. Proposing a canonical source for IUPAC name claims would be helpful, too. Emw (talk) 12:14, 29 June 2013 (UTC)
Symbol support vote.svg Support - additionally it should be investigated if this can be filled in by a bot because it is pretty standardized. --Tobias1984 (talk) 14:51, 11 July 2013 (UTC)
Symbol support vote.svg Support -- Andrew Su (talk) 23:10, 19 July 2013 (UTC)

Description/review (en)[edit]

Agreed to be created; waiting for multilingual text datatype
   On hold
Description voy:Template:Listing A brief description of the listing
Data type Multilingual text (not available yet)
Template parameter content
Domain Items with Wikivoyage listings
Allowed values any text
(OBSOLETE) suggested values brief description of the listing.
Example Exploratorium (Q206518) -> A great kid friendly option, with lots of interactive exhibits teaching about science, with intriguing displays about the mind, natural systems, sound, sight, and much much more.
Source Wikivoyage listings
Proposed by Filceolaire (talk) 00:11, 19 August 2013 (UTC)
Discussion
  • Symbol support vote.svg Support Support as nom. See this RFC. Filceolaire (talk) 00:11, 19 August 2013 (UTC)
  • Symbol support vote.svg Support but why the name "personal"? Wikivoyage POI descriptions feel indeed more personal than Wikipedia sentences, but they are not the result of a single individual, they are most often the result of a wiki collaboration. Nicolas1981 (talk) 08:04, 28 November 2013 (UTC)
  • Symbol support vote.svg Support -- DerFussi 11:27, 24 January 2014 (UTC)
  • Symbol support vote.svg Support --NatiSythen (talk) 07:59, 28 January 2014 (UTC)
  • Symbol support vote.svg Support As stated above multilingual support is necessary. --RolandUnger (talk) 13:10, 2 February 2014 (UTC)
  • Comment: @Filceolaire: Please provide an example and proper description. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:22, 22 November 2015 (UTC)
  • Renamed, description ammended, example added as comments by @Nicolas1981, Pigsonthewing:. Filceolaire (talk) 04:52, 24 November 2015 (UTC)

Awaiting geo-shape type[edit]

Sandbox-Geographic shapes (en)[edit]

Agreed to be created; waiting for geo-shape datatype
   On hold
Description A sandbox type per available data type
Data type ⧼datatypes-type-geo-shape⧽ (not available yet)
Domain any
Example MISSING
Proposed by GZWDer (talk) 09:37, 6 June 2013 (UTC)
Discussion

KML link[edit]

Agreed to be created; waiting for geo-shape datatype
   On hold
Description A link to a page on another wiki containing KML data describing the item.
Data type String
Domain Any geographical feature which may need to be represented by more than one point (e.g. linear features like rivers and roads, polygonal features like cities, and states).
Allowed values Ideally, only a URL or wiki page link.
Example Q2171599 (Creek Turnpike) would have a value of https://en.wikipedia.org/w/index.php?title=Template:Attached_KML/Creek_Turnpike&action=raw or simply w:Template:Attached KML/Creek Turnpike (though the &action=raw is needed to allow access to just the KML data)
Proposed by Scott5114 (talk)

Hundreds, if not thousands, of pages with KML data have been created on the English Wikipedia for use with articles about geographic information. This property would allow other projects to have a direct link to the KML data. It would also mean that KML data could be sourced from several wikis, i.e. the English Wikipedia could use KML data hosted on the Welsh Wikipedia. In the future, should it become technically possible to host the KML data directly on Wikidata (it would certainly be within the project's remit), this property's data could be used by bots to transfer the KML content. Scott5114 (talk) 06:17, 10 April 2013 (UTC)

  • Symbol support vote.svg Support as a good stopgap measure. --Rschen7754 06:19, 10 April 2013 (UTC)
  • Symbol support vote.svg Support small worlds matter! -- Llywelyn2000 (talk) 09:17, 10 April 2013 (UTC)
  • Symbol oppose vote.svg Oppose, we will have a datatype for coordinates here (and before that a IRI datatype that would already be better than a string). That would not be difficult to have a bot make the conversion, but there is amply enough work here for both bots and humans that we need not do the same thing twice. --Zolo (talk) 09:40, 10 April 2013 (UTC)
    • The problem. for lack of a better word, is that linear features aren't exactly distilled down to a single point value. Interstate 75 in Michigan is 395 miles long, and there isn't really one point that's representative of the state's segment of the freeway. The benefit of the KML is that it draws a line on a map instead of displaying a series of disconnected dots. Google is reusing our KML data now. Do a search for "Brockway Mountain Drive", and they display a summary box in the upper right of the search results which resuses data from the Wikipedia article, and displays a red line corresponding to the route of the road on a map. Imzadi 1979  10:13, 10 April 2013 (UTC)
      • Exactly. The reason we have KML data on enwp in the first place is because of the limitations of coordinates to express the location of features such as these (see the "domain" in the proposal). The data already exists and is use, so we need some way of connecting it to Wikidata to allow multiple projects access to it. Unless we'd rather just have copies of the same data floating around on multiple wikis, but that's what Wikidata is supposed to be preventing, no? —Scott5114 [EXACT CHANGE ONLY] 18:24, 10 April 2013 (UTC)
        • Sure, but from what I can see the shape datatype will be more similar to KML than to Wiki-style point coordinates. --Zolo (talk) 18:50, 10 April 2013 (UTC)
          • I see this as more of a stopgap measure, similar to the Commons category property that was already created as a string. --Rschen7754 19:43, 10 April 2013 (UTC)
            • Fair enough. I think Commonscat are somewhat more maintainable than strings containing URLs for pages scattered around various wikis, but the idea is the same. The major difference is that geodatatypes are supposed to come much sooner than support for Commons links. Well, at least that was the initial plan, but it might be worth asking the development team are they seem pretty late on that. --Zolo (talk) 21:15, 10 April 2013 (UTC)
  • Symbol support vote.svg Support This will turn out to be very helpful in the long run. –TCN7JM 03:21, 11 April 2013 (UTC)
  • Symbol support vote.svg Support Agree that this will be helpful in the long run. I think it can work in concert with coordinates. For instance, the coordinate property shows the center of the city, but the KML could show the city's corporate limits. –Fredddie 03:27, 11 April 2013 (UTC)
  • Pictogram voting question.svg Question Can't we keep KML files on Commons? --DixonD (talk) 11:40, 11 April 2013 (UTC)
    • Unless things have changed recently, Commons does not allow KML files to be uploaded, due to security reasons I don't quite understand. (Something involving China and IE6 or something like that.) I feel that KMLs would probably make more sense on Wikidata instead of Commons, anyway, since it's data, not a media file. —Scott5114 [EXACT CHANGE ONLY] 14:28, 11 April 2013 (UTC)

Awaiting time type with precision second[edit]

checkin time (en)[edit]

Approved for creation; waiting for Number datatype
   On hold
Description Time of hotel reservation or airport flight check-in
Represents check-in (Q1068755)
Data type Point in time
Template parameter voy:Template:Listing : "checkin" - Template:Listing (Q14330485)
Domain Hotel reservation or airport flight
Example MISSING
Proposed by GZWDer (talk) 10:39, 18 June 2013 (UTC)
Discussion
  • Symbol support vote.svg Support. Property should be number with unit type hours. Needs a 'day' qualifier property to say which day the time given applies to (mon, weekdays, bank holidays, second tuesday in the month). Filceolaire (talk) 23:53, 18 August 2013 (UTC)
  • Symbol support vote.svg Support as time duration in hours. Danrok (talk) 22:05, 30 August 2013 (UTC)
  • Symbol support vote.svg Support Nicolas1981 (talk) 08:49, 29 January 2014 (UTC)
  • Probably in some places it can be fractional (12.30) so not only hours. --Infovarius (talk) 05:18, 22 October 2014 (UTC)

checkout time (en)[edit]

Approved for creation; waiting for Number datatype
   On hold
Description Time of hotel reservation check-out
Data type Point in time
Template parameter voy:Template:Listing : "checkout" - Template:Listing (Q14330485)
Domain Hotel reservation
Example MISSING
Proposed by GZWDer (talk) 10:39, 18 June 2013 (UTC)
Discussion

Epoch[edit]

Approved for creation; waiting for Number datatype
   On hold
Description epoch of the elements of the orbits of artificial satellites and astronomical objects
Represents epoch (Q2703)
Data type Point in time
Template parameter en:Template:Infobox spaceflight: "orbit_epoch" (Template:Infobox spaceflight (Q14907524)); en:Template:Planetbox orbit: "epoch" (Template:Planetbox orbit (Q8116171))
Domain astronomical objects, artificial satellites, spaceflight
Example Apollo 11 (Q43653) => July 19, 1969, 21:44 UTC; Gliese 876 d (Q869944) => 2,450,602.093 HJD (!!)
Proposed by Paperoastro (talk)
Discussion

Epoch is the seventh parameter of an orbit: it is necessary to define an orbit. In this proposal I'd like to discuss:

  1. we need a new property (this) or we can use point in time (P585)?
  2. epoch refers to 6 orbital parameters: how to join them?
  3. for spaceflights and artificial satellites the epoch is expressed in usual calendar unity; for extrasolar planet in Julian day or some its variants. How to solve it?

Paperoastro (talk) 12:32, 25 October 2013 (UTC)

  • Symbol support vote.svg Support It might be useful to have a specific property because it can be further developed to have customisations and different representations (J2000, TT, etc.). As for bundling orbit parameters, one possible solution is to have an item to represent the orbit and link it with a property "orbit parameters". --Micru (talk) 20:37, 12 November 2013 (UTC)
  • I am not an astronomer and having read the en:Epoch (astronomy) article I am still confused.
On the one hand epoch refers in some way to unusual ways for expressing calendar dates - for these we could use the current wikidata time variable type and ask the devs to offer alternative ways of displaying this at some future date
on the other hand it seems to refer to unusual units of time (Julian years and Julian days) - for these we can use seconds until the devs get round to creating alternative units of time
on the third hand it refers to IAU standards - we can create items for these
What have I misunderstood? Filceolaire (talk) 13:28, 3 June 2014 (UTC)

Contact times of eclipses[edit]

waiting for datatype
   On hold
Description Contact times of eclipses: P1, U1, U2, U3, U4, P4
Data type Point in time
Domain lunar and solar eclipses
Allowed values time in UTC
Example 6 April 2015, 03:22 UTC. qualifier <applies to part:U4 - solar eclipse>
Source Wikipedia list article, e.g. en:List of 21st-century lunar eclipses
I have amended the example as I understand it should be used. Please check I got it right.
Can this property be extended so it can be used on solar eclipses as well? Creating a property that can only be used on lunar eclipses seems a bit narrow. Filceolaire (talk) 00:10, 29 April 2015 (UTC)
Yes, I believe this is correct (see en:Solar eclipse of August 11, 1999#Notable times and coordinates for example. I will ask someone more knowledgeable to comment here. MSGJ (talk) 09:52, 29 April 2015 (UTC)
P1-4 and U1-4 apply to solar and lunar eclipses, but differently. A solar eclipse is a en:Transit (astronomy) so the timing is based on the viewing location INSIDE a shadow, while a lunar eclipse has viewers looking at an object INSIDE a shadow, so everyone sees the same appearance at the same universal time. So knowing the P1-4,U1-4 times for a solar eclipse are less useful for any given observer. Tomruen (talk) 01:08, 30 April 2015 (UTC)
If U4 for a solar eclipse is different from U4 for a lunar eclipse then we should have separate items for these with the "applies to part" qualifier linking to the appropriate item in each case. This means this property could be used for solar eclipses if we just change the label. I would Symbol support vote.svg Support this property if you made this change to the property label and description. Filceolaire (talk) 03:04, 30 April 2015 (UTC)
Could you explain what you mean by "This means this property could be used for solar eclipses if we just change the label." Does that mean that properties can have more than one label? Or do you mean that you could have two statements for "subject item of this property"? Or do you mean something else? MSGJ (talk) 12:24, 30 April 2015 (UTC)
Rename the property as "Contact time for eclipses". Change the description to "Contact time for lunar and solar eclipses (U1, U2 etc. lunar and U1, U2 etc. solar)". Filceolaire (talk) 16:41, 30 April 2015 (UTC)
✓ Done, although no corresponding items created yet MSGJ (talk) 09:22, 5 June 2015 (UTC)
I ammended the example a little. I think this is good now and support - as my comment above. Joe Filceolaire (talk) 16:48, 12 September 2015 (UTC)