Thanks, Irene and Holger, for your prompt replies. Doing what you've done with skos:altLabel totally worked for my purposes, so that's good -- thanks! But I have two observations:
1. rdf:langString is not available as an option in the *datatype *dropdown in EDG. Perhaps it should be? 2. I cannot get EDG to accept either the manually entered text of either "dash:StringOrLangString" or "dash:HTMLOrStringOrLangString" as values for *sh:or*. I get the warning, "Requires at least two choices." I suppose it would work if I imported this constraint expression into the project, but it seems like it should be permitted to add these values manually in EDG. thanks, C On Friday, October 4, 2019 at 1:13:28 PM UTC-7, [email protected] wrote: > > When building property shapes for properties with literals as objects, > such as rdfs:label, mandating a datatype of "string" seems like a good idea > -- in fact, it seems to be necessary if we want search to work properly > (i.e., if we want the filtering logic in search forms to default to > "contains"). > > But the thing is: all or existing values of rdfs:label have a datatype of > what W3C calls rdf:langString (string + lang tag), not just simple strings. > That means they all trigger a constraint violation! > > What should I do about this? I don't see a way to set the datatype to > rdf:langString. > -- 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/7c2736ba-a4f0-4abf-b220-54f6fe2472b0%40googlegroups.com.
