Web Annotation Working Group - Activity in 2016
No matches.
GitHub
w3c/web-annotation
-
2 issues opened.
-
Annotation Collections: different IRIs for embedded IRIs and embedded descriptions. w3c/web-annotation#388, by @gsergiu.
-
Bring back Composites, Independents, and List w3c/web-annotation#387, by @BigBlueHat.
-
-
2 issues closed.
-
If-Match not used in PUT protocol test w3c/web-annotation#386.
-
Ontologies use non-existant owl:previousVersionURI w3c/web-annotation#381.
-
-
3 issues received 6 new comments.
-
Annotation Collections: different IRIs for embedded IRIs and embedded descriptions. w3c/web-annotation#388 (2 comments by @gsergiu, @iherman)
-
Client can't determine if user has authorization to modify annotation w3c/web-annotation#19 (1 comment by @gsergiu)
-
3 pull requests opened.
-
Raw edits for comparison w3c/web-annotation#391, by @azaroth42.
-
Updates for PR w3c/web-annotation#390, by @azaroth42.
-
Updated the PR Transition request w3c/web-annotation#389, by @iherman.
-
-
2 pull requests merged.
-
Updated the PR Transition request w3c/web-annotation#389.
-
Handling #381 w3c/web-annotation#385.
-
-
1 pull request closed.
-
Updates for PR w3c/web-annotation#390.
-
-
2 pull requests received 8 new comments.
TR publications
-
2 documents published.
-
Web Annotation Data Model published as a Candidate Recommendation Snapshot. History of Web Annotation Data Model
-
Web Annotation Vocabulary published as a Candidate Recommendation Snapshot. History of Web Annotation Vocabulary
-
Participants
-
1 participant joined.
-
Randall Leeds (W3C Invited Experts) joined.
-
-
1 participant left.
-
Randall Leeds (W3C Invited Experts) left.
-
GitHub
w3c/web-annotation
-
7 issues opened.
-
If-Match not used in PUT protocol test w3c/web-annotation#386, by @azaroth42.
-
Reference RDF 1.1 Concepts instead of the old version w3c/web-annotation#382, by @lanthaler.
-
Ontologies use non-existant owl:previousVersionURI w3c/web-annotation#381, by @gkellogg.
-
Collection vs Annotation Page w3c/web-annotation#376, by @iherman.
-
Activity vocab (FOAF v vCard Ontology) w3c/web-annotation#375, by @riannella.
-
Web resources SHOULD be dereferencable via their IRI w3c/web-annotation#372, by @gsergiu.
-
Next, Prev, First, Last in AnnotationCollection/AnnotationPage w3c/web-annotation#371, by @gsergiu.
-
-
16 issues closed.
-
Remove un-implemented List, Composite, Independents w3c/web-annotation#369.
-
Reference RDF 1.1 Concepts instead of the old version w3c/web-annotation#382.
-
Try to register profile with IETF w3c/web-annotation#324.
-
External: Reflect Protocol in Social Web Protocols document w3c/web-annotation#118.
-
Create SVG versions of diagrams w3c/web-annotation#286.
-
Collection vs Annotation Page w3c/web-annotation#376.
-
JSON-LD Frames should be dereferenceable ... where? w3c/web-annotation#251.
-
Web resources SHOULD be dereferencable via their IRI w3c/web-annotation#372.
-
JSON-LD aliases in Vocabulary content w3c/web-annotation#320.
-
Clarify distinction between OPTIONS and GET/HEAD w3c/web-annotation#367.
-
ldp:PreferMinimalContainer and oa:PreferContainedIRIs interaction is confusing w3c/web-annotation#366.
-
Protocol example 11 should not include Vary: Prefer w3c/web-annotation#365.
-
Clarification on the usage of rights in the example use case w3c/web-annotation#360.
-
ed sugg: textDirection w3c/web-annotation#348.
-
Add info about which Media Type to Model w3c/web-annotation#346.
-
processLanguage description improvement suggestion w3c/web-annotation#345.
-
-
17 issues received 78 new comments.
-
Web resources SHOULD be dereferencable via their IRI w3c/web-annotation#372 (30 comments by @akuckartz, @azaroth42, @BigBlueHat, @gsergiu, @iherman)
-
Try to register profile with IETF w3c/web-annotation#324 (13 comments by @akuckartz, @azaroth42, @BigBlueHat, @iherman)
-
Next, Prev, First, Last in AnnotationCollection/AnnotationPage w3c/web-annotation#371 (12 comments by @azaroth42, @BigBlueHat, @gsergiu, @iherman)
-
Activity vocab (FOAF v vCard Ontology) w3c/web-annotation#375 (4 comments by @azaroth42, @iherman, @riannella)
-
Remove un-implemented List, Composite, Independents w3c/web-annotation#369 (3 comments by @azaroth42, @iherman)
-
Ontologies use non-existant owl:previousVersionURI w3c/web-annotation#381 (2 comments by @azaroth42, @iherman)
-
External: Reflect Protocol in Social Web Protocols document w3c/web-annotation#118 (2 comments by @azaroth42, @rhiaro)
-
Processing language for mono-lingual and internationalized resources w3c/web-annotation#342 (2 comments by @aphillips, @azaroth42)
-
Track alignment between motivations and other ontologies w3c/web-annotation#256 (1 comment by @azaroth42)
-
Should Annotation concept and document be distinguished? w3c/web-annotation#10 (1 comment by @gsergiu)
-
-
8 pull requests opened.
-
Handling #381 w3c/web-annotation#385, by @iherman.
-
Reference RDF 1.1 Concepts instead of the old version w3c/web-annotation#383, by @lanthaler.
-
fix dcterms:creator to be a foaf:Person, not a literal w3c/web-annotation#380, by @gkellogg.
-
Re-revised PR for CR2 w3c/web-annotation#379, by @azaroth42.
-
Revisions for CR2 w3c/web-annotation#378, by @azaroth42.
-
Clarify usage of AnnotationPage and startIndex w3c/web-annotation#377, by @azaroth42.
-
Minor changes on the PR transition request w3c/web-annotation#374, by @iherman.
-
Added Frame references w3c/web-annotation#373, by @iherman.
-
-
7 pull requests merged.
-
Reference RDF 1.1 Concepts instead of the old version w3c/web-annotation#383.
-
fix dcterms:creator to be a foaf:Person, not a literal w3c/web-annotation#380.
-
Re-revised PR for CR2 w3c/web-annotation#379.
-
Clarify usage of AnnotationPage and startIndex w3c/web-annotation#377.
-
Minor changes on the PR transition request w3c/web-annotation#374.
-
Added Frame references w3c/web-annotation#373.
-
Fixes for PR from Sept/Oct w3c/web-annotation#370.
-
-
1 pull request closed.
-
Revisions for CR2 w3c/web-annotation#378.
-
-
7 pull requests received 13 new comments.
-
fix dcterms:creator to be a foaf:Person, not a literal w3c/web-annotation#380 (3 comments by @azaroth42, @iherman)
-
Reference RDF 1.1 Concepts instead of the old version w3c/web-annotation#383 (2 comments by @iherman)
-
Participants
-
2 organizations left.
-
University of Manchester left.
-
Hypothes.is Project left.
-
GitHub
w3c/web-annotation
-
5 issues opened.
-
Remove un-implemented List, Composite, Independents w3c/web-annotation#369, by @azaroth42.
-
Clarify distinction between OPTIONS and GET/HEAD w3c/web-annotation#367, by @azaroth42.
-
ldp:PreferMinimalContainer and oa:PreferContainedIRIs interaction is confusing w3c/web-annotation#366, by @azaroth42.
-
Protocol example 11 should not include Vary: Prefer w3c/web-annotation#365, by @azaroth42.
-
Ontology has non-existent terms w3c/web-annotation#363, by @azaroth42.
-
-
5 issues closed.
-
Relationship between dc:language and processing language for multilingual resources w3c/web-annotation#343.
-
Processing language for mono-lingual and internationalized resources w3c/web-annotation#342.
-
The textDirection and processingLanguage properties are not needed w3c/web-annotation#335.
-
Ontology has non-existent terms w3c/web-annotation#363.
-
"modified" should be in both AnnotationCollection and AnnotationPage w3c/web-annotation#332.
-
-
9 issues received 25 new comments.
-
Clarification on the usage of rights in the example use case w3c/web-annotation#360 (9 comments by @azaroth42, @BigBlueHat, @riannella)
-
Processing language for mono-lingual and internationalized resources w3c/web-annotation#342 (3 comments by @azaroth42, @gsergiu, @iherman)
-
processLanguage description improvement suggestion w3c/web-annotation#345 (3 comments by @azaroth42, @iherman)
-
Relationship between dc:language and processing language for multilingual resources w3c/web-annotation#343 (2 comments by @azaroth42, @iherman)
-
Remove un-implemented List, Composite, Independents w3c/web-annotation#369 (1 comment by @azaroth42)
-
The textDirection and processingLanguage properties are not needed w3c/web-annotation#335 (1 comment by @azaroth42)
-
-
3 pull requests opened.
-
Fixes for PR from Sept/Oct w3c/web-annotation#370, by @azaroth42.
-
Created the PR transition request draft w3c/web-annotation#368, by @iherman.
-
Fix ontology for missing </div> tag in refinedBy w3c/web-annotation#364, by @azaroth42.
-
-
3 pull requests merged.
-
Fix ontology for missing </div> tag in refinedBy w3c/web-annotation#364.
-
Created the PR transition request draft w3c/web-annotation#368.
-
Add modified to protocol, closes #332 w3c/web-annotation#362.
-
-
2 pull requests received 2 new comments.
TR publications
-
3 documents published.
-
Web Annotation Data Model published as a Candidate Recommendation Snapshot. History of Web Annotation Data Model
-
Web Annotation Protocol published as a Candidate Recommendation Snapshot. History of Web Annotation Protocol
-
Web Annotation Vocabulary published as a Candidate Recommendation Snapshot. History of Web Annotation Vocabulary
-
GitHub
w3c/web-annotation
-
8 issues opened.
-
Clarification on the usage of rights in the example use case w3c/web-annotation#360, by @iherman.
-
/ns/oa/index.* do not resolve w3c/web-annotation#359, by @azaroth42.
-
HttpRequestState used in eg44, but is not in context w3c/web-annotation#358, by @VladimirAlexiev.
-
Clarify that TextualBody can be the source of a SpecificResource or target of Annotation w3c/web-annotation#357, by @azaroth42.
-
Examples of Implementations w3c/web-annotation#356, by @RicardoUsbeck.
-
Provide requirements guidance for future additions/modifications to OA namespace w3c/web-annotation#355, by @azaroth42.
-
Appendices in the vocab document should have been marked informative w3c/web-annotation#354, by @iherman.
-
Ontology documents have typos for Preferences w3c/web-annotation#353, by @azaroth42.
-
-
21 issues closed.
-
TextPositionSelector, thoughts about Unicode code *point* vs. UTF16 code *unit* w3c/web-annotation#350.
-
Vocabulary references rdf:Resource, should be rdfs:Resource w3c/web-annotation#326.
-
Incorrect links in /ns/oa/index.html w3c/web-annotation#330.
-
Ontology documents have typos for Preferences w3c/web-annotation#353.
-
Appendices in the vocab document should have been marked informative w3c/web-annotation#354.
-
Provide requirements guidance for future additions/modifications to OA namespace w3c/web-annotation#355.
-
HttpRequestState used in eg44, but is not in context w3c/web-annotation#358.
-
Clarify principle that features of external resources are not authoritative w3c/web-annotation#339.
-
[Protocol] The ETag sentence in Chapter 4 should refer to RFC 7232 w3c/web-annotation#331.
-
MUST ETag on GET, but only SHOULD If-Match on PUT and DELETE w3c/web-annotation#327.
-
Creating and Updating when canonical is present w3c/web-annotation#329.
-
Clarify scope of the key 'purpose' in Section 3.3.5 w3c/web-annotation#340.
-
Clarify text concerning legal IRIs for Annotation Containers w3c/web-annotation#344.
-
/ns/oa/index.* do not resolve w3c/web-annotation#359.
-
Make table for vocab usage w3c/web-annotation#323.
-
protocol testing requirements w3c/web-annotation#244.
-
Next/Prev are untestable w3c/web-annotation#233.
-
Create reference set of correct/incorrect annotations for test development w3c/web-annotation#55.
-
Clarify that TextualBody can be the source of a SpecificResource or target of Annotation w3c/web-annotation#357.
-
Examples of Implementations w3c/web-annotation#356.
-
Avoid mixed-content error with JSON-LD context in HTTPS w3c/web-annotation#347.
-
-
19 issues received 52 new comments.
-
Avoid mixed-content error with JSON-LD context in HTTPS w3c/web-annotation#347 (9 comments by @azaroth42, @csarven, @gsergiu)
-
Vocabulary references rdf:Resource, should be rdfs:Resource w3c/web-annotation#326 (4 comments by @azaroth42, @BigBlueHat, @gkellogg)
-
TextPositionSelector, thoughts about Unicode code *point* vs. UTF16 code *unit* w3c/web-annotation#350 (4 comments by @aphillips, @azaroth42, @danielweck)
-
HttpRequestState used in eg44, but is not in context w3c/web-annotation#358 (4 comments by @azaroth42, @iherman, @VladimirAlexiev)
-
Appendices in the vocab document should have been marked informative w3c/web-annotation#354 (4 comments by @azaroth42, @iherman, @rtroncy)
-
Examples of Implementations w3c/web-annotation#356 (3 comments by @azaroth42, @fsasaki, @RicardoUsbeck)
-
Clarification on the usage of rights in the example use case w3c/web-annotation#360 (2 comments by @azaroth42, @iherman)
-
JSON-LD Frames should be dereferenceable ... where? w3c/web-annotation#251 (1 comment by @azaroth42)
-
Create reference set of correct/incorrect annotations for test development w3c/web-annotation#55 (1 comment by @azaroth42)
-
Clarify that TextualBody can be the source of a SpecificResource or target of Annotation w3c/web-annotation#357 (1 comment by @iherman)
-
Provide requirements guidance for future additions/modifications to OA namespace w3c/web-annotation#355 (1 comment by @iherman)
-
-
2 pull requests opened.
-
Add modified to protocol, closes #332 w3c/web-annotation#362, by @azaroth42.
-
Update context, ns, vocab docs for non-normative bugs w3c/web-annotation#361, by @azaroth42.
-
-
1 pull request merged.
-
Update context, ns, vocab docs for non-normative bugs w3c/web-annotation#361.
-
-
1 pull request received 2 new comments.
w3c/web-annotation-tests
-
1 pull request closed.
-
Fix JSON in bodyResource w3c/web-annotation-tests#5.
-
-
1 pull request received 1 new comment.
Participants
-
1 organization left.
-
JOANNEUM RESEARCH Forschungsgesellschaft mbH left.
-
GitHub
w3c/web-annotation
-
15 issues opened.
-
TextPositionSelector, thoughts about Unicode code *point* vs. UTF16 code *unit* w3c/web-annotation#350, by @danielweck.
-
Requirements for Agents w3c/web-annotation#349, by @azaroth42.
-
ed sugg: textDirection w3c/web-annotation#348, by @r12a.
-
Avoid mixed-content error with JSON-LD context in HTTPS w3c/web-annotation#347, by @csarven.
-
Add info about which Media Type to Model w3c/web-annotation#346, by @BigBlueHat.
-
processLanguage description improvement suggestion w3c/web-annotation#345, by @r12a.
-
Clarify text concerning legal IRIs for Annotation Containers w3c/web-annotation#344, by @halindrome.
-
Relationship between dc:language and processing language for multilingual resources w3c/web-annotation#343, by @gsergiu.
-
Processing language for mono-lingual and internationalized resources w3c/web-annotation#342, by @gsergiu.
-
Processing language for multilingual resources w3c/web-annotation#341, by @gsergiu.
-
Clarify scope of the key 'purpose' in Section 3.3.5 w3c/web-annotation#340, by @tcole3.
-
Clarify principle that features of external resources are not authoritative w3c/web-annotation#339, by @azaroth42.
-
Cardinality of the processingLanguage? w3c/web-annotation#337, by @gsergiu.
-
Replace textDirection property with recommendation for including control characters in the text w3c/web-annotation#336, by @aaronpk.
-
The textDirection and processingLanguage properties are not needed w3c/web-annotation#335, by @kevinmarks.
-
-
5 issues closed.
-
Requirements for Agents w3c/web-annotation#349.
-
Protocol examples should use comma separated headers in examples w3c/web-annotation#333.
-
Container Representations section should be more demanding w3c/web-annotation#328.
-
Cardinality of the processingLanguage? w3c/web-annotation#337.
-
Replace textDirection property with recommendation for including control characters in the text w3c/web-annotation#336.
-
-
16 issues received 131 new comments.
-
The textDirection and processingLanguage properties are not needed w3c/web-annotation#335 (47 comments by @aaronpk, @aphillips, @azaroth42, @BigBlueHat, @gsergiu, @halindrome, @iherman, @jjett, @kevinmarks, @r12a, @tantek)
-
Cardinality of the processingLanguage? w3c/web-annotation#337 (17 comments by @akuckartz, @azaroth42, @gsergiu, @tkanai)
-
Relationship between dc:language and processing language for multilingual resources w3c/web-annotation#343 (10 comments by @azaroth42, @fsasaki, @gsergiu, @r12a)
-
ed sugg: textDirection w3c/web-annotation#348 (7 comments by @BigBlueHat, @iherman, @lkemmel, @matial, @r12a, @tkanai)
-
Avoid mixed-content error with JSON-LD context in HTTPS w3c/web-annotation#347 (7 comments by @azaroth42, @BigBlueHat, @csarven, @iherman)
-
TextPositionSelector, thoughts about Unicode code *point* vs. UTF16 code *unit* w3c/web-annotation#350 (6 comments by @azaroth42, @danielweck, @iherman, @tilgovi, @tkanai)
-
Replace textDirection property with recommendation for including control characters in the text w3c/web-annotation#336 (6 comments by @azaroth42, @BigBlueHat, @gsergiu, @tomerm)
-
processLanguage description improvement suggestion w3c/web-annotation#345 (5 comments by @aphillips, @gsergiu, @r12a)
-
Requirements for Agents w3c/web-annotation#349 (5 comments by @azaroth42, @BigBlueHat, @iherman, @tcole3)
-
Clarify text concerning legal IRIs for Annotation Containers w3c/web-annotation#344 (5 comments by @azaroth42, @BigBlueHat, @halindrome)
-
Processing language for multilingual resources w3c/web-annotation#341 (4 comments by @akuckartz, @azaroth42, @gsergiu)
-
Protocol examples should use comma separated headers in examples w3c/web-annotation#333 (4 comments by @azaroth42, @BigBlueHat)
-
Processing language for mono-lingual and internationalized resources w3c/web-annotation#342 (2 comments by @gsergiu, @r12a)
-
MUST ETag on GET, but only SHOULD If-Match on PUT and DELETE w3c/web-annotation#327 (2 comments by @azaroth42, @BigBlueHat)
-
-
3 pull requests opened.
-
Exit criteria w3c/web-annotation#352, by @azaroth42.
-
Add error fixtures to repo w3c/web-annotation#351, by @azaroth42.
-
Fix 333 multiple http headers w3c/web-annotation#338, by @BigBlueHat.
-
-
5 pull requests merged.
-
Exit criteria w3c/web-annotation#352.
-
Add error fixtures to repo w3c/web-annotation#351.
-
Fix 333 multiple http headers w3c/web-annotation#338.
-
Fix 328 - Clarify Representation Requirements w3c/web-annotation#334.
-
Protocol Paging content editorial restructuring w3c/web-annotation#321.
-
-
3 pull requests received 5 new comments.
w3c/web-annotation-tests
-
1 pull request opened.
-
Minor grammar formatting update w3c/web-annotation-tests#9, by @jjett.
-
-
1 pull request merged.
-
Minor grammar formatting update w3c/web-annotation-tests#9.
-
TR publications
-
3 documents published.
-
Web Annotation Protocol published as a Candidate Recommendation Snapshot. History of Web Annotation Protocol
-
Web Annotation Data Model published as a Candidate Recommendation Snapshot. History of Web Annotation Data Model
-
Web Annotation Vocabulary published as a Candidate Recommendation Snapshot. History of Web Annotation Vocabulary
-
GitHub
w3c/web-annotation
-
10 issues opened.
-
Protocol examples should use comma separated headers in examples w3c/web-annotation#333, by @azaroth42.
-
"modified" should be in both AnnotationCollection and AnnotationPage w3c/web-annotation#332, by @tkanai.
-
[Protocol] The ETag sentence in Chapter 4 should refer to RFC 7232 w3c/web-annotation#331, by @tkanai.
-
Incorrect links in /ns/oa/index.html w3c/web-annotation#330, by @azaroth42.
-
Creating and Updating when canonical is present w3c/web-annotation#329, by @csarven.
-
Container Representations section should be more demanding w3c/web-annotation#328, by @BigBlueHat.
-
MUST ETag on GET, but only SHOULD If-Match on PUT and DELETE w3c/web-annotation#327, by @BigBlueHat.
-
Vocabulary references rdf:Resource, should be rdfs:Resource w3c/web-annotation#326, by @gkellogg.
-
Try to register profile with IETF w3c/web-annotation#324, by @azaroth42.
-
Make table for vocab usage w3c/web-annotation#323, by @azaroth42.
-
-
2 issues closed.
-
TAG comments (@mnot) w3c/web-annotation#313.
-
Annotation IRI mention in 4. w3c/web-annotation#319.
-
-
9 issues received 16 new comments.
-
Creating and Updating when canonical is present w3c/web-annotation#329 (5 comments by @azaroth42, @csarven, @rhiaro)
-
MUST ETag on GET, but only SHOULD If-Match on PUT and DELETE w3c/web-annotation#327 (3 comments by @azaroth42, @BigBlueHat)
-
Protocol examples should use comma separated headers in examples w3c/web-annotation#333 (1 comment by @BigBlueHat)
-
"modified" should be in both AnnotationCollection and AnnotationPage w3c/web-annotation#332 (1 comment by @azaroth42)
-
[Protocol] The ETag sentence in Chapter 4 should refer to RFC 7232 w3c/web-annotation#331 (1 comment by @azaroth42)
-
Container Representations section should be more demanding w3c/web-annotation#328 (1 comment by @azaroth42)
-
-
3 pull requests opened.
-
Fix 328 - Clarify Representation Requirements w3c/web-annotation#334, by @BigBlueHat.
-
Generate selector note index w3c/web-annotation#325, by @BigBlueHat.
-
Preparation for the Protocol CR w3c/web-annotation#322, by @iherman.
-
-
2 pull requests merged.
-
Generate selector note index w3c/web-annotation#325.
-
Preparation for the Protocol CR w3c/web-annotation#322.
-
-
2 pull requests received 8 new comments.
-
Protocol Paging content editorial restructuring w3c/web-annotation#321 (7 comments by @azaroth42, @BigBlueHat, @iherman)
-
w3c/web-annotation-tests
-
3 issues opened.
-
annotation.id is a MUST w3c/web-annotation-tests#8, by @azaroth42.
-
Determine whether jsonschema format=uri matches IRIs w3c/web-annotation-tests#7, by @azaroth42.
-
bodyResource / targetResource fail incorrectly w3c/web-annotation-tests#6, by @azaroth42.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Fix JSON in bodyResource w3c/web-annotation-tests#5, by @azaroth42.
-
-
1 pull request received 1 new comment.
Participants
-
1 participant left.
-
Chris Birk (W3C Invited Experts) left.
-
GitHub
w3c/web-annotation
-
30 issues opened.
-
JSON-LD aliases in Vocabulary content w3c/web-annotation#320, by @BigBlueHat.
-
Annotation IRI mention in 4. w3c/web-annotation#319, by @BigBlueHat.
-
Discuss re-introducing Named Graph resources w3c/web-annotation#316, by @azaroth42.
-
De-normative-ify reference to ldp-paging w3c/web-annotation#314, by @azaroth42.
-
TAG comments (@mnot) w3c/web-annotation#313, by @azaroth42.
-
"5.1 Create a New Annotation" references using Prefer in response to a creation request w3c/web-annotation#312, by @BigBlueHat.
-
Support for embedded structured data (metadata) in the body w3c/web-annotation#309, by @gsergiu.
-
Which is the relationship between the format and the type of External Web resources? w3c/web-annotation#308, by @gsergiu.
-
Link errors in the vocab document w3c/web-annotation#307, by @iherman.
-
4.1.1 Client Preferences uses `ns/oa` while examples use `ns/ldp` w3c/web-annotation#304, by @BigBlueHat.
-
content-length in protocol examples are wrong w3c/web-annotation#300, by @azaroth42.
-
(Protocol) Editorial issues about IRI w3c/web-annotation#299, by @tkanai.
-
processingLanguage nitpicks w3c/web-annotation#298, by @bjdmeest.
-
Should the fragment specification URLs be https? w3c/web-annotation#296, by @csarven.
-
Fragment Specification for RDFa w3c/web-annotation#295, by @csarven.
-
Fix "SoftwareAgent" in two examples w3c/web-annotation#293, by @hugomanguinhas.
-
Add a `Collection Response with Contained Description` w3c/web-annotation#292, by @BigBlueHat.
-
Admin information to be added to the document for CR w3c/web-annotation#290, by @iherman.
-
Create SVG versions of diagrams w3c/web-annotation#286, by @azaroth42.
-
Diagram inconsistencies (in pull request #279) w3c/web-annotation#280, by @paolociccarese.
-
Add Accept-Post to subsequent example? w3c/web-annotation#275, by @BigBlueHat.
-
Changes' sections should be completed w3c/web-annotation#273, by @iherman.
-
At-Risk feature must be documented in the status section w3c/web-annotation#271, by @iherman.
-
Final few examples needed w3c/web-annotation#269, by @azaroth42.
-
Minor upper/lower case issues w3c/web-annotation#266, by @paolociccarese.
-
Examples 6 and 7 and purpose=commenting w3c/web-annotation#265, by @paolociccarese.
-
'Web Resource' not consistent across the document w3c/web-annotation#264, by @paolociccarese.
-
respec does not correctly highlight turtle examples w3c/web-annotation#260, by @azaroth42.
-
Including resource previews in annotations w3c/web-annotation#257, by @gsergiu.
-
Track alignment between motivations and other ontologies w3c/web-annotation#256, by @azaroth42.
-
-
52 issues closed.
-
Support for embedded structured data (metadata) in the body w3c/web-annotation#309.
-
De-normative-ify reference to ldp-paging w3c/web-annotation#314.
-
"5.1 Create a New Annotation" references using Prefer in response to a creation request w3c/web-annotation#312.
-
Link errors in the vocab document w3c/web-annotation#307.
-
Admin information to be added to the document for CR w3c/web-annotation#290.
-
4.1.1 Client Preferences uses `ns/oa` while examples use `ns/ldp` w3c/web-annotation#304.
-
Fix "SoftwareAgent" in two examples w3c/web-annotation#293.
-
processingLanguage nitpicks w3c/web-annotation#298.
-
(Protocol) Editorial issues about IRI w3c/web-annotation#299.
-
content-length in protocol examples are wrong w3c/web-annotation#300.
-
Add a `Collection Response with Contained Description` w3c/web-annotation#292.
-
Should the fragment specification URLs be https? w3c/web-annotation#296.
-
Fragment Specification for RDFa w3c/web-annotation#295.
-
Add diagrams to Vocab examples w3c/web-annotation#131.
-
Final few examples needed w3c/web-annotation#269.
-
Diagram inconsistencies (in pull request #279) w3c/web-annotation#280.
-
'Web Resource' not consistent across the document w3c/web-annotation#264.
-
Examples 6 and 7 and purpose=commenting w3c/web-annotation#265.
-
Minor upper/lower case issues w3c/web-annotation#266.
-
At-Risk feature must be documented in the status section w3c/web-annotation#271.
-
Changes' sections should be completed w3c/web-annotation#273.
-
Add Accept-Post to subsequent example? w3c/web-annotation#275.
-
Normative refs ; change log w3c/web-annotation#252.
-
respec does not correctly highlight turtle examples w3c/web-annotation#260.
-
Reference to text encoding in spec perhaps not appropriate w3c/web-annotation#227.
-
Add accessibility to the model & vocab w3c/web-annotation#231.
-
Remove "and so forth", clarify utf-8 encoding w3c/web-annotation#237.
-
Model is defined in terms of IRIs; Protocol with URI w3c/web-annotation#241.
-
Add a recommendation for HTTPS into the protocol spec w3c/web-annotation#232.
-
Explain extending spec with new classes, esp Selectors w3c/web-annotation#234.
-
Minor issues with the individuals' formatting in the vocab spec w3c/web-annotation#245.
-
Model Typos w3c/web-annotation#254.
-
Status code requirements should be in the sections of Protocol w3c/web-annotation#228.
-
Model should allow multiple Selectors per SpecificResource w3c/web-annotation#207.
-
Base direction for annotations w3c/web-annotation#224.
-
Use of dc:language w3c/web-annotation#225.
-
white space normalisation w3c/web-annotation#221.
-
Normalisation of Text Quote Selector w3c/web-annotation#222.
-
Request header and language negotiation w3c/web-annotation#220.
-
exactly 0 or 1 language(s) w3c/web-annotation#213.
-
TimeState, generated, and modified should recommend all values use UTC w3c/web-annotation#215.
-
'generated' and 'modified' should use UTC by default w3c/web-annotation#216.
-
(model) have a note on logical and visual order of text for text quote selector implementations w3c/web-annotation#210.
-
Add pointer to TextualBody to bodyValue w3c/web-annotation#226.
-
Can I refine a state via a selector? w3c/web-annotation#195.
-
Deref of namespace should go to vocab? w3c/web-annotation#199.
-
Should oa:start / oa:end be xsd:nonNegativeInteger or xsd:integer ? w3c/web-annotation#200.
-
(model) vague definition of character position for text position selector w3c/web-annotation#206.
-
Data type, cardinality questions, typos w3c/web-annotation#214.
-
Consistent definitions of the id for External Web Resources and Specific Resources w3c/web-annotation#247.
-
Change 'reviewing' to 'assessing'? w3c/web-annotation#249.
-
Relationship between Motivations and Actions (from schema.org) w3c/web-annotation#248.
-
-
37 issues received 152 new comments.
-
Reference to text encoding in spec perhaps not appropriate w3c/web-annotation#227 (23 comments by @aphillips, @azaroth42, @duerst, @fsasaki, @iherman, @r12a, @tilgovi)
-
Support for embedded structured data (metadata) in the body w3c/web-annotation#309 (20 comments by @azaroth42, @BigBlueHat, @gsergiu, @iherman, @jjett)
-
respec does not correctly highlight turtle examples w3c/web-annotation#260 (14 comments by @azaroth42, @halindrome, @iherman)
-
Consistent definitions of the id for External Web Resources and Specific Resources w3c/web-annotation#247 (13 comments by @azaroth42, @gsergiu, @iherman)
-
Including resource previews in annotations w3c/web-annotation#257 (7 comments by @azaroth42, @gsergiu, @iherman)
-
JSON-LD Frames should be dereferenceable ... where? w3c/web-annotation#251 (6 comments by @azaroth42, @iherman)
-
Should the fragment specification URLs be https? w3c/web-annotation#296 (6 comments by @azaroth42, @csarven, @iherman)
-
Which is the relationship between the format and the type of External Web resources? w3c/web-annotation#308 (5 comments by @azaroth42, @gsergiu, @tcole3)
-
Admin information to be added to the document for CR w3c/web-annotation#290 (5 comments by @gkellogg, @halindrome, @iherman)
-
Fragment Specification for RDFa w3c/web-annotation#295 (4 comments by @azaroth42, @csarven, @iherman)
-
Remove purpose=commenting requirement from bodyValue w3c/web-annotation#240 (4 comments by @azaroth42, @BigBlueHat, @hugomanguinhas)
-
4.1.1 Client Preferences uses `ns/oa` while examples use `ns/ldp` w3c/web-annotation#304 (3 comments by @BigBlueHat, @iherman)
-
JSON-LD aliases in Vocabulary content w3c/web-annotation#320 (2 comments by @azaroth42, @BigBlueHat)
-
Add a `Collection Response with Contained Description` w3c/web-annotation#292 (2 comments by @BigBlueHat)
-
Diagram inconsistencies (in pull request #279) w3c/web-annotation#280 (2 comments by @azaroth42, @pciccarese)
-
Add Accept-Post to subsequent example? w3c/web-annotation#275 (2 comments by @azaroth42, @BigBlueHat)
-
Model is defined in terms of IRIs; Protocol with URI w3c/web-annotation#241 (2 comments by @akuckartz, @azaroth42)
-
`account` likely to conflict with foaf:account w3c/web-annotation#130 (2 comments by @BigBlueHat, @iherman)
-
"5.1 Create a New Annotation" references using Prefer in response to a creation request w3c/web-annotation#312 (1 comment by @BigBlueHat)
-
Should Annotation concept and document be distinguished? w3c/web-annotation#10 (1 comment by @iherman)
-
Relationship between Motivations and Actions (from schema.org) w3c/web-annotation#248 (1 comment by @azaroth42)
-
-
37 pull requests opened.
-
Protocol Paging content editorial restructuring w3c/web-annotation#321, by @BigBlueHat.
-
Date of Vocab was wrong w3c/web-annotation#318, by @iherman.
-
Tweaks for mnot's TAG comments w3c/web-annotation#317, by @azaroth42.
-
Remove Link, Vary, and Prefer headers post-create w3c/web-annotation#315, by @BigBlueHat.
-
Fix example 15 in protocol w3c/web-annotation#311, by @BigBlueHat.
-
Raphael -> Raphaël w3c/web-annotation#310, by @iherman.
-
First round of link checking w3c/web-annotation#306, by @iherman.
-
Fix namespace issues with Prefer classes w3c/web-annotation#305, by @BigBlueHat.
-
First round of pubrules' checker changes w3c/web-annotation#303, by @iherman.
-
Final version for CR transition request w3c/web-annotation#302, by @iherman.
-
CR Typos, Updates w3c/web-annotation#301, by @azaroth42.
-
Fix editor info w3c/web-annotation#297, by @BigBlueHat.
-
Updated the admin part of the repo w3c/web-annotation#294, by @iherman.
-
Line folding in HTTP headers is deprecated as of RFC7230 w3c/web-annotation#291, by @BigBlueHat.
-
Protocol tweaky bugs w3c/web-annotation#289, by @BigBlueHat.
-
Remove trailing whitespace from examples w3c/web-annotation#288, by @azaroth42.
-
Fix diagrams, MAY for skolemization w3c/web-annotation#287, by @azaroth42.
-
Changed the SOTD mark on at risk w3c/web-annotation#285, by @iherman.
-
SOTD changes in the protocol spec w3c/web-annotation#284, by @iherman.
-
Minor stylistic errors w3c/web-annotation#283, by @iherman.
-
Better sectioning of the changes' section w3c/web-annotation#282, by @iherman.
-
Yet more diagrams 2 (to be done after 'yet more diagrams') w3c/web-annotation#281, by @pciccarese.
-
Yet more diagrams w3c/web-annotation#279, by @azaroth42.
-
Add CR structure to admin/ w3c/web-annotation#278, by @azaroth42.
-
And diagram source for master w3c/web-annotation#277, by @azaroth42.
-
At Risks, Change Logs w3c/web-annotation#276, by @azaroth42.
-
Added a highlighter for turtle w3c/web-annotation#274, by @iherman.
-
Added the CR transition request mail draft w3c/web-annotation#272, by @iherman.
-
Added figures examples 45 and 46 (style) w3c/web-annotation#270, by @paolociccarese.
-
figures examples 39-44 w3c/web-annotation#268, by @pciccarese.
-
pygments highlighter w3c/web-annotation#267, by @azaroth42.
-
Update index-nametemplate.html w3c/web-annotation#263, by @iherman.
-
Updated the selector note w3c/web-annotation#262, by @iherman.
-
Add diagrams w3c/web-annotation#261, by @azaroth42.
-
Update Appendix C (slightly) w3c/web-annotation#259, by @BigBlueHat.
-
Further typo fixes w3c/web-annotation#258, by @azaroth42.
-
Typo fixes from #254 w3c/web-annotation#255, by @azaroth42.
-
-
36 pull requests merged.
-
Date of Vocab was wrong w3c/web-annotation#318.
-
Tweaks for mnot's TAG comments w3c/web-annotation#317.
-
Remove Link, Vary, and Prefer headers post-create w3c/web-annotation#315.
-
Raphael -> Raphaël w3c/web-annotation#310.
-
First round of link checking w3c/web-annotation#306.
-
Fix namespace issues with Prefer classes w3c/web-annotation#305.
-
First round of pubrules' checker changes w3c/web-annotation#303.
-
Final version for CR transition request w3c/web-annotation#302.
-
CR Typos, Updates w3c/web-annotation#301.
-
Fix editor info w3c/web-annotation#297.
-
Updated the admin part of the repo w3c/web-annotation#294.
-
Line folding in HTTP headers is deprecated as of RFC7230 w3c/web-annotation#291.
-
Remove trailing whitespace from examples w3c/web-annotation#288.
-
Protocol tweaky bugs w3c/web-annotation#289.
-
Fix diagrams, MAY for skolemization w3c/web-annotation#287.
-
Changed the SOTD mark on at risk w3c/web-annotation#285.
-
SOTD changes in the protocol spec w3c/web-annotation#284.
-
Minor stylistic errors w3c/web-annotation#283.
-
Better sectioning of the changes' section w3c/web-annotation#282.
-
Add CR structure to admin/ w3c/web-annotation#278.
-
Yet more diagrams 2 (to be done after 'yet more diagrams') w3c/web-annotation#281.
-
Yet more diagrams w3c/web-annotation#279.
-
And diagram source for master w3c/web-annotation#277.
-
At Risks, Change Logs w3c/web-annotation#276.
-
Update Appendix C (slightly) w3c/web-annotation#259.
-
Added a highlighter for turtle w3c/web-annotation#274.
-
Added the CR transition request mail draft w3c/web-annotation#272.
-
Added figures examples 45 and 46 (style) w3c/web-annotation#270.
-
Update index-nametemplate.html w3c/web-annotation#263.
-
figures examples 39-44 w3c/web-annotation#268.
-
pygments highlighter w3c/web-annotation#267.
-
Updated the selector note w3c/web-annotation#262.
-
Add diagrams w3c/web-annotation#261.
-
Further typo fixes w3c/web-annotation#258.
-
Delete extraneous / unused content w3c/web-annotation#253.
-
Typo fixes from #254 w3c/web-annotation#255.
-
-
1 pull request closed.
-
Fix example 15 in protocol w3c/web-annotation#311.
-
-
1 pull request reopened.
-
Fix example 15 in protocol w3c/web-annotation#311, by @BigBlueHat.
-
-
12 pull requests received 31 new comments.
-
Line folding in HTTP headers is deprecated as of RFC7230 w3c/web-annotation#291 (4 comments by @azaroth42, @BigBlueHat, @tilgovi)
w3c/web-annotation-tests
-
1 issue opened.
-
Manifest structure must extend general RDF test manifest structure w3c/web-annotation-tests#4, by @gkellogg.
-
Participants
-
1 participant left.
-
Benjamin Young (Wiley) left.
-
-
1 organization left.
-
Cornac Servicios Editoriales left.
-
GitHub
w3c/web-annotation
-
38 issues opened.
-
Model Typos w3c/web-annotation#254, by @azaroth42.
-
Normative refs ; change log w3c/web-annotation#252, by @azaroth42.
-
JSON-LD Frames should be dereferenceable ... where? w3c/web-annotation#251, by @azaroth42.
-
'Role' still present in examples w3c/web-annotation#250, by @paolociccarese.
-
Change 'reviewing' to 'assessing'? w3c/web-annotation#249, by @paolociccarese.
-
Relationship between Motivations and Actions (from schema.org) w3c/web-annotation#248, by @gsergiu.
-
Consistent definitions of the id for External Web Resources and Specific Resources w3c/web-annotation#247, by @gsergiu.
-
Minor issues with the individuals' formatting in the vocab spec w3c/web-annotation#245, by @iherman.
-
protocol testing requirements w3c/web-annotation#244, by @azaroth42.
-
Model is defined in terms of IRIs; Protocol with URI w3c/web-annotation#241, by @azaroth42.
-
Remove purpose=commenting requirement from bodyValue w3c/web-annotation#240, by @azaroth42.
-
Remove "and so forth", clarify utf-8 encoding w3c/web-annotation#237, by @azaroth42.
-
Explain extending spec with new classes, esp Selectors w3c/web-annotation#234, by @azaroth42.
-
Next/Prev are untestable w3c/web-annotation#233, by @azaroth42.
-
Add a recommendation for HTTPS into the protocol spec w3c/web-annotation#232, by @BigBlueHat.
-
Add accessibility to the model & vocab w3c/web-annotation#231, by @azaroth42.
-
Change NS to https://.../wa/ w3c/web-annotation#230, by @azaroth42.
-
Status code requirements should be in the sections of Protocol w3c/web-annotation#228, by @azaroth42.
-
Reference to text encoding in spec perhaps not appropriate w3c/web-annotation#227, by @nickstenning.
-
Add pointer to TextualBody to bodyValue w3c/web-annotation#226, by @azaroth42.
-
Use of dc:language w3c/web-annotation#225, by @r12a.
-
Base direction for annotations w3c/web-annotation#224, by @r12a.
-
String body must not have a language associated? w3c/web-annotation#223, by @r12a.
-
Normalisation of Text Quote Selector w3c/web-annotation#222, by @r12a.
-
white space normalisation w3c/web-annotation#221, by @r12a.
-
Request header and language negotiation w3c/web-annotation#220, by @r12a.
-
Defaults for an Annotation Collection w3c/web-annotation#219, by @r12a.
-
How is language assigned to an annotation? w3c/web-annotation#218, by @r12a.
-
'generated' and 'modified' date/time properties specific reference and format w3c/web-annotation#217, by @r12a.
-
'generated' and 'modified' should use UTC by default w3c/web-annotation#216, by @r12a.
-
TimeState, generated, and modified should recommend all values use UTC w3c/web-annotation#215, by @r12a.
-
Data type, cardinality questions, typos w3c/web-annotation#214, by @azaroth42.
-
exactly 0 or 1 language(s) w3c/web-annotation#213, by @r12a.
-
misspellungs w3c/web-annotation#212, by @r12a.
-
(model) missing mechanism to express language preferences in the intendend audience field w3c/web-annotation#211, by @fsasaki.
-
(model) have a note on logical and visual order of text for text quote selector implementations w3c/web-annotation#210, by @fsasaki.
-
(model) make definition of a character more precise w3c/web-annotation#209, by @fsasaki.
-
(model) update reference for language tags: BCP47 instead of RFC5646 w3c/web-annotation#208, by @fsasaki.
-
-
17 issues closed.
-
'Role' still present in examples w3c/web-annotation#250.
-
misspellungs w3c/web-annotation#212.
-
Change NS to https://.../wa/ w3c/web-annotation#230.
-
Remove purpose=commenting requirement from bodyValue w3c/web-annotation#240.
-
Keeping the OA ontology up to date w3c/web-annotation#66.
-
ActivityStreams / Annotation comparison w3c/web-annotation#102.
-
(model) update reference for language tags: BCP47 instead of RFC5646 w3c/web-annotation#208.
-
value or text on the definition of an SVG selector w3c/web-annotation#191.
-
Selector/media table w3c/web-annotation#203.
-
Privacy Interest Group (PING) review w3c/web-annotation#204.
-
(model) make definition of a character more precise w3c/web-annotation#209.
-
'generated' and 'modified' date/time properties specific reference and format w3c/web-annotation#217.
-
Defaults for an Annotation Collection w3c/web-annotation#219.
-
String body must not have a language associated? w3c/web-annotation#223.
-
How is language assigned to an annotation? w3c/web-annotation#218.
-
(model) missing mechanism to express language preferences in the intendend audience field w3c/web-annotation#211.
-
Dis/Allow both hasState and hasSelector on same SpecificResource? w3c/web-annotation#205.
-
-
2 issues reopened.
-
Request header and language negotiation w3c/web-annotation#220, by @r12a.
-
Reference to text encoding in spec perhaps not appropriate w3c/web-annotation#227, by @r12a.
-
-
45 issues received 251 new comments.
-
Relationship between Motivations and Actions (from schema.org) w3c/web-annotation#248 (37 comments by @akuckartz, @azaroth42, @gsergiu, @iherman, @jjett, @paolociccarese, @pciccarese, @tilgovi)
-
exactly 0 or 1 language(s) w3c/web-annotation#213 (25 comments by @asmusf, @azaroth42, @fsasaki, @gsergiu, @hugomanguinhas, @iherman, @r12a)
-
Base direction for annotations w3c/web-annotation#224 (25 comments by @azaroth42, @csarven, @gkellogg, @gsergiu, @iherman, @r12a)
-
Reference to text encoding in spec perhaps not appropriate w3c/web-annotation#227 (21 comments by @aphillips, @azaroth42, @duerst, @fsasaki, @iherman, @nickstenning, @r12a, @tilgovi)
-
(model) vague definition of character position for text position selector w3c/web-annotation#206 (19 comments by @andjc, @aphillips, @azaroth42, @duerst, @iherman, @kojiishi, @mark-buer, @r12a, @tkanai)
-
Model should allow multiple Selectors per SpecificResource w3c/web-annotation#207 (15 comments by @azaroth42, @iherman, @jjett, @paolociccarese, @pciccarese, @tbdinesh, @tcole3)
-
white space normalisation w3c/web-annotation#221 (10 comments by @azaroth42, @iherman, @r12a, @tilgovi)
-
Change NS to https://.../wa/ w3c/web-annotation#230 (8 comments by @akuckartz, @azaroth42, @iherman, @stain)
-
Model is defined in terms of IRIs; Protocol with URI w3c/web-annotation#241 (8 comments by @akuckartz, @azaroth42, @halindrome, @iherman, @r12a)
-
Request header and language negotiation w3c/web-annotation#220 (8 comments by @azaroth42, @iherman, @r12a)
-
Selector/media table w3c/web-annotation#203 (7 comments by @azaroth42, @iherman, @pciccarese, @tilgovi)
-
Change 'reviewing' to 'assessing'? w3c/web-annotation#249 (6 comments by @azaroth42, @jjett, @paolociccarese)
-
Deref of namespace should go to vocab? w3c/web-annotation#199 (6 comments by @azaroth42, @BigBlueHat, @iherman)
-
'generated' and 'modified' should use UTC by default w3c/web-annotation#216 (5 comments by @aphillips, @iherman, @nickstenning)
-
Remove purpose=commenting requirement from bodyValue w3c/web-annotation#240 (4 comments by @BigBlueHat, @iherman, @pciccarese)
-
Consistent definitions of the id for External Web Resources and Specific Resources w3c/web-annotation#247 (2 comments by @azaroth42, @gsergiu)
-
Create reference set of correct/incorrect annotations for test development w3c/web-annotation#55 (2 comments by @azaroth42, @tcole3)
-
ActivityStreams / Annotation comparison w3c/web-annotation#102 (2 comments by @azaroth42, @BigBlueHat)
-
Should oa:start / oa:end be xsd:nonNegativeInteger or xsd:integer ? w3c/web-annotation#200 (2 comments by @BigBlueHat)
-
(model) make definition of a character more precise w3c/web-annotation#209 (2 comments by @azaroth42, @iherman)
-
'generated' and 'modified' date/time properties specific reference and format w3c/web-annotation#217 (2 comments by @akuckartz, @iherman)
-
(model) have a note on logical and visual order of text for text quote selector implementations w3c/web-annotation#210 (2 comments by @iherman, @tilgovi)
-
Minor issues with the individuals' formatting in the vocab spec w3c/web-annotation#245 (1 comment by @azaroth42)
-
Status code requirements should be in the sections of Protocol w3c/web-annotation#228 (1 comment by @iherman)
-
Explain extending spec with new classes, esp Selectors w3c/web-annotation#234 (1 comment by @iherman)
-
(model) missing mechanism to express language preferences in the intendend audience field w3c/web-annotation#211 (1 comment by @iherman)
-
(model) update reference for language tags: BCP47 instead of RFC5646 w3c/web-annotation#208 (1 comment by @iherman)
-
Dis/Allow both hasState and hasSelector on same SpecificResource? w3c/web-annotation#205 (1 comment by @iherman)
-
TimeState, generated, and modified should recommend all values use UTC w3c/web-annotation#215 (1 comment by @azaroth42)
-
-
9 pull requests opened.
-
Delete extraneous / unused content w3c/web-annotation#253, by @azaroth42.
-
Rob thursday w3c/web-annotation#246, by @azaroth42.
-
Python script to build ontology from vocab HTML w3c/web-annotation#243, by @azaroth42.
-
Rob Editor Actions w3c/web-annotation#242, by @azaroth42.
-
Minor fixes w3c/web-annotation#239, by @azaroth42.
-
Fixes for #208 and #102 w3c/web-annotation#238, by @BigBlueHat.
-
Rob actions w3c/web-annotation#236, by @azaroth42.
-
Added media types' table to the draft w3c/web-annotation#235, by @iherman.
-
Load ReSpec over HTTPS w3c/web-annotation#229, by @nickstenning.
-
-
8 pull requests merged.
-
Rob thursday w3c/web-annotation#246.
-
Rob Editor Actions w3c/web-annotation#242.
-
Python script to build ontology from vocab HTML w3c/web-annotation#243.
-
Minor fixes w3c/web-annotation#239.
-
Fixes for #208 and #102 w3c/web-annotation#238.
-
Rob actions w3c/web-annotation#236.
-
Added media types' table to the draft w3c/web-annotation#235.
-
Load ReSpec over HTTPS w3c/web-annotation#229.
-
-
2 pull requests closed.
-
Updating vocabulary w3c/web-annotation#188.
-
Vocab namespaces section w3c/web-annotation#198.
-
-
7 pull requests received 17 new comments.
w3c/web-annotation-tests
-
2 issues opened.
-
JSON Schema creation w3c/web-annotation-tests#3, by @BigBlueHat.
-
Write access? w3c/web-annotation-tests#1, by @BigBlueHat.
-
-
1 issue closed.
-
Write access? w3c/web-annotation-tests#1.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Add common and framework contents from WPT w3c/web-annotation-tests#2, by @BigBlueHat.
-
-
1 pull request merged.
-
Add common and framework contents from WPT w3c/web-annotation-tests#2.
-
Participants
-
1 organization joined.
-
Cornac Servicios Editoriales joined.
-
GitHub
w3c/web-annotation
-
5 issues opened.
-
Model should allow multiple Selectors per SpecificResource w3c/web-annotation#207, by @azaroth42.
-
(model) vague definition of character position for text position selector w3c/web-annotation#206, by @mark-buer.
-
Dis/Allow both hasState and hasSelector on same SpecificResource? w3c/web-annotation#205, by @azaroth42.
-
Privacy Interest Group (PING) review w3c/web-annotation#204, by @iherman.
-
Selector/media table w3c/web-annotation#203, by @iherman.
-
-
8 issues closed.
-
Usage of 'dc:' in the model document? w3c/web-annotation#185.
-
Conformance clause w3c/web-annotation#165.
-
Publish a temporary testing JSON-LD context doc for use with JSON-LD Playground (etc) w3c/web-annotation#71.
-
Extension Capacity w3c/web-annotation#154.
-
Document annotation service endpoint rel w3c/web-annotation#174.
-
Acknowledgement section content and change section w3c/web-annotation#179.
-
Terminology issue: Use IRI as resource identifier w3c/web-annotation#183.
-
Exact syntax for the selectors-as-fragments w3c/web-annotation#197.
-
-
12 issues received 52 new comments.
-
Can I refine a state via a selector? w3c/web-annotation#195 (10 comments by @azaroth42, @iherman, @jjett, @tilgovi)
-
HTML Serialization Use Cases w3c/web-annotation#147 (10 comments by @csarven, @halindrome, @iherman, @tcole3)
-
Privacy Interest Group (PING) review w3c/web-annotation#204 (9 comments by @azaroth42, @BigBlueHat, @dwhly, @iherman, @josephlhall, @shepazu, @tbdinesh)
-
Model should allow multiple Selectors per SpecificResource w3c/web-annotation#207 (6 comments by @azaroth42, @iherman, @tbdinesh)
-
Should oa:start / oa:end be xsd:nonNegativeInteger or xsd:integer ? w3c/web-annotation#200 (5 comments by @azaroth42, @iherman, @stain)
-
Dis/Allow both hasState and hasSelector on same SpecificResource? w3c/web-annotation#205 (2 comments by @iherman)
-
value or text on the definition of an SVG selector w3c/web-annotation#191 (2 comments by @azaroth42, @iherman)
-
-
2 pull requests opened.
-
Media selectors w3c/web-annotation#202, by @iherman.
-
Selector fragment syntax change w3c/web-annotation#201, by @iherman.
-
-
2 pull requests merged.
-
Media selectors w3c/web-annotation#202.
-
Selector fragment syntax change w3c/web-annotation#201.
-
TR publications
-
3 documents published.
-
Web Annotation Data Model published as a Working Draft. History of Web Annotation Data Model
-
Web Annotation Protocol published as a Working Draft. History of Web Annotation Protocol
-
Web Annotation Vocabulary published as a Working Draft. History of Web Annotation Vocabulary
-
Participants
-
1 organization joined.
-
Spec-Ops joined.
-
GitHub
w3c/web-annotation
-
12 issues opened.
-
Should oa:start / oa:end be xsd:nonNegativeInteger or xsd:integer ? w3c/web-annotation#200, by @stain.
-
Deref of namespace should go to vocab? w3c/web-annotation#199, by @azaroth42.
-
Exact syntax for the selectors-as-fragments w3c/web-annotation#197, by @iherman.
-
Can I refine a state via a selector? w3c/web-annotation#195, by @iherman.
-
Resolving http and https namespaces w3c/web-annotation#193, by @csarven.
-
Create a separate document for selectors as a note w3c/web-annotation#192, by @iherman.
-
value or text on the definition of an SVG selector w3c/web-annotation#191, by @iherman.
-
Change of document title: why? w3c/web-annotation#189, by @iherman.
-
Minor pre-publication issues (2016-03-19) w3c/web-annotation#186, by @iherman.
-
Usage of 'dc:' in the model document? w3c/web-annotation#185, by @iherman.
-
Link from AnnotationCollection to target(s) of included Annotations? w3c/web-annotation#184, by @azaroth42.
-
Terminology issue: Use IRI as resource identifier w3c/web-annotation#183, by @tkanai.
-
-
7 issues closed.
-
Resolving http and https namespaces w3c/web-annotation#193.
-
Create a separate document for selectors as a note w3c/web-annotation#192.
-
Minor pre-publication issues (2016-03-19) w3c/web-annotation#186.
-
Change of document title: why? w3c/web-annotation#189.
-
Make Selectors available for the wide world? w3c/web-annotation#110.
-
Link from AnnotationCollection to target(s) of included Annotations? w3c/web-annotation#184.
-
Write constraints document w3c/web-annotation#173.
-
-
18 issues received 99 new comments.
-
Resolving http and https namespaces w3c/web-annotation#193 (15 comments by @akuckartz, @azaroth42, @csarven, @halindrome, @iherman, @rtroncy, @stain)
-
Can I refine a state via a selector? w3c/web-annotation#195 (13 comments by @azaroth42, @iherman, @pciccarese, @tilgovi)
-
Terminology issue: Use IRI as resource identifier w3c/web-annotation#183 (11 comments by @akuckartz, @azaroth42, @iherman, @jjett, @tcole3, @tkanai)
-
Document annotation service endpoint rel w3c/web-annotation#174 (8 comments by @azaroth42, @BigBlueHat, @iherman)
-
value or text on the definition of an SVG selector w3c/web-annotation#191 (5 comments by @azaroth42, @iherman)
-
Link from AnnotationCollection to target(s) of included Annotations? w3c/web-annotation#184 (5 comments by @azaroth42, @BigBlueHat, @iherman)
-
Make Selectors available for the wide world? w3c/web-annotation#110 (4 comments by @azaroth42, @iherman)
-
Create reference set of correct/incorrect annotations for test development w3c/web-annotation#55 (3 comments by @azaroth42, @iherman)
-
Minor pre-publication issues (2016-03-19) w3c/web-annotation#186 (2 comments by @azaroth42, @iherman)
-
Publish a temporary testing JSON-LD context doc for use with JSON-LD Playground (etc) w3c/web-annotation#71 (2 comments by @azaroth42, @iherman)
-
-
6 pull requests opened.
-
Vocab namespaces section w3c/web-annotation#198, by @stain.
-
Added the selector note to the repo in a separate branch w3c/web-annotation#196, by @iherman.
-
Minor editorial comments w3c/web-annotation#194, by @iherman.
-
A few editorial changes w3c/web-annotation#190, by @paolociccarese.
-
Updating vocabulary w3c/web-annotation#188, by @stain.
-
oa.ttl - Specify W3C Document and Software license w3c/web-annotation#187, by @stain.
-
-
3 pull requests merged.
-
Minor editorial comments w3c/web-annotation#194.
-
Added the selector note to the repo in a separate branch w3c/web-annotation#196.
-
A few editorial changes w3c/web-annotation#190.
-
-
2 pull requests closed.
-
oa.ttl - Specify W3C Document and Software license w3c/web-annotation#187.
-
Proposed improvements on the terminology section of the model w3c/web-annotation#181.
-
-
5 pull requests received 40 new comments.
-
Updating vocabulary w3c/web-annotation#188 (17 comments by @azaroth42, @BigBlueHat, @iherman, @stain)
-
oa.ttl - Specify W3C Document and Software license w3c/web-annotation#187 (15 comments by @azaroth42, @iherman, @stain)
-
Proposed improvements on the terminology section of the model w3c/web-annotation#181 (1 comment by @azaroth42)
-
Participants
-
1 organization joined.
-
German Research Center for Artificial Intelligence (DFKI) Gmbh joined.
-
GitHub
w3c/web-annotation
-
31 issues opened.
-
Add warnings to xpath, css, and SVG selector usage w3c/web-annotation#182, by @iherman.
-
Is a JSON-LD library required? w3c/web-annotation#180, by @letmaik.
-
Acknowledgement section content and change section w3c/web-annotation#179, by @iherman.
-
Additional terms into the terminology section w3c/web-annotation#178, by @iherman.
-
Remove TextPositionSelector in favor of RangeSelector? w3c/web-annotation#177, by @azaroth42.
-
Can Collections embed their first Page? w3c/web-annotation#175, by @azaroth42.
-
Document annotation service endpoint rel w3c/web-annotation#174, by @azaroth42.
-
Write constraints document w3c/web-annotation#173, by @azaroth42.
-
Oxford comma... w3c/web-annotation#171, by @iherman.
-
CSS Selector usage comment w3c/web-annotation#170, by @iherman.
-
String Body unusual formatting in the example w3c/web-annotation#169, by @iherman.
-
Adding a good practice adding the format property for fragments w3c/web-annotation#168, by @iherman.
-
Do we allow the extension of clases? w3c/web-annotation#167, by @iherman.
-
Additional terminology issues: relationship, property, instance... w3c/web-annotation#166, by @iherman.
-
Conformance clause w3c/web-annotation#165, by @iherman.
-
Note in section 4.2.4 expansion? w3c/web-annotation#164, by @paolociccarese.
-
Note after fragments list table is not consistent w3c/web-annotation#163, by @paolociccarese.
-
Section 3.3.6 Example Use Case wording w3c/web-annotation#162, by @paolociccarese.
-
Type in Example Use Case in section 3.3.4 w3c/web-annotation#161, by @paolociccarese.
-
Creator "may be either a human or software agent" w3c/web-annotation#160, by @paolociccarese.
-
"created, modified or generated" might be confusing w3c/web-annotation#159, by @paolociccarese.
-
Fix formatting of EXAMPLE 6: String Body w3c/web-annotation#158, by @paolociccarese.
-
Clarification on sentence in section 3.2.5 w3c/web-annotation#157, by @paolociccarese.
-
Would change 'site' to 'website' in Use Case in section 3.2.2 w3c/web-annotation#156, by @paolociccarese.
-
Problem with Example Use Case in section 3.2.1 w3c/web-annotation#155, by @paolociccarese.
-
Extension Capacity w3c/web-annotation#154, by @azaroth42.
-
Range Selector w3c/web-annotation#153, by @tilgovi.
-
0-1 or 0-n string bodies w3c/web-annotation#150, by @azaroth42.
-
Language Literals not supported within the Body w3c/web-annotation#149, by @hugomanguinhas.
-
Validation of FragmentSelector Value w3c/web-annotation#148, by @azaroth42.
-
HTML Serialization Use Cases w3c/web-annotation#147, by @tcole3.
-
-
62 issues closed.
-
Multiple Selectors w3c/web-annotation#93.
-
Multiple States w3c/web-annotation#135.
-
Add warnings to xpath, css, and SVG selector usage w3c/web-annotation#182.
-
Using xsd:date, too, in the model? w3c/web-annotation#141.
-
Remove TextPositionSelector in favor of RangeSelector? w3c/web-annotation#177.
-
Range Selector w3c/web-annotation#153.
-
XPath Selector w3c/web-annotation#95.
-
Is a JSON-LD library required? w3c/web-annotation#180.
-
Additional terms into the terminology section w3c/web-annotation#178.
-
Can Collections embed their first Page? w3c/web-annotation#175.
-
Add JSON-LD Frame as informative annex w3c/web-annotation#80.
-
Annotation Lists w3c/web-annotation#50.
-
Do we allow the extension of clases? w3c/web-annotation#167.
-
Additional terminology issues: relationship, property, instance... w3c/web-annotation#166.
-
Referring to Content in RDF w3c/web-annotation#146.
-
Style selector vs. Styles w3c/web-annotation#144.
-
Intervals in time states? w3c/web-annotation#143.
-
Restriction on 'purpose' w3c/web-annotation#142.
-
Editorial issues on the model version 2016-01-16 w3c/web-annotation#140.
-
Definitions of Specific Resources: Example w3c/web-annotation#138.
-
Definition of specific resources: @Type w3c/web-annotation#137.
-
Language should use the Language Tags Vocabulary w3c/web-annotation#134.
-
Format should use the vocabulary of mime types w3c/web-annotation#133.
-
anno-ACTION-29: Create draft proposal for rendering state/selector w3c/web-annotation#117.
-
Clarification on sentence in section 3.2.5 w3c/web-annotation#157.
-
Adding a good practice adding the format property for fragments w3c/web-annotation#168.
-
CSS Selector usage comment w3c/web-annotation#170.
-
Oxford comma... w3c/web-annotation#171.
-
Note after fragments list table is not consistent w3c/web-annotation#163.
-
Fix formatting of EXAMPLE 6: String Body w3c/web-annotation#158.
-
"created, modified or generated" might be confusing w3c/web-annotation#159.
-
Creator "may be either a human or software agent" w3c/web-annotation#160.
-
Would change 'site' to 'website' in Use Case in section 3.2.2 w3c/web-annotation#156.
-
Problem with Example Use Case in section 3.2.1 w3c/web-annotation#155.
-
Type in Example Use Case in section 3.3.4 w3c/web-annotation#161.
-
Section 3.3.6 Example Use Case wording w3c/web-annotation#162.
-
Note in section 4.2.4 expansion? w3c/web-annotation#164.
-
String Body unusual formatting in the example w3c/web-annotation#169.
-
0-1 or 0-n string bodies w3c/web-annotation#150.
-
Associate license with content w3c/web-annotation#100.
-
Recommend StillImage instead of Image? w3c/web-annotation#18.
-
Annotation alsoKnownAs <uri> w3c/web-annotation#21.
-
Define json-ld profile URI for OA serialization context and structure w3c/web-annotation#30.
-
Make Turtle support optional? w3c/web-annotation#34.
-
Should all responses have the anno json-ld profile? w3c/web-annotation#39.
-
add reference to Annotation Protocol to Model w3c/web-annotation#47.
-
typo in Protocol: rdf:label w3c/web-annotation#77.
-
Simplifying hasBody w3c/web-annotation#79.
-
Annotation updated timestamp w3c/web-annotation#96.
-
Split model into vocab and model+json-ld w3c/web-annotation#97.
-
Allow >1 role per resource w3c/web-annotation#104.
-
Clarify "existing standards" in section 1.1 w3c/web-annotation#108.
-
Define the usage of ‘modified’ w3c/web-annotation#111.
-
Rename `role` to `motive` w3c/web-annotation#112.
-
Add `mbox_sha1sum` for the same reason(s) FOAF did w3c/web-annotation#115.
-
Clarify Selectors w3c/web-annotation#116.
-
Documentation error - language code in Example 17 is incorrect w3c/web-annotation#120.
-
No context description found in the JSON-LD "Complete Example" w3c/web-annotation#136.
-
item vs. member in multiplicity constructs w3c/web-annotation#145.
-
Multiplicity and Collections w3c/web-annotation#92.
-
Language Literals not supported within the Body w3c/web-annotation#149.
-
Validation of FragmentSelector Value w3c/web-annotation#148.
-
-
74 issues received 230 new comments.
-
Make Selectors available for the wide world? w3c/web-annotation#110 (23 comments by @azaroth42, @iherman, @jjett, @pciccarese, @tilgovi)
-
Language Literals not supported within the Body w3c/web-annotation#149 (19 comments by @azaroth42, @gsergiu, @hugomanguinhas, @iherman)
-
Language should use the Language Tags Vocabulary w3c/web-annotation#134 (11 comments by @azaroth42, @gsergiu, @hugomanguinhas, @iherman)
-
Using xsd:date, too, in the model? w3c/web-annotation#141 (9 comments by @akuckartz, @azaroth42, @iherman, @stain)
-
Publish a temporary testing JSON-LD context doc for use with JSON-LD Playground (etc) w3c/web-annotation#71 (8 comments by @azaroth42, @BigBlueHat, @hugomanguinhas, @iherman)
-
Keeping the OA ontology up to date w3c/web-annotation#66 (5 comments by @azaroth42, @iherman, @stain)
-
Definitions of Specific Resources: Example w3c/web-annotation#138 (5 comments by @azaroth42, @gsergiu)
-
Format should use the vocabulary of mime types w3c/web-annotation#133 (5 comments by @azaroth42, @gsergiu, @iherman)
-
0-1 or 0-n string bodies w3c/web-annotation#150 (5 comments by @akuckartz, @azaroth42, @hugomanguinhas, @iherman)
-
Is a JSON-LD library required? w3c/web-annotation#180 (4 comments by @azaroth42, @iherman, @letmaik)
-
Additional terminology issues: relationship, property, instance... w3c/web-annotation#166 (4 comments by @azaroth42, @iherman)
-
anno-ACTION-29: Create draft proposal for rendering state/selector w3c/web-annotation#117 (4 comments by @azaroth42, @BigBlueHat, @iherman)
-
Do we allow the extension of clases? w3c/web-annotation#167 (4 comments by @azaroth42, @iherman, @tilgovi)
-
Rename `role` to `motive` w3c/web-annotation#112 (4 comments by @azaroth42, @gsergiu, @hugomanguinhas)
-
Remove TextPositionSelector in favor of RangeSelector? w3c/web-annotation#177 (3 comments by @iherman, @tilgovi)
-
Note after fragments list table is not consistent w3c/web-annotation#163 (2 comments by @azaroth42, @paolociccarese)
-
Fix formatting of EXAMPLE 6: String Body w3c/web-annotation#158 (2 comments by @azaroth42, @paolociccarese)
-
"created, modified or generated" might be confusing w3c/web-annotation#159 (2 comments by @azaroth42, @paolociccarese)
-
Creator "may be either a human or software agent" w3c/web-annotation#160 (2 comments by @azaroth42, @paolociccarese)
-
Would change 'site' to 'website' in Use Case in section 3.2.2 w3c/web-annotation#156 (2 comments by @azaroth42, @paolociccarese)
-
Problem with Example Use Case in section 3.2.1 w3c/web-annotation#155 (2 comments by @azaroth42, @paolociccarese)
-
Clarification on sentence in section 3.2.5 w3c/web-annotation#157 (2 comments by @azaroth42, @paolociccarese)
-
Type in Example Use Case in section 3.3.4 w3c/web-annotation#161 (2 comments by @azaroth42, @paolociccarese)
-
Section 3.3.6 Example Use Case wording w3c/web-annotation#162 (2 comments by @azaroth42, @paolociccarese)
-
Documentation error - language code in Example 17 is incorrect w3c/web-annotation#120 (2 comments by @azaroth42, @iainsproat)
-
Define json-ld profile URI for OA serialization context and structure w3c/web-annotation#30 (2 comments by @akuckartz, @azaroth42)
-
Should all responses have the anno json-ld profile? w3c/web-annotation#39 (2 comments by @akuckartz, @azaroth42)
-
External: Reflect Protocol in Social Web Protocols document w3c/web-annotation#118 (1 comment by @azaroth42)
-
Adding a good practice adding the format property for fragments w3c/web-annotation#168 (1 comment by @azaroth42)
-
Client can't determine if user has authorization to modify annotation w3c/web-annotation#19 (1 comment by @azaroth42)
-
No context description found in the JSON-LD "Complete Example" w3c/web-annotation#136 (1 comment by @azaroth42)
-
-
5 pull requests opened.
-
Proposed improvements on the terminology section of the model w3c/web-annotation#181, by @iherman.
-
Collections w3c/web-annotation#176, by @azaroth42.
-
Fixes many editorial issues w3c/web-annotation#172, by @azaroth42.
-
Regularize cardinality descriptions w3c/web-annotation#152, by @azaroth42.
-
Add Annotation Frame, fix Context, typos ; #80 w3c/web-annotation#151, by @azaroth42.
-
-
4 pull requests merged.
-
Collections w3c/web-annotation#176.
-
Fixes many editorial issues w3c/web-annotation#172.
-
Regularize cardinality descriptions w3c/web-annotation#152.
-
Add Annotation Frame, fix Context, typos ; #80 w3c/web-annotation#151.
-
-
3 pull requests received 6 new comments.
-
Proposed improvements on the terminology section of the model w3c/web-annotation#181 (4 comments by @azaroth42, @iherman)
-
Participants
-
2 participants joined.
-
Paolo Ciccarese (W3C Invited Experts) joined.
-
Benjamin Young (Wiley) joined.
-
GitHub
w3c/web-annotation
-
15 issues opened.
-
Referring to Content in RDF w3c/web-annotation#146, by @iherman.
-
item vs. member in multiplicity constructs w3c/web-annotation#145, by @iherman.
-
Style selector vs. Styles w3c/web-annotation#144, by @iherman.
-
Intervals in time states? w3c/web-annotation#143, by @iherman.
-
Restriction on 'purpose' w3c/web-annotation#142, by @iherman.
-
Using xsd:date, too, in the model? w3c/web-annotation#141, by @iherman.
-
Editorial issues on the model version 2016-01-16 w3c/web-annotation#140, by @iherman.
-
Definitions of Specific Resources: Example w3c/web-annotation#138, by @gsergiu.
-
Definition of specific resources: @Type w3c/web-annotation#137, by @gsergiu.
-
No context description found in the JSON-LD "Complete Example" w3c/web-annotation#136, by @tkanai.
-
Multiple States w3c/web-annotation#135, by @azaroth42.
-
Language should use the Language Tags Vocabulary w3c/web-annotation#134, by @gsergiu.
-
Format should use the vocabulary of mime types w3c/web-annotation#133, by @gsergiu.
-
Add diagrams to Vocab examples w3c/web-annotation#131, by @azaroth42.
-
`account` likely to conflict with foaf:account w3c/web-annotation#130, by @azaroth42.
-
-
12 issues closed.
-
`account` likely to conflict with foaf:account w3c/web-annotation#130.
-
Selecting more than text w3c/web-annotation#107.
-
Allow pool of "tags" on Annotation w3c/web-annotation#86.
-
Ensure context terms do not collide with URI schemes w3c/web-annotation#126.
-
Intended Audience for Annotation w3c/web-annotation#8.
-
Model principles should state that inferencing is not a priority w3c/web-annotation#24.
-
TLDR prevention at beginning? of Protocol w3c/web-annotation#38.
-
Text Position Selector in the DOM w3c/web-annotation#59.
-
Protocol should include Accept-Post requirement from LDP w3c/web-annotation#85.
-
CSS Selector w3c/web-annotation#94.
-
Support for Notification w3c/web-annotation#49.
-
"Text class" not defined w3c/web-annotation#129.
-
-
35 issues received 161 new comments.
-
Multiple Selectors w3c/web-annotation#93 (26 comments by @azaroth42, @hugomanguinhas, @iherman, @jjett, @tilgovi)
-
Definition of specific resources: @Type w3c/web-annotation#137 (16 comments by @azaroth42, @csarven, @gobengo, @gsergiu, @iherman)
-
Selecting more than text w3c/web-annotation#107 (10 comments by @azaroth42, @BigBlueHat, @iherman, @tilgovi)
-
Using xsd:date, too, in the model? w3c/web-annotation#141 (9 comments by @akuckartz, @azaroth42, @iherman, @stain)
-
Justify each Motivation with a behavior w3c/web-annotation#113 (7 comments by @azaroth42, @BigBlueHat, @gsergiu, @iherman)
-
Annotation alsoKnownAs <uri> w3c/web-annotation#21 (6 comments by @azaroth42, @BigBlueHat, @iherman, @tilgovi)
-
Embedding annotations in the target document w3c/web-annotation#87 (5 comments by @azaroth42, @csarven, @iherman, @shepazu)
-
item vs. member in multiplicity constructs w3c/web-annotation#145 (5 comments by @BigBlueHat, @iherman, @jjett)
-
Add diagrams to Vocab examples w3c/web-annotation#131 (5 comments by @akuckartz, @csarven, @iherman, @jjett)
-
`account` likely to conflict with foaf:account w3c/web-annotation#130 (4 comments by @azaroth42, @iherman)
-
Allow pool of "tags" on Annotation w3c/web-annotation#86 (4 comments by @azaroth42, @iherman, @jjett)
-
Make Selectors available for the wide world? w3c/web-annotation#110 (4 comments by @azaroth42, @iherman, @tilgovi)
-
Language should use the Language Tags Vocabulary w3c/web-annotation#134 (4 comments by @azaroth42, @gsergiu, @iherman)
-
Format should use the vocabulary of mime types w3c/web-annotation#133 (4 comments by @azaroth42, @gsergiu, @iherman)
-
Definitions of Specific Resources: Example w3c/web-annotation#138 (3 comments by @azaroth42, @gsergiu)
-
Client can't determine if user has authorization to modify annotation w3c/web-annotation#19 (3 comments by @azaroth42, @fhirsch, @iherman)
-
No context description found in the JSON-LD "Complete Example" w3c/web-annotation#136 (2 comments by @azaroth42)
-
Create reference set of correct/incorrect annotations for test development w3c/web-annotation#55 (2 comments by @azaroth42, @iherman)
-
Ensure context terms do not collide with URI schemes w3c/web-annotation#126 (1 comment by @azaroth42)
-
anno-ACTION-29: Create draft proposal for rendering state/selector w3c/web-annotation#117 (1 comment by @azaroth42)
-
-
2 pull requests opened.
-
Update jsonld, fix date w3c/web-annotation#139, by @azaroth42.
-
Updates to Model and Vocab w3c/web-annotation#132, by @azaroth42.
-
-
3 pull requests merged.
-
Update jsonld, fix date w3c/web-annotation#139.
-
Updates to Model and Vocab w3c/web-annotation#132.
-
More examples: created, creator, homepage, name, nick, wasGeneratedBy… w3c/web-annotation#127.
-
-
1 pull request received 1 new comment.