- From: gsergiu via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Jan 2016 11:40:00 +0000
- To: public-annotation@w3.org
Well … I don’t say it is impossible. I say it is complicated and it is a must (one way or the other). So … I think these are legitimate questions: 1. Why should the client application (or serializer) drop the type information when it has it and the server (parser) try to guess it, when it can simply read it? 2. What are the arguments against making the type mandatory (when for any mapping tool this is mandatory information)? Are these arguments stronger than the simplicity of serialize/parse functionality? Br, Sergiu Von: Benjamin Goering [mailto:notifications@github.com] Gesendet: Dienstag, 19. Januar 2016 09:05 An: w3c/web-annotation Cc: Gordea Sergiu Betreff: Re: [web-annotation] Definition of specific resources: @Type (#137) @gsergiu<https://github.com/gsergiu> well ... should every parser and serializer implement some complicated rules in order to extract type which is already explicit in the client applications that create the annotation? Keep an eye on this Social WG Editor's Draft from @tantek<https://github.com/tantek> https://www.w3.org/wiki/Post-type-discovery — Reply to this email directly or view it on GitHub<https://github.com/w3c/web-annotation/issues/137#issuecomment-172770090>. -- GitHub Notification of comment by gsergiu Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/137#issuecomment-172825370 using your GitHub account
Received on Tuesday, 19 January 2016 11:40:03 UTC