From a3040651820214e8ca7677d601fd770b2a0fa95b Mon Sep 17 00:00:00 2001 From: Matt Garrish Date: Tue, 14 Nov 2017 08:29:12 -0500 Subject: [PATCH] update landing page to match issue discussion in #94 --- index.html | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/index.html b/index.html index b39e2e0..533e7f5 100644 --- a/index.html +++ b/index.html @@ -815,20 +815,17 @@

Linking to a Manifest

Landing Page

As described in , a Web Publication has an address that can be - dereferenced. The address URL MUST resolve to the landing page, an [[!html]] document that + dereferenced. This URL MUST resolve to the landing page, which is an [[!html]] document that represents the primary entry point for the Web Publication.

-

Unlike other resources, the landing page MUST link to the manifest to ensure - that user agents can discover the Web Publication.

+

The landing page MUST be a resource of the Web Publication, but its inclusion in the default reading + order is OPTIONAL. Unlike other resources, the landing page MUST link to + the manifest to ensure that user agents can discover the Web Publication.

-

To ensure that the Web Publication is consumable in different types of user agents, including those that - do not support Web Publications, the landing page SHOULD include an [[!html]] serialization of the table of contents (see for more - information).

- -

Additional questions about whether specifying HTML is necessary, whether - the resource has to be part of the web publication or not, and whether the table of contents is necessary - to specify at this location if provided in the content.

+

To improve the usability of the Web Publication, particularly in user agents that do not + support Web Publications, provide access on the landing page to navigation aids that facilitate + consumption of the content (e.g., include a table of contents on the page, or + provide a link to one).