Hello Paul;  The XML schema datatypes Composer supports can be turned
on via the Classes View preference.  Choose which data types you need
to display.

<<If I use owl:equivalentClass with the Manchester Syntax the number
of my datatypes double.
I was trying to avoid this. >>

Can you provide a specific example of this?

-- Scott

On Jun 29, 7:07 am, PaulZH <[email protected]> wrote:
> Hi Holger,
>
> On Jun 29, 12:44 pm, Holger Knublauch <[email protected]> wrote:
>
> > Hi Paul,
>
> > On Jun 29, 2010, at 3:40 PM, PaulZH wrote:
>
> > > a) When creating a new instance of class rdfs:Datatype, I expected to
> > > get when using "add existing ..." on property owl:onDatatype the list
> > > of xsd datatypes, but I see none. Is this influenced by a setting?
>
> > Seems to work for me, see screenshot. What exactly are you doing?
>
> I was talking specifically about the whole list of the XML Schema
> (xsd) datatypes, which I do not seem to find.
>
>
>
> > > b) What is the syntax to be used in the value of owl:withRestrictions?
>
> > Did you read this
> >http://composing-the-semantic-web.blogspot.com/2009/10/owl-2-support-...
> > which shows examples of how to enter user-defined datatypes with 
> > restrictions on the TBC forms?
>
> Yes, I did.
>
> >Typically, I would not expect people to enter the low-level properties such 
> >as  owl:withRestrictions manually.
> >Could you clarify why you are attempting this, and why the inline text 
> >notation (Manchester Syntax) would not work?
>
> If I use owl:equivalentClass with the Manchester Syntax the number of
> my datatypes double.
> I was trying to avoid this.
>
> Paul

-- 
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion 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

Reply via email to