Triage Errata and Discuss-Call for v1.2 / v1.3 / other
Open
@niklasl is already working on this.
Since Sep 9, 2026.
- Dominant language
- HTML
- Stars
- 106
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I propose to go through the Errata and Discuss-Call columns, to assign each issue a milestone: v1.2, v1.3, or some other plan of action. WG members, feel free to assign status Discuss-Call to any issue with No Status.
(We should do this on call, but ideally prepare for in comments on the issues suggesting classification, so we can prioritize based on attention.)
Proposed rationale for assigning milestone (must follow our Charter):
- v1.2: errata only (but up to class-3) or alignment with RDF 1.2-basic (i.e.
@direction->rdf:dirLangString) - v1.3: necessary: RDF 1.2 full compliance (i.e. support for triple terms and reifiers (in some form), and the
@annotationcompact+"framed" form of that) - other: planned for new informative text (e.g. an appendix), Best Practises, other Note, with latest-deadline around 1.3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.