Re: First Draft of ODRL 2 JSON Encoding published by ODRL Community Group

Good spotting, absolutely right. I've updated the examples accordingly.

Jonas

On Fri, Sep 27, 2013 at 7:51 PM, Myles, Stuart <SMyles@ap.org> wrote:
> Ř  So should (Policy) Type be "@type": "set" , as opposed to "@type":
> ["set"]?
>
>
>
> Yes – it should. The JSON schema is correct:
>
>
>
> "@type" : {
>
>       "description" : "Indicates the semantics of the Policy",
>
>       "type" : "string",
>
>       "required" : true
>
>     }
>
>
>
> But the examples are incorrect.
>
>
>
> Regards,
>
> Stuart
>
>
>
>
>
> From: Dave.Compton@thomsonreuters.com
> [mailto:Dave.Compton@thomsonreuters.com]
> Sent: Friday, September 27, 2013 4:03 AM
> To: ri@semanticidentity.com
> Cc: public-odrl@w3.org
> Subject: RE: First Draft of ODRL 2 JSON Encoding published by ODRL Community
> Group
>
>
>
>> 1. General: @type
>
>> This is shown as an array: "@type": ["set"]
>
>> Can a Policy have more than one Type?
>
>>
>
>> No, a Policy can be only one Type.
>
>
>
> So should (Policy) Type be "@type": "set" , as opposed to "@type": ["set"]?
>
> Rgds
>
> DC
>
>
>
> From: Renato Iannella [mailto:ri@semanticidentity.com]
> Sent: 27 September 2013 04:29
> To: Compton, Dave J. (TR Technology)
> Cc: public-odrl@w3.org
> Subject: Re: First Draft of ODRL 2 JSON Encoding published by ODRL Community
> Group
>
>
>
>
>
> On 26 Sep 2013, at 21:33, dave.compton@thomsonreuters.com wrote:
>
>
>
> 1. General: @type
>
> This is shown as an array: "@type": ["set"]
>
> Can a Policy have more than one Type?
>
>
>
> No, a Policy can be only one Type.
>
>
>
> 2. Example 1
>
> This shows "prohobition", but should be prohibition?
>
>
>
> Ok, typo fix.
>
>
>
> Cheers...
>
> Renato Iannella
>
> Semantic Identity
>
> http://semanticidentity.com
>
> Mobile: +61 4 1313 2206
>
>
>
>
> This email was sent to you by Thomson Reuters, the global news and
> information company. Any views expressed in this message are those of the
> individual sender, except where the sender specifically states them to be
> the views of Thomson Reuters.
>
> The information contained in this communication is intended for the use
> of the designated recipients named above. If the reader of this
> communication is not the intended recipient, you are hereby notified
> that you have received this communication in error, and that any review,
> dissemination, distribution or copying of this communication is strictly
> prohibited. If you have received this communication in error, please
> notify The Associated Press immediately by telephone at +1-212-621-1898
> and delete this email. Thank you.
> [IP_US_DISC]
>
>
> msk dccc60c6d2c3a6438f0cf467d9a4938

Received on Monday, 7 October 2013 07:48:56 UTC