Hi Miika,
yes I noticed that rdf:langString is not yet in the system triples graph
that we use as implicit import, and thus it doesn't get listed by
auto-complete and the selection dialogs. I was about to suggest the
work-around to define that type yourself, but I noticed that TBC has
follow-up issues with this datatype. I will see if I can fix these
issues for 5.1 (we are freezing the code base for release soon).
Thanks
Holger
On 11/9/2015 21:02, Miika Alonen wrote:
It would be nice to have rdf:langString
(http://www.w3.org/TR/rdf-schema/#ch_langstring) as an option for
range when creating new datatype property AND also in the datatype
list available from "Replace value with...".
--
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 [email protected]
---
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]
<mailto:[email protected]>.
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 [email protected]
---
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].
For more options, visit https://groups.google.com/d/optout.
