Property talk:P2824

From Wikidata
Jump to: navigation, search

Documentation

Gazetteer of Planetary Nomenclature ID
identifier of a feature on an astronomical body in the Gazetteer of Planetary Nomenclature
Data type External identifier
Template parameter en:Template:GPN: |id= - Template:GPN (Q12981608)
Allowed values [1-9][0-9]{0,3}|1[0-9]{4}|
Example Rossby (Q19972237)5194
Source http://planetarynames.wr.usgs.gov/
Formatter URL http://planetarynames.wr.usgs.gov/Feature/$1
Lists
Proposal discussion Property proposal/Natural science
Current uses 8,343
[create] Create a translatable help page (preferably in English) for this property to be included here
Format “([1-9][0-9]{0,3}|1[0-9]{4}|)”: value must be formatted using this pattern (PCRE syntax).
List of this constraint violations: Database reports/Constraint violations/P2824#Format, hourly updated report, SPARQL
Single value: this property generally contains a single value.
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2824#single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items.
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2824#distinct values, SPARQL (every item), SPARQL (by value)
Conflicts with “instance of (P31): human (Q5): this property must not be used with listed properties and values.
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2824#Conflicts with P31, SPARQL
Item “located on astronomical body (P376): Items with this property should also have “located on astronomical body (P376)”.
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P2824#Item P376, SPARQL



Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Allowing 'no value' constraint ?[edit]

Hi,

ValterVB raised an interesting point on my talk page. Should we allow 'no value'/'some value' when a value can be expected but there is none? Right now there is two constraint violations for Mons Argenteus (Q1945231) (added by me) and Henry (Q18559333) (added by Nikki), there will be probably a few more.

FYI, that's something we usually do with Mérimée ID (P380) but with 'some value' ; for example on no label (Q23497952) as we know there will be a value added to the database in 2016-2017.

Paperoastro Sarilho1 YsogoCekli829 Manlleus Meodudlye, with only limited amount of time to spend in the foreseable future. Romaine - like adding observatory codes + mapping usage (like the *observatory codes) mikeu Jc3s5h VIGNERON Harlock81 Ptolusque Pictogram voting comment.svg Notified participants of WikiProject Astronomy

Cdlt, VIGNERON (talk) 10:24, 4 June 2016 (UTC)

I think it should be allowed (I was intending to modify the constraint to allow it, I added a bunch more of them earlier today) because it allows us to distinguish between things which probably do have one and it just hasn't been added yet from things which haven't been assigned one. I think novalue is the right thing to use here. somevalue would mean that it does have an ID but we don't know what it is, but there is no reason to think that the items already have IDs or even that they will definitely get one in the future. It would probably be a good idea to add point in time (P585) qualifiers to the statements. - Nikki (talk) 12:23, 4 June 2016 (UTC)
@Nikki, VIGNERON: The meaning of "no value" is: id exist but we (wikidata user) haven't found, or the value don't exist but we (wikidata user) think that is necessary? --ValterVB (talk) 13:10, 4 June 2016 (UTC)
@ValterVB, Nikki: here, the meaning of "no value" is more id doesn't exist but should exist/is expected. id exist but we (wikidata user) haven't found match the meaning of "some value". In the case of Mérimée ID (P380) "some value" stand for id will exist but we have to wait the next database update (update around once a year, usually in the summer) ; I don't know exactly how database is updated concerning the Gazetteer (if someone has insights, you're welcome to share them). Cdlt, VIGNERON (talk) 13:17, 4 June 2016 (UTC)
The first one would be "some value", the second one would be "no value" (see the glossary). - Nikki (talk) 08:53, 5 June 2016 (UTC)
"Somevalue" is generally taken to mean that it actually exists, but we don't know it (which seems odd for identifiers with formatter urls). It shouldn't be based on some forecast.
--- Jura 08:56, 5 June 2016 (UTC)
I'm not the one using it as a forecast. Maybe you intended to reply to VIGNERON. - Nikki (talk) 09:11, 5 June 2016 (UTC)
True we shouldn't forecast but it's more than forecasting when you are sure the ID will exist (and for Mérimée ID (P380) we are 99,99% sure). Plus, I don't see any real difference between « value is unknown because XXX » or « value is unknown yet », is both case the value is unknown...
Does anybody know precisely and exactly how the Gazetteer of Planetary Nomenclature process of the database works ? Does 'no value' or 'some value' fit best the situation(s) ? I think 'no value' is better here since the value isn't unknown, we do know there is no value.
Cdlt, VIGNERON (talk) 10:41, 5 June 2016 (UTC)

Just for the chronicle[edit]

  • Mars completed at 15 July 2016 (only approved feature) query --ValterVB (talk) 10:02, 15 July 2016 (UTC)
  • Venus completed at 15 July 2016 (only approved feature) query --ValterVB (talk) 10:02, 15 July 2016 (UTC)
  • Mercury completed at 16 July 2016 (only approved feature) query --ValterVB (talk) 15:11, 16 July 2016 (UTC)
  • Ceres completed at 16 July 2016 (only approved feature) query --ValterVB (talk) 16:03, 16 July 2016 (UTC)