| kprice | ef16068 | 2006-08-29 18:08:31 +0000 | [diff] [blame] | 1 | <?xml version="1.0" encoding="utf-8"?>
|
| 2 | <!--Arbortext, Inc., 1988-2005, v.4002-->
|
| 3 | <!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
|
| 4 | <task id="tedtsch" xml:lang="en-us">
|
| 5 | <title>Editing namespace information</title>
|
| 6 | <titlealts>
|
| 7 | <searchtitle>Editing namespace information</searchtitle>
|
| 8 | </titlealts>
|
| 9 | <shortdesc>Your namespace information is used to provide various information
|
| 10 | about the XML file, such as the XML schema and namespace it is associated
|
| 11 | with. If desired, you can change the schema and namespace your XML file is
|
| 12 | associated with or add a new association. Modifying any associations can impact
|
| 13 | what content is allowed in the XML file.</shortdesc>
|
| 14 | <prolog><metadata>
|
| kprice | 9623e9d | 2007-05-03 03:43:05 +0000 | [diff] [blame] | 15 | <keywords><indexterm>XML editor<indexterm>namespace information</indexterm></indexterm>
|
| 16 | <indexterm>XML files<indexterm>namespace information</indexterm></indexterm>
|
| kprice | ef16068 | 2006-08-29 18:08:31 +0000 | [diff] [blame] | 17 | </keywords>
|
| 18 | </metadata></prolog>
|
| 19 | <taskbody>
|
| 20 | <context><p>The following instructions were written for the Resource perspective,
|
| 21 | but they will also work in many other perspectives.</p><p>To edit your schema
|
| 22 | information, follow these steps:</p></context>
|
| 23 | <steps>
|
| 24 | <step><cmd>In the Design view of the XML editor, right-click your root element
|
| 25 | and click <uicontrol>Edit Namespaces</uicontrol>.</cmd></step>
|
| 26 | <step><cmd>Your XML file can be associated with more than one namespace or
|
| 27 | schema.</cmd><info>Select the entry you want to edit and click <uicontrol>Edit</uicontrol>.</info>
|
| 28 | </step>
|
| 29 | <step><cmd>The value in the <uicontrol>Namespace Name</uicontrol> field is
|
| 30 | a namespace the XML file is associated with.</cmd><info>Your XML file should
|
| 31 | be associated with the same namespace(s) its XML schema is associated with.
|
| 32 | For more information about namespaces, refer to the related reference.</info>
|
| 33 | </step>
|
| 34 | <step><cmd>All qualified elements and attributes in the XML file associated
|
| 35 | with the namespace will be prefixed with the <uicontrol>Prefix</uicontrol> value.</cmd>
|
| 36 | </step>
|
| 37 | <step><cmd>The <uicontrol>Location Hint</uicontrol> field contains the location
|
| 38 | of the XML schema the XML file is associated with.</cmd><info>An XML Catalog
|
| 39 | Key or a namespace name can be specified in this field. Click <uicontrol>Browse</uicontrol> to
|
| 40 | view all XML schemas in the workbench and XML Catalog.</info></step>
|
| 41 | <step><cmd>Click <uicontrol>OK</uicontrol>, then click <uicontrol>OK</uicontrol> again.</cmd>
|
| 42 | </step>
|
| 43 | </steps>
|
| 44 | <result><p>If you want to create a new association, click <uicontrol>Add</uicontrol> instead
|
| 45 | of <uicontrol>Edit</uicontrol>. You can then either click the <uicontrol>Specify
|
| 46 | From Registered Namespace</uicontrol> radio button and select the namespace
|
| 47 | declarations you want to add or click the <uicontrol>Specify New Namespace</uicontrol> radio
|
| 48 | button and fill in the fields as necessary.</p></result>
|
| 49 | <postreq>If you do not have namespace information in your XML file, you can
|
| 50 | right-click your root element in the Design view and click <uicontrol>Edit
|
| 51 | Namespaces</uicontrol> to add it. If you do not have a root element, you must
|
| 52 | create one before you can add the namespace information.</postreq>
|
| 53 | </taskbody>
|
| 54 | </task>
|