Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is @context really an array property? #860

Open
mgoodhand opened this issue Sep 6, 2017 · 3 comments
Open

Is @context really an array property? #860

mgoodhand opened this issue Sep 6, 2017 · 3 comments

Comments

@mgoodhand
Copy link

An apparent discrepancy in https://www.w3.org/TR/2015/REC-tabular-metadata-20151217 ...

§ 5.2 Top-Level Properties says

The top-level object of a metadata document or object referenced through an object property (whether it is a table group description, table description, schema, dialect description or transformation definition) must have a @context property. This is an array property, as defined in Section 8.7 of [JSON-LD]

'array property' is a link to § 5.1.1 Array Properties, which says

Array properties hold an array of one or more objects, which are usually description objects.

But @context doesn't fit this definition (array of objects). It is either a simple string (with fixed value 'http://www.w3.org/ns/csvw') or a heterogenous array of length 2, containing the string 'http://www.w3.org/ns/csvw' followed by an object.

I checked Section 8.7 of [JSON-LD] to see if it had an alternative definition of 'array property', but it seems to describe the local context, rather than the allowed content of @context as a whole.

I may be missing something, but @context seems special enough that it's not helpful to describe it as an array property.

Perhaps change

This is an array property, as defined in Section 8.7 of [JSON-LD].

to something like

This specification allows a restricted form of the @context defined in [JSON-LD].

@gkellogg
Copy link
Member

gkellogg commented Sep 6, 2017

I agree that it was a stretch to try to describe the local context as being an array property. We might need to tighten up your replace your suggested replacement, though.

@iherman
Copy link
Member

iherman commented Sep 7, 2017

Summary: Tighten up the text.

@mgoodhand
Copy link
Author

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants