Difference between revisions of "PrF UG files rdf support"

From Protege Wiki
Jump to: navigation, search
(Automated import of articles)
 
Line 4: Line 4:
 
{{PrF_UG_TOC_files}}<div id='prf_ug'>
 
{{PrF_UG_TOC_files}}<div id='prf_ug'>
  
{{#var:Pr}} allows you to create and edit Resource Description Framework (RDF)
+
{{#var:Pr}} allows you
[[PrF_UG_|schema]]
+
to create and edit Resource Description Framework (RDF) [[PrF_UG_|schema]]
and
+
and [[PrF_UG_|instance data]].
[[PrF_UG_|instance data]].
 
 
(For more information about RDF,
 
(For more information about RDF,
see
+
see [[PrF_UG_|http://www.w3.org/RDF]].)
[[PrF_UG_|http://www.w3.org/RDF]].)
+
{{#var:Pr}} provides the following types of [[PrF_UG_|RDF (Schema)]] support:
{{#var:Pr}} provides the following types of
 
[[PrF_UG_|RDF (Schema)]]
 
support:
 
  
 
<ul class='a'>
 
<ul class='a'>
Line 22: Line 18:
  
 
   <li><p>
 
   <li><p>
     an
+
     an [[#RDF_Backend_for_Protege-frames|RDF backend]] for {{#var:PrF}}
    [[#RDF_Backend_for_Protege-frames|RDF backend]]
 
    for {{#var:PrF}}
 
 
     </p>
 
     </p>
  
 
   <li><p>
 
   <li><p>
     additional
+
     additional [[#Additional_RDF_Plug-ins|RDF(S) plug-ins]]
    [[#Additional_RDF_Plug-ins|RDF(S) plug-ins]]
+
     for {{#var:PrF}}, including Sesame and Joseki support
     for {{#var:PrF}},
 
    including Sesame and Joseki support
 
 
     </p>
 
     </p>
 
</ul>
 
</ul>
Line 38: Line 30:
  
 
OWL is an extension of RDF,
 
OWL is an extension of RDF,
so any RDF project can also be regarded as an OWL project which simply does not use the advanced OWL features.
+
so any RDF project can also be regarded as an OWL project
 +
which simply does not use the advanced OWL features.
 
Although the focus of the OWL Plugin is on OWL ontologies,
 
Although the focus of the OWL Plugin is on OWL ontologies,
 
it can also be used to edit RDF ontologies and RDF Schema files or databases.
 
it can also be used to edit RDF ontologies and RDF Schema files or databases.
However,
+
However, we don't recommend mixing pure RDF(S) elements
we don't recommend mixing pure RDF(S) elements with OWL elements in OWL ontologies.
+
with OWL elements in OWL ontologies.
  
 
The following steps show how to:
 
The following steps show how to:
Line 60: Line 53:
 
These steps address the file format only;
 
These steps address the file format only;
 
for additional information,
 
for additional information,
see the
+
see the [[PrF_UG_|{{#var:PrO}} resources]] page.
[[PrF_UG_|{{#var:PrO}} resources]]
 
page.
 
  
 
Please note the following limitations:
 
Please note the following limitations:
Line 73: Line 64:
  
 
   <li><p>
 
   <li><p>
     Currently,
+
     Currently, when you go to import (open from an existing) RDF(S) file,
    when you go to import (open from an existing) RDF(S) file,
 
 
     there is no separate RDF format option.
 
     there is no separate RDF format option.
     You need to select <b>OWL Files (.owl or .rdf)</b> and later select <b>RDF Schema</b> or <b>Pure RDF Schema without OWL</b>.
+
     You need to select <b>OWL Files (.owl or .rdf)</b>
 +
    and later select <b>RDF Schema</b> or <b>Pure RDF Schema without OWL</b>.
 
     </p>
 
     </p>
  
Line 82: Line 73:
 
     When you save your RDF(S) project,
 
     When you save your RDF(S) project,
 
     the interface currently does not save separate RDFS and RDF files;
 
     the interface currently does not save separate RDFS and RDF files;
     instead,
+
     instead, it combines everything in a single file that is given a <b>.owl</b> extension.
    it combines everything in a single file that is given a <b>.owl</b> extension.
 
 
     This may be fixed in future versions.
 
     This may be fixed in future versions.
 
     </p>
 
     </p>
 
</ul>
 
</ul>
  
Note that the use of RDF in {{#var:PrO}} is not necessarily compatible with the RDF Backend for {{#var:PrF}},
+
Note that the use of RDF in {{#var:PrO}} is not necessarily compatible
 +
with the RDF Backend for {{#var:PrF}},
 
which was initially developed prior to the existence of OWL.
 
which was initially developed prior to the existence of OWL.
Overall,
+
Overall, the RDF support in {{#var:PrO}} provides cleaner semantics
the RDF support in {{#var:PrO}} provides cleaner semantics and a richer set of modeling elements.
+
and a richer set of modeling elements.
  
 
=== Importing or Creating an RDF(S) Project with {{#var:PrO}} ===
 
=== Importing or Creating an RDF(S) Project with {{#var:PrO}} ===
Line 98: Line 89:
 
   <li><p>
 
   <li><p>
 
     Create a new project,
 
     Create a new project,
     either by selecting <b>Create New Project</b> from the start-up dialog or <b>File | Create New</b> in the {{#var:Pr}} window.
+
     either by selecting <b>Create New Project</b> from the start-up dialog
 +
    or <b>File | Create New</b> in the {{#var:Pr}} window.
 
     </p>
 
     </p>
  
 
   <li><p>
 
   <li><p>
 
     Select <b>OWL Files (.owl or .rdf)</b> as the Project Type.
 
     Select <b>OWL Files (.owl or .rdf)</b> as the Project Type.
   
 
    </p><p> <div>[[Image:PrF_UG_files_create_rdf_dialog.png|files_create_rdf_dialog]]</div>
 
 
     </p>
 
     </p>
 +
    <div>[[Image:PrF_UG_files_create_rdf_dialog.png|files_create_rdf_dialog]]</div>
  
 
   <li><p>
 
   <li><p>
Line 113: Line 104:
 
     If you are creating a <i>new</i> RDF file,
 
     If you are creating a <i>new</i> RDF file,
 
     leave it unchecked (default).
 
     leave it unchecked (default).
   
 
    </p><p> <div>[[Image:PrF_UG_files_create_from_existing_checkbox.png|files_create_from_existing_checkbox]]</div>
 
 
     </p>
 
     </p>
 +
    <div>[[Image:PrF_UG_files_create_from_existing_checkbox.png|files_create_from_existing_checkbox]]</div>
  
 
   <li><p>
 
   <li><p>
Line 133: Line 123:
 
     For an RDF project,
 
     For an RDF project,
 
     select <b>RDF Schema</b> or <b>Pure RDF Schema without OWL</b>.
 
     select <b>RDF Schema</b> or <b>Pure RDF Schema without OWL</b>.
   
 
    </p><p> <div>[[Image:PrF_UG_files_select_owl_language.png|files_select_owl_language]]</div>
 
 
     </p>
 
     </p>
 +
    <div>[[Image:PrF_UG_files_select_owl_language.png|files_select_owl_language]]</div>
 
</ol>
 
</ol>
  
Line 149: Line 138:
 
   <li><p>
 
   <li><p>
 
     In the OWL Preferences dialog,
 
     In the OWL Preferences dialog,
     activate an RDF profile by changing the Language Profile to <b>RDF Schema</b> or <b>Pure RDF Schema without OWL.</b>
+
     activate an RDF profile by changing the Language Profile
    </p><p> <div>[[Image:PrF_UG_files_owl_preferences_dialog.png|files_owl_preferences_dialog]]</div>
+
    to <b>RDF Schema</b> or <b>Pure RDF Schema without OWL.</b>
 
     </p>
 
     </p>
 +
    <div>[[Image:PrF_UG_files_owl_preferences_dialog.png|files_owl_preferences_dialog]]</div>
  
 
   <li><p>
 
   <li><p>
Line 170: Line 160:
 
     there will be an additional button on the Properties tab,
 
     there will be an additional button on the Properties tab,
 
     which can be used to create RDF properties:
 
     which can be used to create RDF properties:
     [[Image:PrF_UG_files_extra_rdf_button.png|files_extra_rdf_button]]You can also decide whether new classes shall be RDFS classes or OWL classes using "Create class using metaclass",
+
     [[Image:PrF_UG_files_extra_rdf_button.png|files_extra_rdf_button]]
     or you can make rdfs:Class the default metaclass (both with a right-click on the classes tree in the OWLClasses tab).
+
    You can also decide whether new classes shall be RDFS classes
 +
    or OWL classes using "Create class using metaclass",
 +
     or you can make rdfs:Class the default metaclass
 +
    (both with a right-click on the classes tree in the OWLClasses tab).
 
     </p>
 
     </p>
  
Line 177: Line 170:
 
     If you chose <b>Pure RDF Schema without OWL</b>,
 
     If you chose <b>Pure RDF Schema without OWL</b>,
 
     the buttons on the Properties tab will be restricted to RDF properties:
 
     the buttons on the Properties tab will be restricted to RDF properties:
   
 
    </p><p> <div>[[Image:PrF_UG_files_pure_rdf_buttons.png|files_pure_rdf_buttons]]</div>
 
 
     </p>
 
     </p>
 +
    <div>[[Image:PrF_UG_files_pure_rdf_buttons.png|files_pure_rdf_buttons]]</div>
 
</ul>
 
</ul>
  
Line 188: Line 180:
 
You can use {{#var:PrF}} to design RDF schema and create the corresponding instance data.
 
You can use {{#var:PrF}} to design RDF schema and create the corresponding instance data.
 
You can also view and edit your existing RDF files in {{#var:PrF}}.
 
You can also view and edit your existing RDF files in {{#var:PrF}}.
The
+
The [[PrF_UG_|RDF backend]] for {{#var:PrF}}
[[PrF_UG_|RDF backend]]
+
was developed prior to the development of the {{#var:Pr}} OWL interface
for {{#var:PrF}} was developed prior to the development of the {{#var:Pr}} OWL interface and is not necessarily compatible with {{#var:PrO}}.
+
and is not necessarily compatible with {{#var:PrO}}.
 
With the advent of {{#var:PrO}},
 
With the advent of {{#var:PrO}},
 
it is no longer under active development,
 
it is no longer under active development,
Line 201: Line 193:
 
</ul>
 
</ul>
  
<b>Note:</b> This backend is actually an RDFS/RDF backend which saves a schema file
+
<b>Note:</b>
(RDFS)
+
This backend is actually an RDFS/RDF backend which saves a schema file (RDFS)
 
and an instance file (RDF).
 
and an instance file (RDF).
  
Line 218: Line 210:
 
     Only the RDF Schema namespace
 
     Only the RDF Schema namespace
 
     [[PrF_UG_|http://www.w3.org/TR/1999/PR-rdf-schema-19990303]]
 
     [[PrF_UG_|http://www.w3.org/TR/1999/PR-rdf-schema-19990303]]
     is supported when saving (on import,
+
     is supported when saving
    the new namespace is also recognized).
+
    (on import, the new namespace is also recognized).
 
     </p>
 
     </p>
  
 
   <li><p>
 
   <li><p>
     Namespace abbreviations cannot be edited (they are automatically generated).
+
     Namespace abbreviations cannot be edited
 +
    (they are automatically generated).
 
     </p>
 
     </p>
  
 
   <li><p>
 
   <li><p>
 
     <tt>rdfs:seeAlso</tt>, <tt>rdfs:isDefinedBy</tt>, <tt>rdfs:label</tt>,
 
     <tt>rdfs:seeAlso</tt>, <tt>rdfs:isDefinedBy</tt>, <tt>rdfs:label</tt>,
     container,
+
     container, and reified statements are not supported.
    and reified statements are not supported.
 
 
     </p>
 
     </p>
  
Line 238: Line 230:
  
 
   <li><p>
 
   <li><p>
     You cannot make changes to the standard meta classes. (i.e., <tt>rdf:Resource</tt>, <tt>rdf:Property</tt>, <tt>rdfs:Class</tt>,
+
     You cannot make changes to the standard meta classes.
    etc.)
+
    (i.e., <tt>rdf:Resource</tt>, <tt>rdf:Property</tt>, <tt>rdfs:Class</tt>, etc.)
 
     </p>
 
     </p>
  
 
   <li><p>
 
   <li><p>
     XML Schema data types are not recognized as <tt>rdfs:Literal</tt> (but it is unclear that they should be).
+
     XML Schema data types are not recognized as <tt>rdfs:Literal</tt>
 +
    (but it is unclear that they should be).
 
     </p>
 
     </p>
 
</ul>
 
</ul>

Revision as of 13:24, October 15, 2008

RDF(S) Support in


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

Protege allows you to create and edit Resource Description Framework (RDF) schema and instance data. (For more information about RDF, see http://www.w3.org/RDF.) Protege provides the following types of RDF (Schema) support:

Protege-OWL and RDF(S)

OWL is an extension of RDF, so any RDF project can also be regarded as an OWL project which simply does not use the advanced OWL features. Although the focus of the OWL Plugin is on OWL ontologies, it can also be used to edit RDF ontologies and RDF Schema files or databases. However, we don't recommend mixing pure RDF(S) elements with OWL elements in OWL ontologies.

The following steps show how to:

These steps address the file format only; for additional information, see the Protege-OWL resources page.

Please note the following limitations:

  • Although you may see the full OWL interface when editing an RDF(S) project, it is your responsibility to avoid using OWL-specific elements in your project.

  • Currently, when you go to import (open from an existing) RDF(S) file, there is no separate RDF format option. You need to select OWL Files (.owl or .rdf) and later select RDF Schema or Pure RDF Schema without OWL.

  • When you save your RDF(S) project, the interface currently does not save separate RDFS and RDF files; instead, it combines everything in a single file that is given a .owl extension. This may be fixed in future versions.

Note that the use of RDF in Protege-OWL is not necessarily compatible with the RDF Backend for Protege-Frames, which was initially developed prior to the existence of OWL. Overall, the RDF support in Protege-OWL provides cleaner semantics and a richer set of modeling elements.

Importing or Creating an RDF(S) Project with Protege-OWL

  1. Create a new project, either by selecting Create New Project from the start-up dialog or File | Create New in the Protege window.

  2. Select OWL Files (.owl or .rdf) as the Project Type.

    files_create_rdf_dialog
  3. If you are importing an existing file, make sure to check Create from Existing Sources, located at the top of the dialog box. If you are creating a new RDF file, leave it unchecked (default).

    files_create_from_existing_checkbox
  4. Click Next.

  5. Specify any common ontologies to use and click Next.

  6. Specify your default RDF namespace and click Next.

  7. You can now choose your language profile. For an RDF project, select RDF Schema or Pure RDF Schema without OWL.

    files_select_owl_language

Activating RDF(S) Support in an OWL Project

To activate RDF(S) support in an existing Protege-OWL project:

  1. Select the OWL | Preferences menu option.

  2. In the OWL Preferences dialog, activate an RDF profile by changing the Language Profile to RDF Schema or Pure RDF Schema without OWL.

    files_owl_preferences_dialog
  3. Click Close.

  4. The Protege-OWL window will display buttons to create pure RDFS classes and RDF properties. In particular:

  • If you chose RDF Schema, there will be an additional button on the Properties tab, which can be used to create RDF properties: files_extra_rdf_button You can also decide whether new classes shall be RDFS classes or OWL classes using "Create class using metaclass", or you can make rdfs:Class the default metaclass (both with a right-click on the classes tree in the OWLClasses tab).

  • If you chose Pure RDF Schema without OWL, the buttons on the Properties tab will be restricted to RDF properties:

    files_pure_rdf_buttons

RDF Backend for Protege-Frames

You can use Protege-Frames to design RDF schema and create the corresponding instance data. You can also view and edit your existing RDF files in Protege-Frames. The RDF backend for Protege-Frames was developed prior to the development of the Protege OWL interface and is not necessarily compatible with Protege-OWL. With the advent of Protege-OWL, it is no longer under active development, but some support is still available.

Note: This backend is actually an RDFS/RDF backend which saves a schema file (RDFS) and an instance file (RDF).

This interface has a number of limitations:

  • The backend uses the standard Protege-Frames GUI, which is not RDF(S) -specific. It is not clear how you can enter RDF specific elements. You see exactly the same GUI as for "normal" Protege-Frames.

  • Only the RDF Schema namespace http://www.w3.org/TR/1999/PR-rdf-schema-19990303 is supported when saving (on import, the new namespace is also recognized).

  • Namespace abbreviations cannot be edited (they are automatically generated).

  • rdfs:seeAlso, rdfs:isDefinedBy, rdfs:label, container, and reified statements are not supported.

  • Multiple types for a single resource were not supported, prior to the 3.3 release.

  • You cannot make changes to the standard meta classes. (i.e., rdf:Resource, rdf:Property, rdfs:Class, etc.)

  • XML Schema data types are not recognized as rdfs:Literal (but it is unclear that they should be).

Additional RDF Plug-ins

The Protege community has written additional RDF plug-ins to support other RDF frameworks: