Hello Holger, Yes, mostly for the use of datatypes in properties. Well, last night and this morning the problem is with an owl:DatatypeProperty in QUDT, qudt:numericValue, whose rdfs:range is xsd:double. So it is a good example of a custom property but uses a standard datatype.
I created a class instance and tried to set the qudt:numericValue to one of the below: 255 255.0 255e01 255.0e01 "255"^^xsd:double but TBC didn't like any of them. That is when I thought of a template value in the field. I've been thinking about this since reading your mention of SHACL. At first I thought that the solution should be in the TBC IDE, but the notion of it being part of [some] language model makes more sense. Unfortunately, it seems like this kind of thing would make sense at a very high level, and I do not think the benefit would justify the effort. On Wednesday, July 29, 2015 at 5:04:03 PM UTC-7, Holger Knublauch wrote: > > Which datatypes do you have in mind? I assume xsd:string and any numeric > datatypes are not a problem. I can imagine that xsd:date and xsd:dateTime > are. What else? > > Also, could you give me some example of user-defined datatypes that you > have created? With OWL 2 syntax? > > (On the more general issue, note that SHACL has sh:defaultValue, which may > be exploited for useful suggestions for certain properties - > sh:defaultValue lives on a property definition though, not the datatype > itself). > > Holger > > > On 7/30/2015 9:58, Jack Hodges wrote: > > And for non-standard properties (such as those created by us), maybe an > option to provide such a legal default value definition for others. > > On Wednesday, July 29, 2015 at 4:57:22 PM UTC-7, Jack Hodges wrote: >> >> Often times I find myself in a situation where I am putting a value into >> a form field and TBC doesn't like it. I end up spending a fair amount of >> time looking for legal values. It would be [very] nice if, at least for >> standard types, a default legal value could be put into the field so that >> we could then edit it. That would give us both proper syntax and values. >> Maybe I am the only one that would like this. >> > -- > You received this message because you are subscribed to the Google Group > "TopBraid Suite Users", the topics of which include Enterprise Vocabulary > Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid > Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. > To post to this group, send email to topbrai...@googlegroups.com > <javascript:> > --- > 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 topbraid-user...@googlegroups.com <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to topbraid-users@googlegroups.com --- 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 topbraid-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
