W3C home > Mailing lists > Public > public-credentials@w3.org > February 2015

Re: xAPI Badges integration(Including references to badge assertions in Experience API activity streams)

From: Nate Otto <nate@ottonomy.net>
Date: Wed, 4 Feb 2015 21:05:04 -0800
Message-ID: <CAPk0ugnhwrHWMmOy6eXEdJKRHQ+1u2=-=nY4FMduQ9qfmLxJ_w@mail.gmail.com>
To: Dave Longley <dlongley@digitalbazaar.com>
Cc: W3C Credentials Community Group <public-credentials@w3.org>

On Wed, Feb 4, 2015 at 3:08 PM, Dave Longley <dlongley@digitalbazaar.com>
> That sounds just like RDF. JSON-LD is an RDF syntax; if you want
> "triples" like "<subject> <predicate> <object>" then you simply use the
> JSON-LD toRDF API to convert any JSON-LD to that format. Also, the
> Social Web Working Group at W3C is working on Activity Streams and they
> use JSON-LD. It seems there may be some reinventing of existing or
> ongoing standards work at W3C going on here.

I think the xAPI spec
<https://github.com/adlnet/xAPI-Spec/blob/master/xAPI.md> was at least
heavily informed by the Activity Streams spec, though I don't know whether
xAPI is a fully compliant with Activity Streams, or which version if it is.
xAPI statements are JSON-based like,

    "id": "12345678-1234-5678-1234-567812345678",

(Sorry I used any punctuation at all in my previous message, I was just
quickly writing the idea as opposed to specific syntax).

I heard that the xAPI community is interested in adopting JSON-LD to move
forward, though their current spec already seems to have something really
close. Just a few things aren't quite right, like the lack of @contexts and
things like the "display" usage here aren't quite compatible with JSON-LD's
@languge keyword.

*Nate Otto, Developer*
Received on Thursday, 5 February 2015 05:05:32 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:38 UTC