I made the following test case. In 3.0, it would not allow me to drag the
TC class onto the AP label on the GUI, like I could before. It predefined
the type as String, and even when I dragged TC into the text field, it
converted it to a String, instead of a reference.
<?xml version="1.0"?>
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
xmlns:TBC="http://www.rtn.ncs.k.com/TBC#";
xmlns:owl="http://www.w3.org/2002/07/owl#";
xmlns:xsd="http://www.w3.org/2001/XMLSchema#";
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#";
xml:base="http://www.rtn.ncs.k.com/TBC";>
<owl:Ontology rdf:about="">
<owl:versionInfo
rdf:datatype="http://www.w3.org/2001/XMLSchema#string";
>Created with TopBraid Composer</owl:versionInfo>
</owl:Ontology>
<owl:Class rdf:ID="TC">
<rdfs:subClassOf rdf:resource="http://www.w3.org/2002/07/owl#Thing"/>
</owl:Class>
<owl:Thing rdf:ID="Thing_1">
<TBC:AP rdf:datatype="http://www.w3.org/2001/XMLSchema#string";
>TBC:TC</TBC:AP>
</owl:Thing>
<owl:AnnotationProperty rdf:ID="AP"/>
</rdf:RDF>
I brought up 2.6, and did the same thing. It allowed me to drag TC onto
the AP tag, and that produced the following:
<?xml version="1.0"?>
<rdf:RDF
xmlns:TBC="http://www.rtn.ncs.k.com/TBC#";
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
xmlns:xsd="http://www.w3.org/2001/XMLSchema#";
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#";
xmlns:owl="http://www.w3.org/2002/07/owl#";
xml:base="http://www.rtn.ncs.k.com/TBC";>
<owl:Ontology rdf:about="">
<owl:versionInfo
rdf:datatype="http://www.w3.org/2001/XMLSchema#string";
>Created with TopBraid Composer</owl:versionInfo>
</owl:Ontology>
<owl:Class rdf:ID="TC">
<rdfs:subClassOf rdf:resource="http://www.w3.org/2002/07/owl#Thing"/>
</owl:Class>
<owl:Thing rdf:ID="Thing_1">
<TBC:AP rdf:resource="#TC"/>
</owl:Thing>
<owl:AnnotationProperty rdf:ID="AP"/>
</rdf:RDF>
<!-- Created with TopBraid Composer -->
Note that the TBC:AP resource is not typed at all, but IMHO that is better
than applying a String every time. The loss of the drag and drop is
inconvenient.
Jim Miller
Principal Software Engineer
Raytheon NCS, Largo, FL
(727)768-8942
Holger Knublauch <[email protected]>
Sent by: [email protected]
03/10/2009 06:56 PM
Please respond to
[email protected]
To
[email protected]
cc
Subject
[tbc-users] Re: Annotation properties in latest TBE
Hi James,
I don't think anything has changed since 2.6. I just verified that it
still behaves as it should: When an annotation property (or any other) has
no range (or owl:allValuesFrom), then you can assign either literals or
resources to it. So please double-check that no range exists. The system
just displays a string field as default for empty rows, but you can also
use Add existing... to add existing resources, or if possible use drag and
drop. If you enter a string, you can later change its datatype using the
Change datatype context menu item.
If you are unsure, you would need to provide details on the exact
definition of the annotation property (maybe send source code of it).
Holger
On Mar 10, 2009, at 3:43 PM, James A Miller wrote:
Sorry--I typed TBE when I meant TBC-M. I am using 3.0.0.62.
Specifically, I have displayed an individual. I dragged an
AnnotationProperty into it. And when I try to drag something (a Class)
onto the AnnotationProperty, my mouse cursor just goes away. The default
row, and 'Add empty row' gives me a row with a predefined data type of 'S'
(String)--I want it to be generic (non-specific type), like in 2.6. I
didn't have any better luck with Select Existing.
The core problem is that I can't seem to link two classes via an
AnnotationProperty, but I could before. Is there a newer version of the
application?
Jim Miller
Principal Software Engineer
Raytheon NCS, Largo, FL
(727)768-8942
Scott Henninger <[email protected]>
Sent by: [email protected]
03/10/2009 05:46 PM
Please respond to
[email protected]
To
TopBraid Composer Users <[email protected]>
cc
Subject
[tbc-users] Re: Annotation properties in latest TBE
Jim; It works in 3.0 beta as well. Given an annotation property
appearing on the Form, you can Add empty row... and drag/drop a
resource into the field.
I'm guessing you have some other way of doing this? I'm a little
unclear on what is meant by "load the Object".
-- Scott
On Mar 10, 4:19 pm, James A Miller <[email protected]>
wrote:
> I think there is a new "feature" in the new TopBraid, and I don't know
if
> I have been misusing Annotation Properties, or maybe I'm somehow using
TBE
> incorrectly.
>
> I have an Annotation Property, and I am trying to load the Object. TBE
> shows it to be a String field, and won't let me drop an Object there. Is
> it illegal to have an AnnotationProperty that points at a URI reference?
> If it is legal, how do I get TBE to accept it?
>
> This worked, allowing me to point at an Object URI, in TBE 2.6x
>
> Jim
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
