You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 2, 2019. It is now read-only.
My bets go out to: http://jsonapi.org (for the fundamental layer)
And/or: http://json-ld.org (on top of it and later to blend well with semantic web ideas)
It's not necessary to strictly adhere to them since we have to optimize for a very specific case (lots of list-like representations with a finite typology), but if those standards don't interfere it's best to follow them from the onset.
The text was updated successfully, but these errors were encountered:
From conversation with Shane:
It is not always guaranteed that the 'value', i.e. column header is a unique string even if tables are parsed 100% accurate (could be empty) and fabricating artificial headers like 'column_1' is not an elegant. Thus, one minimum improvement is to include a unique key into the array of meta-data in the returned data.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
My bets go out to: http://jsonapi.org (for the fundamental layer)
And/or: http://json-ld.org (on top of it and later to blend well with semantic web ideas)
It's not necessary to strictly adhere to them since we have to optimize for a very specific case (lots of list-like representations with a finite typology), but if those standards don't interfere it's best to follow them from the onset.
The text was updated successfully, but these errors were encountered: