Hi Jeff,
The reasons that the script with ImportRDFFromWorkspace (the 2nd script)
did better job, but skipped instancePattern are as follows as answers to
your analysis of the 1st script:
It didn't use the range of the defined properties to determine the
types of the subjects imported from the table data. It just makes
them all strings.
The 2nd script imports the rdfs:range triples, so the importer knows how
to assert types.
It's not using the instancePattern to create the URLs for each row
of data.
The instance pattern is not used, for importing the spreadsheet to input
graph, . The first column of the spreadsheet in this case should already
have the instance qnames, and they are used. Importing the spreadsheet
to a new graph vs. the input graph are different. More information is at
the Help page of TopBraid Composer.
TopBraid Composer > Import and Export > Import external information>
ImportSpreadsheets
It's not using the className property to classify each row of data,
it just makes them all owl:Thing's
The 2nd script imports the definition for the resource corresponding to
the className.
Gokhan
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
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-users?hl=en
