Good point! The Source Code sub-tab takes the subject in the Form and generates "localized" serializations for that subject. I.e. a serialization of all triples starting with the resource in the form. That's different than creating a serialization for the entire file. Which is also to say that what is shown in the Source Code sub-tab does not come from the text serialization of the file.
The choice to use RDF/XML when namespaces are not defined is really about the confusion that results when adding j.0, etc prefixes and not being able to control their generation. This doesn't occur for the Source Code sub-tab. <Moreover I am a bit confused about the form "vabi/blinds.owl#Blinds" > I believe this means that your URI or default namespace is http://www.bimtoolset.org/ontologies and rdf:about is providing a URL relative to that base. XML stuff ;-) -- Scott On Dec 2, 4:29 pm, "Bohms, H.M. (Michel)" <[email protected]> wrote: > ok, but... > Why CAN we have the abbreviated form in tbc when code is switched? > > Ie in example ontology sent: > > <rdf:Description rdf:about="vabi/blinds.owl#Blinds"> > <rdfs:subClassOf rdf:resource="pmo-lite.owl#Product"/> > <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/> > </rdf:Description> > > Can be viewed as: > > <owl:Class rdf:about="vabi/blinds.owl#Blinds"> > <rdfs:subClassOf rdf:resource="pmo-lite.owl#Product"/> > </owl:Class> > > If it can be done here why can it not be done when exporting? > > Michel > > Ps > Moreover I am a bit confused about the form > "vabi/blinds.owl#Blinds" > > Since the actual original code was: > <rdf:Description > rdf:about="http://www.bimtoolset.org/ontologies/vabi/blinds.owl#Blinds";> > <rdfs:subClassOf > rdf:resource="http://www.bimtoolset.org/ontologies/pmo-lite.owl#Product"/> > <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/> > </rdf:Description> > > Tel +31 15 2763107 > > E-mail [email protected] > > Webhttp://www.linkedin.com/in/michelbohms > > Skype name michelbohms > > Disclaimer > > -----Original Message----- > From: Scott Henninger [mailto:[email protected]] > Sent: woensdag 2 december 2009 20:01 > To: TopBraid Composer Users > Subject: [tbc-users] Re: untypes resources > > <Issue left: syntax of export seems RDF/XML iso RDF/XML Abbrev. (while > actually I selected the abbreviated form)> > > Yes, if there are any resources that have an rdf:type, but no namespace > prefix defined for its URI, then the export wizard will revert to RDF/XML. > The reason is that RDF/XML Abbrev requires qnames, and the underlying > serialization will start guessing at prefixes, starting with j.0, j.1, etc. > The preference is to use the XML/RDF serialization instead. > > The issue can be resolved by making sure your URIs have valid qnames (i.e. > prefix defs). Then RDF/XML Abbrev. will work. > > -- Scott > > On Dec 2, 10:08 am, "Bohms, H.M. (Michel)" <[email protected]> > wrote: > > right.... > > > I could actually decide the same for my own pmo stuff (leave imported...). > > > (still my proposed option when merging could be handy for the once you > > actually decide to eplxitly merge) > > > Issue left: syntax of export seems RDF/XML iso RDF/XML Abbrev. (while > > actually I selected the abbreviated form) > > > -----Original Message----- > > From: Scott Henninger [mailto:[email protected]] > > Sent: woensdag 2 december 2009 17:01 > > To: TopBraid Composer Users > > Subject: [tbc-users] Re: untypes resources > > > The Ontology statement disappears because ...pmo-lite.owl is no longer the > > ontology file, it is what you exported to (the "global" > > ontology). The rdf:about="" refers to the current file. > > > I also noticed that in your merge (I assume you are using Export... > > Export/Merge/Convert), you have included the imported files. For spin and > > other files it may be best to leave these as imports, i.e. do not check > > them in the Graphs to export part of the wizard. > > > -- Scott > > > On Dec 2, 9:29 am, "Bohms, H.M. (Michel)" <[email protected]> wrote: > > > Hi Scott, some more details...(for error1) > > > > The actually originating code is: > > > > <rdf:Description > > > rdf:about="http://www.bimtoolset.org/ontologies/pmo-lite.owl";> > > > <rdf:type > > > rdf:resource="http://www.w3.org/2002/07/owl#Ontology"/> > > > <rdfs:comment > > > rdf:datatype="http://www.w3.org/2001/XMLSchema#string";>Toplevel > > > Product Modelling Ontology by SWOP</rdfs:comment> > > > <owl:imports rdf:resource="http://spinrdf.org/spin"/> > > > </rdf:Description> > > > > After the export/merge we have in: > > > > <rdf:Description > > > rdf:about="http://www.bimtoolset.org/ontologies/pmo-lite.owl";> > > > <rdfs:comment > > > rdf:datatype="http://www.w3.org/2001/XMLSchema#string";>Toplevel > > > Product Modelling Ontology by SWOP</rdfs:comment> > > > </rdf:Description> > > > > So the: > > > <rdf:type > > > rdf:resource="http://www.w3.org/2002/07/owl#Ontology"/> > > > Is gone....! > > > > The only thing there is: > > > <rdf:Description rdf:about=""> > > > <rdf:type > > > rdf:resource="http://www.w3.org/2002/07/owl#Ontology"/> > > > </rdf:Description> > > > > Ie an empty string...if > > > "http://www.bimtoolset.org/ontologies/pmo-lite.owl"; would have been there > > > the error should go... > > > > I think this is in some way incorrect? > > > > Ch/Michel > > > > -----Original Message----- > > > From: Scott Henninger [mailto:[email protected]] > > > Sent: woensdag 2 december 2009 15:31 > > > To: TopBraid Composer Users > > > Subject: [tbc-users] Re: untypes resources > > > > Michel; The warnings are not critical - they are just stating that the > > > resources do not have a type triple, which is often valid for RDF data. > > > In this case, it appears that import statements are missing for the three > > > resources. This probably occurred during the merges and was either a > > > matter of not including the imports or not filtering out some unnecessary > > > triples. Looking at your data, I suspect it is the latter of the two. > > > > To reveal how these resources are used, I'd suggest using some SPARQL > > > queries. For example: > > > SELECT * > > > WHERE { > > > <http://www.bimtoolset.org/ontologies/pmo-lite.owl> ?p ? > > > object . > > > } > > > > reveals a comment statement. The other untyped resources have similar > > > annotation data. > > > > -- Scott > > > > On Dec 2, 4:52 am, "Bohms, H.M. (Michel)" <[email protected]> wrote: > > > > I get three errors of untyped resources that I don't understand. > > > > As far as I can see all is in there (its an exported/merged total > > > > ontology (from TBC 3.2.1) based on many small ontologies). > > > > Anybody an idea? > > > > > thx a lot, Michel > > > > > a technical issue > > > > - I exported/merged as RDF/XML Abbreviated. Howver the generated > > > > code more looks like just RDF/XM (ie non-abbreviated) > > > > > TNO.NL > > > > > Michel Böhms > > > > > Consultant Building Innovation > > > > > TNO Built Environment and Geosciences > > > > > Van Mourik Broekmanweg 6 | PO Box 49 > > > > > 2600 AA | Delft | The Netherlands > > > > > Tel +31 15 2763107 > > > > > E-mail [email protected] <mailto:[email protected]> > > > > > Webhttp://www.linkedin.com/in/michelbohms<http://www.linkedin.com/ > > > > in > > > > /m > > > > ichelbohms> > > > > > Skype name michelbohms > > > > > Disclaimer > > > > <blocked::http://www.tno.nl/content.cfm?&context=overtno&content=o > > > > ve > > > > rt > > > > nosub&laa...> > > > > > This e-mail and its contents are subject to the DISCLAIMER > > > > athttp://www.tno.nl/disclaimer/email.html > > > > > IntUBE-EnergyBIMv2.owl > > > > 1417KViewDownload > > > > -- > > > > 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 > > > athttp://groups.google.com/group/topbraid-composer-users?hl=en. > > > > This e-mail and its contents are subject to the DISCLAIMER > > > athttp://www.tno.nl/disclaimer/email.html > > > -- > > > 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 > > athttp://groups.google.com/group/topbraid-composer-users?hl=en. > > > This e-mail and its contents are subject to the DISCLAIMER > > athttp://www.tno.nl/disclaimer/email.html > > -- > > 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 > athttp://groups.google.com/group/topbraid-composer-users?hl=en. > > This e-mail and its contents are subject to the DISCLAIMER > athttp://www.tno.nl/disclaimer/email.html -- 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.
