Re: [topbraid-users] Base URI 101

[Scott Henninger]

John; The issue here is a bit of a mismatch between Sesame and Composer.  If you open the Sesame connector and look at the Ontology Home (house-like icon), it will probably show as a red URI in the top search box and the Home page is incomplete - i.e. the Overview page for defining prefixes, etc are not available.  The reason is that Composer is expecting a triple {<baseURI> a owl:Ontology}.  If you create the Sesame repository via an export from Composer, this problem won't occur because the exporter includes that triple.  However if the repository was created by some other entity, the type statement may not be present.  In that case, execute the following on the model in the SPARQL View: INSERT {<baseURI> a owl:Ontology} WHERE {} ...where <baseURI> is the value that appears in Name property for the Resource Form in Ontology Home.  Close the file and re-open it.  The Overview, etc. will appear and new resources will be created using one of the prefixes. That should fix the problem.  The reason http://no.suitable.default/namespace# was being used as the default namespace is because our code expects the ontology type statement, which is used to help resolve the namespace.  This may be a deficiency we should look into. Base URI and default namespace actually have separate purposes in Composer:   - Base URI: The name of the graph (or dataset in SPARQL terms)   - Default Namespace: the namespace of entities in the file So when you create a resource (URI/IRI) without specifying a namespace or prefix, it will default to the default namespace.  A best practice, BTW, is to not use the default namespace on models that will be imported by other models.  If both the imported and importing file use a default namespace, then there is potential for confusion with qnames.  That could be a longer story for a different time.. BTW, this is a topic, amongst many others, we cover in our trainings. -- Scott ---- Scott Henninger Platform Product Manager, Senior Product and Training Engineer TopQuadrant, Inc., tel: 402-429-3751 / fax: 703 991-8192 / main: 703 299-9330 Training:    Introduction to Semantic Web Technologies - March. 5-8, 2012, Washington, DC    TopBraid Advanced Products Training - April 9-12, 2012, Washington, DC    Introduction to Semantic Web Technologies - April 24-26, 2012, New York, NY TQ Blog: Voyages of the Semantic Enterprise On 2/14/12 5:17 PM, John Perdoni wrote: Hi all, Firstly thank you very much for the new Sesame connector update in the new beta. You are really doing some sterling work and just before I ask yet another question, I would like to say that the level of support for debutants within this field is unrivalled. As usual not having a deep web background my basic knowledge is once again letting me down, so once again I hope you can take the time to help. Ok, I have a sesame repository which I can now sucessfully connect to and create named graph using the "Create Connection to Sesame Repository" wizard. by filling in the fields as follows: Base Uri: http://example.co.uk Service URL: http://localhost:9090/openrdf-sesame/ Graph name (optional) : http://localhost:9090/openrdf-sesame/namedGraph1 This succesfully creates a "context" (named Graph) within the sesame repository  but I need to understand why when opening up the S2R file and adding a subclass to owl:Thing TBC I get <http://no.suitable.default/namespace#Thing_1> Maybe this is a namespace question, but I  was under the impression (probably wrongly) that namespace were derived from baseUri ie the physical (relative(not 100% sure of this term either ) location of the file) If you could explain in 101 terms how baseURI , namespaces and if you have the time IRI's relate to the above it would be much appreciated. Thanks once again John -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en