Re: [poe] Support JSON-LD

Apologies for the delay in getting back to you on this. I was out of 
the
office yesterday.

A couple of things...

The JSON-LD @context that I provided *does* support scopes being 
mapped
into the RDF equivalent, so it doesn't look we need a change there.

However, in the process of looking more closely at how the "scope" 
property
is defined in the ODRL 2.2 ontology, I think there may be a bug there?
 Here
is the TTL:

:scope
a rdf:Property , owl:ObjectProperty ;
rdfs:isDefinedBy odrl: ;
rdfs:label "Scope"@en ;
skos:definition "The identifier of a scope that provides context to 
the
extent of the entity."@en ;
skos:note "Used to define scopes for Assets and Parties."@en ;
rdfs:range [
a owl:Class ;
owl:unionOf ( :Asset :Party ) ;
] .

As I understand it, that means that the value of :scope must be either
Asset or Party. But surely it should be :PartyScope?

(I will also respond to your request to alter all of the property 
names and
of "complexifying" the JSON structure - but that is a different 
thread).

Regards,

Stuart


On Thu, Feb 16, 2017 at 7:54 PM, Renato Iannella 
<notifications@github.com>
wrote:

> What about all the Classes?
>
> Should we support:
>
>     "assignee": [{
>             "@type": [ "odrl:Party", "vcard:Organisation"],
>             "@id": "http://example.com/org44/",
>             ...
>     }]
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/poe/issues/46#issuecomment-280515609>, or 
mute
> the thread
> 
<https://github.com/notifications/unsubscribe-auth/ADwBfwAs0bORtbhSGlgTGJFD2JIMwqcuks5rdO_BgaJpZM4KZWR0>
> .
>


-- 
GitHub Notification of comment by stuartmyles
Please view or discuss this issue at 
https://github.com/w3c/poe/issues/46#issuecomment-281419688 using your
 GitHub account

Received on Tuesday, 21 February 2017 17:42:44 UTC