Gavin Mendel-Gleason

Should we not rather delete the capabilities?

`Optional(List)` is, in particular, really needed. The `Optional(Set)` combination is actually redundant since sets can work with any cardinality including zero. I haven't thought through all of the other possible...

It is not blocked at the minute, but we can block it.

Fixed in #1378

The following schema seems to exhibit an issue... ```json { "@type" : "Class", "@id" : "HasJSONDocument", "json_document" : "sys:JSONDocument" } ```

We will block use of `JSONDocument`s for now by throwing an error.

We will put this on the road map for sure.

You can now get a log with: ``` curl -X GET http://localhost:6363/api/log/admin/db -uadmin:root ``` Due to #1313 It would be nice if it were truncated by a size parameter however.

I suspect this is actually a very expensive global check being triggered by a poor algorithm for calculating blast radius of schema changes and perhaps thousands of existing documents.

Is this not already implemented?