- The spec should mention that lists of projects from a particular origin should be listed in a feed file/endpoint called
- This file should follow the JSON Feed 1.1 schema.
- For fields specified in JSON Feed that are similar to fields we have specified in OKH 1.0 we should adopt JSON Feed naming throughout (e.g.
- We should mandate that
content_textbe used in place of the
descriptionfield of OKH 1.0 and the
summaryare never used.
Our main use case for the standard in practice has been for platforms (e.g. Appropedia.org, Kitspace.org) to generate and host manifests for projects. Downstream readers of manifests (e.g. crawlers) have no way of listing projects available from a platform.
We need to specify a way for downstream readers to get a list of OKH manifests from a particular platform.
RSS or Atom are possible options but are XML formats. JSON is a more popular serialisation format these days and if we adopt JSON with the Switch from YAML to JSON proposal then it makes sense to stick to a single data serialisation format. Some notes on evaluation of different feed formats are available here.