• In the intro part, e.g., in 1.2, it may worth describing the terminology/editorial practice used for each concept, ie, what the various columns in the table are used for. Ie, the 'term' as used in JSON-LD, the type of the term, and the URI as used in the official vocabulary, ie, in RDF. • Actually, under the column 'Type', I presume what you call a 'Relationship' is what RDF calls an object property, and 'Property' is a data property. It may be worth describing those, too, in the terminology section, because it is not really clear. (And making a reference to the precise RDF terminology for the RDF people among us.) • I wonder whether it is not better to add a definition for what a Web Resource is. Surprisingly, there is no such definition around, I believe even Fielding's PhD talks of Resources only. In the DPUB IG we recently had to provide a definition[1], and this is what we use: • "A Web Resource is a digital resource that can be uniquely addressed by a Unified Resource Identifier (URI)[URI], and whose content can be accessed through standard network protocols like HTTP, FTP, or the File Protocol (i.e., based on the File URI Scheme[file-uri-scheme])" Also, systematically capitalizing the (Web) Resource in the text may make it clear that we are referring to something specific. Ivan [1] http://www.w3.org/TR/pwp/ <http://www.w3.org/TR/pwp/> ---- Ivan Herman, W3C Digital Publishing Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704
Received on Friday, 16 October 2015 11:47:04 UTC