GitHub / json-schema-org/json-schema-spec issues and pull requests
Labelled with: Priority: Low
#1327 - Proposal: Use I-Regexp instead of ECMA-262
Issue -
State: closed - Opened by gregsdennis about 3 years ago
- 31 comments
Labels: Priority: Low, core
#922 - Make evaluation with/against language consistent.
Issue -
State: open - Opened by handrews over 5 years ago
- 5 comments
Labels: Priority: Low, Type: Maintenance, Status: Consensus
#907 - Keyword for extending a schema
Issue -
State: closed - Opened by awwright over 5 years ago
- 23 comments
Labels: Type: Enhancement, Priority: Low, core
#418 - Clarify how base is used with templates.
Pull Request -
State: closed - Opened by handrews about 8 years ago
- 1 comment
Labels: Priority: Low, clarification
#401 - Note that we may remove "dependencies"
Pull Request -
State: closed - Opened by handrews about 8 years ago
Labels: Priority: Low, clarification
#400 - Update ipv6 RFC reference.
Pull Request -
State: closed - Opened by handrews about 8 years ago
Labels: Priority: Low, clarification
#389 - Highlight the challenges of extending meta-schemas
Pull Request -
State: closed - Opened by handrews about 8 years ago
Labels: Priority: Low, core, clarification
#221 - instance equality - trailing zeroes are insignificant?
Issue -
State: closed - Opened by asgs almost 9 years ago
- 14 comments
Labels: Priority: Low, question, core, clarification
#175 - meta-schemas: Descriptions or no descriptions?
Issue -
State: closed - Opened by handrews about 9 years ago
- 4 comments
Labels: Priority: Low, clarification
#171 - Validation: Replace "considered present" language
Pull Request -
State: closed - Opened by awwright about 9 years ago
- 23 comments
Labels: Priority: Low, clarification
#136 - JSON Schema Annotation and Documentation Extension
Issue -
State: closed - Opened by seagreen about 9 years ago
- 9 comments
Labels: Type: Enhancement, Priority: Low