TopBraid EDG SHACL models are designed as separate graphs where constraints that have to do with “data validity” are kept separate from the information that has to do with the UI (e.g., what group/section a property should be displayed in, what order it should have in the section, what UI widget to use with it, etc.). This is in addition to separation according to the domain of interest. For example, EDG has separate models that describe data assets, technical assets such as software and hardware, enterprise assets such as forms, reports, processes, etc. In each of these cases, there are two SHACL models - one with the data validity constraints and one with the UX info.
You can use the same approach and have different graphs. In case of EDG, UX info doesn’t really have any impact on the validation - use of properties like sh:order does not create any data validation. However, one could imagine a situation where one would have two sets of constraints where both sets are used to determine validity, but you using one in one situation and both in another situation or whatever. The idea is the same. Design your model architecture so that these are kept in separate graphs and use them accordingly. > On Apr 12, 2018, at 4:17 PM, Steven Michael Folsom <[email protected]> wrote: > > I would be interested to be able to look at any implementations where > Validation shapes are compiled with non-Validation shapes to build Forms, > where that the validation axioms are maintained in separate shapes from > non-validation (UI) shapes? > > Is anyone doing this? We’ve been considering it for easier maintenance of our > various shapes, but right now it’s easier to see all the axioms needed for > the app in one place… > > Thanks, > Steven > > -- > Steven Folsom > Metadata Specialist > Cornell University Library > pronouns: he/him/they/them > http://orcid.org/0000-0003-3427-5769 <http://orcid.org/0000-0003-3427-5769> > http://vivo.cornell.edu/individual/sf433 > <http://vivo.cornell.edu/individual/sf433> > @sf433 > > > -- > You received this message because you are subscribed to the Google Groups > "TopBraid Suite Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
