manifest: metadata about wpub HOT 8 CLOSED

A manifest SHOULD include metadata about a WP but (aside from the on-going discussion about title) I don't think that this should be a requirement.

With regards to metadata:

• we need built-in extensibility
• we should rely as much as possible on existing vocabularies (schema.org)
• we probably want to look into JSON-LD as a good candidate for what we need

from wpub.

I think that, on an abstract level, the manifest MUST have a metadata "slot", although that slot may be empty. But users must be able to add metadata.

I agree with @HadrienGardeur on the usage of external vocabularies as much as possible, but that is a general design principle.

from wpub.

from wpub.

@iherman that was one of the question that remained unanswered in yesterday's call: how do we document such design principles?

IMO they can be as important (if not more) than the list of requirements that we're currently working on.

from wpub.

from wpub.

About the title, I'd like to add that if we want a WP to be accessible by spec, it is a MUST.
Or we decide that a WP conformant to the spec may not be accessible.

from wpub.

@TzviyaSiegman, isn't this issue obsolete by now? If so, we may want to close it...

from wpub.

This issue resolved with the publication of https://www.w3.org/TR/2018/WD-wpub-20180104

from wpub.