Yes. I would like to have them displayed under Labels and Descriptions. Interestingly, when I imported the IAO ontology, its annotation properties are automatically displayed there. I have tried to assert my own property as owl:AnnotationProperty in EDG but it has no effect.
[image: annotations.png] On Sunday, July 28, 2019 at 11:16:18 PM UTC-4, Holger Knublauch wrote: > > I was assuming you want to have these properties show up under the Labels > and Descriptions section. If this is not the case then you can use the > ontology itself to declare the properties, e.g. > > ex:myAnnotationProperty > a rdf:Property ; > rdfs:label "my annotation" ; > rdfs:domain rdfs:Class ; > rdfs:range xsd:string . > > This would make the property visible in the Additional Characteristics > section of class forms in edit mode. If you cannot use global rdfs:domains, > using a local owl:Restriction at rdfs:Class should also work. > > rdfs:Class > rdfs:subClassOf [ > a owl:Restriction ; > owl:onProperty ex:myAnnotationProperty ; > owl:allValuesFrom xsd:string ; > ] ; > > (These solutions do change the model at a low level though, and may have > other side effects because you are altering the definition of system > classes, which is why simply changing the UI level (SWP) might be less > risky, thus my previous email). > > Holger > > > On 29/07/2019 12:54, Fan Li wrote: > > Thanks, Hogler. I am a little surprised that it requires me to customize > the form template. I am just curious about the design choice. Is it because > annotation property is for OWL only and not for SHACL? Should I use regular > data property instead? > > On Sunday, July 28, 2019 at 6:47:53 PM UTC-4, Holger Knublauch wrote: >> >> On 29/07/2019 04:20, Irene Polikoff wrote: >> >> Sorry, I now see that your question was about EDG and I gave you the TBC >> answer. >> >> In EDG, forms for classes and properties are pre-defined using SWP. I’ll >> get someone from the development team to respond. >> >> >> This answer applies to 6.2. One choice, if you are familiar with Turtle >> syntax, is to enter the values in the Source Code tab, which can be reached >> using the Open in new browser tab button above the form of the class or >> property. Any additional property that you enter would then show up under >> Additional Characteristics. >> >> If you do want to streamline this process, you need to tell the EDG form >> mechanism about the properties that you want to add. There is no >> distinction between (OWL) annotation properties or other properties from >> that perspective. Given that this is about Ontologies (and not instance >> data), in 6.2 and earlier you need to override the SWP-based form >> definition. Basically, create a new SWP file in TBC, and add an import to >> teamwork.ui.ttlx. Navigate to teamwork:SimpleClassFormBody and in the >> context menu behind ui:overrides click on Create ui:override which produces >> something like teamwork:SimpleClassFormBody_1. There you can change the >> ui:prototype to add something like >> >> <swa:Objects arg:predicate="owl:versionInfo"/> >> >> under the Labels and Description section. After you have refreshed the >> system registries or restarted, it would then show up like >> >> If you want to put this into an EDG installation, upload the SWP file >> using Project Upload. >> >> HTH >> Holger >> >> >> >> Sent from my iPhone >> >> On Jul 28, 2019, at 1:47 PM, Irene Polikoff <[email protected]> >> wrote: >> >> There are two options: >> >> 1. Position your cursor in the annotations section on the form and right >> click, you will get a choice of the available annotation properties to add >> to the form. >> >> 2. Find the property you want to appear on the form in the Properties >> View. Drag and drop it into the form. This will work for any property and >> for any resource, not just classes. >> >> Sent from my iPhone >> >> On Jul 27, 2019, at 4:55 PM, Fan Li <[email protected]> wrote: >> >> I think this should be a simple question but I just can't find an answer. >> How to add annotation properties to ontology classes within EDG? >> -- >> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/topbraid-users/b5dd29e2-a15c-4cb5-aad1-714e129649fe%40googlegroups.com >> >> <https://groups.google.com/d/msgid/topbraid-users/b5dd29e2-a15c-4cb5-aad1-714e129649fe%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/topbraid-users/05EDADC2-3F17-4746-B4D4-64C19097F8E0%40topquadrant.com >> >> <https://groups.google.com/d/msgid/topbraid-users/05EDADC2-3F17-4746-B4D4-64C19097F8E0%40topquadrant.com?utm_medium=email&utm_source=footer> >> . >> >> -- > 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] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/0c6d6209-6f83-4165-81d4-c231dcbbe1ef%40googlegroups.com > > <https://groups.google.com/d/msgid/topbraid-users/0c6d6209-6f83-4165-81d4-c231dcbbe1ef%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/ea5ff6b7-e847-4d1c-bca2-9de32b35b347%40googlegroups.com.
