Hi Irene, you are right. When I reproduced, the screenshot in Stefan's 2nd post is what I got and would have expected. It is a slight inconvenience to do it right in two steps but not a big deal.
On Friday, July 26, 2019 at 9:47:36 AM UTC-4, Irene Polikoff wrote: > > It does represent an inconsistency and there is a shape that validates a > shape. When this happens, there will be a validation issue displayed for > the shape itself. This is what Stefan’s screenshot showed. > > On Jul 26, 2019, at 9:38 AM, Fan Li <[email protected] <javascript:>> > wrote: > > Thanks for the explanation! If we have both sh:datatype defined as > xs:integer and sh:max in string within a shape, doesn't it represent an > inconsistency? Maybe we need another shape to validate this shape:) > > On Thursday, July 25, 2019 at 10:07:15 AM UTC-4, Irene Polikoff wrote: >> >> Let’s say you have something like >> >> g:C1-test >> rdf:type sh:PropertyShape ; >> sh:path g:test ; >> sh:maxInclusive "23" ; >> sh:minInclusive "0" ; >> . >> >> Add the datatype constraint. Then change (using source code panel) “23” >> and “0” to 23 and 0. >> >> To get to: >> >> g:C1-test >> rdf:type sh:PropertyShape ; >> sh:path g:test ; >> sh:datatype xsd:integer ; >> sh:maxInclusive 23 ; >> sh:minInclusive 0 ; >> . >> >> Basically, if you set sh:datatype xsd:integer constraint before you >> enter min/max values and save it, then min/max values constraints will be >> saved as integers. >> >> But if you add the integer constraint after entering min/max, then it >> would be saved as a string. The same happens if you enter both of them in a >> single edit transaction since the system does not know yet that it must be >> a digit. >> >> So, in the future, enter the integer constraint first, save it. Then you >> can enter values constraints and they will be integers. >> >> On Jul 25, 2019, at 9:23 AM, Stefan Verweij <[email protected]> wrote: >> >> I have tried that indeed, by selecting *integer *from the dropdown list *at >> datatype *at Type of Values in the UI. But then I get another error that >> says the datatype doesn't match the values at max inclusive (see picture >> again) >> >> <datatype_error.PNG> >> >> >> Op donderdag 25 juli 2019 15:10:54 UTC+2 schreef Irene Polikoff: >>> >>> Have you tried adding sh:datatype XSD:integer constraint? Or do you want >>> values to be strings? >>> >> >> -- >> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/topbraid-users/9f23dec7-eb5e-409a-b794-dac26436820e%40googlegroups.com >> >> <https://groups.google.com/d/msgid/topbraid-users/9f23dec7-eb5e-409a-b794-dac26436820e%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> <datatype_error.PNG> >> >> >> > -- > 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] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/6c17415d-c2cb-4719-a415-fb6d8e7076c9%40googlegroups.com > > <https://groups.google.com/d/msgid/topbraid-users/6c17415d-c2cb-4719-a415-fb6d8e7076c9%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/034acc64-0c2b-4259-8c98-b647ed999d9b%40googlegroups.com.
