Add JSON and JSON Schema classifiers. #142
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Request to add a new Trove classifier.
The name of the classifier(s) you would like to add:
Topic :: Internet :: JSON
for JSONTopic :: Internet :: JSON :: JSON Schema
for JSON Schema underneath itWhy do you want to add this classifier?
No classifier currently collects JSON-adjacent projects despite their ubiquity.
JSON Schema is, thankfully, also quite large at this point, and tooling both within the JSON Schema ecosystem but also in the Open API and Async API ecosystem would likely use the classifier.
I'm not sure if these guidelines are specific to
Framework
classifiers or whether they'd apply here. I can of course speak for myself on wanting to use these in multiple libraries, but if there's a need to drum up more support obviously let me know! My assumption is certainly that one could find 10 or more for JSON and I'd be surprised if that wasn't the case for theJSON Schema
specific one as well.Where does this belong?
There's
Topic :: Text Processing :: Markup :: XML
currently for XML, which I think is the closest existing classifier, though it seems equally awkward (asTopic :: Internet
) to put JSON in that category. If there was aTopic :: Data Formats
or aTopic :: Specifications
perhaps one of those would seem decent places, but that's obviously an invasive kind of thing.