Closed allynt closed 7 years ago
Sometimes they can just be URLs. But in the case of CIM_Reference, I ought to intercept the call to "add a new relationship" w/ an ES-DOC webservice that brings back the appropriate already published documents. Like references, these should not be rendered as an inline subform but as a URI to some external resource.
However, the above technique assumes that the target documents already exist. What do I do if they are not there yet?
How about instead of looking for existing documents, I use a list of canonical names (or some other unique but agreed-upon identifier)? Of course there would be different lists for different properties and this would break the generality of the Q, but I can live w/ that for the sake of making the UI pretty.
Note that this covers more than just models. For example, NumericalRequirements referenced by Conformances.
References should not by default specify a specific version; this will force the viewer to always get the latest version.
Handled as part of #416.
Deal w/ references.