As described in issue #184, allow columns to match if they share a title... #185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tle, where `und` matches any language title.
| @@ -1200,7 +1200,7 @@ | |||
| <p> | |||
| An <a>atomic property</a> that gives a single canonical name for the column. This MUST be a string. Conversion specifications MUST use this property as the basis for the names of properties/elements/attributes in the results of conversions. | |||
| </p> | |||
| <p>The <a>property value</a> of <code>name</code> is that defined within metadata, if it exists. Otherwise, it is the first <a>property value</a> of <code>title</code> as a string without language, if any. Otherwise, it is the string <code>"_col=<em>[N]</em>"</code> where <code><em>[N]</em></code> is the <a href="http://www.w3.org/TR/tabular-data-model/#dfn-column-number">column number</a>. | |||
| <p>The <a>property value</a> of <code>name</code> is that defined within metadata, if it exists. Otherwise, it is the first value from the <a>property value</a> of <code>title</code> having the same language tag as <a>default language</a> or <code>und</code> of not specified, as a string without language, if any. Otherwise, it is the string <code>"_col=<em>[N]</em>"</code> where <code><em>[N]</em></code> is the <a href="http://www.w3.org/TR/tabular-data-model/#dfn-column-number">column number</a>. | |||
There was a problem hiding this comment.
Don't we need a normalisation of any name that originates from the title?
There was a problem hiding this comment.
I think we do...
Ivan
On 04 Feb 2015, at 12:35 , Jeni Tennison notifications@github.com wrote:
In metadata/index.html:
@@ -1200,7 +1200,7 @@
An atomic property that gives a single canonical name for the column. This MUST be a string. Conversion specifications MUST use this property as the basis for the names of properties/elements/attributes in the results of conversions.
<p>The <a>property value</a> of <code>name</code> is that defined within metadata, if it exists. Otherwise, it is the first <a>property value</a> of <code>title</code> as a string without language, if any. Otherwise, it is the string <code>"_col=<em>[N]</em>"</code> where <code><em>[N]</em></code> is the <a href="http://www.w3.org/TR/tabular-data-model/#dfn-column-number">column number</a>.<p>The <a>property value</a> of <code>name</code> is that defined within metadata, if it exists. Otherwise, it is the first value from the <a>property value</a> of <code>title</code> having the same language tag as <a>default language</a> or <code>und</code> of not specified, as a string without language, if any. Otherwise, it is the string <code>"_col=<em>[N]</em>"</code> where <code><em>[N]</em></code> is the <a href="http://www.w3.org/TR/tabular-data-model/#dfn-column-number">column number</a>.Don't we need a normalisation of any name that originates from the title?
—
Reply to this email directly or view it on GitHub.
Ivan Herman, W3C
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704
JeniT
pushed a commit
that referenced
this pull request
Feb 4, 2015
As described in issue #184, allow columns to match if they share a title...
gkellogg
added a commit
to ruby-rdf/rdf-tabular
that referenced
this pull request
Feb 4, 2015
* Return all natural language property (title) metadata, not just for default language. * Don't set @language or lang on embedded metadata * Exclude titles with `und` where that title exists with a language. * When merging match titles where `und` is a language wild-card. * use `aboutUrl`, `propertyUrl` and `valueUrl` as inherited properties which are URI template properties. * change `language` to `lang` to not confuse with `xsd:language` term. * change `schema` to `tableSchema` to not confuse with `http://schema.org/` prefix. * use `url` property instead of `@id` to reference CSVs and templates. * Row now gives an array of Cell, which reference column metadata and include expanded about, property, and value URLs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
..., where
undmatches any language title.