json-schema-org/json-schema-spec

Issues

• 🧹 Clarification: usage of non-canonical identifiers in `$schema`

  #1590 opened 8 months ago by karenetheridge
  11

• Question on description in enumeration

  #1595 opened 7 months ago by francescoingv
  1

• Question About JSON Schema Validation Behavior

  #1594 opened 7 months ago by germanbisurgi
  7

• ✨ Proposal: Add a Global `defaultAdditionalProperties` Toggle at the Root Level

  #1587 opened 9 months ago by dani2819
  2

• ✨ Proposal: Use github actions to publish the specs

  #1539 opened a year ago by AxelNennker
  6

• ✨ Proposal: add regex lookbehind support (ES2018)

  #1591 opened 8 months ago by ryanblock
  1

• Issue: subset schemas don't work with `unevaluatedProperties` across `oneOf` branches

  #1585 opened 9 months ago by smikulcik
  2

• 🧹 Clarification: Optional properties and null vs. undefined when used in languages like Python that only has a single None type

  #1586 opened 9 months ago by Ark-kun
  6

• Add version identifier

  #1532 opened a year ago by joostholslag
  3

• 🧹 Clarification: Scopes section could be improved

  #1566 opened a year ago by gregsdennis
  6

• 🧹 Clarification: MAYs in several sections are linquistic, not requirements

  #1573 opened 9 months ago by gregsdennis
  1

• ✨ Proposal: `format` registry

  #1552 opened a year ago by gregsdennis
  15

• ✨ Proposal: date-time format to accept those in RFC 9557

  #1572 opened 10 months ago by tisonkun
  1

• Link directly to targets

  #1536 opened 9 months ago by gregsdennis
  7

• Reunite the meta-schemas

  #1575 opened 10 months ago by gregsdennis
  1

• Implement a common language style throughout the specifications

  #1509 opened a year ago by gregsdennis
  11

• 🧹 Clarification: Behavior for duplicate `$id`s or `$anchor`s

  #1533 opened a year ago by gregsdennis
  10

• ✨ Proposal: Not all keywords need to produce a validation result.

  #1540 opened a year ago by gregsdennis
  4

• ✨ Proposal: Provide resourceMediaType and resourceSchema when string format is a resource identifier, similar to contentMediaType and contentSchema

  #1557 opened a year ago by torsknod-the-caridian
  4

• Docs: Improve JSON Schema Validation Markdown File Formatting and Content

  #1570 opened 10 months ago by Karan-Palan
  2

• Core: Add section to define expectations for proposals

  #1569 opened 10 months ago by gregsdennis
  3

• Unsupported deprecated keywords are listed in the metaschema

  #1538 opened a year ago by michaelmior
  3

• 🧹 Clarification: Output schema is confusing

  #1567 opened a year ago by lud-wj
  5

• ✨ Proposal: Add `uniqueProperties` to "Validation Keywords for Objects"

  #1565 opened a year ago by sebastianpiskorski
  2

• Proposal: Make `format` validate by default

  #1520 opened a year ago by gregsdennis
  61

• Clarify how schemas embedded inside other document types are identified

  #1513 opened a year ago by gregsdennis
  5

• ✨ Proposal: uniqueItems based several properties or subschema

  #1546 opened a year ago by LasneF
  7

• ✨ Proposal: Support $ref-to-enum in object `required`

  #1551 opened a year ago by etinquis
  5

• $schema introduces specification-level circular dependency

  #1521 opened a year ago by mathematikoi
  12

• 🧹 Clarification: missing definition of `required` for object schema properties

  #1535 opened a year ago by drpump
  3

• Specification Flow could be improved (but what do we work on next?)

  #1527 opened a year ago by gregsdennis
  3

• pattern matching key/value strings with propertyDependencies / how to require properties with a match?

  #1511 opened a year ago by jeremyfiel
  6

• Simplify Issue Management

  #1526 opened a year ago by gregsdennis
  7

• How to interpret schema with both properties and oneOf?

  #1529 opened a year ago by bcherny
  5

• Wild idea for vocabs

  #1523 opened a year ago by gregsdennis
  2

• Clarification Needed on the Status and Future Updates of JSON Schema Specification

  #1530 opened a year ago by VimukthiRajapaksha
  2

• Schema validation crashes with stack overflow

  #1528 opened a year ago by vmelamed
  5

• Future

  #1524 opened a year ago by theELITEbes
  0

• Output unit schema inconsistent with spec

  #1504 opened 2 years ago by tombentley
  4

• Apply transformations to Dynamic References

  #1517 opened a year ago by franklevasseur
  5

• File extension in $id

  #1502 opened a year ago by andriy-dmytruk
  2

• String format validation for IP addresses with network mask

  #1501 opened a year ago by shodhansave
  1

• To validate CRUD of table information with a single Json-Schema, we propose an attribute for PrimaryKey.

  #1495 opened 2 years ago by Yuutakasan
  4

• `min*`, `max*`, `pattern` constrained from validated JSON data

  #1519 opened a year ago by 0x522D43
  2

• Publish new drafts of expired Specification Documents

  #1516 opened a year ago by jischr
  4

• `file://path` is loaded as an absolute path

  #1515 opened a year ago by thejcannon
  3

• Question about references ($ref)

  #1508 opened a year ago by shonigbaum
  2

• owner

  #1498 opened 2 years ago by Myahr208
  0

• Futuristic

  #1496 opened 2 years ago by Astrabacus
  0

• Typo in section 8.2.3 of draft 7 leading to wrong information

  #1499 opened 2 years ago by suprith-hub
  4