Yes thx I’ll start with the 2-step approach (I called the second step conversion, first one we refer to as translation…syntax versus semantic transformation so to say…)
Thx Michel Dr. ir. H.M. (Michel) Bohms Scientist Specialist Structural Reliability T +31 (0)88 866 31 07 M +31 (0)63 038 12 20 E [email protected]<mailto:[email protected]> Location<http://www.tno.nl/locations/DTS> [cid:[email protected]]<http://www.tno.nl/> This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages. From: [email protected] <[email protected]> On Behalf Of Irene Polikoff Sent: Tuesday, September 21, 2021 1:08 PM To: [email protected] Subject: Re: [topbraid-users] enriching the semantic table If you need to script a custom importer for EDG, here is the way to do it: https://www.topquadrant.com/project/importing-data-using-active-data-shapes/ https://datashapes.org/active/import.html#spreadsheets Once you script it, you can use it repeatedly. The custom import can become a part of the EDG UI. If you are using TBC spreadsheet imports, then you could develop a set of rules or queries to post process converted RDF and save them so you could execute them again later. As David described, this could be done in EDG as well, but this means a 2 step approach to conversion. On Sep 21, 2021, at 6:54 AM, David Price <[email protected]<mailto:[email protected]>> wrote: Hi Michel, The spreadsheet importers that are simple and out-of-the-box support a table-maps-to-single class scenario. If you have a more complex ontology and data about multiple classes in the same spreadsheet table, then you are writing a bespoke importer rather than an EDG Import Spreadsheet by Template kind of thing. One approach we take with some customers is to use an external spreadsheet-to-RDF mapping tool (e.g. R2RML) and then just import the RDF into EDG. This is particularly useful if the spreadsheets are very, very large (i.e. a data migration). A second approach is to make it two steps in EDG, and it sounds like you’ve done the first. For the second, it’s probably simpler to make another graph based on the more complex ontology as the target and write SHACL Rules (i.e. sh:SPARQLRule) which you can include into the target traph to be executed via the Transform tab to do the conversion. After conversion you un-include the rules graph so you’re left with only the real ontology and data based on it. The logic of when/if to create new URIs for things is, however, entirely up to you. Re-generating the same URI many times is fine though, as triples processing means that duplicates cannot be written into the graphs. Cheers, David On 21 Sep 2021, at 11:21, 'Bohms, H.M. (Michel)' via TopBraid Suite Users <[email protected]<mailto:[email protected]>> wrote: When I have read in a semantic excel into TBC/EDG I want to convert it to a more structured ontology (ie normalize it) via sparql construct queries. In a sense I am splitting the big nonnormalized table into multiple tables. In this process I have to (I assume) create IDs for individuals that were not in the original table (more as just a column there). Is there some standard approach for this (like create only first time when encountered, reuse when already created )? Thank for pointing me to the right resources! Michel Dr. ir. H.M. (Michel) Bohms Scientist Specialist Structural Reliability T +31 (0)88 866 31 07 M +31 (0)63 038 12 20 E [email protected]<mailto:[email protected]> Location<http://www.tno.nl/locations/DTS> <image001.gif><http://www.tno.nl/> This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages. -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/452d2e85c60f4002be786f9be49aefd4%40tno.nl<https://groups.google.com/d/msgid/topbraid-users/452d2e85c60f4002be786f9be49aefd4%40tno.nl?utm_medium=email&utm_source=footer>. UK +44 (0) 7788 561308 US +1 (336) 283-0808 -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/034D872D-BA23-4D5A-8D82-83C2EC88BD72%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/034D872D-BA23-4D5A-8D82-83C2EC88BD72%40topquadrant.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/EDACBD0D-01F9-4080-B634-63C025010F9C%40topquadrant.com<https://groups.google.com/d/msgid/topbraid-users/EDACBD0D-01F9-4080-B634-63C025010F9C%40topquadrant.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/88da9f75f19f4832915185254ccbbd3c%40tno.nl.
