Difference between revisions of "PrF UG files xml support"
(Automated import of articles) |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
== Experimental XML Format == | == Experimental XML Format == | ||
| − | {{PrF_UG_TOC_files}}<div id='prf_ug'> | + | <noinclude>{{PrF_UG_TOC_files}}<div id='prf_ug'></noinclude> |
| − | Currently, | + | Currently, the XML backend for {{#var:PrF}} is still under development. |
| − | the XML backend for {{#var:PrF}} is still under development. | ||
The intent is to eventually make this the default backend for {{#var:PrF}}, | The intent is to eventually make this the default backend for {{#var:PrF}}, | ||
once it has become stable and supports the full feature set. | once it has become stable and supports the full feature set. | ||
| − | You can | + | You can [[PrF_UG_projects_creating_a_project|create]] a new XML project |
| − | [[PrF_UG_projects_creating_a_project|create]] | + | by selecting <b>File | Create Project</b> |
| − | a new XML project by selecting <b>File | Create Project</b> and then selecting <b>Experimental XML File</b> in the <b>Create New Project</b> dialog: | + | and then selecting <b>Experimental XML File</b> in the <b>Create New Project</b> dialog: |
| − | <div>[[Image:PrF_UG_files_xml_create.png| | + | <div>[[Image:PrF_UG_files_xml_create.png|frame|none| |
| + | Create New Project, "Experimental ..." selected]]</div> | ||
| − | You can also | + | You can also [[PrF_UG_projects_convert_project|convert]] an existing project to XML |
| − | [[PrF_UG_projects_convert_project|convert]] | + | by selecting <b>File | Convert Project</b> |
| − | an existing project to XML by selecting <b>File | Convert Project</b> and then selecting <b>Experimental XML File</b> in the <b>Convert Project</b> dialog box. | + | and then selecting <b>Experimental XML File</b> in the <b>Convert Project</b> dialog box. |
| − | <b>Note:</b> The XML backend uses its own Schema and will <i>not</i> let you import an arbitrary XML file into {{#var:Pr}}. | + | <b>Note:</b> |
| + | The XML backend uses its own Schema | ||
| + | and will <i>not</i> let you import an arbitrary XML file into {{#var:Pr}}. | ||
The first time you save an XML project, {{#var:Pr}} creates the following files: | The first time you save an XML project, {{#var:Pr}} creates the following files: | ||
| Line 37: | Line 39: | ||
{{#var:PrF}} uses a single XML Schema file that is optimized to work with the {{#var:Pr}} model. | {{#var:PrF}} uses a single XML Schema file that is optimized to work with the {{#var:Pr}} model. | ||
All information in the knowledge base is treated as "instances". | All information in the knowledge base is treated as "instances". | ||
| − | The format of these instances, | + | The format of these instances, described in the Schema file, |
| − | described in the Schema file, | + | is designed to be simple, readable, and easily processible by XSLT in straightforward ways. |
| − | is designed to be simple, | ||
| − | readable, | ||
| − | and easily processible by XSLT in straightforward ways. | ||
The Schema is available at: | The Schema is available at: | ||
| − | + | http://protege.stanford.edu/xml/schema/protege.xsd | |
Feedback on the Schema is strongly solicited. | Feedback on the Schema is strongly solicited. | ||
| − | The schema should not be considered fixed at this point and users should not rely on this backend functioning correctly or upon the schema remaining fixed from build to build. | + | The schema should not be considered fixed at this point |
| + | and users should not rely on this backend functioning correctly | ||
| + | or upon the schema remaining fixed from build to build. | ||
We do encourage you to try it out and report any problems that you see. | We do encourage you to try it out and report any problems that you see. | ||
| − | <b>Note:</b> This backend <i>cannot</i> be used to generate XML Schema files. | + | <b>Note:</b> |
| − | For example, | + | This backend <i>cannot</i> be used to generate XML Schema files. |
| − | it does not turn classes in {{#var:PrF}} into XML Schema complex types. | + | For example, it does not turn classes in {{#var:PrF}} into XML Schema complex types. |
An export mechanism that does this may eventually be developed separately. | An export mechanism that does this may eventually be developed separately. | ||
| − | </div> | + | |
| + | <noinclude></div></noinclude> | ||
Latest revision as of 16:48, November 13, 2008
Experimental XML Format
Currently, the XML backend for Protege-Frames is still under development. The intent is to eventually make this the default backend for Protege-Frames, once it has become stable and supports the full feature set.
You can create a new XML project by selecting File | Create Project and then selecting Experimental XML File in the Create New Project dialog:
You can also convert an existing project to XML by selecting File | Convert Project and then selecting Experimental XML File in the Convert Project dialog box.
Note: The XML backend uses its own Schema and will not let you import an arbitrary XML file into Protege.
The first time you save an XML project, Protege creates the following files:
a .pprj file, which contains Protege-specific UI information
a .xml file, which contains XML-encoded ontology information for the knowledge base\
Protege-Frames uses a single XML Schema file that is optimized to work with the Protege model. All information in the knowledge base is treated as "instances". The format of these instances, described in the Schema file, is designed to be simple, readable, and easily processible by XSLT in straightforward ways. The Schema is available at:
http://protege.stanford.edu/xml/schema/protege.xsd
Feedback on the Schema is strongly solicited. The schema should not be considered fixed at this point and users should not rely on this backend functioning correctly or upon the schema remaining fixed from build to build. We do encourage you to try it out and report any problems that you see.
Note: This backend cannot be used to generate XML Schema files. For example, it does not turn classes in Protege-Frames into XML Schema complex types. An export mechanism that does this may eventually be developed separately.
