Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    related question : softwareengineering.stackexchange.com/questions/338102/… Commented Jan 3, 2017 at 18:46
  • Can you clarify why you need a schema validation in the first place? Are the users of the system who update the schemas of each resource different to the users who upload the resources themselves? In other words do you still want/need to validate the resources when they are uploaded even though the schema might be changing every few months? If not then it seems unnecessary to have a schema validation on the server in the first place, you could just trust that the uploaded resources are in the schema the end user wants. Commented Jan 4, 2017 at 18:06
  • Think of it as a set of assertions in some code. Even if I am the only developer and user of the code, I still want to ensure that I don't make a mistake and provide invalid arguments. This is partly for that reason, and also partly because the analysts who will use this API to load data are relying on it for part of their quality control--we don't want to allow strings where we expect integers, and so on. Commented Jan 4, 2017 at 23:04