Property talk:P548

Documentation

• Start a query
• Properties using this qualifier (statistics)
• Count

version type
type of version (qualifier for P348, software version), e.g. alpha, beta, stable

Represents	software version type (Q28530564)
Data type	Item
Domain	Software or other products (note: this should be moved to the property statements)
Allowed values
Example	MediaWiki (Q83) → stable version (Q2804309)
Robot and gadget jobs	DeltaBot does the following jobs: Move source to qualifier
See also	modified version of (P5059), software version identifier (P348)
Lists	Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Database reports/Constraint violations/P548
Proposal discussion	Proposal discussion
Current uses	Total 402,278 Main statement 7 <0.1% of uses Qualifier 402,233 >99.9% of uses Reference 38 <0.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 qualifier (Q54828449): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P548#Scope, hourly updated report, SPARQL

Value type “software version type (Q28530564), amendment and abolition of laws and regulations (Q107524042), type of legislation (Q110430875)”: 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 version type (Q28530564), amendment and abolition of laws and regulations (Q107524042), type of legislation (Q110430875) (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/P548#Value type Q28530564, Q107524042, Q110430875, SPARQL

None of game demo (Q1755420): value must not be any of the specified items.
Replacement property:
Replacement 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/P548#none of, SPARQL

This property is being used by: ca:Plantilla:Infotaula de programari, ca:Plantilla:Infotaula de programari/prova Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Discussion

Values in use

Since the covi pages don’t properly evaluate qualifiers, I’d like to provide a query that allows to get an overview of the value items of version type (P548) qualifiers:

# values used with P548 (version type) qualifiers of P348 (software version) claims
SELECT ?value ?valueLabel (COUNT(?value) AS ?cnt) WHERE {
  ?item ?prop [ pq:P548 ?value ] .
  SERVICE wikibase:label { bd:serviceParam wikibase:language 'en' }
} GROUP BY ?value ?valueLabel ORDER BY DESC(?cnt)

Try it!

—MisterSynergy (talk) 06:51, 20 September 2017 (UTC)

Usage of P548 for to indicate the support of a release

WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.

Most of predefined values for version type (P548) use software version type in the sense of pre-release vs. release (query for those values). But Q2804309 (stable version) and Q21683863 (obsolete version) suggest that the qualifier is meant to indicate whether a version is still supported or not.

Suggested Solution: Change stable version (Q2804309) and obsolete version (Q21683863) so that P548 is only used for the version type (as in prerelease vs. release) and use a different property such as discontinued date (P2669) to indicate whether a version is still supported or not. --Konstin (talk) 15:27, 16 March 2018 (UTC)

 Support I agree with Konstin. Also beta-versions become obsolete when there's a new (beta) version. So we should not mix the type of the release (alpha, beta, rc, stable) with the current status of the version. We have ranks to indicate which version is the newest and we can use discontinued date (P2669) for details. This is also not only how it's done with most items on software but also how it's done in most other areas: Don't delete or change a statement once it becomes outdated but change it's rank and set an end-date. The amount of items which have several stable versions at a time is small, so it's reasonable to add P2669 for those cases. -- MichaelSchoenitzer (talk) 19:48, 16 March 2018 (UTC)

This is an illustration that it’s hard to put a lot of information as qualifiers of statement for versions : you start conflating informations about the statement with informations about the version. Things would be more easy to deal with with proper items for the versions ( in a spirit similar to has edition or translation (P747) and edition or translation of (P629) for books). author  TomT0m / talk page 17:11, 18 March 2018 (UTC)

I've removed the "is supported" part the stable and obsolete version. --Konstin (talk) 12:12, 16 May 2018 (UTC)

Allow the use as property

Why not using it as property for items that actually are software versions?--Malore (talk) 04:03, 15 July 2018 (UTC)

Extension

I have started using this qualifier to disambiguate video game releases (see eg Q1166232#P1933) ; as such I have added as accepted values limited edition (Q6549529) & special edition (Q1341283). Let me know if that causes issues / you believe this is bad in general :-) Jean-Fred (talk) 22:04, 19 July 2019 (UTC)