About using schema

[Sabst]

What about writing more about schema in the spec?
Though technically feasible, doesn't the use of packages like aldeed:collection2 (or jagi:astronomy...) contradict section 2.1 of the spec?
Also, the spec mentions that In the future, client‐side apps will interact with the server using a schema, is this referring to

• the storage schema (as in collection2...)?
• or services-oriented schema that make a clearer distinction between the client and the server standpoints?
• or something else :-) ?

I see an interesting productivity boost in not having to define and code the same thing several times (forms validation, CRUD forms, etc.) and this is just what we gain with libraries like collection2, autoforms...
But can this be Mantra compatible?

[arunoda]

With the schema we meant by GraphQL. These schemas can be consider as this.
But it's completely out side of Mantra.
We'll write more about it on a documentation or somewhere else.