Short version:
[[
The solution is probably to decide which of the two files is the correct version
for that base URI that you wish to use and to either delete the incorrect version,
or change its base URI.
This is done in Composer, and then the project is uploaded to Live.
]]
Hello Catrina,
this error message was added because several customers had difficulty
with multiple files with the same base URI.
At first sight, it appears that this message is working correctly, and
the fix is for you to modify your data before uploading it.
We can see whether this message is correct or not by looking at the
project in Composer.
If you look at the project
Thomson
in the Navigator in TopBraid Composer,
and then look at the two files
RDFVocabularies/TRVocabulary.n3
Hierarchies/GenericHierarchies/KNOS/KNOS_dev_odb.oracle.livecache/TRVocabulary.n3
one or other of them should be marked with a yellow warning triangle.
Double clicking on the file so marked should give a message
The file ???? is not the primary file for the base URI
http://www.ontologies.thomson.com/TRVocabulary
etc.
If this occurs then the error message on project upload is intended, and
TopBraid Live is functioning correctly.
If you do not get a yellow warning triangle in TopBriad Composer
and you cannot get a message about primary files for that specific
base URI then it is most likely a software issue, which we will need to
explore at more depth at TopQuadrant.
So, assuming this warning occurs in Composer, then the error in Live is correct.
The problem is that the ontologies refer to one another using their
base URIs. If you have multiple files with the same base URI then
it is ambiguous as to which one you are referring to.
In TopBraid Composer this ambiguity is resolved by using the last open file with
that base URI - and the user gets to open or close alternate files to manage
this issue.
In TopBraid Live, the complexity of having different choices made by different users,
forces a simpler design.
In TopBraid Live each base URI must be unique across the whole
workspace, and having multiple files with the same base URI is treated as an
error.
The solution is to decide which of the two files is the correct version that
you wish to use and to either delete the incorrect version, or change its base
URI. This is done in Composer, and then the project is uploaded to Live.
Please let me know if this fixes your problem
Jeremy
Hello,
I have a .oracle file created in TBC with the cached configuration.
When I try to upload to TBLive (3.3.1), I receive the following error:
The base URI http://www.ontologies.thomson.com/TRVocabulary from L/
Thomson/RDFVocabularies/TRVocabulary.n3 is also used in L/Thomson/
Hierarchies/GenericHierarchies/KNOS/KNOS_dev_odb.oracle.livecache/
TRVocabulary.n3; to avoid confusion please change it in one or other
file and then try again.
HTTP Error code: 400, Bad request
Should I be uploading the folder created by TBC for the cached
configuration as well as the .oracle file? TBLive does not seem to
like this.
The same issue appears with .oracle files without the cached
configuration too.
My ontologies in oracle just import the TRVocabulary. They have their
own unique base uri.
Thanks,
Catrina
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
