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
@annotation compact+"framed" form of that)
- other: planned for new informative text (e.g. an appendix), Best Practises, other Note, with latest-deadline around 1.3
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):
@direction->rdf:dirLangString)@annotationcompact+"framed" form of that)