Property talk:P348
Contents
- 1 Documentation
- 2 Qualifiers
- 3 German translation
- 4 Constraint:Qualifiers
- 5 Delete old versions?
- 6 Overuse of this property for licenses
- 7 How to mark the latest stable version when older versions are kept
- 8 How to mark a version as unstable
- 9 Labels and descriptions are wrong
- 10 Don't keep old versions
- 11 Document versions
- 12 Automatic updates by Github-wiki-bot
- 13 Property constraints regex may be wrong
- 14 How do I specifiy and later as in
- 15 Adding version URL for software
Documentation
version(s) of the software, current and past
| Description | Version numbers of versions of the software. Qualify with version type (P548) and point in time (P585). |
|---|---|
| Represents | status (Q11424100), version (Q20826013), software versioning (Q10859422) |
| Data type | String |
| Domain | According to this template:
software (Q7397)
According to statements in the property:
When possible, data should only be stored as statementssoftware (Q7397), software component (Q20919931) and file format (Q235557) |
| Allowed values | According to this template:
[words] digits[.digits[.digits]][letters] [build/rc/alpha/beta/-/ digits] [ (text name)];
According to statements in the property:
When possible, data should only be stored as statements[\w\s]*\d+(\.\d+){0,4}\w*(\s|-)?([Bb]uild|B|rc|RC|[Aa]lpha|[Bb]eta|[Uu]pdate|RTM|ESR)?(\s|-)?\d*(\s|-)?(\([\w\s]+\d*\))? |
| Example | Bugzilla (Q55671) → 4.5.1 Avast Antivirus (Q1574) → 2014.9.0.2016.330 AWK (Q213970) → IEEE Std 1003.1-2008 AmigaOS (Q380526) → 4.1 Update 6 Java platform (Q1713118) → 7 Update 51 Plan 9 from Bell Labs (Q725779) → Fourth Edition Windows Internet Explorer 8 (Q841259) → 8.0.6001.18702IC Composer (Q15252222) → 1.0.0-alpha8 AIMP (Q293825) → 3.55 Build 1324 Erlang (Q334879) → R16B03 Kubuntu (Q11250) → 13.04 (Raring Ringtail) Microsoft Office (Q11255) → 15.0.4551.1011 Microsoft Office (Q11255) → 2011 (14.3.9 SP3) CrunchBang Linux (Q11983) → 11 20130506 (Waldorf) MariaDB (Q787177) → 5.5.33a Internet Explorer 10 (Q819537) → 10.0.9200.16521 RTM Pokémon GO (Q20966579) → 0.35.0 Mozilla Firefox (Q698) → 52.2.1 ESR |
| Format and edit filter validation | Abuse filter #61 |
| Tracking: same | no label (Q32069410) |
| Tracking: differences | no label (Q32069376) |
| Tracking: usage | Category:Pages using Wikidata property P348 (Q20989971) |
| Tracking: local yes, WD no | Category:Software version not in Wikidata, but available on Wikipedia (Q26467729) |
| See also | tabular software version (P4669) |
| Lists | |
| Proposal discussion | Originally created without a formal discussion |
| Current uses | 10,574 |
| Search for values |
|
Type “software (Q7397), software component (Q20919931), file format (Q235557)”: element must contain property “instance of (P31)” with classes “software (Q7397), software component (Q20919931), file format (Q235557)” or their subclasses (defined using subclass of (P279)). (Help) Exceptions are possible as rare values may exist. List of this constraint violations: Database reports/Constraint violations/P348#Type Q7397, Q20919931, Q235557, SPARQL, SPARQL (new) |
|
Format “[\w\s]*\d+(\.\d+){0,4}\w*(\s|-)?([Bb]uild|B|rc|RC|[Aa]lpha|[Bb]eta|[Uu]pdate|RTM)?(\s|-)?\d*(\s|-)?(\([\w\s]+\d*\))?”: value must be formatted using this pattern (PCRE syntax). (Help) Exceptions are possible as rare values may exist. List of this constraint violations: Database reports/Constraint violations/P348#Format, SPARQL, SPARQL (new) |
|
Qualifiers “named after (P138), license (P275), location (P276), platform (P400), version type (P548), publication date (P577), start time (P580), end time (P582), point in time (P585), statement is subject of (P805), title (P1476), download link (P4945), DOI (P356), operating system (P306), use (P366)”: this property should be used only with the listed qualifiers. (Help) Exceptions are possible as rare values may exist. List of this constraint violations: Database reports/Constraint violations/P348#Allowed qualifiers, SPARQL, SPARQL (new) |
Qualifiers[edit]
I report this discussion on the project chat (Wikidata:Project_chat/Archive/2013/04#Property:P348_-_Stable_version_.28software_only.29) regarding the qualifiers properties. --Viscontino talk 08:45, 5 April 2013 (UTC)
- Qualifiers are available now, I think we could change the name of this property. The only things we need is a qualifier property (something like "state" or similar, a property which has a general use) and an item where we could link to. (I couldn't find an existing item for "stable version", they might be an item in other languages?) --#Reaper (talk) 13:16, 27 April 2013 (UTC)
- I support this idear. Is their any current discussion about that, because the property name is still "stable version"? --Stiegenaufgang (talk) 16:55, 5 June 2014 (UTC)
Done. John Vandenberg (talk) 02:01, 19 September 2014 (UTC)
Done. German translation[edit]
I think the German translation of this property should be updated, because it has a different meaning than the English one.
- stabile Version → Version (englː version)
- aktuell stabile Version der Software → stabile Version der Software (englː stable version of the software)
Stiegenaufgang (talk) 23:23, 15 November 2014 (UTC)
Constraint:Qualifiers[edit]
Recently I have added the constraint on qualifiers but there are some discrepancies (many qualifiers were added by me):
- country (P17)/continent (P30) × location (P276) – I suggest to use only location (P276)
- operating system (P306) × platform (P400) –
Comment - start time (P580) (end time (P582)?) × publication date (P577) × point in time (P585) – Comment
Matěj Suchánek (talk) 17:05, 22 December 2014 (UTC)
Delete old versions?[edit]
Just to be clear: Should we delete statements with old, superseded versions? (Except if there are multiple development branches, like GnuPG 1.4.x and 2.x.) —DSGalaktos (talk) 14:11, 26 March 2015 (UTC)
- Some links (I suppose Wikidata could handle more versions, using qualifiers and ranks): Wikidata:Bot requests/Archive/2013/04#Keeping last stable software version up to date, Wikidata:Requests for permissions/Bot/SamoaBot 8, Wikidata:Project chat/Archive/2013/04#Property:P348 - Stable version (software_only), Wikidata:Project chat/Archive/2014/12#Unintentional removal of statements in software version (P348), Wikidata talk:Abuse filter#Version. Matěj Suchánek (talk) 16:43, 26 March 2015 (UTC)
- So from the last two links I take it the statements are supposed to stay? —DSGalaktos (talk) 22:14, 26 March 2015 (UTC)
- Yes :) ·addshore· talk to me! 00:05, 27 March 2015 (UTC)
- Does this "Yes" answer the last question or the question in the heading? I guess it's a "yes" again ;) Brevity (talk) 20:40, 2 August 2016 (UTC)
- There is a scalability problem with this. I'm thinking of "rapid release cycles", see w:History of Firefox, w:Firefox version history, w:Google Chrome version history… Even worse, some web applications are tagging new versions like, more than weekly (e.g. Laravel releases, and I guess we could easily find even more frequently released applications). Od1n (talk) 20:19, 6 March 2017 (UTC)
- Does this "Yes" answer the last question or the question in the heading? I guess it's a "yes" again ;) Brevity (talk) 20:40, 2 August 2016 (UTC)
- Yes :) ·addshore· talk to me! 00:05, 27 March 2015 (UTC)
- So from the last two links I take it the statements are supposed to stay? —DSGalaktos (talk) 22:14, 26 March 2015 (UTC)
Overuse of this property for licenses[edit]
I have seen this property in (mis-)use for licenses, i.e. Creative Commons Attribution-ShareAlike 2.0 Generic (Q19068220). I am not sure if it is a good idea to mix both, especially since this property explicitly states it is for software.
Maybe there should be a new property specifically for license versions. What do you think? --Wiki-Wuzzy (talk) 22:41, 15 April 2015 (UTC)
How to mark the latest stable version when older versions are kept[edit]
Use three seashells small boxes on the left of the date to mark the latest version as "Preferred rank". Don't forget to mark the older version(s) as "Normal (or deprecated) rank". The RedBurn (ϕ) 11:21, 25 May 2015 (UTC)
- Just a small follow-up question: Should the current version be marked as preferred and older versions as normal, or the current version as normal and the older versions as deprecated? --1-Byte (talk) 14:21, 1 February 2016 (UTC)
- Is that the recommended way of doing that? The first try of changing the rank of an old version to “deprecated” yields a warning that says setting to deprecated is “also incorrect”. --AVRS (talk) 18:42, 28 March 2016 (UTC)
How to mark a version as unstable[edit]
See P548 Talk: add a qualifier "type of version", which current possible values are "alpha version" and "beta version". The RedBurn (ϕ) 13:01, 25 May 2015 (UTC)
Be sure to add a qualifier "type of version" with value Q19972162 (stable version) to at least the latest stable version to make it possible to selectively retrieve it from a template. The RedBurn (ϕ) 16:27, 25 May 2015 (UTC)
Labels and descriptions are wrong[edit]
For example, in Ukrainian, this property is labelled as "стабільна версія", with the description "остання стабільна версія програмного забезпечення". "стабільна" means "stable", "остання" means "last". Of course, people will continue to delete non-last and non-stable versions. — Vort (talk) 07:36, 4 December 2015 (UTC)
- I just went through the label list and removed loads of outdated labels and descriptions that looked like they included “latest” or “stable”. Main edit, auxiliary edits. I probably broke some grammar, so it would be great if people actually speaking these languages could review the changes and fix problems. Also, I wasn’t able to fix Icelandic, because has edition (P747) has a conflicting label. —Galaktos (talk) 10:20, 4 December 2015 (UTC)
Don't keep old versions[edit]
Regarding the software items I came across, none had a complete listing of versions (as eg compared to the list of releases on GitHub). Version lists just started with the version that was current when the item was created, and had "holes" in the list of newer/updated versions. Thus, the list of version numbers is irrelevant and misleading (eg you cannot compare counts/periodicity of version number updates across software items, which could be interesting facts). IMO, only the newest one(s) should be kept. --Brevity (talk) 20:20, 2 August 2016 (UTC)
- Some articles have tables of versions, for which Wikidata could be referred to. --AVRS (talk) 21:21, 2 August 2016 (UTC)
- Major versions should be kept to track development.
- First version should be kept.
- d1g (talk) 22:20, 9 September 2017 (UTC)
- Entries are not deemed to be complete. We don't delete no longer current, but accurate statements. Just set the recent one as preferred. See Help:Ranks.
--- Jura 08:53, 10 September 2017 (UTC)
Document versions[edit]
Notified participants of WikiProject Informatics
Can this be generalized to just "version" to allow for document versions? This is quite common with technical specifications, e.g., .ZIP File Format Specification, version 6.3.4 (Q26211547) is version 6.3.4 of ZIP (Q136218) (currently it seems to be abusing edition number (P393)) or Creative Commons Attribution-ShareAlike 2.0 Generic (Q19068220) is version 2.0 of Creative Commons Attribution-ShareAlike (Q6905942) (currently abusing this property unless this is generalized to encompass this usage). 50.53.1.33 21:19, 26 September 2016 (UTC)
Support. Specifying the version for the standards is quite common practice both in Wikipedia and in Wikidata. We should rename the label to "version" (as already done in many languages) and expand the scope to documents. —putnik 22:21, 2 April 2018 (UTC)
Support. Specifying the version for the standards is quite common practice both in Wikipedia and in Wikidata. We should rename the label to "version" (as already done in many languages) and expand the scope to documents. —Automatic updates by Github-wiki-bot[edit]
User:Github-wiki-bot automatically extracts stable releases and the release dates of Software from GitHub. – Simon04 (talk) 12:15, 4 August 2017 (UTC)
Property constraints regex may be wrong[edit]
Please check GNU Linux-libre (Q665683) to see how it is conflicting with real data. NMaia (talk) 11:51, 23 March 2018 (UTC)
How do I specifiy and later as in[edit]
version requirement, e.g. version 1.23+ for Property:P1547? --[[kgh]] (talk) 23:28, 4 April 2018 (UTC)
Adding version URL for software[edit]
Lets say I'm adding a version for this game data:
https://starbounder.org/Version_1.3.3
The constrains for "software version" doesn't allow me to add the URL in the version number so it's easy to access the changes made in that specific version. Which is easily accessible with the link I gave before.
Can we add the "URL" category to the version software constrains?
As a workaround I'll be using "download link" but it's not entirely true as the link isn't that.
--Frenchiveruti (talk) 16:22, 12 June 2018 (UTC)
