Skip to content

Commit cea94df

Browse files
committed
Add details for project scope in the charter
1 parent 6ae2363 commit cea94df

File tree

1 file changed

+33
-10
lines changed

1 file changed

+33
-10
lines changed

CHARTER.md

Lines changed: 33 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -17,16 +17,39 @@ JSON Schema aims to enable the confident and reliable use of the JSON data forma
1717
While JSON Schema's primary target is constraint-based data validation, it continues to be used across the whole stack, in different stages of a given project, and for purposes beyond its original design. We aim to enable these additional and emergent use cases.
1818

1919
### 1.1: In-scope (optional)
20-
21-
https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391253
22-
23-
_directions: list or bullet out problem spaces, use cases, repositories_
24-
_or other projects which are included with the work but may not be readily_
25-
_apparent. This may help differentiate the project from other solutions in the_
26-
_space. If you are not using this section, please indicate your intent with the_
27-
_phrase, 'Section Intentionally Left Blank'._
28-
29-
ex. [K8s SIG Architecture Charter](https://github.com/kubernetes/community/blob/HEAD/sig-architecture/charter.md#in-scope)
20+
<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391253 -->
21+
22+
The scope of the JSON Schema project is split into two sections: primary and secondary concerns.
23+
Primary concerns are areas we wish to give focus to, while secondary concerns are more likely to require the creation of a Special Interest Group.
24+
25+
Primary Concerns
26+
- Publication of the JSON Schema standard
27+
- Validation of JSON data
28+
- Semantic annotation of JSON data
29+
- Extensibility
30+
- Critical tooling
31+
- Creation of new
32+
- Ingestion of existing
33+
- Long term support
34+
- (Including linting)
35+
- Documentation
36+
- Test suite
37+
- Community
38+
- Enabling schema authors
39+
- Enabling implementers
40+
- Engaging with industry
41+
- Communicating value
42+
- Ensuring the sustainability of the project
43+
44+
Secondary Concerns
45+
- Hypermedia
46+
- Generating JSON Schema
47+
- Using JSON Schema to generate
48+
- Code (including types or classes)
49+
- UI (including forms)
50+
- Databases
51+
- Relational validation
52+
- Vocabularies registry
3053

3154
### 1.2: Out-of-Scope (optional)
3255
<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391262 -->

0 commit comments

Comments
 (0)