ISSUE-36: Role and evolution of recommended JSON-LD contexts

JSON-LD contexts

Role and evolution of recommended JSON-LD contexts

State:
CLOSED
Product:
Activity Streams 2.0
Raised by:
Pavlik elf
Opened on:
2015-03-29
Description:
As of now we plan to recommend (normative?) JSON-LD @context. As one of main goals, it will allow people not interested in RDF view, to stay in comfort of flattened JSON-LD and use simple strings and pretty much ignore which URIs they map to.

By doing this we can map to all kind of vocabularies, while still providing experience for developers as they work with one consistent namespace.

We should also investigate how to keep such context evolving (v1, v2?) also as IG proposes new domain specific extensions. One possibility could use chain of JSON-LD context which together might provide convenience of working with flattened JSON-LD profile and consistent terminology.
Related Actions Items:
No related actions
Related emails:
  1. Re: Proposal: de-namespace vcard in the normative AS2 JSON-LD context (from perpetual-tripper@wwelves.org on 2015-04-30)
  2. Re: De-namespace *all stable* microformats and put them in Extended Voc? [was Re: Proposal: de-namespace vcard in the normative AS2 JSON-LD context] (from perpetual-tripper@wwelves.org on 2015-04-28)
  3. Re: Proposal: de-namespace vcard in the normative AS2 JSON-LD context (from perpetual-tripper@wwelves.org on 2015-04-23)
  4. Re: extension model of RSS/Atom (ISSUE-16 discussion) (from perpetual-tripper@wwelves.org on 2015-04-12)
  5. Re: social-ISSUE-36 (JSON-LD contexts): Role and evolution of recommended JSON-LD @contexts [Activity Streams 2.0] (from perpetual-tripper@wwelves.org on 2015-04-10)
  6. Re: Regular weekly meeting 7 Apr 2015 (from cwebber@dustycloud.org on 2015-04-07)
  7. Re: Regular weekly meeting 7 Apr 2015 (from perpetual-tripper@wwelves.org on 2015-04-07)
  8. Re: Regular weekly meeting 7 Apr 2015 (from lehors@us.ibm.com on 2015-04-07)
  9. Re: Regular weekly meeting 7 Apr 2015 (from evan@e14n.com on 2015-04-07)
  10. Re: Regular weekly meeting 7 Apr 2015 (from perpetual-tripper@wwelves.org on 2015-04-07)
  11. Re: AS2 Issues List (from jasnell@gmail.com on 2015-03-31)
  12. Re: AS2 Issues List (from perpetual-tripper@wwelves.org on 2015-03-31)
  13. AS2 Issues List (from jasnell@gmail.com on 2015-03-31)
  14. Fwd: Re: List of commonly used property names when used as *inverse*? (from perpetual-tripper@wwelves.org on 2015-03-30)
  15. Re: social-ISSUE-36 (JSON-LD contexts): Role and evolution of recommended JSON-LD @contexts [Activity Streams 2.0] (from perpetual-tripper@wwelves.org on 2015-03-29)
  16. Re: social-ISSUE-36 (JSON-LD contexts): Role and evolution of recommended JSON-LD @contexts [Activity Streams 2.0] (from perpetual-tripper@wwelves.org on 2015-03-29)
  17. social-ISSUE-36 (JSON-LD contexts): Role and evolution of recommended JSON-LD @contexts [Activity Streams 2.0] (from sysbot+tracker@w3.org on 2015-03-29)

Related notes:

danbri mentioned on twitter some interesting possibilities opened by JSON-LD @context https://twitter.com/danbri/status/574255292256509952

Pavlik elf, 29 Mar 2015, 16:54:01

Inverse properties - we could also just use JSON-LD @reverse instead of defining them in vocabulary(ies)
http://www.w3.org/TR/json-ld/#reverse-properties

Pavlik elf, 29 Mar 2015, 19:02:28

gh-issue#105
"Work": "vcard:Work" prone to confusion with with WorkAction

https://github.com/jasnell/w3c-socialwg-activitystreams/issues/105

Pavlik elf, 1 May 2015, 07:29:31

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 36.html,v 1.1 2018/02/22 10:33:30 carine Exp $