From a3040651820214e8ca7677d601fd770b2a0fa95b Mon Sep 17 00:00:00 2001 From: Matt Garrish Date: Tue, 14 Nov 2017 08:29:12 -0500 Subject: [PATCH 1/3] 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).

From 5a5d3e0aa32cfbe86c053a55489ac5c9a9196c5e Mon Sep 17 00:00:00 2001 From: Matt Garrish Date: Tue, 14 Nov 2017 12:29:18 -0500 Subject: [PATCH 2/3] change landing page to entry page --- index.html | 27 +++++++++++++-------------- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/index.html b/index.html index 533e7f5..c06c71f 100644 --- a/index.html +++ b/index.html @@ -1,4 +1,4 @@ - +la @@ -421,7 +421,7 @@

Address

A Web Publication's address is a URL that refers to the Web Publication. It dereferences to the landing page, which enables the retrieval of a representation of the + href="#wp-entry-page">entry page, which enables the retrieval of a representation of the manifest.

The availability of this address does not preclude the creation and use of other identifiers and/or @@ -676,8 +676,6 @@

Table of Contents

  • calculate a table of contents using its own algorithms.
    • -

    This section should be brought in sync with the section on landing page.

    -

    The question is whether the manifest/infoset needs to provide navigation, or whether such mechanisms belong in the content.

    @@ -811,21 +809,22 @@

    Linking to a Manifest

    >wiki analysis.

    -
    -

    Landing Page

    +
    +

    Entry Page

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

    + dereferenced. This URL MUST resolve to the entry page, which MUST be an [[!html]] document + that represents the primary entry point for 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.

    +

    The entry page MUST be a resource of the Web Publication, but it can be any resource, including one that + is not listed in the default reading order. Unlike other resources, the entry page MUST link to the manifest to ensure that user agents can discover the Web + Publication.

    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).

    + support Web Publications, provide access on the entry 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).

    From b7e961edfa26800e93cf62da546fc7f0eacf4c95 Mon Sep 17 00:00:00 2001 From: Matt Garrish Date: Tue, 14 Nov 2017 12:39:53 -0500 Subject: [PATCH 3/3] remove typo --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index c06c71f..bbd06d7 100644 --- a/index.html +++ b/index.html @@ -1,4 +1,4 @@ -la +