Skip to content

Editorial: title mismatch, awkward phrasing, unused RFC4646 reference #1

@clemensv

Description

@clemensv

The following minor editorial issues were found during review:

1. Introduction says "JSON Structure Conditionals" — should match document title

The introduction names the extension "JSON Structure Conditionals" but the document title and abstract use "JSON Structure Conditional Composition". These should be consistent.

2. Awkward sentence structure

A schema document using these keywords is not a data definition but a rule set for evaluating JSON node instances against schema definitions and lays the groundwork for validation.

The coordination is unclear. Suggested rewrite:

A schema document using these keywords is not a data definition; rather, it is a rule set for evaluating JSON node instances against schema definitions and for laying the groundwork for validation.

3. Unused/obsolete RFC4646 reference (line 31)

RFC4646 appears in the references block but is obsolete and does not appear to be cited in the document body. It should be removed (or updated to RFC5646 if a citation is needed).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions