Added Schematron based JSON Semantic validator #240
Conversation
|
I don't see the relationship to JSON Schema here? Schematron is unrelated, AFAIK. |
|
Thanks Henry for taking time to review it. Please take a look at below
issue that requires this type of semantic validator:
https://stackoverflow.com/questions/28629107/json-is-there-an-equivalent-of-schematron-for-json-and-json-schema-that-is-a
I posted a possible solution to that problem.
If that doesn't convince you, then I can send some more information on why
i believe it is relevant to JSON Schema.
Regards,
Amer
…On Tue, Oct 30, 2018 at 12:08 PM Henry Andrews ***@***.***> wrote:
I don't see the relationship to JSON Schema here? Schematron is unrelated,
AFAIK.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#240 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AmCjf50X_unZoz9OuWdS0_SWArSjN6uLks5uqHl3gaJpZM4X5VCm>
.
|
|
I agree with @handrews on this. It seems your semantic validator is a layer that sits on top of JSON schema rather than implements it. I see the relation, I'm just not sure it qualifies as an implementation. |
|
Thanks Greg.
I agree with your characterization that it is not implementation of JSON
Schema per se. However, JSON Schema, though extremely useful for syntax
validation, doesn't have many facilities for co-constraint specifications.
Contrarily, in XML there is XML Schema that is equivalent to JSON Schema
and it has Schematron for co-constraint specifications. So JSON Schema
caters to one half of JSON data validation needs. I made an attempt to use
Schematron to implement the second half of JSON data validation. It is in
no way as perfect as JSON Schema but my point was to draw attention of JSON
validation community to the semantic validation void and suggest a possible
solution. I would leave it up to you folks to decide if it adds any value
for JSON community on your site.
…On Tue, Oct 30, 2018 at 4:25 PM Greg Dennis ***@***.***> wrote:
I agree with @handrews <https://github.com/handrews> on this. It seems
your semantic validator is a layer that sits on top of JSON schema rather
than implements it. I see the relation, I'm just not sure it qualifies as
an implementation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#240 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AmCjf-hU1Rx1-BC9fQHYl4HtfLaTxhZKks5uqLW3gaJpZM4X5VCm>
.
|
|
@amer-ali This page (and the site containing it) are for JSON Schema its implementations. That includes tools that use JSON Schema for purposes beyond what is covered in its specification (e.g. generating web forms from them), but does not include complementary technologies that are not, themselves, JSON Schema based. I'm closing this as out of scope. It has nothing to do with the quality of the idea or implementation, or its relevance for others who use JSON Schema and want additional semantic validation. It is just that there is a very specific purpose for this page, which is to list JSON Schema implementations. If you are interested in discussing ideas around co-constraints and JSON Schema, you will find at least a little discussion in some of the issues tagged with "$data" (the tag should probably be renamed, but we haven't because GitHub puts the tag name in the URI so renaming it would break links). |
Added Schematron based JSON Semantic validator called jsontron.