Update patch set 4

Patch Set 4:

Which consumers consume this already, and care about it being

> consumable in a different way?
>
> As far as I’m aware, no consumers could consume this already, since
> we haven’t made a Purtle release with JSON-LD support yet, and
> don’t yet offer it on Wikidata.

That's right.

> > I wouldn't say it's easier, in fact it's more complicated because
> of the aliasing introduced. You can not just query a "title"
> attribute and assume it does have the same semantics as
> "contact:title" – you can only be sure about this by also
> processing the alias!
>
> As far as I understand, this was strictly speaking true before,
> because "contact:title" could also have been aliased to something
> else. For example: http://tinyurl.com/yb9fjqr4
>
> For any JSON-LD compliant client, this should make no difference.
> For any other client, the resulting JSON should now be easier to
> consume. That seems like a good thing to me.

Yes, exactly.

> Scott: I see different email addresses in the author and committer,
> is that intentional?

Whoops. Fixed.

Re T164655 -- there is a long-ish term project to improve media annotations on commons, and in particular to use semantic annotations which are tied to wikidata items. These annotations would need to reference properties defined on wikidata -- for example:

<region of this image> <is image of gravestone of (P1442)> <Douglas Adams (Q42)>

In order to format this annotation correctly, in W3C-standard JSON-LD format, I need a JSON-LD URI corresponding to P1442 and Q42... which is related to the EPIC task of exporting wikidata information in Linked Data format.

Patch-set: 4