Thank you Gokhan, I just show that and adjusted the class from rdfs:Class to owl:Class and then they showed up under owl:Thing.
Thks On Wednesday, July 18, 2012 2:10:56 PM UTC-4, Gokhan Soydan wrote: > > Hello, > > The generated results seem to have rdfs:Class as their type, so that is > why the root classes show up as a subclass of rdfs:Resource by default. If > they have owl:Class as their type, then the root classes would show up as a > subclass of owl:Thing by default. > > Gokhan > > > > >> After looking at the converted spreadsheet result, I wonder whether all >> the classes should be under owl:Thing or not? Does it matter or not? >> >> Currently they are all showing up under rdfs:resource. >> >> Thanks again. >> >> PS: screenshot attached. >> >> >> On Wednesday, July 18, 2012 12:29:25 PM UTC-4, OntoLearner wrote: >>> >>> Thanks Bob, >>> >>> I just ran the query on my sample data as advised and I am getting some >>> results already. I will come back with more questions if necessary. >>> >>> >>> On Tuesday, July 17, 2012 1:11:04 PM UTC-4, OntoLearner wrote: >>>> >>>> Hello everyone, >>>> >>>> I have a spreadsheet with 5 columns, which needs to be converted into >>>> OWL. The columns contain sub-category (sub-class), and I am trying to >>>> convert the spreadsheet in a way that allows for the lowest level element >>>> to be related to the subclass above it in the hierarchy, and the so that >>>> there is some kind of cascading effect. The columns are: A, B, C, D, E, >>>> and >>>> F, so the result should be as follows: E->D->C-B->A. With A being the >>>> highest class in the chain. By making F a subclass of E, I am hoping to >>>> have a cascading effect, whereby E will be automatically related to D, C, >>>> B, and A. >>>> >>>> Here is an example of my spreadsheet: >>>> >>>> column1 column2 column3 column3 column4 SuperClass 1 SubClass 1-1 >>>> SuperClass 2 SubClass 1-2 SubClass 2-1 >>>> SuperClass 3 SubClass 1-3 SubClass 2-2 >>>> SuperClass 4 SubClass 1-4 SubClass 2-3 >>>> SuperClass 5 SubClass 1-5 SubClass 2-4 >>>> SuperClass 6 SubClass 1-6 SubClass 2-5 >>>> SuperClass 7 SubClass 1-7 SubClass 2-6 SubClass 3-1 SubClass 4-1 >>>> SuperClass 8 SubClass 1-8 SubClass 2-7 SubClass 3-2 SubClass 4-2 >>>> >>>> So column4 is a subclass to column3, column3 subclass to column2, and >>>> column2 subclass to column1, which is my superclass. >>>> >>>> Hopefully this makes sense to you. >>>> >>>> PS: I have also attached sample data for easy reference. >>>> >>> -- >> -- You received this message because you are subscribed to the Google >> Group "TopBraid Suite Users", the topics of which include Enterprise >> Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, >> TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN. >> To post to this group, send email to >> topbraid-users@googlegroups.com >> To unsubscribe from this group, send email to >> topbraid-users+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/topbraid-users?hl=en >> >> >> > > -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
