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 -~----------~----~----~----~------~----~------~--~---
