Hi Johnrobert,
> I'm having all manner of problems with namespaces - does TBC have
> documentation around how it handles things?
TBC follows the usual namespace conventions of RDF but TBC's
documentation is not a complete introduction to RDF. So please check
other literature and let us know if you have specific problems like
those below.
> Basically my situation should (should) be simple:
> 1. take a client's XSD, with namespace there as
> http://www.client.com/ClientOntology
> 2. using the File:Import procedure (the right-click open-with makes an
> even more confusing set of namespaces)
> 3. I added the namespace to the window in "Navigate to Ontology" - with
> "client" prefix
> 4. I go to add an instance of a class and I can NOT avoid this:
> <http://www.client.com/ClientOntology#My_new_instance>
> How do I make these lt/gt or <> go away?
This should disappear if you have a namespace prefix
client:
http://www.client.com/ClientOntology# (note the # at the end).
If this does not work then please provide more details (e.g. send me the
file)
> (and, by the way, none of the properties or classes are
> recognized when I drag in an XML made from the XSD ...)
Yes these two import features are not automatically linked together,
i.e. the XSD importer does not create the Semantic XML annotations such
as sxml:attribute that it would need to automatically map the XML files.
You need to add those annotations yourself until we had a chance to
clean this up.
> I'm disappoointed in the behavior of drag import in genreal, and that's
> why I'm having to manually make each instance -- when I save the
> ontology and send to a colleague for testing and working in Jena -- none
> of the dragged-import XML's are there regardless the lt/gt thing. I
> wind up having to send him the XML files too, then of course TBC tells
> him they're ALREADY imported (even though none of the values are there
> ... ??? this is so weird ... ), so he has to delete all those import
> values and re-drag them in. Which, of course, re-creates all the <>
> gibberish ...
You have lost me here a bit.
> How to drag import XML into the OWL model such that the instances STAY
> in it when saved and shared?
So to make sure we are on the same page, I did the following. I have an
OWL file (in your case it might have been created with the XSD importer
but that should not matter). Then I drag an .xml file from the
Navigator into its imports. The Semantic XML importer will render this
XML file into triples in the import graph. The XML will also import
sxml.owl by itself. I then save the main file and after re-opening the
imported XML is still there. So it seems to be working fine.
When you share such files with your colleagues you need to also give
them the XML files, and - in particular - they need to put those files
into exactly the same file location (relative to the workspace) as you
did, because the system is selecting the file:// path as base URI of the
XML file (and this is referenced in the owl:imports from the main file).
I hope that helps,
Holger
