Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Nov 13, 2012
  1. JSON-LD document definition: dropped reference to Linked Data.

    François Daoust committed
    "Linked Data" is not normatively defined so shouldn't be referenced
    from the JSON-LD document definition in the Conformance section. I
    had put the reference only to have some informative description of
    what a JSON-LD document is, but that's already expressed in the
    introduction anyway.
Commits on Nov 9, 2012
  1. Dropped all references to "JSON-LD processor" from the text.

    François Daoust committed
    There remains one occurrence in a note on low-memory footprint
    JSON-LD processors, but it is self-explanatory. Also another one
    in the Microformat appendix but I'm not clear what the sentence
    actually means.
Commits on Nov 8, 2012
  1. Removed definition of JSON-LD processors from the Conformance section

    François Daoust committed
    Other sections still mention JSON-LD processors, either to describe
    how JSON-LD documents are processed or to put constraints on JSON-LD
    processors through normative statements. Descriptive text would need
    to link to the proper definition of JSON-LD processor in the API doc.
    Normative statements that apply to JSON-LD processors need to be
    dropped. All of this is being covered by issue #184.
Commits on Nov 7, 2012
  1. Merge branch 'master' of

    François Daoust committed
  2. Re-introduced sentence to discourage use of terms starting with an "@"

    François Daoust committed
    The grammar contains a "SHOULD NOT" statement on that. I re-introduced
    a similar statement using "are to be avoided" not to duplicate the
    normative statement.
  3. @lanthaler

    Remove mention of "framing" from the syntax spec

    lanthaler committed
    Framing is not part of the API spec anymore and should thus not be mentioned in the syntax spec.
    Thanks to @cygri for reporting this.
    This closes #191.
  4. @lanthaler

    Remove handling of @type:{} from expansion algorithm

    lanthaler committed
    This is a left-over from framing which is no longer part of the API spec.
    Thanks to @cygri for reporting this.
    This closes #190.
  5. @lanthaler
  6. Merge branch 'master' of into …

    François Daoust committed
  7. Markus feedback on recent Conformance/Grammar updates incorporated.

    François Daoust committed
    - Created issue #184 to discuss the definition of a JSON-LD
    processor. The doc references that issue in the meantime.
    - Incorporated Markus feedback to clarify when a JSON object with
    a null value is ignored
    - Re-introduced statement that discourages the use of empty terms
    in "Context" section. I left it in the grammar as well because that
    also seems the right place to mention it but, technically speaking,
    it could be removed from there since it's not a normative binding.
Commits on Nov 5, 2012
  1. @lanthaler
  2. @lanthaler
  3. @lanthaler
  4. Dropped normative statement from "Basic" and "Advanced" sections.

    François Daoust committed
    Grammar completed as necessary when the normative statements were
    not captured yet (e.g. the constraint on circular dependencies
    for terms definitions in a context).
    Also: IRI definition modified to say that an IRI may either be
    represented as an absolute IRI or a relative IRI. "terms" and
    "compact IRIs" were also in the list previously, but they generate
    IRIs through expansion, and the grammar makes the distinction
    when it says that a value can be an IRI, a compact IRI or a term.
    Normative statements on JSON-LD processors still appear in the
    doc, but should probably be removed.
    Also note the "Referencing Contexts from JSON Documents" section
    retains its normative wording.
    I also updated plural references to terms to include the "s" to
    ensure the whole world gets turned into a link.
  5. New "stand-alone" Grammar section

    François Daoust committed
    Main changes:
    - Clarified that JSON terms are directly imported from the JSON spec,
    and not re-defined in JSON-LD.
    - Moved the definitions of "node definition", "node reference" and
    "term" to the grammar. They are JSON-LD constructs.
    - Introduced new grammar constructs when needed, in particular
    "expanded typed value" and "expanded lanugage-tagged string"
    - Re-wrote the grammar in a more consistent way to use the same
    vocabulary throughout.
    - Fixed grammar when needed (for instance the value in a language
    map could be a language-tagged string, which seemed a typo).
    Not done yet:
    - All normative statements in "Basic Concepts" and "Advanced Concepts"
    should be removed (provided they appear in the grammar that is!)
    - There remains a couple of places where the grammar is not perfect
    (@graph and apparent contradiction in expanded term definition in
    - Examples in the grammar should be moved to previous sections.
    - There may be a few places in "Basic Concepts" and "Advanced Concepts"
    sections that would benefit from linking to the grammar.
    - Some definitions may benefit from a bit of wordsmithing. For instance,
    there could be a note around the definition of an IRI that explains
    that, whenever the grammar says a value must be an IRI, it is taken
    to mean "a string with the lexical form of an IRI".
Commits on Nov 1, 2012
  1. Merge branch 'master' of

    François Daoust committed
  2. Merge branch 'master' of

    François Daoust committed
Commits on Oct 31, 2012
  1. @dlongley

    Incorporate Markus' feedback.

    dlongley committed
    - Editoral changes to how processing state for context
      properties is described.
    - Add note to IRI expansion algorithm for the case where a
      local context is being processed.
    - Include steps to handle local context processing case
      within IRI expansion algorithm.
Commits on Oct 30, 2012
  1. @dlongley
  2. @msporny
  3. @lanthaler

    Add missing comma to example

    lanthaler committed
  4. @lanthaler
Commits on Oct 28, 2012
  1. @lanthaler
  2. @lanthaler
  3. @lanthaler

    Grammar fix

    lanthaler committed
Commits on Oct 27, 2012
  1. Add Conformance section as proposed in #166.

    François Daoust committed
    The JSON-LD Data Model is now in a proper section, followed by
    a terminology section with general terminology and keywords. The
    Conformance section (that refers to the notion of JSON-LD graph
    defined in the JSON-LD Data Model section) appears next.
    No further changes in this commit.
Commits on Oct 23, 2012
  1. @lanthaler
  2. @lanthaler

    Add expandContext to JsonLdOptions

    lanthaler committed
    This closes #156.
  3. @lanthaler
Commits on Oct 22, 2012
  1. @lanthaler

    Fix grammar

    lanthaler committed
    Thanks @scor for reporting this.
  2. @lanthaler

    Improved Named Graphs section

    lanthaler committed
    Addressed feedback from Peter Patel-Schneider:
    "@graph is not needed "to express a set of JSON-LD node definitions that may
    not be directly related to one another".  This wording should be changed."
  3. @lanthaler
  4. @lanthaler

    Create section "Relationship to RDF"

    lanthaler committed
    This addesses #157, #168.
  5. @lanthaler
  6. @lanthaler
Something went wrong with that request. Please try again.