Dear Holger, Scot and others,

We define user defined datatypes now (as we discussed quite some time
ago) as:

<rdfs:Datatype rdf:about="http://www.bimtoolset.org/ontologies/IntUBE-
EnergyBIM.owl#BuildingPartType">
    <rdfs:equivalentClass>
      <rdfs:Datatype>
        <owl:onDatatype rdf:resource="http://www.w3.org/2001/
XMLSchema#string"/>
        <owl:oneOf rdf:parseType="Resource">
          <rdf:rest rdf:parseType="Resource">
            <rdf:rest rdf:parseType="Resource">
              <rdf:rest rdf:parseType="Resource">
                <rdf:rest rdf:parseType="Resource">
                  <rdf:rest rdf:parseType="Resource">
                    <rdf:rest rdf:parseType="Resource">
                      <rdf:rest rdf:resource="http://www.w3.org/
1999/02/22-rdf-syntax-ns#nil"/>
                      <rdf:first rdf:datatype="http://www.w3.org/2001/
XMLSchema#string"
                      >Door</rdf:first>
                    </rdf:rest>
                    <rdf:first rdf:datatype="http://www.w3.org/2001/
XMLSchema#string"
                    >Window</rdf:first>
                  </rdf:rest>
                  <rdf:first rdf:datatype="http://www.w3.org/2001/
XMLSchema#string"
                  >Panel</rdf:first>
                </rdf:rest>
                <rdf:first rdf:datatype="http://www.w3.org/2001/
XMLSchema#string"
                >Wall</rdf:first>
              </rdf:rest>
              <rdf:first rdf:datatype="http://www.w3.org/2001/
XMLSchema#string"
              >SlopingRoof</rdf:first>
            </rdf:rest>
            <rdf:first rdf:datatype="http://www.w3.org/2001/
XMLSchema#string"
            >FlatRoof</rdf:first>
          </rdf:rest>
          <rdf:first rdf:datatype="http://www.w3.org/2001/
XMLSchema#string"
          >Floor</rdf:first>
        </owl:oneOf>
      </rdfs:Datatype>
    </rdfs:equivalentClass>
  </rdfs:Datatype>

I have still two questions here:

1. Is EquivalentClass (as was also used in the primer) really ok?
Shouldn't it be subClass (now all string with this allowed set are
always aBuildingPartType which is ok but if the restriction are milder
like >0 then it becomes more discutable since there are many
userdefined datatype that can be represented by a positive integer..

2. In the primer in case of restriction like >x and <y, the tag
withRestriction is used. Should this tag also not be used HERE in case
of a oneOf which can also be regarded as a restriction?

thanks for advice, Michel

-- 
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