Document and inform about the level of adoption of Technical Reports

Document and inform about the level of adoption of Technical Reports (TR) for different audiences.

Useful to implementers, developers, contributors to TRs (including Work Items), and general public.

Level of Adoption:

• Refine metrics: implementation, intent to implement, community adoption (, standard track).
• Display the metrics in TRs.
• Create general report on the level of adoption of TRs.
• Establish Group guidance on how to increase implementation experience.

Considerations:

• Different classes of TRs and so implementation types (where some may not have test reports).
• Conformance to a TR as a whole backed by data from test reports (and elsewhere).
• Specific feature support backed by data from test reports (and elsewhere).
• May need to convey a lot of information in a limited space.
• TRs are static documents. Compatibility data is dynamic and external to TRs.

Related:

• https://github.com/solid/specification/issues/383
• https://github.com/solid/specification/issues/281

Bonus (eating our own cooking): Build other Solid applications using data from TRs, test reports, and implementations.

The issue names no files or tests; begin by reviewing related issues #383 and #281 and the existing Technical Reports. Done means an agreed way to define and present adoption metrics, plus the requested general report and guidance, with any implementation-facing follow-up made explicit.