AS2.0: JSON and/or RDF based?

Ahoy o/

I think we could try document this topic somewhere on a wiki. In recent
conversation on github with Erik[1] we stumbled upon again on topic of
conceptual model used in Activity Streams 2.0
https://www.w3.org/wiki/Socialwg/Social_Syntax_RDF

Personally I don't see conflict between JSON and RDF mostly thanks to
availability of JSON-LD. Currently AS2.0 not only uses JSON-LD but AS2.0
Vocabulary also takes advantage of RDFS and even OWL. Since we clearly
reuse established conceptual model, maybe we could clarify and document
adopted aspects?

I see it similar to adopting aspects of well established Link Relations,
in our API work for example. It will not conflict with charter JSON
requirement as far as I can tell. Further aligning Link Relations and
RDF[2] can make it all even more straight forward! Also LDP and Hydra,
both mentioned as API candidates, strongly incorporate both Linked Data
and Link Relations. Linked Data Fragments as well provide some solid
*hypermedia* REST read access interface. Last but not least - our
charter also mentions JSON-LD as potential data transfer syntax (-*LD*),
right after "describe the data using URIs in an extensible manner"...

JSON provides well adopted serialization but we still need to work with
conceptual models. While many efforts go into experiments with novel
approaches. I see both W3C and IndieWeb having strong tradition on
building upon existing and established work.

I hope it will not turn into a permathread but instead becomes focused
clarifying and documenting effort :)

Kudos!

[1]
https://github.com/openbadges/openbadges-specification/pull/22#issuecomment-73303945
[2] https://github.com/mnot/I-D/issues/39