Matt Garrish

> I think we should have a clear idea _why_ we need those back links in the first place Given that user agents don't generally expose links, I wouldn't put...

> Meaning that the author of a, say, chapter, could put a standard schema.org data, in JSON-LD, RDFa, or microdata, using `isPartOf`? Exactly. It could just be placed on an...

> Should be part of some best practices doc, I guess. Or do think it should be part of the main spec? Ya, I think somewhere in between -- maybe...

> Discovering the publication from `chapter1.html` provides a UA with the opportunity to "hoist" a reading experience and "re-navigate" to `chapter1.html`. The entry page (loaded from the publication's address) becomes...

The UA conformance section is one of a number of incomplete sections, so if we're arguing it's incomplete we're sort of arguing the obvious. The reason there is only one...

It's a WP issue, so not something we need to take up anymore. The conformance classes aren't in the manifest spec.

Further to the comment I made yesterday, I still think we need to focus on implementable features that can enable publications that work regardless of user agent capabilities more than...

Yes, without being able to express relationships we'll have to introduce something of our own making, as we've done in the interim in the draft. Definitely not the way we...

> and a similar statement would be put into the RS spec, whereby a RS _MAY_ decide not to expand internal entities Do we need to say anything normative? The...

Doesn't this lead us into defining what it meas to reject content: won't load the publication into the user's library; won't open the publication; won't open the offending document; strips...