Difference between revisions of "PrF UG projects import project"
| Line 2: | Line 2: | ||
== Importing a Project == | == Importing a Project == | ||
| − | {{PrF_UG_TOC_projects}}<div id='prf_ug'> | + | <noinclude>{{PrF_UG_TOC_projects}}<div id='prf_ug'></noinclude> |
Importing a project creates a new {{#var:PrF}} project and <b>.pprj</b> file, | Importing a project creates a new {{#var:PrF}} project and <b>.pprj</b> file, | ||
| Line 40: | Line 40: | ||
| − | </div> | + | <noinclude></div></noinclude> |
Latest revision as of 17:32, November 13, 2008
Importing a Project
Importing a project creates a new Protege-Frames project and .pprj file, based on files which contain your ontology information in one of the supported formats. When you import a project, a .pprj file is built, based on the information in your existing files.
To do this, create a new project and make sure that Create from Existing Sources is checked in the Create New Project dialog box.
You can import a project from the following project types:
Text Files: You can import a project from a pair of text files describing the class/slot (e.g., abc.pont) and instance (e.g., abc.pins) information. Importing a text project can be used, for example, for updating from Protege-Frames/Win to Protege.
Database Table: You can import a project from a single table in a JDBC database.
You can not import an XML file into Protege using the Protege XML backend.
Protege-Frames will generate default forms for all classes in the imported project.
