Skip to content

v3 -> v4 changes - #143

Draft
meldra wants to merge 1 commit into
codemeta:masterfrom
meldra:update-v3-v4
Draft

meldra wants to merge 1 commit into
codemeta:masterfrom
meldra:update-v3-v4

Conversation

@meldra

@meldra meldra commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

This change adds a badge shortcode built based on the supported versions config added recently. It will help reduce the number of places the version number needs updating. Sadly, adding shortcodes to codeblocks ruins their formatting.

The badge has been added to the json-ld page to replace the existing badge there, and has also been added to the tools page to further emphasize the latest version as described in #122. It was also added to the context section of the user guide.

The user guide retains links to real-world examples using old versions towards the end of the document. An admonition has been added under the examples links to prompt people to check and not copy it verbatim without due care.

This change adds a `badge` shortcode built based on the supported
versions config added recently. It will help reduce the number of
places the version number needs updating. Sadly, adding shortcodes
to codeblocks ruins their formatting.

The badge has been added to the json-ld page to replace the existing
badge there, and has also been added to the tools page to further
emphasize the latest version as described in codemeta#122. It was also added
to the context section of the user guide.

The user guide retains links to real-world examples using old
versions towards the end of the document. An admonition has been
added under the examples links to prompt people to check and not
copy it verbatim without due care.
@meldra

meldra commented Sep 12, 2026

Copy link
Copy Markdown
Contributor Author

At some point, we need to decide what version string format we want to stick with in the content (with perhaps the context URLS being excepted of course) and be consistent.

The updates this round have kept the formats consistent with the contexts they were in, for example on the tools page, which uses a 3.0.0 format, and uses it to refer to anything in the v3.x version family.

As far as I can tell, there is not an in-use version that uses the last segment of that format.

@meldra

meldra commented Sep 12, 2026

Copy link
Copy Markdown
Contributor Author

uses a 3.0.0 format, and uses it to refer to anything in the v3.x version family.

To be clear, this doesn't really make sense to me. This is a discussion for the community though.

@meldra

meldra commented Sep 12, 2026

Copy link
Copy Markdown
Contributor Author

Draft until v4 officially released

@lindangulopez

Copy link
Copy Markdown
Contributor

Thanks @meldra.

We'll have/can discuss this at the weekly Tuesday meetings:

(i) Version format: agreed. Proposal: major.minor in content (v4.0), context URLs unchanged.

(ii) Clash with #144: with supported = ['4','3','2'], the badge's substr 0 3 gives w3id.org/codemeta/4, which doesn't resolve. Suggest the badge reads .Site.Params.latest instead. I suggest for after v4 release: merge #144, rebase #143, set latest = "4.0".

(iii) Tools page, #122: #131's ⚠️ plus this badge covers what I asked for in #122, so I'll close it once #143 lands. One gap: once latest is 4.0, every v3-only tool gets the ⚠️. Could the tip say v3 tools remain usable?

Esteban will pick up on the PR final v4 on Thursday.

Kind regards,
Linda

@meldra

meldra commented Sep 23, 2026

Copy link
Copy Markdown
Contributor Author

(iii) Tools page, #122: #131's ⚠️ plus this badge covers what I asked for in #122, so I'll close it once #143 lands. One gap: once latest is 4.0, every v3-only tool gets the ⚠️. Could the tip say v3 tools remain usable?

@lindangulopez your rationale for the change was:

New users have no way to distinguish safe, current tools from outdated ones, which undermines confidence and risks incorrect metadata generation.

Should we change focus from that statement and put less emphasis on alerting of risks/safety and instead use affirmation of the latest version? A warning that applies to everything will indeed saturate its meaning and make it useless.

@meldra

meldra commented Sep 24, 2026

Copy link
Copy Markdown
Contributor Author

and instead use affirmation of the latest version

preview demo: https://codemeta.opinions.monster/tools/

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants