Hi Scott,
In a related question, the semantic xml import doesn't seem to assign a
composite:index for elements defined as simpleType in the xsd. Instead it
references simpleType element values via a DatatypeProperty. Is there away
(other than changing simpleTypes to complexTypes in the xsd) to make the
import create an ObjectProperty reference with a composite:index for
simpleTypes instead so that simpleType element orders can be retained?
e.g. if I have the following two sibling elements:
<literal>1</literal>
<op>eq</op>
With 'literal' being defined as a
<xsd:complexType name="literal-type" mixed="true">
<xsd:complexContent>
...
</xsd:complexType>
And 'op' being defined as:
<xsd:simpleType name="op-type">
<xsd:restriction base="xsd:token">
<xsd:enumeration value="+"/>
...
</xsd:restriction>
</xsd:simpleType>
Composite:index is only generated for the literal elements, not on the op
elements and I need to be able to retain order amongst all the siblings, be
they simple or complex elements.
Thanks!
Jeff
On Wednesday, January 20, 2010 11:33:34 AM UTC-6, Scott Henninger wrote:
>
> Pim; Yes, element ordering is build into Semantic XML through
> composite:index. See Help > Import and Export > Creating, Importing,
> Querying, Saving XML documents with Semantic XML
>
> -- Scott
>
> On Jan 20, 11:25 am, "Helm, P.W. (Pim) van den"
> <[email protected]> wrote:
> > I have an gbXML file that I opened as semantic xml via topbraid composer
> > and stored as OWL (so I call this the owl result). Within gbXML
> > cartesianpoints are descibed as:
> > <CartesianPoint>
> > <Coordinate>480.00000</Coordinate>
> > <Coordinate>1320.00000</Coordinate>
> > <Coordinate>0.00000</Coordinate>
> > </CartesianPoint>
> >
> > Although this doesn't indicate any order, actually it is assumed to be
> > in the order of x, y and z coordinate.
> >
> > In my owl result I will losse this order. Is there any query possible
> > that can construct the order by finding all first coordinate sxml:child
> > elements and typing them as x-value, and the second as y-value, etc?
> >
> > So actually I need a query that can determine the order again in how it
> > is described in the original xml (that is also available in the owl via
> > the sxml:child attributes). Can anyone help me with this? Or is this
> > imposible to do?
> >
> > Kind regards,
> > Pim van den Helm
> > This e-mail and its contents are subject to the DISCLAIMER athttp://
> www.tno.nl/disclaimer/email.html
>
>
--
-- 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
[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.
