The Working Group would also like to thank the members of the - for all the hard work + Digital Publishing Interest Group for all the hard work they did paving the road for this specification.
- diff --git a/common/js/biblio.js b/common/js/biblio.js index 0b8db7e..c5ebd2b 100644 --- a/common/js/biblio.js +++ b/common/js/biblio.js @@ -1,8 +1,8 @@ -/* - * WARNING: Use this file sparingly! - * +/* + * WARNING: Use this file sparingly! + * * Check http://www.specref.org/ first - * + * */ /* general entry template @@ -17,7 +17,20 @@ */ var biblio = { - "PWPUB": { + "link-relation": { + "title": "Identifier: A Link Relation to Convey a Preferred URI for Referencing", + "authors": [ + "H. Van de Sompel", + "M. Nelson", + "G. Bilder", + "J. Kunze", + "S. Warner" + ], + "rawDate": "2017-08", + "publisher": "IETF", + "href": "https://tools.ietf.org/html/draft-vandesompel-identifier-00", + }, + "pwpub": { "title": "Packaged Web Publications", "href": "https://w3.org/TR/pwpub/", "authors": [ @@ -25,7 +38,7 @@ var biblio = { ], "date": "..." }, - "WPUB": { + "wpub": { "title": "Web Publications", "href": "https://w3.org/TR/wpub/", "authors": [ diff --git a/index.html b/index.html index f3689f4..682e5c2 100644 --- a/index.html +++ b/index.html @@ -143,54 +143,82 @@Wherever appropriate, this document relies on the terminology defined by the note on “Publishing and Linking on the Web”[[publishing-linking]]. In particular, the terms that are very important for this document include user, user agent, browser, or address.
++ In this specification, the general term URL is used as defined and used in other W3C specification like HTML [[html51]], and is defined by the relevant WhatWG document [[url]]. + In particular, such a URL allows for the usage of characters from Unicode following [[rfc3987]]. + See the note in the HTML5 document for further details. +
+The default reading order is a specific progression through the primary resources defined in - the manifest by the creator of a Web Publication.
-A user might follow alternative pathways through the content, but in the absence of such interaction - the default reading order defines the expected progression from one primary resource to the - next.
+ The default reading order is a specific progression through the primary resources defined in the manifest by the creator of a Web Publication. +
-An IRI, or Internationalized Resource Identifier, is an extension to the URI specification to allow - characters from Unicode. There is a mapping algorithm for translating between IRIs and the equivalent - encoded URI form. IRIs are defined by [[!rfc3987]].
A manifest represents structured information about a Web Publication, such as informative - metadata, a list of all primary and secondary resources, and - the default reading order.
+ A user might follow alternative pathways through the content, but in the absence of such interaction the default reading order defines the expected progression from one primary resource to the next. +
+A primary resource is one that is listed in the default reading order of a Web - Publication.
+ A primary resource is one that is listed in the default reading order of a Web Publication. +
+A secondary resource is one that is required for the processing or rendering of a primary - resource.
A Web Publication is a collection of one or more primary resources, organized together through - a manifest into a single logical work with a default reading order. The Web Publication - is uniquely identifiable and presentable using Open Web Platform technologies.
A Web Publication canonical identifier is assigned to a Web Publication by the publisher. - It SHOULD be a dereferenceable IRI and the Web Publication Address. If not, it MUST be possible to - make a 1-to-1 mapping to the Web Publication Address. If a dereferenceable IRI it MAY be used as the - value of the href attribute of a canonical link element (i.e., a link element with a - rel='canonical' attribute).
A Web Publication identifier is metadata that is intended to be used to refer to a Web Publication - in a persistent and unambiguous manner. IRIs, URIs, DOIs, ISBNs, PURLs are all examples of - identifiers frequently used in publishing.
A Web Publication Address is a URL or other dereferenceable IRI which refers to the location of a - Web Publication and enables the retrieval of a representation of the manifest of the Web - Publication.
+ A secondary resource is one that is required for the processing or rendering of a primary resource. +
++ A manifest represents structured information about a Web Publication, such as informative metadata, a list of all primary and secondary resources, and the default reading order. +
++ A Web Publication is a collection of one or more primary resources, organized together through a manifest into a single logical work with a default reading order. + The Web Publication is uniquely identifiable and presentable using Open Web Platform technologies. +
++ An identifier is a metadata that can be used to refer to a Web Content in a persistent and unambiguous manner. + URLs, URNs, DOIs, ISBNs, or PURLs are all examples of identifiers frequently used in publishing. +
++ A Web Publication Address is a URL that refers to a Web Publication and enables the retrieval of a representation of the manifest of the Web Publication. +
+
+ A Web Publication canonical identifier is an identifier assigned to a Web Publication by the publisher.
+ It SHOULD either be a Web Publication Address, or it MUST be possible to make a 1-to-1 mapping to a Web Publication Address.
+ If it is URL, it MAY be used as the value of the href attribute of a canonical link element (i.e., a link element with a rel='canonical' attribute [[rfc6596]]).
+
This specification defines the content of a manifest on two levels.
+ ++ An abstract manifest is defined to identify what type of information is necessary at the Web Publication level (as opposed to individual resource level) for a user agent to process the publication properly. +
+ ++ The concrete manifest defines the file format(s), encodings, etc., used to represent the abstract manifest, and how those file(s) can be accessed. The same abstract manifest MAY be expressable via different concrete manifest formats. +
+As discussed on the group teleconference on the 2017-08-14, the separation of these two terms may be temporary, and subsequent editorial passes may merge the two notions.
+An abstract manifest should contain the following information.
+ +These requirements reflect the current minimum consensus, though a number of issues remain open. The issues may usually lead to a “MUST” instead of a “SHOULD” in the list above.
+ +Ignoring issues such as location, serialization, etc. What is the minimum viable manifest?
+ +Note that this is the question for the abstract manifest. How that information is acquired may also depend on the fallback mechanism.
++ Whether the minimum manifest must include any metadata, or a specific slot to handle metadata +
+ +The discussion led to the question whether the manifest MUST list all Secondary resources or not. In this sense, this became a duplicate of issue #23 ended up at the same question.
+ +The question is whether the manifest MUST list all Secondary resources or not.
+ +Should Natural Langauge be Required for the Publication for WCAG 2 Compliance?
+ + +Format of the Manifest (JSON, XML, embedded into HTML, etc.).
+If we have a collection of information about a web publication as a whole ("manifest") that exists separately from most of the publication's resources, we need to find a way to associate the manifest with the other publication resources.
+ +Should the TOC be a separate HTML file or is the listing of primary resources in the manifest an implicit TOC?
+ +When published, a Web Publication SHOULD be assigned a canonical identifier. This canonical identifier MUST be unique - to the Web Publication and, if assigned, MUST be included in the Web Publication manifest. The Identifying IRI - (i.e., the canonical identifier if it is an IRI or the locator mapped from the canonical identifier) MUST enable - the retrieval of a representation of the manifest of the Web Publication. The Identifying IRI does not preclude - the creation and use of other identifiers and / or locators to retrieve a representation of a Web Publication - in whole or part.
-