Tuesday, 30 June 2015
- Re: [web-annotation] Is fixing the list of fragment identifiers a good idea?
- Re: [web-annotation] Is fixing the list of fragment identifiers a good idea?
- Re: [web-annotation] Is fixing the list of fragment identifiers a good idea?
- Re: [web-annotation] Is fixing the list of fragment identifiers a good idea?
- [note]
Monday, 29 June 2015
Saturday, 27 June 2015
Friday, 26 June 2015
- CfC: publish FPWD of Web Annotation Protocol; concluded with support
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
Thursday, 25 June 2015
- RE: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [web-annotation] Is fixing the list of fragment identifiers a good idea?
- Re: [web-annotation] Is fixing the list of fragment identifiers a good idea?
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [web-annotation] Is fixing the list of fragment identifiers a good idea?
- Re: [web-annotation] Is fixing the list of fragment identifiers a good idea?
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- [web-annotation] Is fixing the list of fragment identifiers a good idea?
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- [note] Web Annotation Data Model
- [note] Web Annotation Data Model
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
Wednesday, 24 June 2015
- [testing] Sparql based model validation
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [web-annotation] Should all responses have the anno json-ld profile?
- Re: TPAC Double-Booking
- Re: TPAC Double-Booking
- Re: [web-annotation] Should all responses have the anno json-ld profile?
- Re: TPAC Double-Booking
- TPAC Double-Booking
- Meeting minutes, 2015-06-24...
- Re: [web-annotation] TLDR prevention at beginning? of Protocol
- Re: [web-annotation] TLDR prevention at beginning? of Protocol
- Re: [web-annotation] TLDR prevention at beginning? of Protocol
- Re: [web-annotation] Should all responses have the anno json-ld profile?
- anno-ACTION-21: Discuss testing and use of java vs python on ldp call
- RE: Agenda: Web Annotation Teleconference 24 June 2015
- Re: Agenda: Web Annotation Teleconference 24 June 2015
- RE: Agenda: Web Annotation Teleconference 24 June 2015
- Re: Chasing the Copy-Edit Use Case annotation
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Chasing the Copy-Edit Use Case annotation
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: JSON Serialization?
- Re: JSON Serialization?
- Re: JSON Serialization?
Tuesday, 23 June 2015
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: Reported to Social Web WG
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Reported to Social Web WG
- Re: JSON Serialization?
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: JSON Serialization?
- Re: JSON Serialization?
- Re: JSON Serialization?
- Re: JSON Serialization?
Monday, 22 June 2015
- Re: JSON Serialization?
- Agenda: Web Annotation Teleconference 24 June 2015
- Re: JSON Serialization?
- Re: JSON Serialization?
- Re: Agenda +Testing
- Re: JSON Serialization?
- Re: Agenda +Testing
- Re: JSON Serialization?
- Re: Agenda +Testing
- Re: JSON Serialization?
- Agenda +Testing
- Re: JSON Serialization?
- Re: CfC: publish FPWD of Web Annotation Protocol; respond by 25 June 2015
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
Sunday, 21 June 2015
- Re: [model] Modeling a Tweet: Tags
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
Saturday, 20 June 2015
Friday, 19 June 2015
- RE: client/server model
- Re: [web-annotation] TLDR prevention at beginning? of Protocol
- RE: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [web-annotation] Should all responses have the anno json-ld profile?
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- RE: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [web-annotation] Annotation Containers should permit non- ldp:BasicContainer
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- RE: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [web-annotation] Annotation Containers should permit non- ldp:BasicContainer
- Re: Annotate an image fragment inside a html page
- Re: [web-annotation] Annotation Containers should permit non- ldp:BasicContainer
- Re: [web-annotation] Annotation Containers should permit non- ldp:BasicContainer
Thursday, 18 June 2015
- Re: Annotate an image fragment inside a html page
- Re: Updated Protocol draft available
- Re: Updated Protocol draft available
- Re: [model] Modeling a Tweet: Tags
- Re: CfC: publish FPWD of Web Annotation Protocol; respond by 25 June 2015
- Re: [web-annotation] Should all responses have the anno json-ld profile?
- Re: [web-annotation] Should all responses have the anno json-ld profile?
- [web-annotation] Should all responses have the anno json-ld profile?
- Re: Updated Protocol draft available
- RE: [model] Why Motivations cannot be on Bodies
- Re: [model] Why Motivations cannot be on Bodies
- Re: [model] Why Motivations cannot be on Bodies
- Re: [model] Modeling a Tweet: Tags
- Re: [web-annotation] JSON-LD contexts for Model/Protocol
- Re: [web-annotation] TLDR prevention at beginning? of Protocol
- Re: [model] Modeling a Tweet: Tags
- Re: [model] Modeling a Tweet: Tags
- Re: [model] Modeling a Tweet: Tags
- Re: [model] Modeling a Tweet: Tags
- Re: Updated Protocol draft available
- Re: [model] Modeling a Tweet: Tags
- Re: [web-annotation] TLDR prevention at beginning? of Protocol
- Re: [model] Modeling a Tweet: Tags
- Re: [web-annotation] JSON-LD contexts for Model/Protocol
- Re: [model] Modeling a Tweet: Tags
- Re: [model] Modeling a Tweet: Tags
- Re: [model] Modeling a Tweet: Tags
- Re: [model] Modeling a Tweet: Tags
- Re: [model] Modeling a Tweet: Tags
- Re: [model] Why Motivations cannot be on Bodies
- Re: Updated Protocol draft available
- Re: [model] Modeling a Tweet: Tags
- [web-annotation] TLDR prevention at beginning? of Protocol
- RE: [model] Proposal: Allow motivatedBy on SpecificResource
- [web-annotation] Annotation Containers should permit non- ldp:BasicContainer
- Re: CfC: publish FPWD of Web Annotation Protocol; respond by 25 June 2015
- [web-annotation] JSON-LD contexts for Model/Protocol
- [web-annotation] JSON-LD Profile: Where?
- [web-annotation] Make Turtle support optional?
- [model] Why Motivations cannot be on Bodies
- Re: [web-annotation] Multiple JSON-LD Contexts
- Closed: [web-annotation] Multiple JSON-LD Contexts
- Re: [web-annotation] Non-Annotation Containers not in scope for Protocol
- Closed: [web-annotation] Non-Annotation Containers not in scope for Protocol
- Re: [model] Modeling a Tweet: Tags
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- RE: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: CfC: publish FPWD of Web Annotation Protocol; respond by 25 June 2015
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: Fwd: JSON Serialization?
- Re: Fwd: JSON Serialization?
- RE: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: Draft Minutes 17 June 2015 Annotation WG teleconference
- RE: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: CfC: publish FPWD of Web Annotation Protocol; respond by 25 June 2015
- Re: [model] Modeling a Tweet: Tags
- CfC: publish FPWD of Web Annotation Protocol; respond by 25 June 2015
Wednesday, 17 June 2015
Thursday, 18 June 2015
- Re: Updated Protocol draft available
- Re: Updated Protocol draft available
- Re: Updated Protocol draft available
- [model] Modeling a Tweet: Tags
- Re: [model] Proposal: Allow motivatedBy on SpecificResource
- Re: Fwd: JSON Serialization?
- Re: JSON Serialization?
- Fwd: JSON Serialization?
- Re: client/server model
- Updated Protocol draft available
Wednesday, 17 June 2015
- Re: JSON Serialization?
- RE: [model] Proposal: Allow motivatedBy on SpecificResource
- Draft Minutes 17 June 2015 Annotation WG teleconference
- RE: client/server model
- RE: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- JSON Serialization?
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: client/server model
Tuesday, 16 June 2015
- Re: The Copy-Edit Use Case
- [model] Proposal: Allow motivatedBy on SpecificResource
- RE: The Copy-Edit Use Case
- Re: The Copy-Edit Use Case
- RE: The Copy-Edit Use Case
- Re: The Copy-Edit Use Case
- Re: The Copy-Edit Use Case
- RE: The Copy-Edit Use Case
- RE: The Copy-Edit Use Case
- Re: client/server model
- Re: Activity Streams and Annotations
- RE: client/server model
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
Monday, 15 June 2015
- Re: client/server model
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: client/server model
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- RE: client/server model
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: client/server model
- client/server model
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- RE: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- RE: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- The Copy-Edit Use Case
Saturday, 13 June 2015
- Re: [protocol] Authentication
- Re: JSON-LD & N3
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: Agenda: Teleconference 17 June 2015
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: Resolution to defer Patch work
Friday, 12 June 2015
- Re: Resolution to defer Patch work
- Agenda: Teleconference 17 June 2015
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- RE: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- RE: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- JSON-LD & N3 - Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
Thursday, 11 June 2015
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: Educational Publishing Use Case
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Minutes of telco 2015-06-11
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- RE: Educational Publishing Use Case
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
Wednesday, 10 June 2015
- Fwd: [wbs] response to 'TR Design Survey'
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- TPAC 2015 Registration Now Open
- Re: CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Resolution to defer Patch work
- CfC: Resolution Annotation Protocol to make JSON-LD default returned if no HTTP Accept request header (deadline 24 June 2015)
- Re: Turtle Trouble (was: Re: [protocol] Patch formats)
- Re: Turtle Trouble
- Re: Turtle Trouble
- anno-ACTION-20: Follow up on json-ld resolution
- Re: [protocol] Authentication
- Re: Turtle Trouble (was: Re: [protocol] Patch formats)
- (Updated) Agenda Teleconference 10 June 2015 (v2)
- Re: Turtle Trouble (was: Re: [protocol] Patch formats)
- Re: Educational Publishing Use Case
- Re: Turtle Trouble (was: Re: [protocol] Patch formats)
- Re: Turtle Trouble (was: Re: [protocol] Patch formats)
- Re: Turtle Trouble (was: Re: [protocol] Patch formats)
- Re: Turtle Trouble (was: Re: [protocol] Patch formats)
- Re: Turtle Trouble (was: Re: [protocol] Patch formats)
Tuesday, 9 June 2015
Monday, 8 June 2015
- Re: [protocol] Authentication
- Re: Turtle Trouble (was: Re: [protocol] Patch formats)
- Re: Turtle Trouble (was: Re: [protocol] Patch formats)
- Re: [protocol] Authentication
- Turtle Trouble (was: Re: [protocol] Patch formats)
Saturday, 6 June 2015
Friday, 5 June 2015
- [protocol] Authentication
- Re: Question about body and motivatedBy
- [protocol] Patch formats
- Re: Question about body and motivatedBy
- Re: Question about body and motivatedBy
- Re: Draft Protocol question -- Creating a child basic container for annotations
- Re: Body as Named graph
Thursday, 4 June 2015
Wednesday, 3 June 2015
- Annotation meeting minutes - 2015-06-03
- RE: Draft Protocol question -- Creating a child basic container for annotations
- Educational Publishing Use Case
- Body as Named graph