Comments (5)
Hey! When reading this issue I moved it by mistake into the "In Discussion" status but I can't find a way to find the previous status to revert it. Is "In discussion" the right status for this issue?
from json-schema-spec.
I don't think the intention was to imply that these behaviors are mutually exclusive. If that's not clear enough, we should fix that.
I'd also be in favor of dropping that section entirely. IMO, the only thing that matters is what inputs are available and what output is expected. Whatever behavior is possible from the inputs you have is a possible behavior for a keyword. Categorizing keyword behavior seems more appropriate for a research paper.
from json-schema-spec.
I'd also be in favor of dropping that section entirely. IMO, the only thing that matters is what inputs are available and what output is expected. Whatever behavior is possible from the inputs you have is a possible behavior for a keyword. Categorizing keyword behavior seems more appropriate for a research paper.
This opinion leans into #1159 where I proposed that we reorganize the meta-schemas. If behaviors like "applicator", "annotation", and "assertion" are the output of a meta-analysis of keywords, then it doesn't make sense to organize our vocabularies using these concepts, which means we need some other way to organize them. To me, that's by applicable JSON type (e.g. all of the "object" keywords together) and/or keyword purpose (e.g. boolean logic, conditionals, etc)
from json-schema-spec.
I'm definitely in favor of revisiting vocabulary organization, but I'm still strongly of the following opinion ...
vocabulary organization is arbitrary and no matter what we choose, there will always be use cases where it doesn't make sense. I'd rather define keywords than vocabularies. Then people can combine them however they like without being constrained by the categorization we choose for them.
I strongly believe that there needs to be a decoupling of keywords from vocabularies. If we do that, it matters very little how we group keywords into vocabularies or if we define vocabularies at all. We can even provide both a type-optimized and composition-opitmized set of vocabularies that group the keywords in different ways. But most importantly, anyone can define their own vocabularies tailored to their needs if ours don't make sense for them.
from json-schema-spec.
Okay. Let's have the vocab rework conversation over there, whatever it ends up being. I really just wanted to link these two since they seem related.
"Applicator" in particular is useful as a concept because it makes unevaluated*
easier to define since unevaluated*
MUST run after all other applicators. I'm not convinced removing it is the right direction, but I'm also not sure what needs to be done.
from json-schema-spec.
Related Issues (20)
- Pattern: clarification on whether leading and trailing delimiters are allowed or required HOT 2
- Omitted `prefixItems` vs empty HOT 1
- Evaluation path: relative to $ref resolved schema or resource/document root? HOT 4
- JSON
- Feature Request: Constraint for single occurrence of a property structure in JSON Schema HOT 1
- Use JSON Pointers instead of 'properties' or 'prefixItems' keywords HOT 16
- Json-schema HOT 1
- How do I get the use Json to get the "about" and "mention" property to work with several subjects? HOT 4
- Statement on annotation values is unclear
- To validate CRUD of table information with a single Json-Schema, we propose an attribute for PrimaryKey. HOT 3
- Futuristic
- owner
- Typo in section 8.2.3 of draft 7 leading to wrong information HOT 4
- String format validation for IP addresses with network mask
- File extension in $id HOT 2
- Output unit schema inconsistent with spec
- Question about references ($ref) HOT 2
- Implement a common language style throughout the specifications HOT 2
- pattern matching key/value strings with propertyDependencies / how to require properties with a match? HOT 2
- Clarify how schemas embedded inside other document types are identified
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from json-schema-spec.