I am the most current, stable versions of TBC 2.6.2 and AG 3.1 Java
Edition using Jena Extensions on Windows Vista using Eclipse Version:
3.4.0  I made 2 triplestores in AG.  Both are located in the same
location (i.e. C:\ag\triplestores) but with different triplestore
names.  In all my tests, the only thing I vary is the name of the
triplestore in all of the configuration code.

PROBLEM1

I can execute a bit of JENA/AG code to through straight JAVA, input a
file.OWL into an AG triplestore.  I can verify the size of the AG
triple store before and after.  Example: I have a file called cdm.owl
and it has 44 triples.  I upload this file to AG through JENA, and the
resulting AG TripleStore has 44 triples.  When I do an
fsModel.differences(agModel) and agModel.differences(fsModel) I get no
differences either way.  Also, I can verify by looking at the change
in several key files in the AG TripleStore.

However, when I try to connect to the AG triplestore (using the exact
same information that I use to connect to it through the ag/jena code)
I see only 4 triples in the triple view:

(1) ontology:CDM rdf:type owl:Ontology
(2) ontology:CDM.owl rdf:type owl:Ontology
(3) ontology:standard.owl rdf:type owl:Ontology
(4) ontology:standard.owl rdf:type owl:Ontology

PROBLEM2

So looking at the problem from another perspective, I was interested
to see if I could "export" cdm.owl to Allegrograph via Export->Export/
Merge/Convert RDF Graphs0>AllegroGraph Database Stoarge (*.allegro)
format

TBC can in fact export the file.owl into the AG TripleStore.  However,
there are 55 statements (verse the 44 when I do it through JENA).
Now, it shows up in TBC Triples View but it doesn't show up in the
code!  I correctly connect to the AG TripleStore (which shows there
are 55 triples in the triplestore), but when I query the JENA Model's
size through Jena code, it says the size is 0.

best,
mmv

ps sorry for taking so long to get back, had a few fires to put out.

On Oct 14, 9:13 pm, Scott Henninger <[EMAIL PROTECTED]>
wrote:
> Matt;  Chances are that they are there in Composer-ME, but lack RDFS/
> OWL constructs to view the triples in, for example, the Classes
> hierarchy.  Check the Triples tab (Show View -> Triples) to see if the
> triples are visible to Composer.  If the problem is that the classes
> are not appearing in the Classes hierarchy, the class defs may use
> rdfs:Class instead of owl:Class.  Look for these in the Classes
> hierarchy under rdfs:Class (make sure "Start hierarchy with owl:Thing"
> is turned off).
>
> If these don't resolve the problem there are the usual questions about
> versions (both Maestro and Allegro), OS, what parts aren't appearing
> as expected, etc.
> -- Scott
>
> On Oct 14, 5:28 pm,Matt<[EMAIL PROTECTED]> wrote:
>
> > When I connect to AllegroGraph through TBC (http://agraph.franz.com/
> > tbc/Using_TopBraid-Composer_with_AllegroGraph.pdf) the model is empty
> > even though I know there are statements in the triplestore.  I tried
> > changing the Prefix and BaseURI (as you can see below) that I use in
> > code to successfully pull up the model.  However, while I can verify
> > the statements exist in code, I can't see them in tbc.
>
> > #AllegroGraph metadata for TopBraid
> > #Tue Oct 14 11:19:44 CDT 2008
> > Prefix-rdf=http\://www.w3.org/1999/02/22-rdf-syntax-ns\#
> > Prefix-=http\://www.phinformatics.org/Ontology/Tester1.owl\#
> > Prefix-xsd=http\://www.w3.org/2001/XMLSchema\#
> > Host=154.230.22.14
> > Name=default
> > Prefix-owl=http\://www.w3.org/2002/07/owl\#
> > Port=4567
> > Prefix-rdfs=http\://www.w3.org/2000/01/rdf-schema\#
> > Directory=C\:\\test\\Ag\\ts
> > BaseURI=http\://www.phinformatics.org/Ontology/Tester1.owl
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
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-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to