Hello again, yes there is a reason. The real ontology is much more complex and I need a way to add data to it form an external source with an external application. So my solution is to define a new ontology (o2) which imports the existing ontology (o1) and assigns Elements from the external source to different classes of the ontology (o1). I need a flexibe control over the assignment.
In the ontology (o2) I want to define individuals the external application can use to assign Elements form the source as individuals to classes of the ontology (o1). Therefore I need a way to define one of the classes form (o1) which are subclasses of the class "ont1" in the ontology (o2) as range for "hasType" while creating the new individual. To avoid mistakes if someone else (or me in a few weeks;)) creates a new assignment of a different datasource I would like to define the ontology (o2) in a way that only the possible assignments are selectable. But if the ontology (o1) is changed, the possible range for the object property "hasType" should also change automatically. If there is a better way to do the assignement I am greatful for any suggestions. greetings Christoph Am Montag, 11. November 2013 16:33:11 UTC+1 schrieb Irene Polikoff: > > Chris, > > Any reason why you would not simply say that the range is class Type? > > > On Nov 11, 2013, at 10:25 AM, chris <[email protected] <javascript:>> > wrote: > > Hello, > > I have an ontology with a class "Element", a class "Type" with some > subclasses "Type_1", "Type_2", ..., and an object property "hasType" with > the class "Element" as domain and one of the subclasses from "Type" as > range like: > > <owl:AsymmetricProperty rdf:ID="hasType"> > <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string";>has > type</rdfs:label> > <rdfs:range> > <owl:Class> > <owl:oneOf rdf:parseType="Collection"> > <rdf:Description rdf:ID="Type_1"/> > <rdf:Description rdf:ID="Type_2"/> > </owl:oneOf> > </owl:Class> > </rdfs:range> > <rdfs:domain rdf:resource="#Element"/> > </owl:AsymmetricProperty> > > So I am able to create a new Instance of the class "Element" and choose > "Type_1" or "Type_2" from a list as value for "hasType". > > But I want to define the range of the property "hasType" in a more > flexible way. Is it possible (e. g. with manchester syntax) to define the > range of the property "hasType" as one subclass of the class "Type"? > E. g. if I add the subclass "Type_3" to the class "Type" it becomes > automatically part of the possible range from the object property "hasType". > > best regards > > Christoph > > -- > -- 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 > Insight, SPARQLMotion, SPARQL Web Pages and SPIN. > To post to this group, send email to > [email protected] <javascript:> > To unsubscribe from this group, send email to > [email protected] <javascript:> > 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 Groups > "TopBraid Suite Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- 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 Insight, SPARQLMotion, SPARQL Web Pages 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 --- 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]. For more options, visit https://groups.google.com/groups/opt_out.
