Audiobooks Working Group - Activity in 2018
No matches.
TR publications
-
1 document published.
-
Web Publications published as a Working Draft. History of Web Publications
-
GitHub
w3c/pwpub
-
2 issues opened.
-
Font obfuscation in PWP w3c/pwpub#28, by @llemeurfr.
-
2 issues received 9 new comments.
-
Choose a media-type and file extension for Web Publications packaged in "OCF lite" w3c/pwpub#29 (8 comments by @GarthConboy, @iherman, @llemeurfr)
-
-
1 pull request opened.
-
Add first draft of ocf-lite w3c/pwpub#30, by @llemeurfr.
-
-
1 pull request received 6 new comments.
w3c/wpub
-
9 issues opened.
-
Must the primary entry page be part of the web publication? w3c/wpub#386, by @dauwhe.
-
Option to switch to publication mode w3c/wpub#385, by @dauwhe.
-
Requesting TAG design review of WPUB spec w3c/wpub#384, by @dauwhe.
-
A.2 example 39: TOC ignored ex. Stray <a>, intentional? w3c/wpub#381, by @jccr.
-
Minor issues on the TOC algorithm w3c/wpub#379, by @iherman.
-
Elements to ignore by TOC extraction algorithm? w3c/wpub#378, by @iherman.
-
Other link-like elements allowed in the (HTML) TOC? w3c/wpub#377, by @iherman.
-
TOC directly encoded in the manifest? w3c/wpub#376, by @iherman.
-
Write an audiobook explainer w3c/wpub#372, by @dauwhe.
-
-
8 issues closed.
-
A.2 example 39: TOC ignored ex. Stray <a>, intentional? w3c/wpub#381.
-
Other link-like elements allowed in the (HTML) TOC? w3c/wpub#377.
-
Simplifying the WebIDL w3c/wpub#338.
-
Write an audiobook explainer w3c/wpub#372.
-
Audiobooks: The Big Picture w3c/wpub#361.
-
1 issue reopened.
-
Other link-like elements allowed in the (HTML) TOC? w3c/wpub#377, by @iherman.
-
-
19 issues received 155 new comments.
-
Must the primary entry page be part of the web publication? w3c/wpub#386 (27 comments by @BigBlueHat, @dauwhe, @iherman, @llemeurfr, @mattgarrish)
-
Packaging for audiobooks w3c/wpub#352 (20 comments by @danielweck, @dauwhe, @dwsinger, @HadrienGardeur, @iherman, @llemeurfr, @lrosenthol, @murata2makoto)
-
What is an "opaque origin" and why do we care? w3c/wpub#321 (19 comments by @danielweck, @dauwhe, @iherman, @JayPanoz, @mattgarrish)
-
Only allow embedded manifests w3c/wpub#327 (17 comments by @BigBlueHat, @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish)
-
TOC directly encoded in the manifest? w3c/wpub#376 (17 comments by @dauwhe, @GarthConboy, @HadrienGardeur, @iherman, @laudrain, @llemeurfr, @mattgarrish, @TzviyaSiegman)
-
Elements to ignore by TOC extraction algorithm? w3c/wpub#378 (9 comments by @HadrienGardeur, @iherman, @mattgarrish, @rdeltour)
-
Several pagelists? w3c/wpub#342 (8 comments by @HadrienGardeur, @laudrain, @llemeurfr, @RachelComerford, @rickj, @TzviyaSiegman)
-
Other link-like elements allowed in the (HTML) TOC? w3c/wpub#377 (6 comments by @iherman, @rdeltour)
-
What does "Reading Order" mean in the context of a Web Publication? w3c/wpub#38 (5 comments by @dauwhe, @fbrzvnrnd, @TzviyaSiegman)
-
Proposal for handling localizable texts (writeup of the F2F discussions) w3c/wpub#354 (5 comments by @aphillips, @iherman)
-
Additional text or hints on what would become pagelist targets. w3c/wpub#341 (2 comments by @avneeshsingh, @wareid)
-
-
8 pull requests opened.
-
Clarify the primary entry page w3c/wpub#389, by @mattgarrish.
-
Updates to explainer based on WG feedback w3c/wpub#387, by @dauwhe.
-
add more detail about other options to audiobook explainer w3c/wpub#383, by @dauwhe.
-
Revised html structure section w3c/wpub#382, by @mattgarrish.
-
Explanations for canonicalization w3c/wpub#380, by @iherman.
-
Move explainers to their own folder w3c/wpub#375, by @dauwhe.
-
Create AUDIOBOOKS_EXPLAINER.md w3c/wpub#373, by @wareid.
-
-
9 pull requests merged.
-
Clarify the primary entry page w3c/wpub#389.
-
Updates to explainer based on WG feedback w3c/wpub#387.
-
Revised html structure section w3c/wpub#382.
-
Explanations for canonicalization w3c/wpub#380.
-
Move explainers to their own folder w3c/wpub#375.
-
Create AUDIOBOOKS_EXPLAINER.md w3c/wpub#373.
-
-
6 pull requests received 38 new comments.
-
Add content and processing requirements for machine-readable toc w3c/wpub#371 (13 comments by @danielweck, @iherman, @mattgarrish, @rdeltour, @TzviyaSiegman)
-
Clarify the primary entry page w3c/wpub#389 (10 comments by @HadrienGardeur, @iherman, @mattgarrish)
-
w3c/dpub-pwp-ucr
-
1 issue closed.
-
"Sync up" language is confusing w3c/dpub-pwp-ucr#163.
-
-
1 issue received 1 new comment.
-
3 pull requests opened.
-
Updates for Accessibility w3c/dpub-pwp-ucr#195, by @francofaa.
-
edu use cases w3c/dpub-pwp-ucr#194, by @francofaa.
-
Incorporating audiobooks 20181130 w3c/dpub-pwp-ucr#193, by @francofaa.
-
-
5 pull requests merged.
-
Updates for Accessibility w3c/dpub-pwp-ucr#195.
-
edu use cases w3c/dpub-pwp-ucr#194.
-
Suggestion to address issue #163 w3c/dpub-pwp-ucr#189.
-
Incorporating audiobooks 20181130 w3c/dpub-pwp-ucr#193.
-
adjusted OWP use cases w3c/dpub-pwp-ucr#191.
-
-
1 pull request received 3 new comments.
-
Updates for Accessibility w3c/dpub-pwp-ucr#195 (3 comments by @avneeshsingh, @francofaa, @TzviyaSiegman)
-
w3c/pub-manifest
-
1 issue opened.
-
manifest processing model, what if null base URL? (related to origin issue) w3c/pub-manifest#12, by @danielweck.
-
-
1 issue received 11 new comments.
-
manifest processing model, what if null base URL? (related to origin issue) w3c/pub-manifest#12 (11 comments by @danielweck, @iherman)
-
Participants
-
1 organization joined.
-
Taiwan Digital Publishing Forum joined.
-
GitHub
w3c/dpub-pwp-ucr
-
1 issue opened.
-
Should we define "handle"? w3c/dpub-pwp-ucr#188, by @dauwhe.
-
-
2 issues received 2 new comments.
-
11 pull requests opened.
-
updating from gh-pages w3c/dpub-pwp-ucr#192, by @francofaa.
-
adjusted OWP use cases w3c/dpub-pwp-ucr#191, by @francofaa.
-
Style updating and proofreading of audiobooks use cases w3c/dpub-pwp-ucr#190, by @francofaa.
-
Suggestion to address issue #163 w3c/dpub-pwp-ucr#189, by @francofaa.
-
use case: addition of archival example w3c/dpub-pwp-ucr#187, by @francofaa.
-
Changed editors: replaced Laurent to Franco w3c/dpub-pwp-ucr#186, by @iherman.
-
Conformance Classes w3c/dpub-pwp-ucr#185, by @atyposh.
-
Erroneous uses of Portable Web Publication w3c/dpub-pwp-ucr#184, by @francofaa.
-
added toc requirement + use cases w3c/dpub-pwp-ucr#183, by @francofaa.
-
updating references pr w3c/dpub-pwp-ucr#182, by @francofaa.
-
Wp spec ref col add 20181030 w3c/dpub-pwp-ucr#181, by @francofaa.
-
-
10 pull requests merged.
-
updating from gh-pages w3c/dpub-pwp-ucr#192.
-
Style updating and proofreading of audiobooks use cases w3c/dpub-pwp-ucr#190.
-
Wp spec ref col add 20181030 w3c/dpub-pwp-ucr#181.
-
Changed editors: replaced Laurent to Franco w3c/dpub-pwp-ucr#186.
-
added toc requirement + use cases w3c/dpub-pwp-ucr#183.
-
Conformance Classes w3c/dpub-pwp-ucr#185.
-
updating references pr w3c/dpub-pwp-ucr#182.
-
Audiobooks Use cases w3c/dpub-pwp-ucr#179.
-
language change w3c/dpub-pwp-ucr#168.
-
Removing req11 20181030 w3c/dpub-pwp-ucr#180.
-
-
3 pull requests closed.
-
Erroneous uses of Portable Web Publication w3c/dpub-pwp-ucr#184.
-
use case: addition of archival example w3c/dpub-pwp-ucr#187.
-
query w3c/dpub-pwp-ucr#170.
-
-
4 pull requests received 7 new comments.
w3c/wpub
-
3 issues opened.
-
Example for a TOC as JSON in an Audiobook w3c/wpub#369, by @HadrienGardeur.
-
Condition to have no readingOrder in a manifest w3c/wpub#368, by @llemeurfr.
-
Audiobooks: The Big Picture w3c/wpub#361, by @dauwhe.
-
-
11 issues closed.
-
Dual-approach for the TOC w3c/wpub#350.
-
Condition to have no readingOrder in a manifest w3c/wpub#368.
-
Resources SHOULD or MAY provide a link to the manifest w3c/wpub#191.
-
wording of the spec on different identifiers w3c/wpub#263.
-
Processing our manifest into WebIDL w3c/wpub#268.
-
4.7.3 Pagelist - typo "pagesList" vs. "pageList" w3c/wpub#346.
-
typo? "table-of-contents" w3c/wpub#347.
-
Use LinkRole instead of PublicationLink w3c/wpub#235.
-
Is PublicationLink a misnomer? w3c/wpub#356.
-
-
21 issues received 121 new comments.
-
Do we need a more detailed definition for the HTML TOC format? w3c/wpub#291 (35 comments by @dauwhe, @deborahgu, @GarthConboy, @HadrienGardeur, @iherman, @llemeurfr, @rdeltour, @TzviyaSiegman, @wareid)
-
Packaging for audiobooks w3c/wpub#352 (24 comments by @danielweck, @GarthConboy, @HadrienGardeur, @iherman, @llemeurfr, @lrosenthol, @wareid)
-
Is PublicationLink a misnomer? w3c/wpub#356 (17 comments by @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish)
-
Only allow embedded manifests w3c/wpub#327 (10 comments by @BigBlueHat, @dauwhe, @GarthConboy, @iherman)
-
Additional text or hints on what would become pagelist targets. w3c/wpub#341 (8 comments by @danielweck, @iherman, @laudrain, @llemeurfr, @mattgarrish, @TzviyaSiegman)
-
What is an "opaque origin" and why do we care? w3c/wpub#321 (3 comments by @BigBlueHat, @danielweck, @JayPanoz)
-
Condition to have no readingOrder in a manifest w3c/wpub#368 (2 comments by @HadrienGardeur, @llemeurfr)
-
Clarify the coercion process from strings to objects in `Text Values or Objects` w3c/wpub#314 (2 comments by @BigBlueHat, @iherman)
-
Proposal for handling localizable texts (writeup of the F2F discussions) w3c/wpub#354 (2 comments by @BigBlueHat, @HadrienGardeur)
-
typo? `name` property instead of `title` for PublicationLink object w3c/wpub#357 (1 comment by @iherman)
-
-
9 pull requests opened.
-
Add content and processing requirements for machine-readable toc w3c/wpub#371, by @mattgarrish.
-
Start work on WPUB Explainer document w3c/wpub#370, by @dauwhe.
-
Manifest generation script reinstated w3c/wpub#367, by @iherman.
-
Made the changes on the TOC per issue resolution of #276 w3c/wpub#364, by @iherman.
-
Title element is reused when necessary w3c/wpub#363, by @iherman.
-
Turned all occurences of PublicationLink to Linkedresource w3c/wpub#362, by @iherman.
-
test - ignore w3c/wpub#360, by @mattgarrish.
-
Remove infoset w3c/wpub#359, by @mattgarrish.
-
Made some minor changes w3c/wpub#358, by @iherman.
-
-
7 pull requests merged.
-
Start work on WPUB Explainer document w3c/wpub#370.
-
Manifest generation script reinstated w3c/wpub#367.
-
Title element is reused when necessary w3c/wpub#363.
-
Made the changes on the TOC per issue resolution of #276 w3c/wpub#364.
-
Remove infoset w3c/wpub#359.
-
Made some minor changes w3c/wpub#358.
-
-
2 pull requests closed.
-
title element is a MUST for embedded manifests w3c/wpub#331.
-
test - ignore w3c/wpub#360.
-
-
8 pull requests received 101 new comments.
-
Add content and processing requirements for machine-readable toc w3c/wpub#371 (30 comments by @avneeshsingh, @iherman, @llemeurfr, @mattgarrish, @rdeltour)
-
Manifest generation script reinstated w3c/wpub#367 (7 comments by @HadrienGardeur, @iherman, @mattgarrish)
-
Turned all occurences of PublicationLink to Linkedresource w3c/wpub#362 (4 comments by @HadrienGardeur, @iherman)
-
title element is a MUST for embedded manifests w3c/wpub#331 (3 comments by @HadrienGardeur, @iherman)
w3c/pub-manifest
-
2 issues opened.
-
Explicit typing for Linked Resource not necessary? w3c/pub-manifest#13, by @iherman.
-
Use existing Vocabulary terms from ActivityStreams for Link semantics w3c/pub-manifest#14, by @BigBlueHat.
-
-
2 issues received 8 new comments.
-
Use existing Vocabulary terms from ActivityStreams for Link semantics w3c/pub-manifest#14 (5 comments by @baldurbjarnason, @dauwhe, @HadrienGardeur, @iherman, @laudrain)
-
Explicit typing for Linked Resource not necessary? w3c/pub-manifest#13 (3 comments by @HadrienGardeur, @iherman)
-
GitHub
w3c/wpub
-
14 issues opened.
-
Is PublicationLink a misnomer? w3c/wpub#356, by @iherman.
-
Packaging for audiobooks w3c/wpub#352, by @HadrienGardeur.
-
Dual-approach for the TOC w3c/wpub#350, by @HadrienGardeur.
-
Explain the purpose of the "canonical manifest" w3c/wpub#349, by @mattgarrish.
-
typo? "table-of-contents" w3c/wpub#347, by @danielweck.
-
4.7.3 Pagelist - typo "pagesList" vs. "pageList" w3c/wpub#346, by @danielweck.
-
4.5.3 Links - typo "resourceList" should be "resources" w3c/wpub#345, by @danielweck.
-
4.5.2 Resource List - typo "resourceList" should be "resources" w3c/wpub#344, by @danielweck.
-
Several pagelists? w3c/wpub#342, by @iherman.
-
Additional text or hints on what would become pagelist targets. w3c/wpub#341, by @iherman.
-
Simplifying the WebIDL w3c/wpub#338, by @HadrienGardeur.
-
14 issues closed.
-
Explain the purpose of the "canonical manifest" w3c/wpub#349.
-
Duration of an audiobook w3c/wpub#307.
-
Obtaining language from http headers w3c/wpub#54.
-
use of "cover image" w3c/wpub#261.
-
Other navigation elements beyond ToC w3c/wpub#223.
-
is a canonical identifier necessary w3c/wpub#58.
-
How we name things is potentially confusing w3c/wpub#312.
-
Supplemental Content in Audiobooks w3c/wpub#320.
-
Flatland: An Audiobook Experiment of Many Dimensions w3c/wpub#247.
-
-
35 issues received 207 new comments.
-
Packaging for audiobooks w3c/wpub#352 (27 comments by @dauwhe, @GarthConboy, @HadrienGardeur, @iherman, @llemeurfr, @lrosenthol)
-
What is an "opaque origin" and why do we care? w3c/wpub#321 (24 comments by @iherman, @JayPanoz, @llemeurfr, @RachelComerford, @rdeltour)
-
Dual-approach for the TOC w3c/wpub#350 (23 comments by @HadrienGardeur, @iherman, @laudrain, @liisamk, @llemeurfr)
-
Resources SHOULD or MAY provide a link to the manifest w3c/wpub#191 (15 comments by @GarthConboy, @HadrienGardeur, @iherman, @mattgarrish)
-
Is PublicationLink a misnomer? w3c/wpub#356 (14 comments by @HadrienGardeur, @iherman, @laudrain, @llemeurfr, @mattgarrish, @TzviyaSiegman)
-
Proposal for handling localizable texts (writeup of the F2F discussions) w3c/wpub#354 (12 comments by @HadrienGardeur, @iherman, @llemeurfr, @murata2makoto, @toshiakikoike)
-
Other navigation elements beyond ToC w3c/wpub#223 (12 comments by @avneeshsingh, @baldurbjarnason, @danielweck, @HadrienGardeur, @iherman, @llemeurfr, @lrosenthol, @TzviyaSiegman)
-
WP rendering in non WP aware browsers w3c/wpub#271 (11 comments by @avneeshsingh, @HadrienGardeur, @iherman, @mattgarrish)
-
Simplifying the WebIDL w3c/wpub#338 (9 comments by @danielweck, @HadrienGardeur, @iherman, @TzviyaSiegman)
-
Duration of an audiobook w3c/wpub#307 (8 comments by @danielweck, @HadrienGardeur, @iherman, @llemeurfr)
-
Mixed media in audiobook linear reading order w3c/wpub#322 (6 comments by @HadrienGardeur, @iherman, @llemeurfr)
-
Additional text or hints on what would become pagelist targets. w3c/wpub#341 (5 comments by @iherman, @JayPanoz, @laudrain, @llemeurfr, @lrosenthol)
-
We need a section of the document that explicitly defines the bounds of a publication w3c/wpub#205 (4 comments by @iherman, @JayPanoz, @lrosenthol)
-
List of recommended audio formats for audio-only WP w3c/wpub#323 (3 comments by @HadrienGardeur, @iherman, @llemeurfr)
-
Do we need a more detailed definition for the HTML TOC format? w3c/wpub#291 (2 comments by @iherman, @jccr)
-
Clarify the coercion process from strings to objects in `Text Values or Objects` w3c/wpub#314 (1 comment by @iherman)
-
4.5.2 Resource List - typo "resourceList" should be "resources" w3c/wpub#344 (1 comment by @iherman)
-
Hints about resources in "default reading order" or "list of resources" w3c/wpub#222 (1 comment by @TzviyaSiegman)
-
Proposal: Add GitHub Issue Template for Affordance issues w3c/wpub#233 (1 comment by @TzviyaSiegman)
-
Discrepancy between the spec and the canonical manifest on title w3c/wpub#325 (1 comment by @TzviyaSiegman)
-
-
6 pull requests opened.
-
Moved the canonicalization out of the top level w3c/wpub#355, by @iherman.
-
Reading order and resources together set the bounds of a publication w3c/wpub#353, by @iherman.
-
Reference to opaque origin in the manifest lifecycle w3c/wpub#343, by @iherman.
-
linking issues raised in #191 w3c/wpub#340, by @mattgarrish.
-
Added the pagelist entry w3c/wpub#339, by @iherman.
-
-
5 pull requests merged.
-
Moved the canonicalization out of the top level w3c/wpub#355.
-
Added the pagelist entry w3c/wpub#339.
-
linking issues raised in #191 w3c/wpub#340.
-
-
2 pull requests closed.
-
Reference to opaque origin in the manifest lifecycle w3c/wpub#343.
-
Add `doJsonLd: true` respec config opt w3c/wpub#326.
-
-
7 pull requests received 95 new comments.
-
Added the pagelist entry w3c/wpub#339 (55 comments by @avneeshsingh, @danielweck, @HadrienGardeur, @iherman, @laudrain, @llemeurfr, @lrosenthol, @mattgarrish, @TzviyaSiegman)
-
incorporate webidl definitions into the body of the specification w3c/wpub#348 (17 comments by @HadrienGardeur, @iherman, @mattgarrish)
-
Reference to opaque origin in the manifest lifecycle w3c/wpub#343 (7 comments by @iherman, @JayPanoz, @mattgarrish, @rdeltour)
-
Reading order and resources together set the bounds of a publication w3c/wpub#353 (6 comments by @iherman, @lrosenthol, @mattgarrish)
-
w3c/dpub-pwp-ucr
-
16 pull requests opened.
-
Removing req11 20181030 w3c/dpub-pwp-ucr#180, by @francofaa.
-
Audiobooks Use cases w3c/dpub-pwp-ucr#179, by @wareid.
-
offlining and accessibility use cases w3c/dpub-pwp-ucr#178, by @francofaa.
-
remove me from editor list w3c/dpub-pwp-ucr#177, by @mattgarrish.
-
use case for multi heading structure w3c/dpub-pwp-ucr#176, by @francofaa.
-
Typos falvarado 20181017 w3c/dpub-pwp-ucr#175, by @francofaa.
-
litmag example, author of multiple chapters across multiple wp w3c/dpub-pwp-ucr#174, by @francofaa.
-
Updating from wpub falvarado 20181018 w3c/dpub-pwp-ucr#173, by @francofaa.
-
3.2 falvarado 20181018 w3c/dpub-pwp-ucr#172, by @francofaa.
-
Filling out section on Presentation w3c/dpub-pwp-ucr#171, by @francofaa.
-
query w3c/dpub-pwp-ucr#170, by @francofaa.
-
2.2.5 falvarado 20181017 w3c/dpub-pwp-ucr#169, by @francofaa.
-
language change w3c/dpub-pwp-ucr#168, by @francofaa.
-
Added use case for poor internet connection w3c/dpub-pwp-ucr#167, by @francofaa.
-
addition of potential use case, query w3c/dpub-pwp-ucr#166, by @francofaa.
-
2.1.1 falvarado 20181017 w3c/dpub-pwp-ucr#165, by @francofaa.
-
-
10 pull requests merged.
-
remove me from editor list w3c/dpub-pwp-ucr#177.
-
use case for multi heading structure w3c/dpub-pwp-ucr#176.
-
Typos falvarado 20181017 w3c/dpub-pwp-ucr#175.
-
litmag example, author of multiple chapters across multiple wp w3c/dpub-pwp-ucr#174.
-
Filling out section on Presentation w3c/dpub-pwp-ucr#171.
-
3.2 falvarado 20181018 w3c/dpub-pwp-ucr#172.
-
2.2.5 falvarado 20181017 w3c/dpub-pwp-ucr#169.
-
Added use case for poor internet connection w3c/dpub-pwp-ucr#167.
-
addition of potential use case, query w3c/dpub-pwp-ucr#166.
-
2.1.1 falvarado 20181017 w3c/dpub-pwp-ucr#165.
-
-
2 pull requests received 4 new comments.
-
Filling out section on Presentation w3c/dpub-pwp-ucr#171 (3 comments by @iherman, @laudrain, @TzviyaSiegman)
-
w3c/pub-manifest
-
1 issue received 2 new comments.
-
Usage of JSON-LD language maps in WPM? w3c/pub-manifest#15 (2 comments by @HadrienGardeur, @iherman)
-
w3c/pub-vocab
-
1 pull request opened.
-
Added the pageslist rel value w3c/pub-vocab#1, by @iherman.
-
GitHub
w3c/wpub
-
7 issues opened.
-
manifest must be embedded in primary entry page w3c/wpub#333, by @mattgarrish.
-
The primary entry page may be under specified w3c/wpub#329, by @llemeurfr.
-
3.5 Resources is flawed w3c/wpub#328, by @llemeurfr.
-
Only allow embedded manifests w3c/wpub#327, by @BigBlueHat.
-
Discrepancy between the spec and the canonical manifest on title w3c/wpub#325, by @iherman.
-
usage of rel=canonical ? w3c/wpub#324, by @iherman.
-
6 issues closed.
-
The primary entry page may be under specified w3c/wpub#329.
-
manifest must be embedded in primary entry page w3c/wpub#333.
-
Audiobooks and WPUB w3c/wpub#78.
-
usage of rel=canonical ? w3c/wpub#324.
-
3.5 Resources is flawed w3c/wpub#328.
-
-
21 issues received 60 new comments.
-
Hints about resources in "default reading order" or "list of resources" w3c/wpub#222 (7 comments by @dauwhe, @ghost, @HadrienGardeur, @JayPanoz, @llemeurfr, @TzviyaSiegman)
-
Do we need a more detailed definition for the HTML TOC format? w3c/wpub#291 (6 comments by @baldurbjarnason, @dauwhe, @ghost, @iherman, @llemeurfr, @rdeltour)
-
The primary entry page may be under specified w3c/wpub#329 (4 comments by @iherman, @llemeurfr, @mattgarrish)
-
manifest must be embedded in primary entry page w3c/wpub#333 (4 comments by @BigBlueHat, @dauwhe, @GarthConboy, @mattgarrish)
-
WP rendering in non WP aware browsers w3c/wpub#271 (4 comments by @avneeshsingh, @BigBlueHat, @TzviyaSiegman)
-
primary entry page must be added to reading order when reading order not specified w3c/wpub#334 (3 comments by @HadrienGardeur, @mattgarrish)
-
List of recommended audio formats for audio-only WP w3c/wpub#323 (2 comments by @llemeurfr, @lloydrasmussen)
-
We need a section of the document that explicitly defines the bounds of a publication w3c/wpub#205 (2 comments by @dauwhe, @mattgarrish)
-
Discrepancy between the spec and the canonical manifest on title w3c/wpub#325 (2 comments by @iherman)
-
Can a table of contents refer to resources outside the default reading order? w3c/wpub#276 (1 comment by @iherman)
-
Proposal: Add GitHub Issue Template for Affordance issues w3c/wpub#233 (1 comment by @TzviyaSiegman)
-
7 pull requests opened.
-
Accessibility tweaks w3c/wpub#337, by @mattgarrish.
-
clarify property names w3c/wpub#336, by @mattgarrish.
-
primary entry page issues w3c/wpub#335, by @mattgarrish.
-
Remove `@` from keywords w3c/wpub#332, by @iherman.
-
title element is a MUST for embedded manifests w3c/wpub#331, by @iherman.
-
Took care of the issues reported in 328 w3c/wpub#330, by @iherman.
-
Add `doJsonLd: true` respec config opt w3c/wpub#326, by @BigBlueHat.
-
-
6 pull requests merged.
-
Accessibility tweaks w3c/wpub#337.
-
clarify property names w3c/wpub#336.
-
primary entry page issues w3c/wpub#335.
-
Remove `@` from keywords w3c/wpub#332.
-
Took care of the issues reported in 328 w3c/wpub#330.
-
Lifecycle update w3c/wpub#318.
-
-
1 pull request reopened.
-
title element is a MUST for embedded manifests w3c/wpub#331, by @mattgarrish.
-
-
7 pull requests received 76 new comments.
-
title element is a MUST for embedded manifests w3c/wpub#331 (48 comments by @BigBlueHat, @deborahgu, @HadrienGardeur, @iherman, @JayPanoz, @laudrain, @llemeurfr, @mattgarrish, @TzviyaSiegman)
-
clarify property names w3c/wpub#336 (20 comments by @avneeshsingh, @clapierre, @HadrienGardeur, @iherman, @madeleinerothberg, @mattgarrish)
-
TR publications
-
1 document published.
-
Web Publications published as a Working Draft. History of Web Publications
-
Participants
-
1 participant left.
-
Bill McCoy (W3C) left.
-
-
2 organizations left.
-
Datalogics, Inc. left.
-
Consensys left.
-
GitHub
w3c/wpub
-
21 issues opened.
-
List of recommended audio formats for audio-only WP w3c/wpub#323, by @avneeshsingh.
-
Mixed media in audiobook linear reading order w3c/wpub#322, by @bduga.
-
What is an "opaque origin" and why do we care? w3c/wpub#321, by @dauwhe.
-
Supplemental Content in Audiobooks w3c/wpub#320, by @wareid.
-
"Web Publications" is not a search engine-friendly name w3c/wpub#319, by @bitsgalore.
-
WebIDL normative? w3c/wpub#317, by @iherman.
-
Minor comments on the JSON schema w3c/wpub#316, by @iherman.
-
How we name things is potentially confusing w3c/wpub#312, by @dauwhe.
-
Why is resource list required? w3c/wpub#311, by @dauwhe.
-
How do we represent Kana for book title/publisher name/creator name w3c/wpub#309, by @ghost.
-
Alternate formats or bitrate for an audiobook w3c/wpub#308, by @HadrienGardeur.
-
Duration of an audiobook w3c/wpub#307, by @HadrienGardeur.
-
Minor discrepancy between the draft and WebIDL? w3c/wpub#303, by @iherman.
-
Drop the default reading order from WP w3c/wpub#302, by @murata2makoto.
-
Final specification for the accessibility terms? w3c/wpub#300, by @iherman.
-
inker - omission or intentional? w3c/wpub#294, by @mattgarrish.
-
Do we need a more detailed definition for the HTML TOC format? w3c/wpub#291, by @iherman.
-
Array of strings in links/resources/readingOrder w3c/wpub#290, by @HadrienGardeur.
-
What does it mean for a resource to be listed as a link? w3c/wpub#289, by @dauwhe.
-
-
13 issues closed.
-
WebIDL normative? w3c/wpub#317.
-
Minor comments on the JSON schema w3c/wpub#316.
-
Why is resource list required? w3c/wpub#311.
-
Final specification for the accessibility terms? w3c/wpub#300.
-
Minor discrepancy between the draft and WebIDL? w3c/wpub#303.
-
What does it mean for a resource to be listed as a link? w3c/wpub#289.
-
Feedback while working on a JSON Schema for WP w3c/wpub#287.
-
Array of strings in links/resources/readingOrder w3c/wpub#290.
-
Mixture of Person and Organization? w3c/wpub#284.
-
inker - omission or intentional? w3c/wpub#294.
-
Note lack of availability of manifest properties? w3c/wpub#286.
-
-
1 issue reopened.
-
29 issues received 314 new comments.
-
Do we need a more detailed definition for the HTML TOC format? w3c/wpub#291 (94 comments by @baldurbjarnason, @dauwhe, @deborahgu, @GarthConboy, @ghost, @HadrienGardeur, @iherman, @laudrain, @llemeurfr, @mattgarrish, @rdeltour, @TzviyaSiegman)
-
Duration of an audiobook w3c/wpub#307 (22 comments by @danielweck, @ghost, @HadrienGardeur, @iherman, @llemeurfr)
-
Note lack of availability of manifest properties? w3c/wpub#286 (20 comments by @HadrienGardeur, @iherman, @laudrain, @llemeurfr, @mattgarrish)
-
Manifest: are we creating a JSON-LD metadata framework or a JSON structure? w3c/wpub#288 (19 comments by @akuckartz, @BigBlueHat, @HadrienGardeur, @iherman, @llemeurfr)
-
Letting the author control pagination vs scrolling w3c/wpub#207 (17 comments by @dauwhe, @frivoal, @ghost, @HadrienGardeur, @llemeurfr, @murata2makoto)
-
Feedback while working on a JSON Schema for WP w3c/wpub#287 (16 comments by @HadrienGardeur, @iherman)
-
WP rendering in non WP aware browsers w3c/wpub#271 (15 comments by @avneeshsingh, @BigBlueHat, @dauwhe, @GeorgeKerscher, @nruffilo, @TzviyaSiegman)
-
indicate different metadata (including narrators/creators/format) for different format of resource/track w3c/wpub#229 (11 comments by @ghost, @HadrienGardeur)
-
Processing our manifest into WebIDL w3c/wpub#268 (11 comments by @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish)
-
How we name things is potentially confusing w3c/wpub#312 (9 comments by @HadrienGardeur, @iherman, @laudrain, @mattgarrish, @RachelComerford)
-
What does it mean for a resource to be listed as a link? w3c/wpub#289 (9 comments by @BigBlueHat, @dauwhe, @HadrienGardeur, @iherman, @mattgarrish, @TzviyaSiegman)
-
Why is resource list required? w3c/wpub#311 (8 comments by @ghost, @HadrienGardeur, @iherman, @mattgarrish, @TzviyaSiegman)
-
Clarify the coercion process from strings to objects in `Text Values or Objects` w3c/wpub#314 (7 comments by @akuckartz, @BigBlueHat, @iherman)
-
Can a table of contents refer to resources outside the default reading order? w3c/wpub#276 (7 comments by @avneeshsingh, @BigBlueHat, @ghost, @iherman, @laudrain, @llemeurfr, @mattgarrish)
-
Drop the default reading order from WP w3c/wpub#302 (6 comments by @BigBlueHat, @GarthConboy, @laudrain, @llemeurfr, @murata2makoto)
-
Minor discrepancy between the draft and WebIDL? w3c/wpub#303 (6 comments by @HadrienGardeur, @iherman, @mattgarrish)
-
Conformance criterion for UA w3c/wpub#270 (5 comments by @dauwhe, @iherman, @mattgarrish, @RachelComerford)
-
How do we represent Kana for book title/publisher name/creator name w3c/wpub#309 (4 comments by @ghost, @HadrienGardeur, @llemeurfr)
-
Final specification for the accessibility terms? w3c/wpub#300 (4 comments by @avneeshsingh, @HadrienGardeur, @iherman)
-
Array of strings in links/resources/readingOrder w3c/wpub#290 (4 comments by @HadrienGardeur, @iherman)
-
What is an "opaque origin" and why do we care? w3c/wpub#321 (3 comments by @iherman, @JayPanoz, @mattgarrish)
-
"Web Publications" is not a search engine-friendly name w3c/wpub#319 (3 comments by @bitsgalore, @danielweck, @mattgarrish)
-
Mixed media in audiobook linear reading order w3c/wpub#322 (2 comments by @danielweck, @HadrienGardeur)
-
Alternate formats or bitrate for an audiobook w3c/wpub#308 (2 comments by @HadrienGardeur, @llemeurfr)
-
-
14 pull requests opened.
-
Lifecycle update w3c/wpub#318, by @iherman.
-
WebIDL Alignment w3c/wpub#315, by @iherman.
-
clarify resource list w3c/wpub#313, by @mattgarrish.
-
Accessibility terms update w3c/wpub#310, by @iherman.
-
Introduction of a canonical manifest w3c/wpub#306, by @iherman.
-
add default empty arrays w3c/wpub#305, by @mattgarrish.
-
Added infos on single values vs arrays and strings vs objects w3c/wpub#304, by @iherman.
-
update links description to try and better clarify uses w3c/wpub#301, by @mattgarrish.
-
Note on links w3c/wpub#298, by @iherman.
-
add reference to issue 291 w3c/wpub#297, by @mattgarrish.
-
allow person or organization w3c/wpub#296, by @mattgarrish.
-
fixes for 286 and 294 w3c/wpub#295, by @mattgarrish.
-
The default reading order should be required in the WebIDL w3c/wpub#292, by @iherman.
-
-
14 pull requests merged.
-
WebIDL Alignment w3c/wpub#315.
-
clarify resource list w3c/wpub#313.
-
Introduction of a canonical manifest w3c/wpub#306.
-
Accessibility terms update w3c/wpub#310.
-
add default empty arrays w3c/wpub#305.
-
Note on links w3c/wpub#298.
-
update links description to try and better clarify uses w3c/wpub#301.
-
allow person or organization w3c/wpub#296.
-
add reference to issue 291 w3c/wpub#297.
-
fixes for 286 and 294 w3c/wpub#295.
-
WebIDL update w3c/wpub#285.
-
-
13 pull requests received 114 new comments.
-
WebIDL update w3c/wpub#285 (33 comments by @danielweck, @dauwhe, @HadrienGardeur, @iherman, @laudrain, @llemeurfr, @mattgarrish, @TzviyaSiegman)
-
Introduction of a canonical manifest w3c/wpub#306 (25 comments by @HadrienGardeur, @iherman, @mattgarrish)
-
Accessibility API should also be a (possible) list values as opposed to a single one w3c/wpub#293 (25 comments by @avneeshsingh, @HadrienGardeur, @iherman, @mattgarrish)
-
Added infos on single values vs arrays and strings vs objects w3c/wpub#304 (8 comments by @HadrienGardeur, @iherman, @mattgarrish)
-
update links description to try and better clarify uses w3c/wpub#301 (5 comments by @iherman, @llemeurfr, @mattgarrish)
-
clarify resource list w3c/wpub#313 (4 comments by @HadrienGardeur, @iherman, @mattgarrish, @TzviyaSiegman)
-
w3c/pub-manifest
-
1 issue opened.
-
Usage of JSON-LD language maps in WPM? w3c/pub-manifest#15, by @iherman.
-
-
1 issue received 28 new comments.
-
Usage of JSON-LD language maps in WPM? w3c/pub-manifest#15 (28 comments by @danbri, @ghost, @HadrienGardeur, @iherman, @llemeurfr, @r12a)
-
TR publications
-
1 document published.
-
Web Publications published as a Working Draft. History of Web Publications
-
Participants
-
1 participant left.
-
Peter Krautzberger (W3C Invited Experts) left.
-
GitHub
w3c/wpub
-
14 issues opened.
-
Feedback while working on a JSON Schema for WP w3c/wpub#287, by @HadrienGardeur.
-
Note lack of availability of manifest properties? w3c/wpub#286, by @mattgarrish.
-
Mixture of Person and Organization? w3c/wpub#284, by @iherman.
-
WP rendering in non WP aware browsers w3c/wpub#271, by @avneeshsingh.
-
Conformance criterion for UA w3c/wpub#270, by @WSchindler.
-
Draft 2018-07-11: Minor editorial glitches w3c/wpub#269, by @WSchindler.
-
Processing our manifest into WebIDL w3c/wpub#268, by @HadrienGardeur.
-
encodingFormat supersedes fileFormat w3c/wpub#267, by @HadrienGardeur.
-
wording of the spec on different identifiers w3c/wpub#263, by @llemeurfr.
-
use of "cover image" w3c/wpub#261, by @TzviyaSiegman.
-
Cover infoset requirements is unclear w3c/wpub#260, by @deborahgu.
-
reading progression - conflict in spec w3c/wpub#259, by @TzviyaSiegman.
-
Support for a generic contributor element w3c/wpub#256, by @HadrienGardeur.
-
-
26 issues closed.
-
reading progression - conflict in spec w3c/wpub#259.
-
Info Set for privacy w3c/wpub#203.
-
accessibility report? w3c/wpub#239.
-
Expressing the overall language for the Metadata w3c/wpub#218.
-
Expressing the language of an item, say, "name" w3c/wpub#219.
-
Setting the (text) direction w3c/wpub#220.
-
Draft 2018-07-11: Minor editorial glitches w3c/wpub#269.
-
encodingFormat supersedes fileFormat w3c/wpub#267.
-
"expected" schema.org values w3c/wpub#228.
-
table of contents in resources? w3c/wpub#251.
-
Is "accessibility" a property or a categorization? w3c/wpub#255.
-
Linking to an external metadata record w3c/wpub#162.
-
Support for a generic contributor element w3c/wpub#256.
-
embedded manifest requires id? w3c/wpub#245.
-
Linking to alternate representations w3c/wpub#159.
-
Handling roles for creators w3c/wpub#167.
-
Search is a service and an affordance w3c/wpub#149.
-
Using the Readium Web Publication Manifest serialization w3c/wpub#119.
-
Experimenting with the Web App Manifest w3c/wpub#118.
-
Reference resources that are not part of the publication w3c/wpub#186.
-
Limiting reading order to the manifest w3c/wpub#148.
-
Linking to a privacy policy w3c/wpub#163.
-
Infoset feedback: title w3c/wpub#182.
-
avoiding resource declaration duplication w3c/wpub#59.
-
Minor issues on the lifecycle algorithms w3c/wpub#170.
-
-
1 issue reopened.
-
Setting the (text) direction w3c/wpub#220, by @mattgarrish.
-
-
40 issues received 240 new comments.
-
use of "cover image" w3c/wpub#261 (36 comments by @avneeshsingh, @danielweck, @deborahgu, @GarthConboy, @HadrienGardeur, @iherman, @laudrain, @llemeurfr, @mattgarrish, @TzviyaSiegman)
-
Setting the (text) direction w3c/wpub#220 (28 comments by @css-meeting-bot, @iherman, @JayPanoz, @llemeurfr, @mattgarrish, @TzviyaSiegman)
-
We need a section of the document that explicitly defines the bounds of a publication w3c/wpub#205 (26 comments by @bduga, @BigBlueHat, @css-meeting-bot, @dauwhe, @GarthConboy, @HadrienGardeur, @iherman, @TzviyaSiegman)
-
WP affords personalization w3c/wpub#138 (21 comments by @avneeshsingh, @baldurbjarnason, @clapierre, @deborahgu, @iherman, @JayPanoz, @laudrain, @llemeurfr, @mattgarrish)
-
Letting the author control pagination vs scrolling w3c/wpub#207 (12 comments by @avneeshsingh, @frivoal, @GarthConboy, @ghost, @HadrienGardeur, @jccr, @llemeurfr)
-
Other navigation elements beyond ToC w3c/wpub#223 (12 comments by @avneeshsingh, @BigBlueHat, @css-meeting-bot, @deborahgu, @GarthConboy, @iherman, @laudrain, @llemeurfr)
-
wording of the spec on different identifiers w3c/wpub#263 (11 comments by @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish)
-
Mixture of Person and Organization? w3c/wpub#284 (10 comments by @iherman, @laudrain, @mattgarrish, @RachelComerford, @tcole3)
-
Processing our manifest into WebIDL w3c/wpub#268 (10 comments by @HadrienGardeur, @iherman, @llemeurfr)
-
Linking to an external metadata record w3c/wpub#162 (9 comments by @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish)
-
Can a table of contents refer to resources outside the default reading order? w3c/wpub#276 (8 comments by @avneeshsingh, @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish)
-
Cover infoset requirements is unclear w3c/wpub#260 (6 comments by @deborahgu, @iherman, @laudrain, @mattgarrish, @TzviyaSiegman, @WSchindler)
-
Infoset feedback: title w3c/wpub#182 (5 comments by @BCWalters, @iherman, @laudrain, @TzviyaSiegman)
-
Hints about resources in "default reading order" or "list of resources" w3c/wpub#222 (4 comments by @BigBlueHat, @ghost, @HadrienGardeur)
-
Note lack of availability of manifest properties? w3c/wpub#286 (3 comments by @HadrienGardeur, @iherman)
-
Which infoset items MAY/SHOULD/MUST be expressed in JSON vs HTML? w3c/wpub#197 (1 comment by @iherman)
-
Using the Readium Web Publication Manifest serialization w3c/wpub#119 (1 comment by @HadrienGardeur)
-
Reference resources that are not part of the publication w3c/wpub#186 (1 comment by @HadrienGardeur)
-
-
18 pull requests opened.
-
WebIDL update w3c/wpub#285, by @iherman.
-
Store the script and data for the generation of the acknowledgement w3c/wpub#283, by @iherman.
-
note adjustments w3c/wpub#282, by @mattgarrish.
-
remove the note about a11y metadata in external records w3c/wpub#281, by @mattgarrish.
-
Remove myself as author w3c/wpub#279, by @dauwhe.
-
Reduced the font size for examples and notes w3c/wpub#278, by @iherman.
-
Pre publ editing w3c/wpub#277, by @iherman.
-
Language and dir rewrite w3c/wpub#275, by @iherman.
-
Added a section clarifying what the base is for manifest w3c/wpub#274, by @iherman.
-
allow any type of cover w3c/wpub#273, by @mattgarrish.
-
Moved IDL definitions into a separate directory w3c/wpub#272, by @iherman.
-
Fixes #260. Clarifying cover infoset requirements. w3c/wpub#266, by @deborahgu.
-
Canonical identifier clarifications w3c/wpub#265, by @mattgarrish.
-
WP script improvements w3c/wpub#264, by @iherman.
-
base direction cleanup w3c/wpub#262, by @mattgarrish.
-
Added the contributor as a creator. w3c/wpub#258, by @iherman.
-
Updated the extension section w3c/wpub#257, by @iherman.
-
-
15 pull requests merged.
-
note adjustments w3c/wpub#282.
-
remove the note about a11y metadata in external records w3c/wpub#281.
-
Pre publ editing w3c/wpub#277.
-
Language and dir rewrite w3c/wpub#275.
-
allow any type of cover w3c/wpub#273.
-
Added a section clarifying what the base is for manifest w3c/wpub#274.
-
Moved IDL definitions into a separate directory w3c/wpub#272.
-
Canonical identifier clarifications w3c/wpub#265.
-
WP script improvements w3c/wpub#264.
-
Updated the extension section w3c/wpub#257.
-
Added the contributor as a creator. w3c/wpub#258.
-
base direction cleanup w3c/wpub#262.
-
Updated the moby dick manifest examples w3c/wpub#252.
-
3 pull requests closed.
-
Remove myself as author w3c/wpub#279.
-
Reduced the font size for examples and notes w3c/wpub#278.
-
Fixes #260. Clarifying cover infoset requirements. w3c/wpub#266.
-
-
1 pull request reopened.
-
13 pull requests received 133 new comments.
-
Added the contributor as a creator. w3c/wpub#258 (32 comments by @HadrienGardeur, @iherman, @laudrain, @llemeurfr, @mattgarrish)
-
Language and dir rewrite w3c/wpub#275 (23 comments by @iherman, @llemeurfr, @mattgarrish, @r12a, @TzviyaSiegman)
-
Added a section clarifying what the base is for manifest w3c/wpub#274 (8 comments by @iherman, @mattgarrish)
-
add significant authoring/editing contributions as acknowledgement w3c/wpub#280 (4 comments by @iherman, @mattgarrish)
-
Fixes #260. Clarifying cover infoset requirements. w3c/wpub#266 (3 comments by @deborahgu, @mattgarrish)
-
w3c/dpub-pwp-ucr
-
1 pull request opened.
-
Rearrange existing requirements w3c/dpub-pwp-ucr#164, by @atyposh.
-
-
1 pull request merged.
-
Rearrange existing requirements w3c/dpub-pwp-ucr#164.
-
-
1 pull request received 1 new comment.
w3c/pub-manifest
-
1 issue received 1 new comment.
GitHub
w3c/wpub
-
24 issues opened.
-
Is "accessibility" a property or a categorization? w3c/wpub#255, by @mattgarrish.
-
table of contents in resources? w3c/wpub#251, by @mattgarrish.
-
Flatland: An Audiobook Experiment of Many Dimensions w3c/wpub#247, by @HadrienGardeur.
-
embedded manifest requires id? w3c/wpub#245, by @mattgarrish.
-
https for schema.org? w3c/wpub#241, by @mattgarrish.
-
accessibility report? w3c/wpub#239, by @TzviyaSiegman.
-
"Links" or "extraResources" ? w3c/wpub#237, by @iherman.
-
Proper management of vocabulary and context files... w3c/wpub#236, by @iherman.
-
Use LinkRole instead of PublicationLink w3c/wpub#235, by @iherman.
-
representation of table of contents in the manifest w3c/wpub#234, by @iherman.
-
Proposal: Add GitHub Issue Template for Affordance issues w3c/wpub#233, by @BigBlueHat.
-
"expected" schema.org values w3c/wpub#228, by @mattgarrish.
-
yet another 'resource list' in the manifest? w3c/wpub#225, by @iherman.
-
Other navigation elements beyond ToC w3c/wpub#223, by @HadrienGardeur.
-
Setting the (text) direction w3c/wpub#220, by @iherman.
-
Expressing the language of an item, say, "name" w3c/wpub#219, by @iherman.
-
Expressing the overall language for the Metadata w3c/wpub#218, by @iherman.
-
Order sensitivity of terms like 'creator', 'author', ... w3c/wpub#217, by @iherman.
-
"order" in the reading order in JSON-LD w3c/wpub#212, by @iherman.
-
Is 'cover' a structural property? w3c/wpub#210, by @iherman.
-
Letting the author control pagination vs scrolling w3c/wpub#207, by @HadrienGardeur.
-
-
17 issues closed.
-
Must the manifest be listed in the resource list? w3c/wpub#192.
-
Replace the "infoset" term? w3c/wpub#63.
-
representation of table of contents in the manifest w3c/wpub#234.
-
"Links" or "extraResources" ? w3c/wpub#237.
-
Proper management of vocabulary and context files... w3c/wpub#236.
-
https for schema.org? w3c/wpub#241.
-
Order sensitivity of terms like 'creator', 'author', ... w3c/wpub#217.
-
Is 'cover' a structural property? w3c/wpub#210.
-
yet another 'resource list' in the manifest? w3c/wpub#225.
-
Progression/direction between resources w3c/wpub#126.
-
"order" in the reading order in JSON-LD w3c/wpub#212.
-
Proposed changes / additions to WAM w3c/wpub#127.
-
Add to reading/publication list w3c/wpub#153.
-
2 issues reopened.
-
Must the manifest be listed in the resource list? w3c/wpub#192, by @dauwhe.
-
Resources SHOULD or MAY provide a link to the manifest w3c/wpub#191, by @iherman.
-
-
46 issues received 237 new comments.
-
yet another 'resource list' in the manifest? w3c/wpub#225 (26 comments by @avneeshsingh, @GarthConboy, @GeorgeKerscher, @HadrienGardeur, @iherman, @jeankaplansky, @laudrain, @llemeurfr, @TzviyaSiegman)
-
Setting the (text) direction w3c/wpub#220 (25 comments by @BigBlueHat, @danielweck, @iherman, @laudrain, @llemeurfr)
-
Letting the author control pagination vs scrolling w3c/wpub#207 (20 comments by @bduga, @BigBlueHat, @dauwhe, @frivoal, @GarthConboy, @HadrienGardeur, @iherman, @llemeurfr, @TzviyaSiegman)
-
Must the manifest be listed in the resource list? w3c/wpub#192 (15 comments by @BigBlueHat, @dauwhe, @GarthConboy, @iherman, @llemeurfr, @TzviyaSiegman)
-
WP affords personalization w3c/wpub#138 (12 comments by @avneeshsingh, @bduga, @clapierre, @diagram-codesprint, @iherman, @JayPanoz, @llemeurfr, @lseeman)
-
Mismatch in the accessibility references in the current text and schema... w3c/wpub#216 (12 comments by @avneeshsingh, @clapierre, @GeorgeKerscher, @iherman, @laudrain)
-
WP provides a TOC without leaving the resource w3c/wpub#146 (11 comments by @ghost, @HadrienGardeur, @iherman, @llemeurfr, @TzviyaSiegman)
-
Bring back popular EPUB 2.x/3.x metadata? w3c/wpub#187 (9 comments by @dauwhe, @HadrienGardeur, @iherman, @laudrain, @llemeurfr)
-
"order" in the reading order in JSON-LD w3c/wpub#212 (8 comments by @akuckartz, @dauwhe, @HadrienGardeur, @iherman, @llemeurfr)
-
"Links" or "extraResources" ? w3c/wpub#237 (7 comments by @GarthConboy, @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish)
-
representation of table of contents in the manifest w3c/wpub#234 (7 comments by @HadrienGardeur, @iherman, @TzviyaSiegman)
-
table of contents in resources? w3c/wpub#251 (6 comments by @dauwhe, @HadrienGardeur, @iherman, @mattgarrish)
-
What does modification date mean? w3c/wpub#73 (6 comments by @atyposh, @baldurbjarnason, @RachelComerford)
-
Expressing the language of an item, say, "name" w3c/wpub#219 (6 comments by @HadrienGardeur, @iherman)
-
Flatland: An Audiobook Experiment of Many Dimensions w3c/wpub#247 (5 comments by @danielweck, @GarthConboy, @HadrienGardeur, @llemeurfr)
-
Is 'cover' a structural property? w3c/wpub#210 (4 comments by @HadrienGardeur, @iherman, @llemeurfr)
-
Other navigation elements beyond ToC w3c/wpub#223 (4 comments by @danielweck, @GarthConboy, @HadrienGardeur, @laudrain)
-
Hints about resources in "default reading order" or "list of resources" w3c/wpub#222 (4 comments by @danielweck, @GarthConboy, @HadrienGardeur, @TzviyaSiegman)
-
Which infoset items MAY/SHOULD/MUST be expressed in JSON vs HTML? w3c/wpub#197 (2 comments by @BigBlueHat, @iherman)
-
Proposal: Add GitHub Issue Template for Affordance issues w3c/wpub#233 (2 comments by @iherman, @TzviyaSiegman)
-
Do we consider a (JSON) manifest to be part of a `<script>` element w3c/wpub#122 (1 comment by @iherman)
-
Is an exhaustive "resource list" required to create a Web Publication? w3c/wpub#198 (1 comment by @iherman)
-
-
24 pull requests opened.
-
Table of contents clarifications w3c/wpub#254, by @mattgarrish.
-
Script to generate and embedded WP manifest w3c/wpub#253, by @iherman.
-
Updated the moby dick manifest examples w3c/wpub#252, by @iherman.
-
No self referencing of manifests w3c/wpub#250, by @iherman.
-
Update affiliation w3c/wpub#249, by @frivoal.
-
Post pr review w3c/wpub#248, by @iherman.
-
TOC changed per discussion in issue 234 w3c/wpub#246, by @iherman.
-
Changing externalResources to links w3c/wpub#244, by @iherman.
-
Vocabulary cleanup: w3c/wpub#243, by @iherman.
-
update schema.org references to use https w3c/wpub#242, by @mattgarrish.
-
Minor changes w3c/wpub#240, by @iherman.
-
Restructure to de-dup definitions w3c/wpub#238, by @mattgarrish.
-
Additional resources w3c/wpub#232, by @iherman.
-
Edited manually what was in PR #200 w3c/wpub#231, by @iherman.
-
Issue #145 - added affordance for reading-state w3c/wpub#230, by @wareid.
-
add explanatory intro for webidl appendix w3c/wpub#227, by @mattgarrish.
-
Added draft for the TOC affordance w3c/wpub#226, by @iherman.
-
Aligned WebIDL proposal with recent discussions w3c/wpub#224, by @HadrienGardeur.
-
First attempt for Schema.org mapping w3c/wpub#221, by @iherman.
-
First attempt at crafting a JSON-LD context w3c/wpub#215, by @HadrienGardeur.
-
Added text for the affordance "Guided Navigation" w3c/wpub#214, by @iherman.
-
Manifest rewrite w3c/wpub#213, by @iherman.
-
Toronto f2f resolutions start w3c/wpub#211, by @iherman.
-
Removed "Processing the default reading order" w3c/wpub#206, by @HadrienGardeur.
-
-
22 pull requests merged.
-
Table of contents clarifications w3c/wpub#254.
-
Script to generate and embedded WP manifest w3c/wpub#253.
-
No self referencing of manifests w3c/wpub#250.
-
Update affiliation w3c/wpub#249.
-
Post pr review w3c/wpub#248.
-
TOC changed per discussion in issue 234 w3c/wpub#246.
-
Changing externalResources to links w3c/wpub#244.
-
Vocabulary cleanup: w3c/wpub#243.
-
update schema.org references to use https w3c/wpub#242.
-
Minor changes w3c/wpub#240.
-
Restructure to de-dup definitions w3c/wpub#238.
-
Additional resources w3c/wpub#232.
-
Edited manually what was in PR #200 w3c/wpub#231.
-
add explanatory intro for webidl appendix w3c/wpub#227.
-
Issue #145 - added affordance for reading-state w3c/wpub#230.
-
Added draft for the TOC affordance w3c/wpub#226.
-
First attempt for Schema.org mapping w3c/wpub#221.
-
Aligned WebIDL proposal with recent discussions w3c/wpub#224.
-
First attempt at crafting a JSON-LD context w3c/wpub#215.
-
Toronto f2f resolutions start w3c/wpub#211.
-
Manifest rewrite w3c/wpub#213.
-
Removed "Processing the default reading order" w3c/wpub#206.
-
-
2 pull requests closed.
-
Added text for the affordance "Guided Navigation" w3c/wpub#214.
-
Reordered & relisted requirements to match prose w3c/wpub#200.
-
-
17 pull requests received 88 new comments.
-
Additional resources w3c/wpub#232 (12 comments by @HadrienGardeur, @iherman, @llemeurfr, @TzviyaSiegman)
-
Table of contents clarifications w3c/wpub#254 (11 comments by @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish)
-
Aligned WebIDL proposal with recent discussions w3c/wpub#224 (9 comments by @dauwhe, @HadrienGardeur, @iherman)
-
First attempt at crafting a JSON-LD context w3c/wpub#215 (8 comments by @HadrienGardeur, @iherman, @llemeurfr)
-
Removed "Processing the default reading order" w3c/wpub#206 (5 comments by @HadrienGardeur, @iherman)
-
Added text for the affordance "Guided Navigation" w3c/wpub#214 (4 comments by @HadrienGardeur, @iherman, @mattgarrish)
w3c/dpub-pwp-ucr
-
1 issue opened.
-
"Sync up" language is confusing w3c/dpub-pwp-ucr#163, by @BigBlueHat.
-
-
1 issue closed.
-
Assumptions about web history w3c/dpub-pwp-ucr#87.
-
-
1 issue received 8 new comments.
-
"Sync up" language is confusing w3c/dpub-pwp-ucr#163 (8 comments by @atyposh, @BigBlueHat, @llemeurfr, @TzviyaSiegman)
-
-
1 pull request merged.
-
Added a "Sync content from different forms" w3c/dpub-pwp-ucr#162.
-
w3c/pub-manifest
-
2 issues opened.
-
Spreads and having control over them w3c/pub-manifest#23, by @HadrienGardeur.
-
Letting the author control device orientation w3c/pub-manifest#24, by @HadrienGardeur.
-
-
1 issue received 8 new comments.
-
Spreads and having control over them w3c/pub-manifest#23 (8 comments by @danielweck, @dauwhe, @HadrienGardeur, @TzviyaSiegman)
-
Participants
-
2 organizations joined.
-
Deque Systems, Inc. joined.
-
Scenarex Inc. joined.
-
GitHub
w3c/wpub
-
17 issues opened.
-
Document should call out specific actions/notes for User Agents w3c/wpub#204, by @lrosenthol.
-
Info Set for privacy w3c/wpub#203, by @rickj.
-
WAM required or not w3c/wpub#199, by @GarthConboy.
-
Which infoset items MAY/SHOULD/MUST be expressed in JSON vs HTML? w3c/wpub#197, by @BigBlueHat.
-
Which manifest applies? w3c/wpub#194, by @dauwhe.
-
Must the manifest be listed in the resource list? w3c/wpub#192, by @dauwhe.
-
Resources SHOULD or MAY provide a link to the manifest w3c/wpub#191, by @deborahgu.
-
"resources that belong to more than one Web Publication" w3c/wpub#190, by @deborahgu.
-
linking to multiple manifests w3c/wpub#189, by @dauwhe.
-
Sortable metadata strings w3c/wpub#188, by @HadrienGardeur.
-
Bring back popular EPUB 2.x/3.x metadata? w3c/wpub#187, by @HadrienGardeur.
-
Reference resources that are not part of the publication w3c/wpub#186, by @HadrienGardeur.
-
A WP should be able to reference external metadata w3c/wpub#185, by @GarthConboy.
-
9 issues closed.
-
Content Integrity w3c/wpub#125.
-
Document Collection Interface w3c/wpub#3.
-
Teaching the Web object permanence w3c/wpub#157.
-
Relationships to the Web App Manifest specification. w3c/wpub#32.
-
WAM required or not w3c/wpub#199.
-
What is the Browsing Context of a Web Publication? w3c/wpub#104.
-
A WP should be able to reference external metadata w3c/wpub#185.
-
-
38 issues received 273 new comments.
-
Is it acceptable to use HTML for the serialization of some infoset items, or should it all be in separate (JSON) file? w3c/wpub#193 (77 comments by @BigBlueHat, @css-meeting-bot, @danielweck, @dauwhe, @deborahgu, @GarthConboy, @HadrienGardeur, @iherman, @JayPanoz, @llemeurfr, @mattgarrish, @RachelComerford, @TzviyaSiegman)
-
Is an exhaustive "resource list" required to create a Web Publication? w3c/wpub#198 (52 comments by @BigBlueHat, @css-meeting-bot, @dauwhe, @deborahgu, @GarthConboy, @HadrienGardeur, @iherman, @mattgarrish, @tcole3)
-
Reference resources that are not part of the publication w3c/wpub#186 (25 comments by @BigBlueHat, @HadrienGardeur, @iherman, @RachelComerford, @TzviyaSiegman)
-
What is the Browsing Context of a Web Publication? w3c/wpub#104 (17 comments by @BigBlueHat, @css-meeting-bot, @GarthConboy, @HadrienGardeur, @iherman, @RachelComerford, @TzviyaSiegman)
-
Bring back popular EPUB 2.x/3.x metadata? w3c/wpub#187 (15 comments by @avneeshsingh, @BigBlueHat, @HadrienGardeur, @iherman, @kovidgoyal, @llemeurfr, @mattgarrish, @TzviyaSiegman)
-
linking to multiple manifests w3c/wpub#189 (13 comments by @BigBlueHat, @danielweck, @deborahgu, @HadrienGardeur, @iherman, @mattgarrish, @TzviyaSiegman)
-
Which infoset items MAY/SHOULD/MUST be expressed in JSON vs HTML? w3c/wpub#197 (10 comments by @deborahgu, @HadrienGardeur, @iherman, @TzviyaSiegman)
-
Which manifest applies? w3c/wpub#194 (7 comments by @GarthConboy, @ghost, @HadrienGardeur, @mattgarrish)
-
Must the manifest be listed in the resource list? w3c/wpub#192 (7 comments by @HadrienGardeur, @iherman, @mattgarrish, @TzviyaSiegman)
-
WP provides a TOC without leaving the resource w3c/wpub#146 (6 comments by @ghost, @HadrienGardeur, @iherman)
-
"resources that belong to more than one Web Publication" w3c/wpub#190 (5 comments by @deborahgu, @mattgarrish)
-
Do we consider a (JSON) manifest to be part of a `<script>` element w3c/wpub#122 (4 comments by @dauwhe, @HadrienGardeur)
-
Resources SHOULD or MAY provide a link to the manifest w3c/wpub#191 (3 comments by @deborahgu, @iherman, @llemeurfr)
-
Linking to an external metadata record w3c/wpub#162 (3 comments by @BigBlueHat, @GarthConboy, @HadrienGardeur)
-
A WP should be able to reference external metadata w3c/wpub#185 (2 comments by @GarthConboy, @HadrienGardeur)
-
Response to Chrome team's feedback about accessibility section w3c/wpub#154 (1 comment by @TzviyaSiegman)
-
We need a section of the document that explicitly defines the bounds of a publication w3c/wpub#205 (1 comment by @wareid)
-
-
5 pull requests opened.
-
Remove WAM and separate context. w3c/wpub#202, by @iherman.
-
Reordered & relisted requirements to match prose w3c/wpub#200, by @BigBlueHat.
-
Work-In-Progress: expression experiments w3c/wpub#196, by @BigBlueHat.
-
Rename entry point to entry page w3c/wpub#195, by @BigBlueHat.
-
remove "Why Web Publications" from the introduction w3c/wpub#184, by @mattgarrish.
-
-
5 pull requests merged.
-
Remove WAM and separate context. w3c/wpub#202.
-
Rename entry point to entry page w3c/wpub#195.
-
Work-In-Progress: expression experiments w3c/wpub#196.
-
remove "Why Web Publications" from the introduction w3c/wpub#184.
-
-
4 pull requests received 15 new comments.
-
Reordered & relisted requirements to match prose w3c/wpub#200 (8 comments by @BigBlueHat, @HadrienGardeur, @iherman, @mattgarrish)
-
update accessibility section in infoset to be a link to a report w3c/wpub#171 (2 comments by @iherman, @mattgarrish)
-
w3c/dpub-pwp-ucr
-
1 issue closed.
-
invigorated socio-cultural engagement w3c/dpub-pwp-ucr#88.
-
-
2 issues received 10 new comments.
-
Assumptions about web history w3c/dpub-pwp-ucr#87 (8 comments by @atyposh, @marcoscaceres, @sideshowbarker)
-
-
1 pull request opened.
-
Added a "Sync content from different forms" w3c/dpub-pwp-ucr#162, by @iherman.
-
Participants
-
2 organizations joined.
-
Harvard Business Publishing joined.
-
Japan Electronic Publishing Association joined.
-
GitHub
w3c/wpub
-
10 issues opened.
-
Publisher Options for Offlining (caching of) a WP w3c/wpub#183, by @tcole3.
-
Infoset feedback: title w3c/wpub#182, by @laudrain.
-
Infoset feedback: Privacy policies w3c/wpub#181, by @laudrain.
-
Infoset feedback: versioning w3c/wpub#180, by @laudrain.
-
Infoset feedback: Address / Canonical identifier w3c/wpub#179, by @laudrain.
-
Infoset feedback : Accessibility compliance information w3c/wpub#178, by @laudrain.
-
Scope of our infoset w3c/wpub#176, by @HadrienGardeur.
-
infoset feedback w3c/wpub#175, by @TzviyaSiegman.
-
Clarify Introduction w3c/wpub#174, by @TzviyaSiegman.
-
Edit Intro w3c/wpub#173, by @TzviyaSiegman.
-
-
1 issue closed.
-
infoset feedback w3c/wpub#175.
-
-
22 issues received 105 new comments.
-
Scope of our infoset w3c/wpub#176 (18 comments by @BCWalters, @dauwhe, @GarthConboy, @HadrienGardeur, @iherman, @laudrain, @TzviyaSiegman, @WSchindler)
-
WP affords offline reading capabilities. w3c/wpub#141 (13 comments by @HadrienGardeur, @iherman, @jmulliken, @TzviyaSiegman, @WSchindler)
-
Search is a service and an affordance w3c/wpub#149 (13 comments by @BigBlueHat, @dauwhe, @jmulliken, @js-choi, @pkra, @WSchindler)
-
Publisher Options for Offlining (caching of) a WP w3c/wpub#183 (12 comments by @BigBlueHat, @dauwhe, @GarthConboy, @HadrienGardeur, @iherman, @laudrain, @pkra, @WSchindler)
-
Infoset feedback: Privacy policies w3c/wpub#181 (10 comments by @BCWalters, @dauwhe, @HadrienGardeur, @iherman, @laudrain, @mattgarrish)
-
WP affords personalization w3c/wpub#138 (6 comments by @avneeshsingh, @iherman, @JayPanoz, @jmulliken)
-
WP affords time-based media and text w3c/wpub#134 (3 comments by @GeorgeKerscher, @iherman, @jmulliken)
-
WP affords filtered navigation/reading experience w3c/wpub#140 (3 comments by @BigBlueHat, @jmulliken, @WSchindler)
-
What does "Reading Order" mean in the context of a Web Publication? w3c/wpub#38 (3 comments by @dauwhe, @jmulliken, @pkra)
-
-
2 pull requests opened.
-
Change editoral note about context to ref #104 w3c/wpub#177, by @BigBlueHat.
-
Update index.html w3c/wpub#172, by @laudrain.
-
-
3 pull requests merged.
-
Change editoral note about context to ref #104 w3c/wpub#177.
-
Added reading progression direction to WebIDL w3c/wpub#169.
-
Update index.html w3c/wpub#172.
-
-
2 pull requests received 6 new comments.
w3c/dpub-pwp-ucr
-
1 issue opened.
-
offlining use cases w3c/dpub-pwp-ucr#161, by @TzviyaSiegman.
-
-
1 issue received 1 new comment.
TR publications
-
1 document published.
-
Web Publications published as a Working Draft. History of Web Publications
-
Participants
-
1 participant left.
-
David Wood (Consensys) left.
-
-
2 organizations joined.
-
Consensys joined.
-
Earth Science Data Systems Program joined.
-
-
1 organization left.
-
Sony Group Corporation left.
-
GitHub
w3c/wpub
-
10 issues opened.
-
Minor issues on the lifecycle algorithms w3c/wpub#170, by @iherman.
-
How would an extension to WAM work for a WP implementation? w3c/wpub#168, by @iherman.
-
Handling roles for creators w3c/wpub#167, by @HadrienGardeur.
-
Track AMP related activity and specs w3c/wpub#166, by @BigBlueHat.
-
Google proposed Find in Page API under review by the TAG w3c/wpub#165, by @BigBlueHat.
-
Linking to a privacy policy w3c/wpub#163, by @HadrienGardeur.
-
Linking to an external metadata record w3c/wpub#162, by @HadrienGardeur.
-
Default direction need to be compatible with epub 3.1 w3c/wpub#160, by @ghost.
-
Linking to alternate representations w3c/wpub#159, by @HadrienGardeur.
-
Teaching the Web object permanence w3c/wpub#157, by @BigBlueHat.
-
-
23 issues closed.
-
Covers are currently missing from our infoset w3c/wpub#128.
-
Default direction need to be compatible with epub 3.1 w3c/wpub#160.
-
Google proposed Find in Page API under review by the TAG w3c/wpub#165.
-
Improving infoset & WebIDL for creators w3c/wpub#151.
-
Track AMP related activity and specs w3c/wpub#166.
-
Relationship to the Web Animation work. w3c/wpub#70.
-
Expressing metadata in multiple scripts/languages w3c/wpub#124.
-
Working out the manifest life cycle w3c/wpub#121.
-
MathML and WPUB w3c/wpub#72.
-
Naming the media overlay work w3c/wpub#69.
-
Associating a manifest with publication resources w3c/wpub#13.
-
Machine-Readable navigation w3c/wpub#9.
-
Navigating a web publication w3c/wpub#2.
-
manifest: requirements for offline w3c/wpub#22.
-
Role of the HTML document returned by the WPUB URL w3c/wpub#103.
-
-
44 issues received 128 new comments.
-
Linking to alternate representations w3c/wpub#159 (16 comments by @BigBlueHat, @HadrienGardeur, @iherman, @mattgarrish, @TzviyaSiegman)
-
What should be in the spec for affordances? w3c/wpub#143 (8 comments by @ghost, @iherman, @WSchindler)
-
Search is a service and an affordance w3c/wpub#149 (7 comments by @BigBlueHat, @HadrienGardeur, @iherman, @llemeurfr)
-
WP affords moving forward and backward w3c/wpub#144 (6 comments by @avneeshsingh, @BigBlueHat, @HadrienGardeur, @iherman, @llemeurfr)
-
Response to Chrome team's feedback about accessibility section w3c/wpub#154 (5 comments by @avneeshsingh, @deborahgu, @iherman, @mattgarrish)
-
Default direction need to be compatible with epub 3.1 w3c/wpub#160 (4 comments by @ghost, @iherman, @mattgarrish)
-
WP affords treatment of the publication as a logical whole w3c/wpub#136 (4 comments by @HadrienGardeur, @iherman, @TzviyaSiegman)
-
Linking to an external metadata record w3c/wpub#162 (3 comments by @HadrienGardeur, @laudrain, @llemeurfr)
-
WP affords offline reading capabilities. w3c/wpub#141 (3 comments by @HadrienGardeur, @iherman, @jmulliken)
-
How would an extension to WAM work for a WP implementation? w3c/wpub#168 (2 comments by @HadrienGardeur, @iherman)
-
Do we consider a (JSON) manifest to be part of a `<script>` element w3c/wpub#122 (2 comments by @HadrienGardeur, @iherman)
-
Should linking from manifests support URI templates? w3c/wpub#67 (2 comments by @HadrienGardeur, @iherman)
-
Google proposed Find in Page API under review by the TAG w3c/wpub#165 (2 comments by @BigBlueHat, @iherman)
-
How do we identify a web publication and its components? w3c/wpub#5 (2 comments by @iherman, @tcole3)
-
Do all documents in the reading order have to be reachable from the ToC w3c/wpub#39 (2 comments by @iherman)
-
MUST the manifest include information about secondary resources or not? w3c/wpub#23 (2 comments by @iherman)
-
i18n of metadata values, in case JSON is chosen as a serialization format w3c/wpub#1 (2 comments by @iherman)
-
Proposal: an HTML-first Table of Contents approach to Web Publication w3c/wpub#35 (1 comment by @iherman)
-
-
6 pull requests opened.
-
update accessibility section in infoset to be a link to a report w3c/wpub#171, by @mattgarrish.
-
Added reading progression direction to WebIDL w3c/wpub#169, by @HadrienGardeur.
-
Removed references to closed issues (after March issues' cleanup) w3c/wpub#164, by @iherman.
-
Added new dictionary in WebIDL for creators w3c/wpub#161, by @HadrienGardeur.
-
ORCID logo rendering done properly w3c/wpub#158, by @iherman.
-
add description of cover to infoset w3c/wpub#156, by @mattgarrish.
-
-
6 pull requests merged.
-
Added new dictionary in WebIDL for creators w3c/wpub#161.
-
add description of cover to infoset w3c/wpub#156.
-
ORCID logo rendering done properly w3c/wpub#158.
-
clarify the agent of infoset requirements w3c/wpub#155.
-
Added a new information item for progression direction. w3c/wpub#142.
-
2 pull requests closed.
-
media type registration for manifest file w3c/wpub#81.
-
8 pull requests received 20 new comments.
-
update accessibility section in infoset to be a link to a report w3c/wpub#171 (9 comments by @avneeshsingh, @GeorgeKerscher, @laudrain, @mattgarrish)
-
Added a new information item for progression direction. w3c/wpub#142 (4 comments by @ghost, @iherman, @mattgarrish)
-
Add manifest example to spec, and add sample document to repo w3c/wpub#109 (2 comments by @iherman, @mattgarrish)
-
Removed references to closed issues (after March issues' cleanup) w3c/wpub#164 (1 comment by @iherman)
-
w3c/pwpub
-
4 issues opened.
-
FYI: Web Packaging discussions at Mozilla w3c/pwpub#27, by @iherman.
-
Update authority w3c/pwpub#26, by @BigBlueHat.
-
Is "signing as an origin" sufficient? w3c/pwpub#25, by @BigBlueHat.
-
Is "Indexed by URL" sufficient? w3c/pwpub#24, by @BigBlueHat.
-
-
2 issues received 3 new comments.
Participants
-
1 organization joined.
-
INNOVIMAX joined.
-
GitHub
w3c/wpub
-
21 issues opened.
-
Response to Chrome team's feedback about accessibility section w3c/wpub#154, by @avneeshsingh.
-
Add to reading/publication list w3c/wpub#153, by @HadrienGardeur.
-
Improving infoset & WebIDL for creators w3c/wpub#151, by @HadrienGardeur.
-
Some collected items on manifest items w3c/wpub#150, by @iherman.
-
Search is a service and an affordance w3c/wpub#149, by @HadrienGardeur.
-
Limiting reading order to the manifest w3c/wpub#148, by @HadrienGardeur.
-
WP provides a TOC without leaving the resource w3c/wpub#146, by @iherman.
-
WP affords saving and retrieve progression w3c/wpub#145, by @iherman.
-
WP affords moving forward and backward w3c/wpub#144, by @iherman.
-
What should be in the spec for affordances? w3c/wpub#143, by @iherman.
-
WP affords offline reading capabilities. w3c/wpub#141, by @jmulliken.
-
WP affords filtered navigation/reading experience w3c/wpub#140, by @TzviyaSiegman.
-
WP affords guided navigation w3c/wpub#139, by @TzviyaSiegman.
-
WP affords personalization w3c/wpub#138, by @TzviyaSiegman.
-
WP affords "paging" through a publication w3c/wpub#137, by @TzviyaSiegman.
-
WP affords treatment of the publication as a logical whole w3c/wpub#136, by @TzviyaSiegman.
-
WP affords inclusion of data w3c/wpub#135, by @TzviyaSiegman.
-
WP affords time-based media and text w3c/wpub#134, by @TzviyaSiegman.
-
WP affords alternative modalities w3c/wpub#133, by @TzviyaSiegman.
-
Covers are currently missing from our infoset w3c/wpub#128, by @HadrienGardeur.
-
Proposed changes / additions to WAM w3c/wpub#127, by @TzviyaSiegman.
-
-
2 issues closed.
-
manifest: metadata w3c/wpub#21.
-
Web Publication affordances examination w3c/wpub#52.
-
-
27 issues received 163 new comments.
-
Proposed changes / additions to WAM w3c/wpub#127 (56 comments by @akuckartz, @baldurbjarnason, @BigBlueHat, @HadrienGardeur, @iherman, @js-choi, @laudrain, @llemeurfr, @mattgarrish, @rdeltour, @TzviyaSiegman)
-
Progression/direction between resources w3c/wpub#126 (31 comments by @danielweck, @dauwhe, @GarthConboy, @HadrienGardeur, @iherman, @JayPanoz, @laudrain, @llemeurfr, @mattgarrish, @murata2makoto, @TzviyaSiegman)
-
WP affords moving forward and backward w3c/wpub#144 (12 comments by @HadrienGardeur, @iherman, @llemeurfr, @TzviyaSiegman)
-
Improving infoset & WebIDL for creators w3c/wpub#151 (8 comments by @BillKasdorf, @HadrienGardeur, @laudrain, @llemeurfr, @TzviyaSiegman)
-
Expressing metadata in multiple scripts/languages w3c/wpub#124 (7 comments by @HadrienGardeur, @iherman, @llemeurfr)
-
Relationships to the Web App Manifest specification. w3c/wpub#32 (7 comments by @HadrienGardeur, @llemeurfr, @triblondon, @TzviyaSiegman)
-
Covers are currently missing from our infoset w3c/wpub#128 (6 comments by @dauwhe, @HadrienGardeur, @mattgarrish)
-
Language of web publication v. language of manifest/resources w3c/wpub#53 (5 comments by @HadrienGardeur, @iherman, @mattgarrish)
-
WP provides a TOC without leaving the resource w3c/wpub#146 (2 comments by @avneeshsingh, @TzviyaSiegman)
-
What does "Reading Order" mean in the context of a Web Publication? w3c/wpub#38 (2 comments by @BigBlueHat, @iherman)
-
WP affords filtered navigation/reading experience w3c/wpub#140 (2 comments by @HadrienGardeur, @TzviyaSiegman)
-
Response to Chrome team's feedback about accessibility section w3c/wpub#154 (1 comment by @mattgarrish)
-
-
7 pull requests opened.
-
clarify the agent of infoset requirements w3c/wpub#155, by @mattgarrish.
-
Added the WP address as a requirement in our WebIDL w3c/wpub#152, by @HadrienGardeur.
-
Linking issues to affordances' sections w3c/wpub#147, by @iherman.
-
Added a new information item for progression direction. w3c/wpub#142, by @iherman.
-
Lifecycle diagrams w3c/wpub#131, by @iherman.
-
Lifecycle integration w3c/wpub#130, by @HadrienGardeur.
-
Change in the language/direction infoset items w3c/wpub#129, by @iherman.
-
-
5 pull requests merged.
-
Added the WP address as a requirement in our WebIDL w3c/wpub#152.
-
Linking issues to affordances' sections w3c/wpub#147.
-
Lifecycle diagrams w3c/wpub#131.
-
Change in the language/direction infoset items w3c/wpub#129.
-
Lifecycle integration w3c/wpub#130.
-
-
1 pull request closed.
-
Review of rfc statements w3c/wpub#117.
-
-
5 pull requests received 38 new comments.
-
Lifecycle integration w3c/wpub#130 (26 comments by @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish, @rdeltour)
-
Change in the language/direction infoset items w3c/wpub#129 (5 comments by @HadrienGardeur, @iherman, @lrosenthol)
-
Added a new information item for progression direction. w3c/wpub#142 (4 comments by @dauwhe, @ghost, @iherman, @laudrain)
-
w3c/pub-manifest
-
1 issue opened.
-
Using rel="publication" w3c/pub-manifest#8, by @HadrienGardeur.
-
-
1 issue received 6 new comments.
w3c/pwpub
-
1 issue opened.
-
Review WebPackage PWP use cases w3c/pwpub#23, by @BigBlueHat.
-
-
1 issue received 1 new comment.
TR publications
-
3 documents published.
-
Packaged Web Publications published as a First Public Working Draft. History of Packaged Web Publications
-
Web Annotation Extensions for Web Publications published as a First Public Working Draft. History of Web Annotation Extensions for Web Publications
-
Web Publications published as a First Public Working Draft. History of Web Publications
-
Participants
-
1 participant joined.
-
Laura Brady (W3C Invited Experts) joined.
-
-
1 organization joined.
-
Microsoft Corporation joined.
-
-
1 organization left.
-
Vivliostyle Inc. left.
-
GitHub
w3c/wpub
-
7 issues opened.
-
Progression/direction between resources w3c/wpub#126, by @HadrienGardeur.
-
Content Integrity w3c/wpub#125, by @BigBlueHat.
-
Expressing metadata in multiple scripts/languages w3c/wpub#124, by @HadrienGardeur.
-
top level context w3c/wpub#123, by @HadrienGardeur.
-
Do we consider a (JSON) manifest to be part of a `<script>` element w3c/wpub#122, by @iherman.
-
Working out the manifest life cycle w3c/wpub#121, by @iherman.
-
Clarify relationship with WICG/IETF’s Web Package Format (WPK) w3c/wpub#120, by @js-choi.
-
-
3 issues closed.
-
manifest embedded, linked, both? w3c/wpub#25.
-
top level context w3c/wpub#123.
-
-
2 issues reopened.
-
Expressing metadata in multiple scripts/languages w3c/wpub#124, by @HadrienGardeur.
-
Experimenting with the Web App Manifest w3c/wpub#118, by @mattgarrish.
-
-
11 issues received 147 new comments.
-
Experimenting with the Web App Manifest w3c/wpub#118 (31 comments by @baldurbjarnason, @BigBlueHat, @clapierre, @HadrienGardeur, @iherman, @jce1028, @js-choi, @mattgarrish, @rdeltour)
-
Expressing metadata in multiple scripts/languages w3c/wpub#124 (28 comments by @BigBlueHat, @HadrienGardeur, @iherman, @murata2makoto, @plinss, @TzviyaSiegman)
-
Do we consider a (JSON) manifest to be part of a `<script>` element w3c/wpub#122 (26 comments by @BigBlueHat, @danbri, @dauwhe, @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish)
-
Working out the manifest life cycle w3c/wpub#121 (22 comments by @BigBlueHat, @HadrienGardeur, @iherman, @mattgarrish, @rdeltour)
-
Using the Readium Web Publication Manifest serialization w3c/wpub#119 (21 comments by @aslagle, @danielweck, @fchasen, @HadrienGardeur, @iherman, @jccr, @jce1028)
-
Web Publication affordances examination w3c/wpub#52 (6 comments by @GarthConboy, @HadrienGardeur, @iherman, @JayPanoz)
-
Clarify relationship with WICG/IETF’s Web Package Format (WPK) w3c/wpub#120 (4 comments by @js-choi, @jyasskin, @lrosenthol, @TzviyaSiegman)
-
Relationships to the Web App Manifest specification. w3c/wpub#32 (4 comments by @BigBlueHat, @HadrienGardeur, @iherman)
-
w3c/pwpub
-
1 issue received 1 new comment.
w3c/wpub-ann
-
1 issue opened.
-
RDF and JSON-LD w3c/wpub-ann#45, by @akuckartz.
-
-
1 pull request opened.
-
not useful in an abstract w3c/wpub-ann#44, by @dret.
-