Property talk:P1547

From Wikidata
Jump to navigation Jump to search

Documentation

depends on software
subject software depends on object software
Descriptionthe subject software depends on the object software
Representssoftware dependency (Q56859575)
Data typeItem
Domain
According to this template: software (Q7397)
According to statements in the property:
software (Q7397), software bug (Q179550), fictional software (Q55566469) or software version (Q20826013)
When possible, data should only be stored as statements
Allowed valuesshould be instance of software (Q7397), or of a item which is a subclass of software (Q7397) (note: this should be moved to the property statements)
ExampleSMPlayer (Q2596578)MPlayer (Q131344)
LaTeX (Q5310)TeX (Q5301)
Sourceinfobox, software documentation, software packages metadata (note: this information should be moved to a property statement; use property source website for the property (P1896))
Robot and gadget jobsallowed values consistency check
Tracking: usageCategory:Pages using Wikidata property P1547 (Q124982334)
See alsoGUI toolkit or framework (P1414), based on (P144), software engine (P408)
Lists
Proposal discussionProposal discussion
Current uses
Total32,027
Main statement31,97999.9% of uses
Qualifier480.1% of 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)
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/P1547#Scope, 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/P1547#Entity types
Value type “software (Q7397), software version (Q20826013): This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value software (Q7397), software version (Q20826013) (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/P1547#Value type Q7397, Q20826013, SPARQL
Conflicts with “instance of (P31): video game (Q7889): this property must not be used with the listed properties and values. (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/P1547#Conflicts with P31, search, SPARQL

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

Extension request[edit]

Can this property be used for other domains?--Micru (talk) 09:23, 18 October 2014 (UTC)[reply]

Example?
I think we have enough properties to cover real dependencies now. d1g (talk) 21:44, 9 September 2017 (UTC)[reply]

Optional dependencies?[edit]

How can optional dependencies be specified? --Hhm8 (talk) 19:40, 27 November 2018 (UTC)[reply]

Good question. I would use has characteristic (P1552)optional (Q59864995)Dexxor (talk) 19:33, 22 May 2020 (UTC)[reply]

video game expansion packs / DLCs[edit]

It’s been floated to use this property to model the relationship between video game expansion pack (Q209163) (and downloadable content (Q1066707)) and video game (Q7889) − for example, BioShock 2: Minerva's Den (Q24806656)depends on software (P1547)BioShock 2 (Q302839) and StarCraft: Brood War (Q840409)depends on software (P1547)StarCraft (Q165929). Does this make sense? There is some usage of it already Jean-Fred (talk) 13:00, 4 September 2020 (UTC)[reply]

SELECT ?item ?itemLabel ?game ?gameLabel WHERE {
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
  ?item wdt:P1547 ?game.
  ?game wdt:P31/wdt:P279* wd:Q7889.
}
Try it!

It is definitely not wrong but wouldn’t it be nice to create a new property expansion of that can be used for both video games and board games? —Dexxor (talk) 14:44, 4 September 2020 (UTC)[reply]

Also a possibility :) I’ll make a proposal and mention this property. Jean-Fred (talk) 16:03, 4 September 2020 (UTC)[reply]
Huh, turns out Wikidata:Property proposal/expansion has been open for a while ; had completely forgotten about it. Jean-Fred (talk) 16:32, 4 September 2020 (UTC)[reply]
I started Wikidata:Property proposal/expansion of. Jean-Fred (talk) 09:48, 7 September 2020 (UTC)[reply]