Catrina; The "No appropriate form definition could be found" probably comes from viewing a resource that is an instance of a class that does not have a form layout defined for it, or the resource is not associated with a class. Form layout is defined for a class and controls how each class instance is displayed in the Form View (Composer and Ensemble). A default layout is defined for owl:Thing and inherited by all of its subclasses. This means that classes not in the owl:Thing hierarchy do not have a form layout defined.
Are you using a custom Form Layout? If so, are the instances you are viewing attached to a class, and does a layout definition exist for that class? Are form layouts defined in the main file (hierarchy) or the imported (vocabulary) file, or both? I'm assuming that the hierarchy file has the class definitions. Could the type definitions be mismatched (namespace problem being a potential culprit) in the vocabulary file? <When using an Oracle RDF store and imports, where should the imports live?> The general answer to this is anywhere your server (Composer/Live) can get to the URL. owl:imports statements define the URI for the file being imported. Composer (or Live) will first look for the file in the workspace (indexed by base URI). If it cannot be found there, then Composer/Live will attempt to get the ontology from the Web. I have tried this in the format you mentioned (Oracle file importing a text serialization) and it works fine. However, if this is not happening in your case, then we will need to look into this further. Is this using TBC-ME as the server or Live? Are there any differences, no matter how small, between the vocabulary definition in Oracle vs. text file? Does the import happen correctly in Composer, or is the problem only with Ensemble? If there are other potential sources of differences between the vocabulary file being imported, please note and we will see what we can do to help. -- Scott On Sep 14, 10:17 am, Catrina <[email protected]> wrote: > I have created an ontology that contains hierarchy content and imports > a vocabulary ontology (which stores the class and property > definitions). The hierarchy is stored in an Oracle RDF store, but the > vocabulary is only stored on our server within the same project. > > I created an .oracle file to access the hierarchy stored in the RDF > store. Then, I use the .oracle file to view the hierarchy in > Ensemble. However, when I try to view a hierarchy node in the form > panel of Ensemble, I get the following error message: > > No appropriate form definition could be found. > > If I store the vocabulary definition triples in the Oracle RDF store > with the hierarchy content, then I do not get this error and the form > displays as expected. However, when I do NOT store the vocabulary > definition triples in the Oracle RDF store with the hierarchy content, > then the form views do not display as desired. > > When using an Oracle RDF store and imports, where should the imports > live? > > Thanks, > Catrina --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
