Thanks for the reply. I do not recall saying anything about dtype:numericUnion in my mails and as far as I can see qudt:numericValue is defined with an xsd:double range. That said, I can see that there are instances of qudt:numericValue that follow the conventions you and I both used, but yours is successful and mine was not. Maybe it is some kind of glitch in my TBC (which happens on occasion, though I close and reopen daily to be safe).
But the suggestion is still valid I think, at least in terms of standard types (but maybe not if no errors occur). Jack 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 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.
