Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update landing page to match issue discussion in #94 #101

Merged
merged 3 commits into from
Nov 14, 2017
Merged

update landing page to match issue discussion in #94 #101

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a304065
update landing page to match issue discussion in #94
mattgarrish Nov 14, 2017
5a5d3e0
change landing page to entry page
mattgarrish Nov 14, 2017
b7e961e
remove typo
mattgarrish Nov 14, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 16 additions & 20 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
<!DOCTYPE html>
la<!DOCTYPE html>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the one thing I don't approve of in this text. 😉

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lol, I would have caught it eventually...

<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<meta charset="utf-8" />
Expand Down Expand Up @@ -421,7 +421,7 @@ <h4>Address</h4>

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

<p>The availability of this address does not preclude the creation and use of other identifiers and/or
Expand Down Expand Up @@ -676,8 +676,6 @@ <h4>Table of Contents</h4>
<li>calculate a table of contents using its own algorithms.</li>
</ol>

<p class="ednote">This section should be brought in sync with the section on <a>landing page</a>.</p>

<p class="issue" data-number="9">The question is whether the manifest/infoset needs to provide
navigation, or whether such mechanisms belong in the content.</p>

Expand Down Expand Up @@ -811,24 +809,22 @@ <h2>Linking to a Manifest</h2>
>wiki analysis</a>.</p>
</section>

<section id="wp-landing-page">
<h3>Landing Page</h3>
<section id="wp-entry-page">
<h3>Entry Page</h3>

<p>As described in <a href="#wp-address"></a>, a <a>Web Publication</a> has an <a>address</a> that can be
dereferenced. The address URL MUST resolve to the <dfn>landing page</dfn>, an [[!html]] document that
represents the primary entry point for the Web Publication.</p>

<p>Unlike other resources, the landing page MUST <a href="#wp-linking">link to the manifest</a> to ensure
that user agents can discover the Web Publication.</p>

<p>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 <a
href="#enh-toc">table of contents</a> (see <a href="#wp-table-of-contents"></a> for more
information).</p>

<p class="issue" data-number="94">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.</p>
dereferenced. This URL MUST resolve to the <dfn>entry page</dfn>, which MUST be an [[!html]] document
that represents the primary entry point for the Web Publication.</p>

<p>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 <a>default reading order</a>. Unlike other resources, the entry page MUST <a
href="#wp-linking">link to the manifest</a> to ensure that user agents can discover the Web
Publication.</p>

<p class="note">To improve the usability of the Web Publication, particularly in user agents that do not
support Web Publications, provide access on the entry page to navigation aids that facilitate consumption
of the content (e.g., include a <a href="#enh-toc">table of contents</a> on the page, or provide a link
to one).</p>
</section>
</section>
<section id="wp-lifecycle">
Expand Down