[
> sh:name “My name” ;
> sh:minCount 1 ;
> ] .
>
> Thank you.
>
> Rebecca Younes
>
> From: <topbraid-users@googlegroups.com> on behalf of Holger Knublauch
> <hol...@topquadrant.com>
9:22 PM
To: "topbraid-users@googlegroups.com" <topbraid-users@googlegroups.com>
Subject: Re: [topbraid-users] Compiling Validation and UI/Form semanatics
On 11/05/2018 22:19, Steven Michael Folsom wrote:
I realize the examples are not normative, but could the example given at
https:/
Holger
Knublauch <hol...@topquadrant.com>
*Reply-To: *"topbraid-users@googlegroups.com"
<topbraid-users@googlegroups.com>
*Date: *Saturday, April 14, 2018 at 7:16 PM
*To: *"topbraid-users@googlegroups.com" <topbraid-users@googlegroups.com>
*Subject: *Re: [topb
On 14/04/2018 3:59, Irene Polikoff wrote:
Overrides are not supported, but inheritance is supported.
For example, you could define minCount but not define maxCount, then
add a definition of maxCount in the “sub shape”.
There are 2 ways of addressing this:
* Classes can also be shapes.
Overrides are not supported, but inheritance is supported.
For example, you could define minCount but not define maxCount, then add a
definition of maxCount in the “sub shape”.
There are 2 ways of addressing this:
Classes can also be shapes. If you model that way, all you need to do is to
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