Suggestions for tomorrow's telecon

Issue #96 (PR #187): Use of aboutUrl, propertyUrl and valueUrl. (should be able to close #101).

Issue #184 (PR #185): Schema merge should match column values where language is `und` to those with a language. This has implications for embedded metadata, and if `und` values in title are removed if they match a language-specific value.

Issue #186: propertyUri can have multiple values, but RDF column metadata assumes one. General discussion on metadata in RDF.

Issue #64: suppression of columns in mapping; this also relates to issue #179 on phantom columns.

Issue #170: Reconsider Need for Core Tabular Data Model (in transformations). This seems to be unnecessary given process for created embedded metadata.

Issue #175: Need default metadata. Also, there should be a normative spec for extracting embedded metadata in syntax doc.

Issue #182: Fall-back value of the `name` property. I think this is clear from current wording, and doesn't need much discussion.

Issue #183: Property value of Natural Language property should return all language values: also clear as defined in current wording.

Left over from last weeks list:

#142 "value space for common properties" – Resolve to allow just the six forms of literals and URIs described in that issue, and not more involved JSON-LD content.

#166 "datatype handling and template expansion" – Resolve to use post-conversion values without performing value separation.

#22 "type vs datatype" - no change

#87 "title term ambiguous" – Close with no change.

#97 "property name for row relation to table" – Close, as we have settled on csvw:row.

#113 "csvw:Table in output conflation"

#116 "Blank node shorthand"







Gregg Kellogg
gregg@greggkellogg.net

Received on Tuesday, 3 February 2015 19:27:09 UTC