- From: Erik Wilde <dret@berkeley.edu>
- Date: Thu, 13 Nov 2014 17:29:56 +0100
- To: James M Snell <jasnell@gmail.com>, "public-socialweb@w3.org" <public-socialweb@w3.org>
- CC: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>, Owen Shepherd <owen.shepherd@e43.eu>, Markus Lanthaler <markus.lanthaler@gmx.net>
hello james. On 2014-11-13, 16:54, James M Snell wrote: > Requiring an RDF world view would be a mistake. Use of JSON-LD does > not require us to take that view. It does, however, enable those who > want to take that view to do so. that sounds excellent to me. the best way to make sure we do this cleanly, in my view, would be to keep AS2 the way AS1 was defined, with the "AS infoset" being described in the AS2 spec itself. then there would be an additional "processing AS2 as RDF" spec that would be clearly and cleanly layered on top of the AS2 core spec, and would explain how users interested in taking an RDF view of AS can do so. the AS2 core syntax just would have to make sure it has the necessary JSON-LD hooks so that this is possible. to me, this would mean that JSON-minded implementers could simply work with the AS2 core spec and it would explain everything they need to know. RDF-minded implementers could work with the "AS2-as-RDF" spec and it would explain everything they need to know. regardless of our own opinions and preferences, there is a *huge* developer base out there that is craving for easy-to-use JSON services, and could be easily distracted and confused if we tell them that it looks like JSON, but really has to be subject to all the rules that are inherited via JSON-LD from RDF. if we layer things right, we can serve that community, and the RDF-minded folks are served as well. > That said, in order to define that minimal vocabulary, we > need a minimal set of basic use cases from which to build around. The > work that Erik has been doing looking at the AS1 base schema is a > great start. http://dret.github.io/W3C/SocialWG/AS1-in-AS2.html looks a little different know, but is still looking for input. how can we make progress on this, after evan gave us such a good starting point with the list of supported concepts in pump.io? thanks and cheers, dret. -- erik wilde | mailto:dret@berkeley.edu - tel:+1-510-2061079 | | UC Berkeley - School of Information (ISchool) | | http://dret.net/netdret http://twitter.com/dret |
Received on Thursday, 13 November 2014 16:29:05 UTC