Thx Holger & Irene,
Indeed using an index might be the simplest thing (better than I guess a predefened next and/or previous property). Furthermore, I consider changing our pmo: hasPart into your child one...getting extra TBC support for it for free.... I'll experiment a bit, thx Michel -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Holger Knublauch Sent: 12 March 2009 17:07 To: [email protected] Subject: [tbc-users] Re: 'Order' in OWL? Yes, order is a common request and an important topic. In addition to the rdf collections such as rdf:List and rdf:Seq, you can hand-code ordering by attaching additional triples to the ordered elements. For example, in those cases where the ordered elements are "owned" by the parent, you can simply attach an index to each of them, as described in the Composite Design Pattern [1]. This pattern (based on the composite ontology described below) is extensively supported by TopBraid, so that, for example the fields on the forms will be ordered accordingly. We are also using this pattern for the conversion between XML and RDF/OWL using Semantic XML. There may be other solutions, none of them is easy though, because RDF only has triples... Holger [1] http://composing-the-semantic-web.blogspot.com/2007/07/composite-design- pattern-in-rdfowl.html On Mar 12, 2009, at 2:30 AM, Michel Bohms wrote: > > Dear All, > > I am currently experimenting with the use of SPIN/Sparql when mapping > one ontology to another. > > The source ontology is typically a semantic one (say a Wall class with > height, width and length properties). > The target ontology is typically a less-semantic cad-like explicit > shape representation one (a BoundaryREPresentation (BREP), with > points, lines, faces etc.). > > The target ontology is based on existing schema/data structures like > coming from ISO STEP or IAI, initiatives often not yet OWL but other > languages like EXPRESS. > > In such other languages it is typically possible to model 'order' like > a Face has 4 ordered Lines: Line1, Line2, Line3, Line4, which when > connected in that order give the boundary of the face. > > Now comes my issue: how would I model this 'order' in an OWL-version > of such model? How can I put an order to my taget individuals in my > object properties? In the past I have heard reasons for OWL not > supporting order, being not really a semantic aspect. > > All ideas welcome, thx, Michel Bohms > > This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
