Thanks Gokhan, I have tried using sml:ImportRDFFromWorkspace also but is still same issue , I will assume that if is importing to the right class then it will be easy to assume that the properties is already existing at the run time for the script. The funny thing is that it somehow imports some of the object properties right and then instead of creating a new data property as you said it implicitly imports to the right property but as a data property. D.
On Sep 23, 9:21 am, Gokhan Soydan <[email protected]> wrote: > Dswan (Ifeanyi), > > Could you also please import the ontology, where the classes and > properties mentioned in your spreadsheet are defined, into your > SPARQLMotion script using "sml:ImportRDFFromWorkspace" module? So, this > ontology to import into the script would have statements like: > "myProperty rdf:type owl:ObjectProperty" in it. > > I assume that your own property definitions don't already exist during > the script execution, so the sml:ConvertSpreadsheetToRDF assumes that it > has to create new properties, and automatically creates datatype > properties instead. > > Gokhan > > > > Ifeanyi Nwokeabia wrote: > > Hi Holger > > Thanks for the reply,yes I have tried all those variations but maybe I > > am missing something simple ... but lets take a simple case scenario, > > I have an ontology open and then imported the sparqlinMotion lib > > then created a simple module with just the > > sml:ConvertSpreadsheetToRDF with all the parameters properly defined, > > this will simply imports everything just as a data properties even > > though the ontology is open and there is no need to have the system > > triples. Maybe I am missing something please let me know. I can also > > email you the ontology and a sample file.... > > Thanks > > Dswan > > > :sml:ConvertSpreadsheetToRDF > > > On Tue, Sep 22, 2009 at 9:48 PM, Holger Knublauch > > <[email protected] <mailto:[email protected]>> wrote: > > > Hi Dswan, > > > I am not an expert on the spreadsheet importer, but it could be that > > your script does not import the right triples to work with. What are > > the modules that act as RDF input to the module - do you have an > > sml:ImportCurrentRDF, for example? The system may fail to see that > > your properties are owl:ObjectProperties because it may lack the > > corresponding rdf:type triples. If you have used > > sml:ImportRDFFromWorkspace, then you may also need to bring in the > > system triples (sml:ImportSystemTriples), because they define the > > rdf:types of owl:ObjectProperty and its sub-classes. Only with these > > triples, the system would be able to see that (for example), > > owl:TransitiveProperty is a subclass of owl:ObjectProperty. > > > If that's not the case, please provide more details such as a > > screenshot of your script. > > > Regards, > > Holger > > > On Sep 22, 2009, at 4:19 PM, Dswan wrote: > > > > I am using sml:ConvertSpreadsheetToRDF sparqlInmotion to import > > some > > > huge files with the properties defined in top row accordingly . > > > Everything imports right into the right properties but most of the > > > properties that are supposed to be imported as object > > properties as > > > defined in the ontology class show up as data properties instead. I > > > tried using the normal import from owl file spreadsheet(text file) > > > for a small sample set and it works fine with the data properties > > > showing up right and as the right instances of the right class. > > > I am using 3.1.0 Maestro > > > Thanks > > > Dswan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
