- From: Renato Iannella via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Jul 2017 00:40:11 +0000
- To: public-poe-archives@w3.org
riannella has just labeled an issue for https://github.com/w3c/poe as "Model": == Does the JSON-LD serialization distinguish human-readable and machine-readable strings for DC terms? == From: @bert-github Source: https://lists.w3.org/Archives/Public/public-poe-comments/2017Jul/0001.html Hello POE WG, [This is a personal comment, not related to the i18n review of my other e-mail.] The JSON-LD encoding allows Dublin Core annotations. There is an example of such an annotation in the section "Policy metadata"[1] in the "ODRL Information Model". However, the Dublin Core terms "creator", "coverage" and "description" can, in general, contain either human-readable text or machine-readable text (such as a URL) and ODRL does not explain how the two are distinguished in the JSON-LD encoding. The example, in fact, shows two URLs, but doesn't use the JSON-LD key "@id" to type them as URLs. Shouldn't it be something like ... "dc:coverage": { "@id": "https://www.iso.org/obp/ui/#iso:code:3166:AU-QLD" } ... Also (but maybe this is just a typo), Dublin Core recommends the W3CDTF profile of ISO 8601 for dates, so maybe the example would be better with a "T" instead of a ":" in the middle: "dc:issued": "2017-01-01T12:00" instead of "dc:issued": "2017-01-01:12:00" [1] https://w3c.github.io/poe/model/#provenace See https://github.com/w3c/poe/issues/213
Received on Friday, 21 July 2017 00:40:12 UTC