Skip to content

Basic: Enumerate the goals of the syntax more clearly #3

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

Closed
msporny opened this issue Jun 28, 2011 · 1 comment
Closed

Basic: Enumerate the goals of the syntax more clearly #3

msporny opened this issue Jun 28, 2011 · 1 comment

Comments

@msporny
Copy link
Member

msporny commented Jun 28, 2011

Gregg Kellogg wrote:

  • Straight-forward representation of data in JSON using forms based on existing practice,
  • Ability to represent data as triples (subject-predicate-object or entity-attribute-value),
  • Ability to supplement with additional semantic information (e.g., @context for defining terms, prefixes and datatypes),
  • Compatible with RDF data representations,
  • Use of simple terms as attribute names,
  • No requirement to provide datatyping information of values explicitly within representation (but ability to do so),
  • Ability to represent relationship between an entity and one or more other entities, either by referencing document as a URI, to a representation included within the JSON-LD document, or as a sub-element of another entity
@msporny
Copy link
Member Author

msporny commented Nov 29, 2011

This is a very old bug... the goals of the syntax have been clearly outlined for some time now. Closing the issue.

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

1 participant