Page Comparison

...

What we need and do not have is a validator that can take an ObjectSchema object and a filled JSONAdaptor (aka a JSON object) and validate that the Adaptor object conforms to the requirements of the ObjectSchema. (John)

It seems that our use cases drive us away from using the Google refine UI or backend, as it doesn't support our core use cases, and then is not totally supportive of our persistence requirements. These include:

...

Google refine looks very good if we create an extension for reconciling data. The other problems are:

• No support for adding new rows or new data
  • It is key, when supporting undo/redo history, that additions be just another modification operation. In google refine you would have to start over.
  Google refine has its own persistence mechanisms. It is unlikely that we would want to take on the migration and security implications of storing any state in a deployed copy google refine. Not storing state is an option, though it would require extending google refine to accept an undo/redo history to apply to a new matrix. This is probably fairly easy
  • .

See data model below for details on the shape of the objects listed above.

...