What are the best practices for modeling templates for future instances? We would like to be able to render a form where the properties are well defined: based on type there is an appropriate widget (multiselect, dropdown, integer value, textbox with freetext, etc), order is defined, etc.

Is it recommended to define classes having properties and all possible properties should be rendered? What about the required widgets? Shall we define range for the property which will constraint the type of the widget? Or shall we use annotation?

Is it a good idea at all, to model the template? Can we use reasoning to validate the instance based on the template info?

Somehow I feel like this information is really data about the instances, but as it was already described here, owl classes - unlike OO - are not property restricted: properties are defining classes and not classes the properties. Or did I miss something?

Thanks, Barna

asked 12 Feb '10, 17:13

Barna's gravatar image

accept rate: 0%

Hi Barna,

We use ontologies to define how information is displayed on the screen. This is a key aspect to visualizing information in both, TopBraid Composer and TopBraid Ensemble. You can see this User Interface ontology at http://www.topquadrant.com/topbraid/2007/01/forms.owl. It is entirely about the display and does not deal with whether members of a certain class should have certain property values.

The latter part of modeling is already supported by the standard RDFS/OWL definitions. If you expect to reuse properties across classes, you should use restrictions in class definitions. Restrictions are local constraints, while domains and ranges are global.

Given that UI templates are purely about the UI, it does not make much sense to use them for data validation. But you can certainly use the domain model for data validation.

As you look at the forms ontology, you will probably want to understand how to use it and to see how would the actual display information look like. If you wanted to, you could experiment with it by downloading TopBraid Composer and creating a form for something. When you save an ontology that has form customizations, a file with .tbc suffix is created. For example, my-ontology.owl.tbc. This is an RDF file that contains form information. You can open it with any editor. If you decide to try this out, make sure to read the following article in the TBC Help facility: TopBraid Composer > User Interface Overview > Resource Editor >Form Layout Panel

You should also be aware of Fresnel vocabularies for display of information. Fresnel takes a similar approach of using a UI ontology.

permanent link

answered 15 Feb '10, 18:47

Irene%20Polikoff's gravatar image

Irene Polikoff
accept rate: 0%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 12 Feb '10, 17:13

question was seen: 1,103 times

last updated: 15 Feb '10, 18:47