Property talk:P4428
Latest comment: 6 years ago by Katjos in topic Usage for description of software features
Documentation
implementation of
implementation of a standard, program, specification or programming language
implementation of a standard, program, specification or programming language
Represents | implementation of a programming language (Q4117406), programming language (Q9143) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type | Item | ||||||||||||
Example | CPython (Q599384) → Python (Q28865) Scribunto module (Q11382506) → Lua (Q207316) JavaScript (Q2005) → ECMAScript (Q259138) HTTP client (Q2979024) → HTTP (Q8777) | ||||||||||||
Tracking: usage | Category:Pages using Wikidata property P4428 (Q105635681) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
[create Create a translatable help page (preferably in English) for this property to be included here]
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P4428#Scope, hourly updated report, SPARQLValue type “programming language (Q9143), technical standard (Q317623), computer program (Q40056), specification (Q2101564), application programming interface (Q165194), algorithm (Q8366), rule (Q1151067), domain-specific language (Q691358), Wikimedia template (Q11266439), function (Q11348), software design pattern (Q181156)”: This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value programming language (Q9143), technical standard (Q317623), computer program (Q40056), specification (Q2101564), application programming interface (Q165194), algorithm (Q8366), rule (Q1151067), domain-specific language (Q691358), Wikimedia template (Q11266439), function (Q11348), software design pattern (Q181156) (or a subclass thereof). (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/P4428#Value type Q9143, Q317623, Q40056, Q2101564, Q165194, Q8366, Q1151067, Q691358, Q11266439, Q11348, Q181156, SPARQL
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/P4428#Entity types
Usage for description of software features
editWhen adding software applications I found different uses of properties to describe the aim and features. In some cases manifestation of (P1557) is used to describe the implementation of a software package (e.g. ontology editor (Q453843) or FileZilla (Q300662). Others use implementation of (P4428) (e.g.Mozilla Thunderbird (Q483604) or Microsoft Outlook (Q80911)). I would rather use implementation of (P4428) to describe features and aim of the software. I would be interested in the communities feedback or a link to best practices. --Katjos (talk) 14:13, 10 March 2018 (UTC)