-
-
Notifications
You must be signed in to change notification settings - Fork 52
Description
Agenda
Topic | Owner | Decision/NextSteps |
---|---|---|
Review last call's action items Area of focus and interest of JSON Schema Org |
@Relequestual | Action items were reviewed Please read current-work README Focus items list |
Feedback on Discussion #257 | @awwright | Rolled over to next meeting |
Updates to ADR, explaining new SDLC PR #1346 | @jdesrosiers | Read PR #1346 |
Bowtie calls for contributions to the suite |
@Julian | Read more here Good First Issues to tackle. Tutorial for contributers. See Tutorial |
JRef and JRI merge into referencing repo | @handrews | See here and feedback from community is seeked JRef PR JRI PR |
Highlights
- @Julian shared brief introduction, updates and called upon people to contribute to Bowtie Meta-Validator
JRef
andJRI
merged to referencing repo and wg now seeks community feedback on the same- Discussion on
media-type
overriding, explicit expectation etc. - Updates to
current-work
focus of JSON Schema org were shared. The list can be seen here
Actions
- Read (if haven't already) the ADR for new SDLC PR #1346
- Gather feedback from community on JRef and JRI. Referencing Repo
- Call upon contributors to help with
Bowtie
- Feedback on discussion #257. Updates rolled over to next meeting
- Add comments to specification regarding JSON Schema's use of
Serialization
andDeserialized
use in implementations - @jdesrosiers to create issues to discuss topics regarding referencing,
href
etc - Discuss
media-type
Attendees
Account |
---|
@Relequestual |
@awwright |
@jdesrosiers |
@Julian |
@gregsdennis |
@jviotti |
@handrews |
Details
Bowtie
Bowtie is a meta-validator of the JSON Schema specification. There are various issues that need help from contributors and interested people are encouraged to take a look at Bowtie Issues. A tutorial is provided for contributers. See Tutorial
Introduction was followed by a discussion on skipped
v error/fail
as output from the meta-validator. Briefly put, skipped
is for when there are limitations of various kind an implementation is bound by or implementer decides as to why a behavior/test is skipped. For example lua
not having a clear distinction between empty array and empty object. In such cases, skipped
allows to add a response providing explanation rather than outputing error
which is for Bowtie to catch unexpected problems and providing an explicit trace.
For an example of skipped
, click on Details
of .net implementation here.
Unknown, explicit or overriding media-type
The discussion brought up concerns about security and trust establishment (where are the boundaries for trust drawn and moved under ambit of specification ?) with respect to media-type being served (locally or remotely) and overriding causing concerns with trust establishment boundary and security in certain contexts.
A few points made were, allowing user to explicitly describe an expected media-type (by use of additional keyword ?). Another addition to the discussion was regarding media-type loaded from HTTP content-type and the dereferencing function determining media-type of the URI, whereas schema loaded any other method being allowed to assume media-type. Furthermore, JRI
provides hooks for picking a point for such a decision i.e preload
and serve
functions and expected media-type are in JRI xref
section.
Further discussion are to be had in this regard and security section might need expanding.