Difference between revisions of "PrF UG files project types"

From Protege Wiki
Jump to: navigation, search
(Automated import of articles)
 
Line 13: Line 13:
  
 
   <li><p>
 
   <li><p>
     Information about the project ontology (classes,
+
     Information about the project ontology
    slots,
+
    (classes, slots, etc.) and project instances,
    etc.) and project instances,
 
 
     stored in one or more additional files.
 
     stored in one or more additional files.
 
     </p>
 
     </p>
Line 22: Line 21:
 
No matter which format you choose,
 
No matter which format you choose,
 
the information specific to the {{#var:PrF}} interface is saved in a <b>.pprj</b> file.
 
the information specific to the {{#var:PrF}} interface is saved in a <b>.pprj</b> file.
You can create,
+
You can create, open, and save your projects directly via the <b>.pprj</b> file.
open,
 
and save your projects directly via the <b>.pprj</b> file.
 
 
You do not need to name or access any other files unless you wish to
 
You do not need to name or access any other files unless you wish to
[[PrF_UG_projects_import_project|import]]
+
[[PrF_UG_projects_import_project|import]] a project.
a project.
 
  
Choosing the project type,
+
Choosing the project type, or <i>backend</i>,
or <i>backend</i>,
+
determines how the project ontology and instances are stored.
determines how the project ontology and instances are stored. {{#var:PrF}} supports three file formats:
+
{{#var:PrF}} supports three file formats:
  
 
<ul class='a'>
 
<ul class='a'>
 
   <li><p>
 
   <li><p>
 
     <b>{{#var:Pr}} Files</b> (the default) creates two text files in {{#var:PrF}} format.
 
     <b>{{#var:Pr}} Files</b> (the default) creates two text files in {{#var:PrF}} format.
     See
+
     See [[PrF_UG_files_protege_files|{{#var:Pr}} Files]].
    [[PrF_UG_files_protege_files|{{#var:Pr}} Files]].
 
 
     </p>
 
     </p>
  
Line 44: Line 39:
 
     To do this,
 
     To do this,
 
     you must have a database installed and configured on your system.
 
     you must have a database installed and configured on your system.
     See
+
     See [[PrF_UG_files_database_backend|{{#var:Pr}} Database Format]].
    [[PrF_UG_files_database_backend|{{#var:Pr}} Database Format]].
 
 
     </p>
 
     </p>
  
 
   <li><p>
 
   <li><p>
 
     <b>Experimental XML</b> saves the project in XML format.
 
     <b>Experimental XML</b> saves the project in XML format.
     See
+
     See [[PrF_UG_files_xml_support|Experimental XML Format]].
    [[PrF_UG_files_xml_support|Experimental XML Format]].
 
 
     </p>
 
     </p>
 
</ul>
 
</ul>
Line 59: Line 52:
 
you would select <b>{{#var:Pr}} Files</b> or <b>Experimental XML</b>.
 
you would select <b>{{#var:Pr}} Files</b> or <b>Experimental XML</b>.
 
If you have installed support for additional backends,
 
If you have installed support for additional backends,
e.g.,
+
e.g., if you selected BASIC + OWL as your installation,
if you selected BASIC + OWL as your installation,
 
 
you will see additional file formats.
 
you will see additional file formats.
  
 
If you decide you wish to change your project type,
 
If you decide you wish to change your project type,
e.g.,
+
e.g., from {{#var:Pr}} Files to Experimental XML,
from {{#var:Pr}} Files to Experimental XML,
+
you can [[PrF_UG_projects_convert_project|convert]] your project.
you can
 
[[PrF_UG_projects_convert_project|convert]]
 
your project.
 
 
This changes the format of the backend,
 
This changes the format of the backend,
while leaving the <b>.pprj</b> file unchanged. {{#var:Pr}} still uses the <b>.pprj</b> file to access the project.
+
while leaving the <b>.pprj</b> file unchanged.
 +
{{#var:Pr}} still uses the <b>.pprj</b> file to access the project.
 
You should not see a difference within {{#var:Pr}}.
 
You should not see a difference within {{#var:Pr}}.
  
You can also
+
You can also [[PrF_UG_projects_export_project|export]]
[[PrF_UG_projects_export_project|export]]
 
 
a project to CLIPS or HTML formats.
 
a project to CLIPS or HTML formats.
In this case,
+
In this case, the project itself stays the same,
the project itself stays the same,
 
 
but a snapshot of the current version is created in the selected format.
 
but a snapshot of the current version is created in the selected format.
  
 
</div>
 
</div>

Revision as of 14:10, October 15, 2008

Understanding Project Types


Protege-Frames User's Guide
Project Types
Understanding Project Types
Protege Files
Protege DB Format
Experimental XML Format
Protege-OWL
RDF(S) Support in Protege
Using the RDF Backend
Exporting a Project to CLIPS
Exporting a Project to HTML
Glossary, Editing Help

Every Protege-Frames project stores two kinds of information:

  • Protege-specific information, stored in a .pprj (Protégé project) file

  • Information about the project ontology (classes, slots, etc.) and project instances, stored in one or more additional files.

No matter which format you choose, the information specific to the Protege-Frames interface is saved in a .pprj file. You can create, open, and save your projects directly via the .pprj file. You do not need to name or access any other files unless you wish to import a project.

Choosing the project type, or backend, determines how the project ontology and instances are stored. Protege-Frames supports three file formats:

  • Protege Files (the default) creates two text files in Protege-Frames format. See Protege Files.

  • Protege Database creates the project as a table in a JDBC database. To do this, you must have a database installed and configured on your system. See Protege Database Format.

  • Experimental XML saves the project in XML format. See Experimental XML Format.

Normally, for a Protege-Frames project, you would select Protege Files or Experimental XML. If you have installed support for additional backends, e.g., if you selected BASIC + OWL as your installation, you will see additional file formats.

If you decide you wish to change your project type, e.g., from Protege Files to Experimental XML, you can convert your project. This changes the format of the backend, while leaving the .pprj file unchanged. Protege still uses the .pprj file to access the project. You should not see a difference within Protege.

You can also export a project to CLIPS or HTML formats. In this case, the project itself stays the same, but a snapshot of the current version is created in the selected format.