SYSMOAS11 — Storing derived property values or implied relationships to the repository does not scale

Based on a discussion with Ed. I'm not sure if it's a spec of a tooling issue.

On the Pilot Implementation side, it is now the default to not write derived property values or implied relationships to the repository.
This can reduce the JSON size by a factor of 10 or more. It was pretty much the expectation that this would be the only way to save large models efficiently in a repository (or to an interchange file, for that matter).

We still have the option to write JSON including derived properties and/or implied relationships, to accommodate clients that don’t have the ability to recreate those values.
For example, at the moment some visualizers requires that the derived properties be stored in the repository. But this is never really going to work at scale.

Probably the right way to handle this is to never store derived properties and implied relationships in the repository.
Then, for clients that can’t recreate these, have a server-side service that does the derivations and produces JSON for the client that looks as if the derived values had been storied in the repository.

Proposal:
Provide an API endpoint or an option to calculate the derivations and produce the full JSON on retrieval
Provide an API endpoint or an option to strip the derivations from the full JSON on storing