- From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Date: Thu, 9 May 2013 00:58:36 +0100
- To: James Smith <jgsmith@gmail.com>
- Cc: public-openannotation <public-openannotation@w3.org>
On 8 May 2013 18:22, James Smith <jgsmith@gmail.com> wrote: >> cnt:charEncoding should be cnt:characterEncoding - it is useful to > This was a typo on my part in transcribing to email. The code has cnt:characterEncoding for the RDF/JSON production. I've dropped it from the JSON-LD version since JSON-LD strings are Unicode, the Unicode encoding (UTF-8, -16, ...) presumably holds for the entire JSON-LD document, and I didn't see it in the suggested context while I did see other properties from the cnt: namespace. No, it is not really needed, as by its definition it is more of a provenance thing, like "I read this string from a file and assumed this encoding"; which probably is not true as you are generating the SVG. > I'm targeting JSON-LD at this point. This is a JavaScript application living in the browser, so I figure JSON-LD is a natural fit for that aspect of a video annotation system. I'll leave RDF/XML as an exercise for a server component. (as JSON-LD supporter) Great! Then I guess you should stay far away from Content as XML ;) -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester http://soiland-reyes.com/stian/work/
Received on Wednesday, 8 May 2013 23:59:23 UTC