diff --git a/common/context.jsonld b/common/context.jsonld index 8af222c..59c60ea 100644 --- a/common/context.jsonld +++ b/common/context.jsonld @@ -55,6 +55,10 @@ "@container": "@set", "@id": "http://www.w3.org/ns/wpub#resources" }, + "externalResources": { + "@container": "@set", + "@id": "http://www.w3.org/ns/wpub#resources" + }, "tableOfContents": { "@id": "http://www.w3.org/ns/wpub#tableOfContents" }, diff --git a/common/js/biblio.js b/common/js/biblio.js index 746e5e8..d4b084f 100644 --- a/common/js/biblio.js +++ b/common/js/biblio.js @@ -120,5 +120,13 @@ var biblio = { "schema.org": { "title": "Schema.org", "href": "https://schema.org" + }, + "onix": { + "title": "ONIX for Books", + "href": "http://www.editeur.org/83/Overview" + }, + "bibtex": { + "title": "BibTeX Format Description", + "href" : "http://www.bibtex.org/Format/" } } diff --git a/experiments/w3c_rec/full_version.html b/experiments/w3c_rec/full_version.html index 5c2370b..d645f11 100644 --- a/experiments/w3c_rec/full_version.html +++ b/experiments/w3c_rec/full_version.html @@ -5,7 +5,7 @@ ... diff --git a/index.html b/index.html index 87bb7d8..6c34680 100644 --- a/index.html +++ b/index.html @@ -305,12 +305,10 @@
It is also RECOMMENDED that the accessibility report be provided in a human-readable format, such as HTML [[!html]]. Augmenting these reports - with machine-processable metadata, such as provided in Schema.org[[schema.org]], is also + with machine-processable metadata, such as provided in Schema.org[[!schema.org]], is also RECOMMENDED.
Machine-readable accessibility metadata may be recommended in whatever format is @@ -429,28 +429,6 @@
The infoset SHOULD include a reference to a cover - image. This image can be used by user agents to present the Web Publication to users - (e.g., in a library or bookshelf, or when initially loading the Web Publication).
- -User agents SHOULD NOT use the cover image as the sole means of selecting or accessing Web - Publications. A user agent SHOULD use the Web Publication's title and creators as text alternatives for such interfaces.
- -More than one cover image MAY be referenced from the infoset to provide alternative sizes and - resolutions for different device screens.
- -A user agent MAY create a cover for a Web Publication if one is not present. This specification - does not define requirements for the creation of such cover images (e.g., the user agent could - use a placeholder image, generate an image dynamically, or incorporate properties of the infoset - into a graphic, such as the title or creators).
- - -Users often have the legal right to know and control what information is collected about them, - how such information is stored and for how long, whether it is personally identifiable, and how - it can be expunged. Including a statement that addresses all such privacy concerns is - consequently an important part of publishing Web Publications. Even if no information is - collected, such a declaration increases the trust users have in the content.
- -To address this concern, a link to a privacy policy can be included in the infoset. It is RECOMMENDED that the privacy policy be - included as a resource of the Web Publication.
- -It is RECOMMENDED that the privacy policy be provided in a human-readable format, such as HTML [[!html]].
- -Refer to for more information about privacy considerations in Web - Publications.
- - - -This was not decided on the Toronto F2F, and is still open.
+ The list of extra resources enumerates all + resources that are used in the processing and rendering of a Web Publication but are not within its bounds (i.e., are not listed in the default reading order or the resource list) but are, rather, external to the Web Publication. +
+ +The completeness of the resource list will affect the usability of the Web Publication in certain + scenarios (e.g., the ability to access privacy policy information). For this reason, it + is strongly RECOMMENDED to provide a comprehensive list of all of the Web Publication's + external resources beyond those listed in the default reading order or resource list.
+ +In some cases, a comprehensive list of these resources might not be easily achieved (e.g., + third-party scripts that reference resources from deep within their source), but a user agent + SHOULD still be able to render a Web Publication even if some of these resources are not + identified as belonging to the Web Publication (e.g., when it is taken offline without + them).
+ + + +The infoset SHOULD include a reference to a cover + image. This image can be used by user agents to present the Web Publication to users + (e.g., in a library or bookshelf, or when initially loading the Web Publication).
+ +User agents SHOULD NOT use the cover image as the sole means of selecting or accessing Web + Publications. A user agent SHOULD use the Web Publication's title and creators as text alternatives for such interfaces.
+ +More than one cover image MAY be referenced from the infoset to provide alternative sizes and + resolutions for different device screens.
+ +A user agent MAY create a cover for a Web Publication if one is not present. This specification + does not define requirements for the creation of such cover images (e.g., the user agent could + use a placeholder image, generate an image dynamically, or incorporate properties of the infoset + into a graphic, such as the title or creators).
+ + +Users often have the legal right to know and control what information is collected about them, + how such information is stored and for how long, whether it is personally identifiable, and how + it can be expunged. Including a statement that addresses all such privacy concerns is + consequently an important part of publishing Web Publications. Even if no information is + collected, such a declaration increases the trust users have in the content.
+ +To address this concern, a link to a privacy policy can be included in the infoset. It is RECOMMENDED that the privacy policy be + included as a resource of the Web Publication.
+ +It is RECOMMENDED that the privacy policy be provided in a human-readable format, such as HTML [[!html]].
+ +Refer to for more information about privacy considerations in Web + Publications.
+ + + +Desciptive Properties in the Web Publication Manifest are based, wherever possible, on the terms defined by Schema.org [[schema.org]] (including Schema.org [[!schema.org]] (including hosted extensions of Schema.org). This means that the descriptive infoset properties are mapped to one or several Schema.org properties (inheriting their syntax and semantics).
@@ -843,7 +866,7 @@As defined in , the Web Publication Manifest MAY inlude accessibility +
As defined in , the Web Publication Manifest MAY include accessibility
metadata. These SHOULD be mapped on the family of accessibility terms, as expressed by
Schema.org. (A more detailed description of these terms, as well as the possible values, are
described on the WebSchemas Wiki
@@ -917,6 +940,8 @@ Note that the author MAY also provide a reference to a more detailed Accessibility Report, beyond the accessibility information expressed by these terms.Accessibility
+
{
"@context" : ["http://schema.org","https://www.w3.org/ns/wpub.jsonld"],
@@ -1023,9 +1048,9 @@
Canonical Identifier
As desribed in , a Web Publication's creators are the +
As described in , a Web Publication's creators are the
individuals or entities responsible for the creation of the Web Publication. There
- isn’t one single Schema.org term this item must be mapped onto; instead, there are a number
+ isn’t one specific single Schema.org term this item must be mapped onto; instead, there are a number
of terms and, if this Infoset Item is used, the Web Publication Manifest SHOULD use one of
those. The value of these terms are one or more Person
objects or, in some cases, Structural Infoset Properties
rel
If the document is reorganized the "specific" external resources (cover, accessibility report, etc) should be separated in from the general structures and list definitions.
+readingOrder
PublicationLink
objectPublicationLink
objectresources
PublicationLink
objectPublicationLink
object
+ As defined in , the list of extra resources enumerates all resources that are used in the processing and rendering of a Web Publication but are not within its bounds but are, rather, external to the Web Publication. If present in the Web Publication Manifest, this item MUST be mapped on the extraResources
term, defined specifically for Web Publications.
+
+ The extraResources
to be used in JSON has not yet been decided; waiting on the resolution of issue #225
+
Term name with link to definition | +Short description | +
---|---|
+ extraResources
+ |
+ An array of:
|
+
As defined in , the manifest SHOULD provide a link to an @@ -1625,6 +1686,118 @@
The term tableOfContents
has not been approved by the Working
Group yet; it is currently a placeholder.
+ As described in , the infoset SHOULD include a reference to a cover. When present, link to such resource MUST be expressed using a PublicationLink
. The rel
value of the PublicationLink
MUST include the https://www.w3.org/ns/wpub/cover-page
identifier.
+
+ The Working Group will attempt to define the cover-page
term by IANA, to avoid using a URL.
+
+{ + "@context" : ["http://schema.org","https://www.w3.org/ns/wpub.jsonld"], + "@type" : "Book", + ... + "url" : "https://publisher.example.org/mobydick", + "name" : "Moby Dick", + "resources" : [{ + "@type" : "PublicationLink", + "url" : "whale-image.jpg", + "fileFormat" : "image/jpeg" + "rel" : "https://www.w3.org/ns/wpub/cover-page" + },{ + ... + }], + ... +} ++
+ As described in , it is RECOMMENDED that the privacy policy be included as a resource of the Web Publication. When present, link to such resource MUST be expressed using a PublicationLink
object. The rel
value of the PublicationLink
MUST include the privacy-policy
(IANA) identifier.
+
+{ + "@context" : ["http://schema.org","https://www.w3.org/ns/wpub.jsonld"], + "@type" : "CreativeWork", + ... + "identifier" : "http://www.w3.org/TR/tabular-data-model/", + "url" : "http://www.w3.org/TR/2015/REC-tabular-data-model-20151217/", + ... + "externalResources" : [{ + "@type" : "PublicationLink", + "url" : "https://www.w3.org/Consortium/Legal/privacy-statement-20140324", + "fileFormat" : "text/html", + "rel" : "privacy-policy" + },{ + ... + }], + ... +} ++
+ As described in the authors MAY provide an accessibility report providing information about the suitability of a Web Publication for consumption by users with varying preferred reading modalities. This report may be complementary to the information expressed by the descriptive properties as described in . This report is accessed via an external resource (e.g., and HTML file). When present, link to such resource MUST be expressed using a PublicationLink
object. The rel
value of the PublicationLink
MUST include the https://www.w3.org/ns/wpub#accessibility-report
identifier.
+
+ The Working Group will attempt to define the accessibility-report
term by IANA, to avoid using a URL.
+
+{ + "@context" : ["http://schema.org","https://www.w3.org/ns/wpub.jsonld"], + "@type" : "Book", + ... + "url" : "https://publisher.example.org/mobydick", + "name" : "Moby Dick", + "extraResources" : [{ + "@type" : "PublicationLink", + "url" : "https://www.publisher.example.org/mobydick-accessibility.html", + "rel" : "https://www.w3.org/ns/wpub/accessibility-report" + },{ + ... + }], + ... +} ++
+ As described in , the infoset items of a Web Publication MAY be extended by linking to further metadata records. This may include, for example, links to an external ONIX [[onix]] or BibTeX [[bibtex]] file. When present, link to such resource MUST be expressed using a PublicationLink
object. The rel
value of the PublicationLink
MUST include the describedby
(IANA) identifier.
+
+{ + "@context" : ["http://schema.org","https://www.w3.org/ns/wpub.jsonld"], + "@type" : "Book", + ... + "url" : "https://publisher.example.org/mobydick", + "name" : "Moby Dick", + "extraResources" : [{ + "@type" : "PublicationLink", + "url" : "https://www.publisher.example.org/mobydick-onix.xml", + "fileFormat" : "application/xml", + "rel" : "describedby" + },{ + ... + }], + ... +} ++ +