Property talk:P6931

From Wikidata
Jump to navigation Jump to search

Documentation

Repology project name
package name and identifier in Repology
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “software (Q7397), typeface (Q17451): item must contain property “instance of (P31)” with classes “software (Q7397), typeface (Q17451)” or their subclasses (defined using subclass of (P279)). (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/P6931#Type Q7397, Q17451, SPARQL
Single value: this property generally contains a single value. (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/P6931#Single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (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/P6931#Unique value, SPARQL (every item), SPARQL (by value)
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (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/P6931#Entity types
Scope is as main value (Q54828448): the property must be used by specified way only (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/P6931#Scope, SPARQL

Discussion[edit]

Note on Repology names[edit]

The immutability of project names in Repology is not guaranteed.

  • First of all, Repology project names are based on package names from different repositories, and these may change at any moment.
  • Next, Repology applies its own rules to merge multiple entries originally created by different package names (of the same project) into a single entry.
This is a continuous process, so as far as new rules are added and updated, names will change too.
  • Sometimes different projects with the same name happen, so disambiguation suffixes have to be introduced (e.g. clementine-wm vs clementine-player).
  • There's no clean policy on which single name is picked out of variety (7kaa vs. seven-kingdoms vs. seven-kingdoms-ancient-adversaries) yet. If we come with one at some point, we could rename a bunch of entries.

A rework of naming scheme is also planned in near future, mainly to make disambiguation suffixes more explicit, this will change a lot of names at once too. But this can probably be coordinated to apply corresponding changes to Wikidata at the same time. --AMDmi3 (talk) 19:54, 1 July 2019 (UTC)[reply]

You could expose a static numeric ID for linking to compensate for the volatile slug. Matthias M. (talk) 13:57, 30 August 2023 (UTC)[reply]

Repology contact[edit]

I'm Repology author, my contacts are

--AMDmi3 (talk) 19:54, 1 July 2019 (UTC)[reply]