Wednesday, 31 August 2016
- RE: testdev repository
- Re: Question about annotation IDs
- Re: Question about annotation IDs
- Re: Question about annotation IDs
- Question about annotation IDs
Tuesday, 30 August 2016
Monday, 29 August 2016
Friday, 26 August 2016
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- testdev repository
- Meeting minutes, 2016-08-26
- Re: Web Anno Agenda: Telco: 2016-08-26
- Re: If-Match and Weak ETags
- Changes to wptreport to improve the output
Thursday, 25 August 2016
- Web Anno Agenda: Telco: 2016-08-26
- Re: FW: [w3c/web-platform-tests] Annotation model first real tests (#3509)
Wednesday, 24 August 2016
- RE: If-Match and Weak ETags
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] ed sugg: textDirection
- Re: [web-annotation] ed sugg: textDirection
- FW: [w3c/web-platform-tests] Annotation model first real tests (#3509)
- Re: [web-annotation] processLanguage description improvement suggestion
- Re: [web-annotation] Processing language for mono-lingual and internationalized resources
- Re: [web-annotation] Processing language for multilingual resources
Tuesday, 23 August 2016
- Closed: [web-annotation] Requirements for Agents
- Re: [web-annotation] Requirements for Agents
- Re: [web-annotation] TextPositionSelector, thoughts about Unicode code *point* vs. UTF16 code *unit*
- Re: [web-annotation] Avoid mixed-content error with JSON-LD context in HTTPS
- Re: [web-annotation] Avoid mixed-content error with JSON-LD context in HTTPS
- Re: [web-annotation] ed sugg: textDirection
- Re: [web-annotation] TextPositionSelector, thoughts about Unicode code *point* vs. UTF16 code *unit*
Monday, 22 August 2016
- Re: [web-annotation] TextPositionSelector, thoughts about Unicode code *point* vs. UTF16 code *unit*
- Re: [web-annotation] TextPositionSelector, thoughts about Unicode code *point* vs. UTF16 code *unit*
- Re: [web-annotation] TextPositionSelector, thoughts about Unicode code *point* vs. UTF16 code *unit*
- Re: [web-annotation] TextPositionSelector, thoughts about Unicode code *point* vs. UTF16 code *unit*
- [web-annotation] TextPositionSelector, thoughts about Unicode code *point* vs. UTF16 code *unit*
- Re: If-Match and Weak ETags
Sunday, 21 August 2016
Friday, 19 August 2016
- Tests pushed
- Minutes of meeting 2016-08-19
- Re: [web-annotation] ed sugg: textDirection
- Re: [web-annotation] Requirements for Agents
- Re: [web-annotation] ed sugg: textDirection
- Re: [web-annotation] Requirements for Agents
- RE: Annotation Model - Testing Annotation Keys
- Re: Annotation Model - Testing Annotation Keys
- Re: Web Anno Agenda: Telco: 2016-08-19
- Annotation Model - Testing Annotation Keys
Thursday, 18 August 2016
- Re: Making the annotation tests more informative
- Re: Making the annotation tests more informative
- Web Anno Agenda: Telco: 2016-08-19
- Re: Making the annotation tests more informative
- RE: Making the annotation tests more informative
Wednesday, 17 August 2016
- RE: Making the annotation tests more informative
- Re: [web-annotation] Requirements for Agents
- Re: [web-annotation] ed sugg: textDirection
- Re: [web-annotation] Requirements for Agents
- [web-annotation] Requirements for Agents
Tuesday, 16 August 2016
- Re: [web-annotation] ed sugg: textDirection
- Re: [web-annotation] Avoid mixed-content error with JSON-LD context in HTTPS
- [web-annotation] ed sugg: textDirection
- Re: [web-annotation] Processing language for mono-lingual and internationalized resources
- Re: [web-annotation] Avoid mixed-content error with JSON-LD context in HTTPS
- Re: [web-annotation] Avoid mixed-content error with JSON-LD context in HTTPS
- Re: [web-annotation] Avoid mixed-content error with JSON-LD context in HTTPS
- Closed: [web-annotation] Protocol examples should use comma separated headers in examples
- Closed: [web-annotation] Container Representations section should be more demanding
- Re: [web-annotation] Protocol Paging content editorial restructuring
- Re: [web-annotation] Avoid mixed-content error with JSON-LD context in HTTPS
Friday, 12 August 2016
- Re: [web-annotation] processLanguage description improvement suggestion
- Re: [web-annotation] processLanguage description improvement suggestion
- [web-annotation] Avoid mixed-content error with JSON-LD context
- Re: [web-annotation] processLanguage description improvement suggestion
- Making the annotation tests more informative
- Re: Agenda: Telco 2016-08-12
- Meeting minutes, 2016-08-12
- [web-annotation] Add info about which Media Type to Model
- Re: [web-annotation] Processing language for multilingual resources
- Agenda: Telco 2016-08-12
- RE: annotation data model -- running test scripts
- Re: annotation data model -- running test scripts
- Re: annotation data model -- running test scripts
- Re: [web-annotation] processLanguage description improvement suggestion
- Re: [web-annotation] Relationship between dc:language and processing language for multilingual resources
- Re: [web-annotation] Relationship between dc:language and processing language for multilingual resources
- [web-annotation] processLanguage description improvement suggestion
- Re: [web-annotation] Relationship between dc:language and processing language for multilingual resources
- Re: [web-annotation] Relationship between dc:language and processing language for multilingual resources
- Re: [web-annotation] Relationship between dc:language and processing language for multilingual resources
- Re: [web-annotation] Relationship between dc:language and processing language for multilingual resources
- Re: [web-annotation] Processing language for multilingual resources
- Re: [web-annotation] Relationship between dc:language and processing language for multilingual resources
- Re: [web-annotation] Relationship between dc:language and processing language for multilingual resources
- RE: annotation data model -- running test scripts
Thursday, 11 August 2016
- Re: annotation data model -- running test scripts
- Re: [web-annotation] Legal IRI for Annotation Containers
- Re: [web-annotation] Legal IRI for Annotation Containers
- Re: [web-annotation] Legal IRI for Annotation Containers
- annotation data model -- running test scripts
- Re: [web-annotation] Legal IRI for Annotation Containers
- Re: [web-annotation] Relationship between dc:language and processing language for multilingual resources
- Re: [web-annotation] Processing language for multilingual resources
- Re: [web-annotation] Legal IRI for Annotation Containers
- [web-annotation] Legal IRI for Annotation Containers
Tuesday, 9 August 2016
- Re: [web-annotation] Relationship between dc:language and processing language for multilingual resources
- [web-annotation] Relationship between dc:language and processing language for multilingual resources
- [web-annotation] Processing language for mono-lingual and internationalized resources
- Re: [web-annotation] Cardinality of the processingLanguage?
- [web-annotation] Processing language for multilingual resources
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Replace textDirection property with recommendation for including control characters in the text
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] Cardinality of the processingLanguage?
Monday, 8 August 2016
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Cardinality of the processingLanguage?
- Closed: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
Sunday, 7 August 2016
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
Saturday, 6 August 2016
Friday, 5 August 2016
- Re: [web-annotation] Fix 333 multiple http headers
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- [web-annotation] Clarify scope of the key 'purpose' in Section 3.3.5
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Replace textDirection property with recommendation for including control characters in the text
- Closed: [web-annotation] Replace textDirection property with recommendation for including control characters in the text
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Minutes of meeting, 2016-08-05
- [web-annotation] Clarify principle that features of external resources are not authoritative
- Re: [web-annotation] Fix 333 multiple http headers
- Re: [web-annotation] Replace textDirection property with recommendation for including control characters in the text
- Re: [web-annotation] Replace textDirection property with recommendation for including control characters in the text
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] Replace textDirection property with recommendation for including control characters in the text
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- [web-annotation] Cardinality of the processingLanguage?
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
Thursday, 4 August 2016
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] Replace textDirection property with recommendation for including control characters in the text
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- [web-annotation] Replace textDirection property with recommendation for including control characters in the text
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Agenda: Telco 2016-08-05
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] Next/Prev are untestable
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
Wednesday, 3 August 2016
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] Next/Prev are untestable
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] Next/Prev are untestable
- Re: [web-annotation] How do we model "groups" in the Annotation model?
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
Tuesday, 2 August 2016
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] The textDirection and processingLanguage properties are not needed
- [web-annotation] The textDirection and processingLanguage properties are not needed
- Re: [web-annotation] Protocol examples should use comma separated headers in examples
- Re: [web-annotation] Protocol examples should use comma separated headers in examples
- Re: [web-annotation] Protocol examples should use comma separated headers in examples
Monday, 1 August 2016
- Re: [web-annotation] Protocol examples should use comma separated headers in examples
- Re: [web-annotation] MUST ETag on GET, but only SHOULD If-Match on PUT and DELETE
- Re: [web-annotation] MUST ETag on GET, but only SHOULD If-Match on PUT and DELETE
- Re: progress on schemas for model testing
- Re: progress on schemas for model testing