Audiobooks Working Group - Activity in 2017
No matches.
Participants
-
1 participant joined.
-
David Wood (Consensys) joined.
-
-
1 organization left.
-
Ephox Corporation left.
-
GitHub
w3c/wpub
-
4 issues opened.
-
Using the Readium Web Publication Manifest serialization w3c/wpub#119, by @HadrienGardeur.
-
Experimenting with the Web App Manifest w3c/wpub#118, by @HadrienGardeur.
-
broken link in B.2 Informative References w3c/wpub#115, by @WSchindler.
-
Minor editorial issues (grammar) w3c/wpub#114, by @WSchindler.
-
-
3 issues closed.
-
Minor editorial issues (grammar) w3c/wpub#114.
-
broken link in B.2 Informative References w3c/wpub#115.
-
6 issues received 12 new comments.
-
Relationships to the Web App Manifest specification. w3c/wpub#32 (2 comments by @baldurbjarnason, @HadrienGardeur)
-
Using the Readium Web Publication Manifest serialization w3c/wpub#119 (2 comments by @GarthConboy, @llemeurfr)
-
Root of locators for identifying/retrieving content within a Web Publication w3c/wpub#44 (1 comment by @iherman)
-
4 pull requests opened.
-
Review of rfc statements w3c/wpub#117, by @mattgarrish.
-
Description of image w3c/wpub#116, by @iherman.
-
Added the diagram of Rachel, redone in google drawing w3c/wpub#113, by @iherman.
-
added simplified WP diagram w3c/wpub#112, by @RachelComerford.
-
-
2 pull requests merged.
-
Description of image w3c/wpub#116.
-
Added the diagram of Rachel, redone in google drawing w3c/wpub#113.
-
-
1 pull request closed.
-
added simplified WP diagram w3c/wpub#112.
-
-
3 pull requests received 26 new comments.
-
Description of image w3c/wpub#116 (14 comments by @avneeshsingh, @iherman, @mattgarrish, @TzviyaSiegman)
-
added simplified WP diagram w3c/wpub#112 (11 comments by @iherman, @mattgarrish, @RachelComerford, @tobie, @TzviyaSiegman)
-
w3c/wpub-ann
-
3 issues opened.
-
[Proposal] Iterate the Web Annotation Data Model itself w3c/wpub-ann#41, by @BigBlueHat.
-
"Selectors" is already normatively defined w3c/wpub-ann#40, by @therealglazou.
-
rename the document w3c/wpub-ann#38, by @TzviyaSiegman.
-
-
1 issue closed.
-
rename the document w3c/wpub-ann#38.
-
-
3 issues received 26 new comments.
-
rename the document w3c/wpub-ann#38 (14 comments by @baldurbjarnason, @BigBlueHat, @iherman, @mattgarrish, @tcole3, @TzviyaSiegman, @WSchindler)
-
[Proposal] Iterate the Web Annotation Data Model itself w3c/wpub-ann#41 (7 comments by @BigBlueHat, @iherman, @tcole3, @TzviyaSiegman)
-
"Selectors" is already normatively defined w3c/wpub-ann#40 (5 comments by @azaroth42, @BigBlueHat, @tcole3)
-
-
4 pull requests opened.
-
Add reference to issue 40 w3c/wpub-ann#43, by @tcole3.
-
ERS Frag Ids being considered for PWP Only w3c/wpub-ann#42, by @tcole3.
-
Shortened version of the document w3c/wpub-ann#39, by @iherman.
-
Fragid pre fpwd w3c/wpub-ann#37, by @iherman.
-
-
4 pull requests merged.
-
Add reference to issue 40 w3c/wpub-ann#43.
-
ERS Frag Ids being considered for PWP Only w3c/wpub-ann#42.
-
Shortened version of the document w3c/wpub-ann#39.
-
Fragid pre fpwd w3c/wpub-ann#37.
-
-
4 pull requests received 6 new comments.
w3c/pwpub
-
3 issues opened.
-
Ace cannot unzip some EPUB w3c/pwpub#18, by @laudrain.
-
Do we need a dedicated media type and file extension for PWP? w3c/pwpub#17, by @HadrienGardeur.
-
Should the PWP document refer to the full HTTP Payload? w3c/pwpub#14, by @iherman.
-
-
4 issues closed.
-
How to Define Conformance with the PWP Specification? w3c/pwpub#12.
-
Define the Term "Packaged Web Publication" w3c/pwpub#9.
-
Ace cannot unzip some EPUB w3c/pwpub#18.
-
First attempt at listing requirements w3c/pwpub#6.
-
-
7 issues received 36 new comments.
-
Do we need a dedicated media type and file extension for PWP? w3c/pwpub#17 (18 comments by @baldurbjarnason, @HadrienGardeur, @iherman, @lrosenthol, @TzviyaSiegman)
-
Should the PWP document refer to the full HTTP Payload? w3c/pwpub#14 (7 comments by @baldurbjarnason, @dauwhe, @HadrienGardeur, @iherman)
-
Define the Term "Packaged Web Publication" w3c/pwpub#9 (3 comments by @css-meeting-bot, @iherman, @prototypo)
-
-
6 pull requests opened.
-
Updated David Wood's affiliation w3c/pwpub#22, by @prototypo.
-
Dw adjust rfc2119 usage w3c/pwpub#21, by @prototypo.
-
Changes required for publication as a FPWD w3c/pwpub#20, by @prototypo.
-
Moved conformance classes from a note to prose. w3c/pwpub#19, by @prototypo.
-
Added initial requirements for PWP conformance w3c/pwpub#16, by @prototypo.
-
Added PWP definition w3c/pwpub#15, by @prototypo.
-
-
6 pull requests merged.
-
Updated David Wood's affiliation w3c/pwpub#22.
-
Dw adjust rfc2119 usage w3c/pwpub#21.
-
Changes required for publication as a FPWD w3c/pwpub#20.
-
Moved conformance classes from a note to prose. w3c/pwpub#19.
-
Added PWP definition w3c/pwpub#15.
-
Added initial requirements for PWP conformance w3c/pwpub#16.
-
-
2 pull requests received 2 new comments.
Participants
-
2 participants joined.
-
Florian Rivoal (W3C Invited Experts) joined.
-
Nellie McKesson (W3C Invited Experts) joined.
-
-
3 organizations joined.
-
Knowbly Learning Systems joined.
-
Stanford University joined.
-
Houghton Mifflin Harcourt (HMH) joined.
-
GitHub
w3c/wpub-ann
-
9 issues opened.
-
Use Cases for Span Selectors and Multi Resource Selectors (Do we need both) w3c/wpub-ann#34, by @tcole3.
-
Use Cases for Span Selector - are there any? w3c/wpub-ann#32, by @tcole3.
-
Is Embedded Resource Selector sometimes ambiguous? w3c/wpub-ann#30, by @tcole3.
-
Use cases for side bias - are there any? w3c/wpub-ann#29, by @tcole3.
-
Do we need the intermediate selectors for SpanSelector? w3c/wpub-ann#28, by @iherman.
-
Do we need to specify the 'result' of selections? w3c/wpub-ann#27, by @iherman.
-
Is a multi selector in fact a Selector? w3c/wpub-ann#26, by @iherman.
-
Do we need to redefine Range Selector? w3c/wpub-ann#25, by @iherman.
-
Is the modeling of the new Embedded Resource Selector consistent? w3c/wpub-ann#24, by @iherman.
-
-
7 issues closed.
-
Is Embedded Resource Selector sometimes ambiguous? w3c/wpub-ann#30.
-
Do we need to redefine Range Selector? w3c/wpub-ann#25.
-
Is the modeling of the new Embedded Resource Selector consistent? w3c/wpub-ann#24.
-
frag ids - whither scope w3c/wpub-ann#21.
-
Frag ids - source vs. scope w3c/wpub-ann#22.
-
Is there a need for multi-resource selectors? w3c/wpub-ann#11.
-
-
13 issues received 48 new comments.
-
Do we need to specify the 'result' of selections? w3c/wpub-ann#27 (6 comments by @BigBlueHat, @iherman, @tcole3, @tilgovi, @Treora)
-
Use cases for side bias - are there any? w3c/wpub-ann#29 (5 comments by @danielweck, @mattgarrish, @tkanai)
-
Do we need the intermediate selectors for SpanSelector? w3c/wpub-ann#28 (5 comments by @iherman, @tcole3, @Treora)
-
Is the modeling of the new Embedded Resource Selector consistent? w3c/wpub-ann#24 (4 comments by @iherman, @tcole3, @Treora)
-
Do we need scope, as well as Embedded Resource and Multiple Resource Selectors? w3c/wpub-ann#10 (3 comments by @iherman, @Treora)
-
Use cases for Position (not satisfied by Selector) - are there any? w3c/wpub-ann#9 (1 comment by @tcole3)
-
4 pull requests opened.
-
Frag Ids Only for ERS w3c/wpub-ann#36, by @tcole3.
-
Narrow Scope of Fragment Ids w3c/wpub-ann#35, by @tcole3.
-
Editorial updates w3c/wpub-ann#33, by @tcole3.
-
Separate Range Selector w3c/wpub-ann#31, by @tcole3.
-
-
4 pull requests merged.
-
Frag Ids Only for ERS w3c/wpub-ann#36.
-
Editorial updates w3c/wpub-ann#33.
-
Separate Range Selector w3c/wpub-ann#31.
-
Extend Range Selector, add Multi Selector w3c/wpub-ann#23.
-
-
2 pull requests closed.
-
Narrow Scope of Fragment Ids w3c/wpub-ann#35.
-
MRS use case w3c/wpub-ann#20.
-
-
6 pull requests received 11 new comments.
w3c/pwpub
-
5 issues opened.
-
How to Define Conformance with the PWP Specification? w3c/pwpub#12, by @prototypo.
-
What Packaging Format/Style Should a PWP Use? w3c/pwpub#11, by @prototypo.
-
What Metadata are Specific to a PWP? w3c/pwpub#10, by @prototypo.
-
Define the Term "Packaged Web Publication" w3c/pwpub#9, by @prototypo.
-
First attempt at listing requirements w3c/pwpub#6, by @HadrienGardeur.
-
-
5 issues received 71 new comments.
-
Define the Term "Packaged Web Publication" w3c/pwpub#9 (32 comments by @BillKasdorf, @GarthConboy, @HadrienGardeur, @iherman, @lrosenthol, @mattgarrish, @prototypo, @TzviyaSiegman)
-
First attempt at listing requirements w3c/pwpub#6 (31 comments by @GarthConboy, @HadrienGardeur, @iherman, @llemeurfr, @lrosenthol, @mattgarrish, @TzviyaSiegman)
-
What Packaging Format/Style Should a PWP Use? w3c/pwpub#11 (4 comments by @HadrienGardeur, @iherman, @lrosenthol)
-
How to Define Conformance with the PWP Specification? w3c/pwpub#12 (2 comments by @lrosenthol, @TzviyaSiegman)
-
-
3 pull requests opened.
-
Dw-addSectionStructure w3c/pwpub#13, by @prototypo.
-
Added a draft PWP definition with a note for Issue #111. w3c/pwpub#8, by @prototypo.
-
Added David Wood (@prototypo) as editor. w3c/pwpub#7, by @prototypo.
-
-
3 pull requests merged.
-
Dw-addSectionStructure w3c/pwpub#13.
-
Added David Wood (@prototypo) as editor. w3c/pwpub#7.
-
-
1 pull request closed.
-
Modification of the abstract for a PR preview test. w3c/pwpub#4.
-
-
2 pull requests received 3 new comments.
w3c/wpub
-
8 issues opened.
-
Define the Term "Packaged Web Publication" w3c/wpub#111, by @prototypo.
-
Requirement for an HTML document w3c/wpub#108, by @mattgarrish.
-
What is the Browsing Context of a Web Publication? w3c/wpub#104, by @BigBlueHat.
-
Role of the HTML document returned by the WPUB URL w3c/wpub#103, by @HadrienGardeur.
-
What does a WPub URL resolve to? w3c/wpub#94, by @prototypo.
-
Security: Should WP restrict types of content? w3c/wpub#91, by @lrosenthol.
-
Security: Can a WP contain JavaScript? w3c/wpub#90, by @lrosenthol.
-
-
7 issues closed.
-
Requirement for an HTML document w3c/wpub#108.
-
Define the Term "Packaged Web Publication" w3c/wpub#111.
-
What does a WPub URL resolve to? w3c/wpub#94.
-
Security: Should WP restrict types of content? w3c/wpub#91.
-
Security: Can a WP contain JavaScript? w3c/wpub#90.
-
Allow links to multiple publications? w3c/wpub#76.
-
-
11 issues received 203 new comments.
-
What does a WPub URL resolve to? w3c/wpub#94 (92 comments by @azaroth42, @baldurbjarnason, @bduga, @BigBlueHat, @dauwhe, @GarthConboy, @HadrienGardeur, @iherman, @laudrain, @llemeurfr, @mattgarrish, @prototypo, @rdeltour, @TzviyaSiegman, @WSchindler)
-
Role of the HTML document returned by the WPUB URL w3c/wpub#103 (72 comments by @baldurbjarnason, @BigBlueHat, @dauwhe, @GarthConboy, @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish, @pkra, @tcole3, @TzviyaSiegman, @WSchindler)
-
What is the Browsing Context of a Web Publication? w3c/wpub#104 (13 comments by @BigBlueHat, @iherman, @laudrain, @lrosenthol, @mattgarrish, @pkra)
-
"the infoset should not include specialised metadata" ??? w3c/wpub#74 (3 comments by @baldurbjarnason, @HadrienGardeur, @iherman)
-
Privacy: Should WP restrict and/or gate access to some OWP features? w3c/wpub#92 (2 comments by @caraya, @lrosenthol)
-
-
16 pull requests opened.
-
Shift address requirements and add HTML requirement w3c/wpub#110, by @mattgarrish.
-
Add manifest example to spec, and add sample document to repo w3c/wpub#109, by @dauwhe.
-
expand on resource list definition w3c/wpub#107, by @mattgarrish.
-
updates per comments in issue #103 w3c/wpub#105, by @mattgarrish.
-
Minor editorial change in an editorial note w3c/wpub#102, by @iherman.
-
update landing page to match issue discussion in #94 w3c/wpub#101, by @mattgarrish.
-
various editorial and structural changes w3c/wpub#100, by @mattgarrish.
-
add construction section w3c/wpub#99, by @mattgarrish.
-
Added a paragraph on the landing page in the lifecycle section w3c/wpub#98, by @iherman.
-
add relationship to wam section w3c/wpub#96, by @mattgarrish.
-
add link to privacy policy as an infoset item w3c/wpub#95, by @mattgarrish.
-
Suggested an editors note in Section 4.5 w3c/wpub#93, by @prototypo.
-
Added link to code of conduct w3c/wpub#88, by @TzviyaSiegman.
-
-
15 pull requests merged.
-
Shift address requirements and add HTML requirement w3c/wpub#110.
-
expand on resource list definition w3c/wpub#107.
-
updates per comments in issue #103 w3c/wpub#105.
-
Minor editorial change in an editorial note w3c/wpub#102.
-
update landing page to match issue discussion in #94 w3c/wpub#101.
-
various editorial and structural changes w3c/wpub#100.
-
add construction section w3c/wpub#99.
-
Suggested an editors note in Section 4.5 w3c/wpub#93.
-
add link to privacy policy as an infoset item w3c/wpub#95.
-
add relationship to wam section w3c/wpub#96.
-
Added link to code of conduct w3c/wpub#88.
-
-
14 pull requests received 73 new comments.
-
update landing page to match issue discussion in #94 w3c/wpub#101 (18 comments by @BigBlueHat, @GarthConboy, @HadrienGardeur, @iherman, @mattgarrish)
-
Added a paragraph on the landing page in the lifecycle section w3c/wpub#98 (15 comments by @BigBlueHat, @dauwhe, @HadrienGardeur, @iherman, @lrosenthol, @mattgarrish)
-
Suggested an editors note in Section 4.5 w3c/wpub#93 (14 comments by @dauwhe, @iherman, @lrosenthol, @mattgarrish, @prototypo)
-
add link to privacy policy as an infoset item w3c/wpub#95 (4 comments by @iherman, @lrosenthol, @mattgarrish)
-
clarify in scope the intent to facilitate different UA models w3c/wpub#97 (4 comments by @dauwhe, @iherman, @lrosenthol, @mattgarrish)
-
elaborate on usefulness of locators and note potential json limitations w3c/wpub#106 (3 comments by @iherman, @mattgarrish, @tcole3)
-
Add manifest example to spec, and add sample document to repo w3c/wpub#109 (2 comments by @iherman, @lrosenthol)
-
changes to linking to manifest section based on tpac discussions w3c/wpub#89 (1 comment by @iherman)
-
Participants
-
2 organizations joined.
-
Sony Group Corporation joined.
-
Cenveo Publisher Services joined.
-
GitHub
w3c/wpub-ann
-
14 issues opened.
-
Frag ids - source vs. scope w3c/wpub-ann#22, by @tcole3.
-
frag ids - whither scope w3c/wpub-ann#21, by @tcole3.
-
Relationship to Web Annotations w3c/wpub-ann#18, by @TzviyaSiegman.
-
opened in wrong space - ignore w3c/wpub-ann#16, by @RachelComerford.
-
Use case for a component appearing in multiple locations? w3c/wpub-ann#12, by @iherman.
-
Is there a need for multi-resource selectors? w3c/wpub-ann#11, by @iherman.
-
Do we need scope, as well as Embedded Resource and Multiple Resource Selectors? w3c/wpub-ann#10, by @iherman.
-
Use cases for Position (not satisfied by Selector) - are there any? w3c/wpub-ann#9, by @tcole3.
-
(Editorial) Simplifying the model tables w3c/wpub-ann#7, by @iherman.
-
Do we need fragment ids? w3c/wpub-ann#6, by @iherman.
-
Changing the name of the "Specific Resource" to something simpler? w3c/wpub-ann#3, by @iherman.
-
Is there a need for a multi-source span selector for WP-s? w3c/wpub-ann#2, by @iherman.
-
Semantics for range selections for WPUB w3c/wpub-ann#1, by @iherman.
-
-
7 issues closed.
-
Relationship to Web Annotations w3c/wpub-ann#18.
-
opened in wrong space - ignore w3c/wpub-ann#16.
-
(Editorial) Simplifying the model tables w3c/wpub-ann#7.
-
Is there a need for a multi-source span selector for WP-s? w3c/wpub-ann#2.
-
Semantics for range selections for WPUB w3c/wpub-ann#1.
-
-
1 issue reopened.
-
Do we need scope, as well as Embedded Resource and Multiple Resource Selectors? w3c/wpub-ann#10, by @iherman.
-
-
13 issues received 66 new comments.
-
Do we need scope, as well as Embedded Resource and Multiple Resource Selectors? w3c/wpub-ann#10 (16 comments by @BigBlueHat, @iherman, @RachelComerford, @tcole3)
-
Changing the name of the "Specific Resource" to something simpler? w3c/wpub-ann#3 (10 comments by @azaroth42, @iherman, @tcole3)
-
The use case of WP requires a small extension of the WA model: "source" for Selectors. w3c/wpub-ann#4 (9 comments by @azaroth42, @iherman)
-
Use case for a component appearing in multiple locations? w3c/wpub-ann#12 (8 comments by @iherman, @RachelComerford, @tcole3)
-
Use cases for Position (not satisfied by Selector) - are there any? w3c/wpub-ann#9 (8 comments by @BigBlueHat, @iherman, @tcole3)
-
Is there a need for multi-resource selectors? w3c/wpub-ann#11 (4 comments by @iherman, @RachelComerford)
-
-
9 pull requests opened.
-
Extend Range Selector, add Multi Selector w3c/wpub-ann#23, by @iherman.
-
MRS use case w3c/wpub-ann#20, by @iherman.
-
Reference to anno plus improvements w3c/wpub-ann#19, by @iherman.
-
Add Position Specifiers w3c/wpub-ann#17, by @tcole3.
-
Extend TextPositionSelector and DataPositionSelector w3c/wpub-ann#15, by @tcole3.
-
Minor patches w3c/wpub-ann#14, by @iherman.
-
Editorial Changes w3c/wpub-ann#13, by @iherman.
-
Wa extensions w3c/wpub-ann#8, by @iherman.
-
Some improvements... w3c/wpub-ann#5, by @iherman.
-
-
5 pull requests merged.
-
Reference to anno plus improvements w3c/wpub-ann#19.
-
Add Position Specifiers w3c/wpub-ann#17.
-
Minor patches w3c/wpub-ann#14.
-
Editorial Changes w3c/wpub-ann#13.
-
Wa extensions w3c/wpub-ann#8.
-
-
2 pull requests closed.
-
Extend TextPositionSelector and DataPositionSelector w3c/wpub-ann#15.
-
Some improvements... w3c/wpub-ann#5.
-
-
8 pull requests received 35 new comments.
-
Extend TextPositionSelector and DataPositionSelector w3c/wpub-ann#15 (6 comments by @azaroth42, @iherman, @tcole3)
w3c/wpub
-
5 issues opened.
-
Accessibility requirements for navigation w3c/wpub#86, by @avneeshsingh.
-
Minor editorial glitch w3c/wpub#82, by @WSchindler.
-
Audiobooks and WPUB w3c/wpub#78, by @llemeurfr.
-
Publication memory w3c/wpub#77, by @mattgarrish.
-
Allow links to multiple publications? w3c/wpub#76, by @mattgarrish.
-
-
2 issues closed.
-
Minor editorial glitch w3c/wpub#82.
-
Publication memory w3c/wpub#77.
-
-
9 issues received 43 new comments.
-
"the infoset should not include specialised metadata" ??? w3c/wpub#74 (16 comments by @baldurbjarnason, @BillKasdorf, @dauwhe, @eshellman, @iherman, @mattgarrish)
-
Publication memory w3c/wpub#77 (11 comments by @baldurbjarnason, @dauwhe, @iherman, @lrosenthol, @mattgarrish)
-
-
7 pull requests opened.
-
Navigation w3c/wpub#87, by @mattgarrish.
-
Layout and Pagination (edit to #65) w3c/wpub#85, by @dauwhe.
-
Replace lifecycle section with an editor note w3c/wpub#84, by @mattgarrish.
-
Changes to infoset and extensibility w3c/wpub#83, by @mattgarrish.
-
media type registration for manifest file w3c/wpub#81, by @mattgarrish.
-
expanded intro w3c/wpub#80, by @mattgarrish.
-
Manifest linking w3c/wpub#79, by @mattgarrish.
-
-
7 pull requests merged.
-
Navigation w3c/wpub#87.
-
Layout and Pagination (edit to #65) w3c/wpub#85.
-
First Draft of an Internal Locators Section w3c/wpub#75.
-
Replace lifecycle section with an editor note w3c/wpub#84.
-
Changes to infoset and extensibility w3c/wpub#83.
-
Manifest linking w3c/wpub#79.
-
expanded intro w3c/wpub#80.
-
-
2 pull requests closed.
-
Layout and pagination w3c/wpub#65.
-
Add sections on navigation and manifest processing w3c/wpub#71.
-
-
9 pull requests received 70 new comments.
-
Changes to infoset and extensibility w3c/wpub#83 (21 comments by @baldurbjarnason, @dauwhe, @eshellman, @iherman, @laudrain, @mattgarrish, @RachelComerford, @tcole3)
-
Layout and Pagination (edit to #65) w3c/wpub#85 (13 comments by @baldurbjarnason, @dauwhe, @frivoal, @iherman, @TzviyaSiegman)
-
GitHub
w3c/wpub
-
11 issues opened.
-
"the infoset should not include specialised metadata" ??? w3c/wpub#74, by @eshellman.
-
What does modification date mean? w3c/wpub#73, by @lrosenthol.
-
MathML and WPUB w3c/wpub#72, by @rkwright.
-
Relationship to the Web Animation work. w3c/wpub#70, by @iherman.
-
Naming the media overlay work w3c/wpub#69, by @iherman.
-
Should linking from manifests support URI templates? w3c/wpub#67, by @iherman.
-
Replace the "infoset" term? w3c/wpub#63, by @rdeltour.
-
better explain lack of exhaustive resource list w3c/wpub#60, by @mattgarrish.
-
avoiding resource declaration duplication w3c/wpub#59, by @mattgarrish.
-
is a canonical identifier necessary w3c/wpub#58, by @mattgarrish.
-
-
4 issues closed.
-
What makes primary resources "primary" w3c/wpub#55.
-
better explain lack of exhaustive resource list w3c/wpub#60.
-
14 issues received 66 new comments.
-
What makes primary resources "primary" w3c/wpub#55 (16 comments by @BigBlueHat, @BillKasdorf, @danielweck, @dauwhe, @HadrienGardeur, @llemeurfr, @lrosenthol, @mattgarrish, @TzviyaSiegman, @WSchindler)
-
Root of locators for identifying/retrieving content within a Web Publication w3c/wpub#44 (15 comments by @azaroth42, @BillKasdorf, @dauwhe, @iherman, @llemeurfr, @mattgarrish, @murata2makoto, @tcole3)
-
Should some additional metadata items move to core infoset requirements w3c/wpub#66 (12 comments by @baldurbjarnason, @BigBlueHat, @css-meeting-bot, @iherman, @laudrain, @TzviyaSiegman)
-
"the infoset should not include specialised metadata" ??? w3c/wpub#74 (2 comments by @baldurbjarnason, @GarthConboy)
-
MUST the manifest include information about secondary resources or not? w3c/wpub#23 (1 comment by @stain)
-
-
8 pull requests opened.
-
First Draft of an Internal Locators Section w3c/wpub#75, by @tcole3.
-
Add sections on navigation and manifest processing w3c/wpub#71, by @dauwhe.
-
Layout and pagination w3c/wpub#65, by @frivoal.
-
First pass at integrating the metadata proposal w3c/wpub#64, by @baldurbjarnason.
-
Remove extra "a" in definition of identifier w3c/wpub#61, by @dauwhe.
-
genericize resource naming w3c/wpub#57, by @mattgarrish.
-
-
5 pull requests merged.
-
First pass at integrating the metadata proposal w3c/wpub#64.
-
Remove extra "a" in definition of identifier w3c/wpub#61.
-
genericize resource naming w3c/wpub#57.
-
6 pull requests received 37 new comments.
-
Layout and pagination w3c/wpub#65 (10 comments by @dauwhe, @frivoal, @iherman, @murata2makoto, @TzviyaSiegman)
-
First pass at integrating the metadata proposal w3c/wpub#64 (9 comments by @baldurbjarnason, @HadrienGardeur, @iherman, @mattgarrish)
-
Add sections on navigation and manifest processing w3c/wpub#71 (7 comments by @baldurbjarnason, @BillKasdorf, @dauwhe, @mattgarrish, @RachelComerford)
-
rewrite abstract to be both narrower in scope and more descriptive w3c/wpub#62 (7 comments by @dauwhe, @iherman, @mattgarrish, @RachelComerford, @rdeltour)
-
Extracted some issues from the metadata text and made it explicit. w3c/wpub#68 (2 comments by @iherman, @mattgarrish)
-
Participants
-
5 organizations joined.
-
Penguin Random House joined.
-
Ascend Learning joined.
-
Rakuten Group, Inc. joined.
-
Feedbooks joined.
-
Ephox Corporation joined.
-
GitHub
w3c/wpub
-
29 issues opened.
-
The canonical-ness of identification needs clarification w3c/wpub#56, by @BigBlueHat.
-
What makes primary resources "primary" w3c/wpub#55, by @mattgarrish.
-
Obtaining language from http headers w3c/wpub#54, by @mattgarrish.
-
Web Publication affordances examination w3c/wpub#52, by @BigBlueHat.
-
separate implicit information from failure handling w3c/wpub#48, by @mattgarrish.
-
Default natural language w3c/wpub#45, by @murata2makoto.
-
Picking a language w3c/wpub#42, by @mattgarrish.
-
Define relationship with WCAG w3c/wpub#40, by @TzviyaSiegman.
-
Is the ToC sufficient to provide reading order? w3c/wpub#36, by @BigBlueHat.
-
Relationships to the Web App Manifest specification. w3c/wpub#32, by @iherman.
-
Do we need definitions for identifier and locator? w3c/wpub#27, by @tcole3.
-
Should the manifest be an implicit TOC? w3c/wpub#26, by @TzviyaSiegman.
-
manifest embedded, linked, both? w3c/wpub#25, by @TzviyaSiegman.
-
Requirements for a WP title w3c/wpub#24, by @deborahgu.
-
manifest: requirements for offline w3c/wpub#22, by @TzviyaSiegman.
-
manifest: metadata w3c/wpub#21, by @TzviyaSiegman.
-
manifest: title w3c/wpub#20, by @TzviyaSiegman.
-
First-class citizenship of resources in PWPs w3c/wpub#19, by @murata2makoto.
-
WP-dependent URIs of resources w3c/wpub#18, by @murata2makoto.
-
non-linear resources - primary, secondary or something else? w3c/wpub#16, by @mattgarrish.
-
Minimum Viable Manifest w3c/wpub#15, by @TzviyaSiegman.
-
-
19 issues closed.
-
manifest format w3c/wpub#7.
-
Picking a language w3c/wpub#42.
-
Is the ToC sufficient to provide reading order? w3c/wpub#36.
-
Should the manifest be an implicit TOC? w3c/wpub#26.
-
Requirements for a WP title w3c/wpub#24.
-
manifest: title w3c/wpub#20.
-
WP-dependent URIs of resources w3c/wpub#18.
-
Minimum Viable Manifest w3c/wpub#15.
-
separate implicit information from failure handling w3c/wpub#48.
-
previous and next via link relations w3c/wpub#14.
-
The URI, URL, and URN of a web publication w3c/wpub#11.
-
Default natural language w3c/wpub#45.
-
Do we need definitions for identifier and locator? w3c/wpub#27.
-
First-class citizenship of resources in PWPs w3c/wpub#19.
-
Information content of the abstract manifest w3c/wpub#6.
-
36 issues received 510 new comments.
-
Minimum Viable Manifest w3c/wpub#15 (78 comments by @avneeshsingh, @baldurbjarnason, @bduga, @BigBlueHat, @BillKasdorf, @dauwhe, @deborahgu, @HadrienGardeur, @iherman, @laudrain, @lrosenthol, @mattgarrish, @murata2makoto, @pkra, @rdeltour, @TzviyaSiegman)
-
The canonical-ness of identification needs clarification w3c/wpub#56 (41 comments by @baldurbjarnason, @BigBlueHat, @dauwhe, @iherman, @mattgarrish, @rdeltour, @tcole3, @WSchindler)
-
MUST the manifest include information about secondary resources or not? w3c/wpub#23 (41 comments by @baldurbjarnason, @BigBlueHat, @dauwhe, @GarthConboy, @HadrienGardeur, @iherman, @lrosenthol, @mattgarrish, @pkra)
-
non-linear resources - primary, secondary or something else? w3c/wpub#16 (39 comments by @BigBlueHat, @clapierre, @danielweck, @dauwhe, @HadrienGardeur, @llemeurfr, @lrosenthol, @mattgarrish, @pkra, @RachelComerford, @TzviyaSiegman, @WSchindler)
-
manifest: title w3c/wpub#20 (34 comments by @baldurbjarnason, @BigBlueHat, @deborahgu, @iherman, @lrosenthol, @mattgarrish, @pkra, @TzviyaSiegman)
-
Proposal: an HTML-first Table of Contents approach to Web Publication w3c/wpub#35 (31 comments by @baldurbjarnason, @BigBlueHat, @dauwhe, @GarthConboy, @HadrienGardeur, @iherman, @JayPanoz, @laudrain, @llemeurfr, @lrosenthol, @rdeltour, @tcole3, @TzviyaSiegman)
-
manifest: requirements for offline w3c/wpub#22 (30 comments by @baldurbjarnason, @bduga, @BigBlueHat, @iherman, @laudrain, @lrosenthol, @mattgarrish, @rickj, @TzviyaSiegman)
-
Requirements for a WP title w3c/wpub#24 (24 comments by @baldurbjarnason, @BillKasdorf, @danielweck, @dauwhe, @GarthConboy, @iherman, @lrosenthol, @mattgarrish, @rdeltour, @TzviyaSiegman)
-
Do all documents in the reading order have to be reachable from the ToC w3c/wpub#39 (24 comments by @avneeshsingh, @baldurbjarnason, @BigBlueHat, @clapierre, @danielweck, @HadrienGardeur, @iherman, @laudrain, @lrosenthol, @mattgarrish, @rdeltour)
-
WP-dependent URIs of resources w3c/wpub#18 (23 comments by @HadrienGardeur, @iherman, @lrosenthol, @mattgarrish, @murata2makoto, @TzviyaSiegman)
-
Is the ToC sufficient to provide reading order? w3c/wpub#36 (20 comments by @avneeshsingh, @baldurbjarnason, @BigBlueHat, @HadrienGardeur, @iherman, @mattgarrish, @rdeltour, @TzviyaSiegman)
-
separate implicit information from failure handling w3c/wpub#48 (18 comments by @BigBlueHat, @iherman, @lrosenthol, @mattgarrish)
-
For manifest in FPWD: Should Natural Language be Required per WCAG 2 w3c/wpub#29 (12 comments by @avneeshsingh, @iherman, @laudrain, @lrosenthol, @mattgarrish)
-
Should the manifest be an implicit TOC? w3c/wpub#26 (11 comments by @baldurbjarnason, @BigBlueHat, @dauwhe, @GarthConboy, @iherman, @lrosenthol, @mattgarrish, @pkra, @TzviyaSiegman)
-
Web Publication affordances examination w3c/wpub#52 (10 comments by @BigBlueHat, @dauwhe, @iherman, @llemeurfr, @lrosenthol)
-
Relationships to the Web App Manifest specification. w3c/wpub#32 (9 comments by @BigBlueHat, @HadrienGardeur, @iherman, @llemeurfr, @rdeltour)
-
Picking a language w3c/wpub#42 (8 comments by @BigBlueHat, @HadrienGardeur, @iherman, @lrosenthol, @mattgarrish)
-
Do we need definitions for identifier and locator? w3c/wpub#27 (7 comments by @iherman, @mattgarrish, @rdeltour, @tcole3)
-
What makes primary resources "primary" w3c/wpub#55 (6 comments by @BigBlueHat, @HadrienGardeur, @mattgarrish)
-
For manifest in FPWD: Should manifest TITLE be Required per WCAG 2? w3c/wpub#30 (5 comments by @avneeshsingh, @iherman, @lrosenthol, @TzviyaSiegman)
-
manifest embedded, linked, both? w3c/wpub#25 (5 comments by @iherman, @lrosenthol, @mattgarrish, @rdeltour)
-
Is WP enhanced web content or a special implementation of the web? w3c/wpub#12 (2 comments by @iherman, @TzviyaSiegman)
-
Root of locators for identifying/retrieving content within a Web Publication w3c/wpub#44 (2 comments by @laudrain, @tcole3)
-
What does "Reading Order" mean in the context of a Web Publication? w3c/wpub#38 (2 comments by @baldurbjarnason, @GarthConboy)
-
-
13 pull requests opened.
-
rewording of title and language w3c/wpub#49, by @mattgarrish.
-
Retrieving a TOC from HTML files w3c/wpub#47, by @iherman.
-
default reading order fallbacks via TOC w3c/wpub#46, by @iherman.
-
Run ReSpec sync instead w3c/wpub#41, by @marcoscaceres.
-
Modification of the manifest abstract model (proposal) w3c/wpub#37, by @llemeurfr.
-
minor typo corrections w3c/wpub#34, by @llemeurfr.
-
Consolidation of the draft w3c/wpub#33, by @iherman.
-
Normalize URL references w3c/wpub#31, by @rdeltour.
-
update identifier, address, canonical definitions w3c/wpub#28, by @tcole3.
-
Identifiers and locators - 1st draft (partial) w3c/wpub#17, by @tcole3.
-
7 pull requests merged.
-
Run ReSpec sync instead w3c/wpub#41.
-
Consolidation of the draft w3c/wpub#33.
-
minor typo corrections w3c/wpub#34.
-
update identifier, address, canonical definitions w3c/wpub#28.
-
Identifiers and locators - 1st draft (partial) w3c/wpub#17.
-
6 pull requests closed.
-
default reading order fallbacks via TOC w3c/wpub#46.
-
Retrieving a TOC from HTML files w3c/wpub#47.
-
rewording of title and language w3c/wpub#49.
-
Normalize URL references w3c/wpub#31.
-
13 pull requests received 131 new comments.
-
default reading order fallbacks via TOC w3c/wpub#46 (45 comments by @arhomberg, @BigBlueHat, @BillKasdorf, @GarthConboy, @HadrienGardeur, @iherman, @JayPanoz, @llemeurfr, @mattgarrish, @TzviyaSiegman)
-
cleanup of infoset requirements and fallbacks for title, language, toc and default reading order w3c/wpub#51 (28 comments by @BigBlueHat, @HadrienGardeur, @iherman, @llemeurfr, @mattgarrish)
-
Retrieving a TOC from HTML files w3c/wpub#47 (19 comments by @BigBlueHat, @GarthConboy, @HadrienGardeur, @iherman, @mattgarrish, @TzviyaSiegman)
-
update to replace "abstract manifest" with infoset plus various cleanup w3c/wpub#43 (6 comments by @iherman, @llemeurfr, @mattgarrish)
-
Modification of the manifest abstract model (proposal) w3c/wpub#37 (5 comments by @iherman, @llemeurfr, @mattgarrish)
-
Identifiers and locators - 1st draft (partial) w3c/wpub#17 (4 comments by @BigBlueHat, @iherman, @tcole3)
-
cleanup of infoset requirements and fallbacks for title, language, toc and default reading order w3c/wpub#50 (1 comment by @mattgarrish)
-
w3c/pwpub
-
1 issue opened.
-
First-class citizenship of resources in PWPs w3c/pwpub#5, by @murata2makoto.
-
-
1 issue received 2 new comments.
-
First-class citizenship of resources in PWPs w3c/pwpub#5 (2 comments by @lrosenthol, @murata2makoto)
-
-
4 pull requests opened.
-
Modification of the abstract for a PR preview test. w3c/pwpub#4, by @iherman.
-
Add async attribute w3c/pwpub#3, by @tobie.
-
A new test to see if pr-preview works now w3c/pwpub#2, by @iherman.
-
Minor test to see whether the pr-preview mechanism works w3c/pwpub#1, by @iherman.
-
-
2 pull requests merged.
-
A new test to see if pr-preview works now w3c/pwpub#2.
-
-
1 pull request closed.
-
Add async attribute w3c/pwpub#3.
-
-
1 pull request received 1 new comment.
Participants
-
2 participants joined.
-
Deborah Kaplan (W3C Invited Experts) joined.
-
Ivan Herman (W3C) joined.
-
-
4 organizations joined.
-
J. Paul Getty Trust joined.
-
Knowbility joined.
-
Google LLC joined.
-
Wiley joined.
-
GitHub
w3c/wpub
-
13 issues opened.
-
previous and next via link relations w3c/wpub#14, by @dauwhe.
-
Associating a manifest with publication resources w3c/wpub#13, by @dauwhe.
-
The URI, URL, and URN of a web publication w3c/wpub#11, by @dauwhe.
-
Multiple-origin web publications w3c/wpub#10, by @dauwhe.
-
Machine-Readable navigation w3c/wpub#9, by @lrosenthol.
-
Remixing Content w3c/wpub#8, by @lrosenthol.
-
manifest format w3c/wpub#7, by @mattgarrish.
-
Information content of the abstract manifest w3c/wpub#6, by @dauwhe.
-
How do we identify a web publication and its components? w3c/wpub#5, by @dauwhe.
-
Who is responsible for a publication's user interface? w3c/wpub#4, by @dauwhe.
-
Document Collection Interface w3c/wpub#3, by @dauwhe.
-
Navigating a web publication w3c/wpub#2, by @dauwhe.
-
-
13 issues received 413 new comments.
-
Information content of the abstract manifest w3c/wpub#6 (104 comments by @dauwhe, @GarthConboy, @hadrien, @HadrienGardeur, @laudrain, @lrosenthol, @mattgarrish, @pkra, @TzviyaSiegman)
-
How do we identify a web publication and its components? w3c/wpub#5 (92 comments by @baldurbjarnason, @dauwhe, @frivoal, @GarthConboy, @HadrienGardeur, @llemeurfr, @lrosenthol, @mattgarrish, @murata2makoto, @TzviyaSiegman)
-
Machine-Readable navigation w3c/wpub#9 (65 comments by @avneeshsingh, @dauwhe, @GarthConboy, @HadrienGardeur, @JayPanoz, @laudrain, @llemeurfr, @lrosenthol, @mattgarrish, @rdeltour, @TzviyaSiegman)
-
The URI, URL, and URN of a web publication w3c/wpub#11 (44 comments by @bduga, @BigBlueHat, @dauwhe, @frivoal, @GarthConboy, @HadrienGardeur, @llemeurfr, @lrosenthol, @murata2makoto, @rdeltour, @TzviyaSiegman)
-
Who is responsible for a publication's user interface? w3c/wpub#4 (19 comments by @acabal, @dauwhe, @JayPanoz)
-
Navigating a web publication w3c/wpub#2 (17 comments by @avneeshsingh, @dauwhe, @GarthConboy, @HadrienGardeur)
-
Remixing Content w3c/wpub#8 (16 comments by @dauwhe, @HadrienGardeur, @JayPanoz, @llemeurfr, @lrosenthol)
-
Is WP enhanced web content or a special implementation of the web? w3c/wpub#12 (16 comments by @danielweck, @dauwhe, @HadrienGardeur, @laudrain, @lrosenthol, @mattgarrish, @rdeltour, @WSchindler)
-
manifest format w3c/wpub#7 (14 comments by @BigBlueHat, @dauwhe, @HadrienGardeur, @lrosenthol, @mattgarrish)
-
i18n of metadata values, in case JSON is chosen as a serialization format w3c/wpub#1 (13 comments by @danielweck, @HadrienGardeur, @llemeurfr, @lrosenthol, @murata2makoto)
-
Associating a manifest with publication resources w3c/wpub#13 (7 comments by @dauwhe, @GarthConboy, @HadrienGardeur, @lrosenthol, @murata2makoto)
-
Multiple-origin web publications w3c/wpub#10 (4 comments by @HadrienGardeur, @lrosenthol, @murata2makoto)
-
Lifecycle
-
1 charter started.
-
Chartered until 1 July 2020. Participants had to rejoin under this charter.
-
Participants
-
4 participants joined.
-
Fred Chasen (W3C Invited Experts) joined.
-
Peter Krautzberger (W3C Invited Experts) joined.
-
Heather Flanagan (W3C Invited Experts) joined.
-
Bill McCoy (W3C) joined.
-
-
1 participant left.
-
Ivan Herman (W3C) left.
-
-
25 organizations joined.
-
Macmillan Learning joined.
-
Kodansha, Publishers, Ltd. joined.
-
Pearson plc joined.
-
Vivliostyle Inc. joined.
-
Fondazione LIA joined.
-
Monotype joined.
-
HarperCollins Publishers joined.
-
Kaplan Publishing joined.
-
Adobe joined.
-
PONS GmbH joined.
-
University of Michigan joined.
-
Voyager Japan, Inc. joined.
-
W. W. Norton & Company joined.
-
NIC.br - Brazilian Network Information Center joined.
-
University of Illinois joined.
-
Hachette Livre joined.
-
EDRLab joined.
-
The Rebus Foundation joined.
-
Evident Point Software joined.
-
DAISY Consortium joined.
-
Book Industry Study Group joined.
-
Datalogics, Inc. joined.
-
Educational Testing Service joined.
-
Benetech joined.
-
VitalSource | Ingram Content Group joined.
-
-
2 organizations left.
-
Wiley left.
-
Google LLC left.
-
GitHub
w3c/wpub
-
1 issue opened.
-
1 issue received 3 new comments.
-
i18n of metadata values, in case JSON is chosen as a serialization format w3c/wpub#1 (3 comments by @llemeurfr, @lrosenthol)
-