Simplifying assumptions and suggested issue resolutions

We seem to be having a problem closing out issues on the issue tracker, and the meetings are too sparsely attended (IMO) to make real progress there. I think the time has come to make some simplifying assumptions that can allow us to move forward on some metadata issues:

#43 "ignore invalid metadata files located through link header" - resolve in favor, and treat like any other metadata files

#76 "Metadata Merge I" – resolve by agreeing to my merge language in PR #169 to merge all metadata sources.

#77 "Metadata Merge II" – resolve by agreeing to my merge language in PR #169 to merge all metadata sources.

#78 "Metadata Merge III" – resolve by agreeing to my merge language in PR #169 to merge all metadata sources.

#80 "JSON-LD context" – resolve as a string array of a string followed by an object, where the string MUST be "http://www.w3.org/ns/csvw". The object MAY contain @language and @base and MUST NOT contain any other values.

#81 "Should JSON-LD keywords be aliased" – "Resolve not to alias keywords"

#86 "schema term ambiguous" – resolve to rename the "schema" property to "tableSchema" to avoid confusion with schema.org

#93 "metadata and mapped data conflation" – Resolve to continue to use the #table fragment identifier on the table metadata @id to make these distinct. (Also, if it exists, the #tablegroup fragment on the TableGroup @id)

#96 "cell-value URI template" – Resolve as suggested in my last comment on that issue.

#98 "row reference" – resolve to always emit a csvw:rownum triple referencing the source row. We may later consider making this optional.

#101 "predicateUrl, urlTemplate and default" – See #96

#128 "language term ambiguous" – Remove alias of xsd:language

#136 "confusion on arrays and atomic values" – Resolve by agreeing to my merge language in PR #169 to merge all metadata sources.

#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.

#144 "Metadata merge order" – Resolve by agreeing to my merge language in PR #169 to merge all metadata sources.

#145 "overal metadata" – Resolve by agreeing to my merge language in PR #169 to merge all metadata sources.

#150 "Merge and common dc properties" – Resolve by agreeing to my merge language in PR #169 to merge all metadata sources.

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

#169 (PR) "Update merge semantics" – Accept PR but may tweak creation of embedded metadata to be independent of metadata @language.

#170 "Need for Core Tabular Data" – Resolve to only use annotated model for conversion as being essentially equivalent given merge model.

#171 (PR) "Specified formats for dates & times" – Accept PR with possible improvements later.

Furthermore, the following issues can simply be closed:

#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" – Resolve to close with no change.

#149 "@context explicit" – Duplicate of #80, and close the same way.


Thats more than enough for one go. Based on discussion, we can either resolve, close, or prioritize for next F2F meeting or telecon discussion.

If we can agree to some of these now, it will take a lot off of our plate, and give us the chance to make some headway between now and the F2F, which I think is important.

Gregg Kellogg
gregg@greggkellogg.net

Received on Wednesday, 21 January 2015 18:25:08 UTC