Hi Jeff, this already works, and spl:Attributes will be handled the same way that rdfs:domains and OWL restrictions will. However, I noticed after the recent change (to make spl:Attribute use a CONSTRUCT instead of an ASK as you requested), that CONSTRUCT templates are not handled the same way. Thus you either need to roll back to the official version of SPL or wait for the next release where this is fixed.
Regards Holger On Dec 7, 2009, at 8:44 AM, Schmitz, Jeffrey A wrote: > Hello, > In most of my Class definitions I define spin Attributes for properties > (specified using the Attribute spl:predicate property) associated with the > class. Is there a way to get these properties to show up on the form view > for class instances even when there is no currently defined value for the > spl:predicate defined for the Attribute? This would be much like the form > view currently takes into account property domain and range definitions when > deciding what to show on the form view for class instances. > > Thanks, > Jeff > > > > -- > > 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. > > -- 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.
