Add documentation example for dual license projects

[VillePihlava]

Hello!

I develop public transit related software for Digitransit in Finland. We were asked to add a publiccode.yml file to our repository: HSLdevcom/digitransit-ui#5620. This PR adds an example for dual-license projects to make the documentation more clear.

[vercel]

@VillePihlava is attempting to deploy a commit to the bfabio's projects Team on Vercel.

A member of the Team first needs to authorize it.

[fvsamson]

LGTM

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
publiccode-yml	Ready	Preview, Comment	Jan 29, 2026 4:46pm

[bfabio]

Hi @VillePihlava, this is actually already supported, the current spec states:

The string must contain a valid SPDX expression, referring to one (or multiple) open-source license
https://yml.publiccode.tools/schema.core.html#section-legal

This means you can use this SPDX expression for your case: "EUPL-1.2 OR AGPL-3.0-or-later" (or "EUPL-1.2 OR AGPL-3.0-only")

[VillePihlava]

This means you can use this SPDX expression for your case: "EUPL-1.2 OR AGPL-3.0-or-later" (or "EUPL-1.2 OR AGPL-3.0-only")

Thanks, didn't realize it worked this way. I did read the part of the spec you quoted, but misinterpreted "one (or multiple)" as referring to licenses such as AGPL-3.0-or-later.

I can close this PR or amend the docs with a short text for dual-license setups just in case someone else makes the same mistake in the future. Which course of action do you prefer?

[bfabio]

I can close this PR or amend the docs with a short text for dual-license setups just in case someone else makes the same mistake in the future. Which course of action do you prefer?

Pointing out that feature as an example would be nice, thanks!

[VillePihlava]

Pointing out that feature as an example would be nice, thanks!

I added an example for a dual-license SPDX expression.

[bfabio]

@VillePihlava thanks!

@yaml-9000 patch

[yaml-9000]

Thanks for your contribution 🙏

This is now marked as a bugfix-change proposal to the standard,
this means that this change won't break any compatibility with the old versions of the Standard.

Example of bugfix changes are typo fixes.

The next eligible voting round will take place on January 30, 2026

cc @publiccodeyml/steering-committee

_{📄 Voting procedure | 📄 Working Group Charter | 🤖 bot commands}

[bfabio]

@yaml-9000 vote-start

[yaml-9000]

Voting is now open on this proposal!

If you are a member of the Steering Committee you can now vote!

The polls will stay open for 14 days, until Fri, 13 Feb 2026 09:05:39 GMT.

Leave a 👍 (thumbs up) on this comment to accept the proposal or a 👎 (thumbs down) to reject it.

cc @publiccodeyml/steering-committee

_{📄 Voting procedure | 📄 Working Group Charter | 🤖 bot commands}