Fwd: Error in the example 21 of Typed Values

Gregg, 

is there something we can take in our current work, and then closing it on the RDF WG level?

Ivan

---
Ivan Herman
Tel:+31 641044153
http://www.ivan-herman.net

(Written on mobile, sorry for brevity and misspellings...)



Begin forwarded message:

> Resent-From: public-rdf-comments@w3.org
> From: "Michael Steidl \(NIT\)" <mwsteidl@newsit.biz>
> Date: 29 August 2018 at 14:13:47 GMT+2
> To: <public-rdf-comments@w3.org>
> Subject: Error in the example 21 of Typed Values
> 
> Hi all,
>  
> I had a look at the examples of Typed Values https://www.w3.org/TR/json-ld/#typed-values
> and got confused by Example 21 vs Example 23
>  
> The narrative below Example 23 explains:
> As a general rule, when @value and @type are used in the same JSON object, the @type keyword is expressing a value type. Otherwise {if @id is present in the object}, the @type keyword is expressing a node type.
>  
> Sections 8.2 and 8.3 of the specification support that view at a formal level.
>  
> The JSON-LD code of example 23 and the comments in grey align to that.
>  
> But Example 21 shows as code
> "modified":
>     {
>       "@id": "http://purl.org/dc/terms/modified",
>       "@type": "http://www.w3.org/2001/XMLSchema#dateTime"
>     }
> and explains by a table below it that a JSON-LD processor will interpret this code as @type defines the type of the value of modified.
> This is a clear contradiction to the explanation below Example 23.
>  
>  
> Please clarify if my view is wrong or if example 21 has an error.
>  
> Thanks,
> Michael
>  
>  
> Michael Steidl
> Lead of the Photo Metadata and Video Metadata
> Working Groups of IPTC (www.iptc.org)
> Email: mwsteidl@newsit.biz
>  
>