[142131] Updates and edits to the XSD documentation
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html
index 7c7dfb3..45f35b6 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html
@@ -9,8 +9,8 @@
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta content="concept" name="DC.Type" />
<meta name="DC.Title" content="Working with XML schemas" />
-<meta name="abstract" content="This sections contains information on the following:" />
-<meta name="description" content="This sections contains information on the following:" />
+<meta name="abstract" content="XML schemas are an XML language for describing and constraining the content of XML files." />
+<meta name="description" content="XML schemas are an XML language for describing and constraining the content of XML files." />
<meta scheme="URI" name="DC.Relation" content="tcxmlsch.html" />
<meta scheme="URI" name="DC.Relation" content="timpschm.html" />
<meta scheme="URI" name="DC.Relation" content="tnavsrc.html" />
@@ -32,7 +32,11 @@
<h1 class="topictitle1">Working with XML schemas</h1>
-<div><p>This sections contains information on the following:</p>
+<div><p>XML schemas are an XML language for describing and constraining
+the content of XML files.</p>
+
+<p>This sections contains information on the following:</p>
+
</div>
<div><div class="reltasks"><strong>Related tasks</strong><br />
@@ -45,7 +49,7 @@
<div><a href="tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
-<div><a href="rxsdicons.html" title="The following XML schema editor icons appear in the Outline, Graph, and Properties view.">Icons used in the XML schema editor</a></div>
+<div><a href="rxsdicons.html" title="The following XML schema editor icons appear in the Outline, Design, and Properties view.">Icons used in the XML schema editor</a></div>
<div><a href="rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div>
</div>
</div>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html
index 4d7b06f..869ad39 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html
@@ -9,10 +9,13 @@
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta content="concept" name="DC.Type" />
<meta name="DC.Title" content="XML schema editor" />
-<meta name="abstract" content="XML schemas are an XML language for describing and constraining the content of XML files." />
-<meta name="description" content="XML schemas are an XML language for describing and constraining the content of XML files." />
+<meta name="abstract" content="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations." />
+<meta name="description" content="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations." />
<meta content="XML schema editor, overview" name="DC.subject" />
<meta content="XML schema editor, overview" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/tcxmlsch.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/tvdtschm.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="cxmlsced" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -27,14 +30,14 @@
-<div><p>XML schemas are an XML language for describing and constraining
-the content of XML files.</p>
+<div><p>This product provides an XML schema editor for creating, viewing,
+and validating XML schemas. XML schemas are a formal specification
+of element names that indicates which elements are allowed in an XML file,
+and in which combinations. </p>
-<p>XML schemas are a formal specification of element names that indicates
-which elements are allowed in an XML file, and in which combinations. A schema
-is functionally equivalent to a DTD, but is written in XML; a schema also
-provides for extended functionality such as data typing, inheritance, and
-presentation rules.</p>
+<p>A schema is functionally equivalent to a DTD, but is written in XML; a
+schema also provides for extended functionality such as data typing, inheritance,
+and presentation rules.</p>
<p>For more information on XML schema, refer to:</p>
@@ -47,8 +50,7 @@
</ul>
-<p>This product provides an XML schema editor for creating, viewing, and validating
-XML schemas. Using the XML schema editor, you can:</p>
+<p>Using the XML schema editor, you can:</p>
<ul>
<li>Create and delete XML schema components such as complex types, simple
@@ -62,10 +64,10 @@
<p>The XML Schema specification from the W3C Web site is used for validation.</p>
-<div class="section"><h4 class="sectiontitle">XML schema editor views - Graph, Outline, Properties, and
+<div class="section"><h4 class="sectiontitle">XML schema editor views - Design, Outline, Properties, and
Source</h4>There are four main views you can work with in the XML schema
editor:<ul>
-<li>Graph - the Graph view provides a graphical way to edit your schema</li>
+<li>Design - the Design view provides a graphical way to edit your schema</li>
<li>Outline - the Outline view shows you the main components in your XML schema.
You can use this view to add and remove certain components.</li>
@@ -95,6 +97,12 @@
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations.">Creating XML schemas</a></div>
+<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div>
+<div><a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html
index 815ef1f..6903e72 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html
@@ -13,6 +13,7 @@
<meta name="description" content="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names." />
<meta content="XML namespaces, overview" name="DC.subject" />
<meta content="XML namespaces, overview" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/tedtpref.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="rnmspc" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -267,7 +268,10 @@
</div>
-<div />
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/tedtpref.html" title="You can set various preferences for XML schema files such as the default target namespace and XML Schema language constructs prefix used.">Editing XML schema file preferences</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html
index 3b48670..e319a3b 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html
@@ -13,6 +13,9 @@
<meta name="description" content="The XML schema editor has a built-in mechanism to handle referential integrity issues. When you delete certain nodes, clean up for any nodes affected will automatically occur." />
<meta content="XML schema editor, referential integrity, clean up in" name="DC.subject" />
<meta content="XML schema editor, referential integrity, clean up in" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/tdelscmp.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="rrefintg" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -72,7 +75,14 @@
</div>
-<div />
+<div><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div>
+<div><a href="../topics/tdelscmp.html" title="If you have created any XML schema components you no longer need, you can delete them.">Deleting XML schema components</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html
index 456f000..92f68a6 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html
@@ -9,8 +9,8 @@
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta content="reference" name="DC.Type" />
<meta name="DC.Title" content="Icons used in the XML schema editor" />
-<meta name="abstract" content="The following XML schema editor icons appear in the Outline, Graph, and Properties view." />
-<meta name="description" content="The following XML schema editor icons appear in the Outline, Graph, and Properties view." />
+<meta name="abstract" content="The following XML schema editor icons appear in the Outline, Design, and Properties view." />
+<meta name="description" content="The following XML schema editor icons appear in the Outline, Design, and Properties view." />
<meta content="XML schema editor, icons, Icons" name="DC.subject" />
<meta content="XML schema editor, icons, Icons" name="keywords" />
<meta content="XHTML" name="DC.Format" />
@@ -27,7 +27,7 @@
-<div><p>The following XML schema editor icons appear in the Outline, Graph,
+<div><p>The following XML schema editor icons appear in the Outline, Design,
and Properties view.</p>
<div class="section" />
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html
index 0e9940a..500b3b0 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html
@@ -45,8 +45,8 @@
and click <span class="uicontrol">Add Attribute Group</span>.</span> It appears
in the <span class="uicontrol">Attribute Groups</span> folder.</li>
-<li class="stepexpand"><span>Select your new group, and in the Graph view, right-click the attribute
-group and select <span class="menucascade"><span class="uicontrol">Refactor</span> > <span class="uicontrol">Rename</span>
+<li class="stepexpand"><span>Select your new group, and in the Design view, right-click the
+attribute group and select <span class="menucascade"><span class="uicontrol">Refactor</span> > <span class="uicontrol">Rename</span>
</span>. In the <span class="uicontrol">New Name</span> field, type a name
for the attribute group.</span></li>
@@ -54,11 +54,11 @@
view, click <span class="uicontrol">Add Attribute</span>.</span> The attribute
appears below the attribute group in the Outline view.
<ol type="a">
-<li class="substepexpand"><span>Select the attribute, and in the Graph view, click the current
+<li class="substepexpand"><span>Select the attribute, and in the Design view, click the current
(default) name of the attribute, then type the new <span class="uicontrol">Name</span>.</span>
</li>
-<li class="substepexpand"><span>In the Graph view, click the current (default) attribute type
+<li class="substepexpand"><span>In the Design view, click the current (default) attribute type
and select a type from the menu. Alternately, you can select browse to invoke
the Set Type menu for more options.</span> The Set Type dialog lists all
built-in and user-defined types currently available. You can change the <span class="uicontrol">Scope</span> of
@@ -83,34 +83,22 @@
</li>
<li class="stepexpand"><span>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, in the Graph view, right-click the complex
+To add an attribute reference, in the Design view, right-click the complex
type containing the element, and click <span class="uicontrol">Add Attribute Ref</span>.</span>
A declaration that references a global attribute enables the referenced
attribute to appear in the instance document in the context of the referencing
-declaration.
-<ol type="a">
-<li><span>Select the reference, then select the attribute group you want
-it to reference in the Properties view, from the<span class="uicontrol">Ref</span> menu.</span>
-</li>
-
-</ol>
-
+declaration. Select the reference, then select the attribute group you want
+it to reference in the Properties view, from the<span class="uicontrol">Ref</span> menu.
</li>
<li class="stepexpand"><span>An attribute group reference provides a reference to an attribute
-group. To add an attribute group reference, in the Graph view, right-click
+group. To add an attribute group reference, in the Design view, right-click
the complex type containing the element, and click <span class="uicontrol">Add Attribute
Group Ref</span>.</span> A declaration that references a global attribute
enables the referenced attribute to appear in the instance document in the
-context of the referencing declaration.
-<ol type="a">
-<li><span>Select the reference, then select the attribute group you want
-it to reference in the Properties view, from the<span class="uicontrol">Ref</span> menu.</span>
-</li>
-
-</ol>
-
-</li>
+context of the referencing declaration. Select the reference, then select
+the attribute group you want it to reference in the Properties view, from
+the<span class="uicontrol">Ref</span> menu.</li>
<li class="stepexpand"><span>An <samp class="codeph">any</samp> element enables element content according
to namespaces, and the corresponding <samp class="codeph">any</samp> attribute element
@@ -119,17 +107,33 @@
The <samp class="codeph">any</samp> appears below the attribute group in the Outline
view. You can specify the following values for an <samp class="codeph">any</samp> attribute:
<ul>
-<li>For a <strong>namespace</strong> value, you can select <strong>##any</strong> (this allows
-any well-formed XML from any namespace), <strong>##local </strong> (this allows any
-well-formed XML that is not declared to be in a namespace), <strong>##other </strong> (this
-allows any well-formed XML that is not from the target namespace of the type
-being defined) or <strong>##targetNamespace </strong> (which is shorthand for the target
-namespace of the type being defined). </li>
+<li>For a <span class="uicontrol">namespace</span> value, you can
+select:<ul>
+<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li>
-<li>For a <span class="uicontrol">processContents</span> value, you can select <strong>skip</strong> (the
-XML processor will not validate the attribute content at all), <strong>lax</strong> (the
-XML processor will validate the attribute content as much as it can), or <strong>strict</strong> (the
-XML processor will validate all the attribute content).</li>
+<li><strong>##local </strong>. This allows any well-formed XML that is not declared
+to be in a namespace.</li>
+
+<li><strong>##other</strong>. This allows any well-formed XML that is not from the target
+namespace of the type being defined.</li>
+
+<li><strong>##targetNamespace </strong>. This is shorthand for the target namespace
+of the type being defined.</li>
+
+</ul>
+</li>
+
+<li>For a <span class="uicontrol">processContents</span> value, you can select:<ul>
+<li><strong>skip</strong>. The XML processor will not validate the attribute content
+at all.</li>
+
+<li><strong>lax</strong>. The XML processor will validate the attribute content as much
+as it can.</li>
+
+<li><strong>strict</strong>. The XML processor will validate all the attribute content.</li>
+
+</ul>
+</li>
</ul>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html
index a7c7276..8540ecb 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html
@@ -9,8 +9,8 @@
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta content="task" name="DC.Type" />
<meta name="DC.Title" content="Adding an any element" />
-<meta name="abstract" content="You can use the any element to provide something similar to a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax." />
-<meta name="description" content="You can use the any element to provide something similar to a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax." />
+<meta name="abstract" content="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax." />
+<meta name="description" content="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax." />
<meta content="XML schema editor, adding, an any element, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, an any element, XML schema files" name="keywords" />
<meta content="XHTML" name="DC.Format" />
@@ -27,10 +27,10 @@
-<div><p>You can use the <samp class="codeph">any</samp> element to provide something
-similar to a DTD's ANY content model, however, it must be done in conjunction
-with namespaces. This enables you to include any well-formed XML content,
-such as an HTML Web page that conforms to XHTML 1.0 syntax.</p>
+<div><p>You can use the <samp class="codeph">any</samp> element in a similar way as
+a DTD's ANY content model, however, it must be done in conjunction with namespaces.
+This enables you to include any well-formed XML content, such as an HTML Web
+page that conforms to XHTML 1.0 syntax.</p>
<div class="section"><p>For example:</p>
<div class="p"><pre><element name = "MyWebPage">
@@ -40,13 +40,12 @@
</complexType>
</element></pre>
</div>
-<p>The preceding schema fragment allows a <var class="varname"><MyWebPage></var> element
+<p>The preceding schema fragment allows a <samp class="codeph"><MyWebPage></samp> element
to contain any well-formed XHTML data that appears in the specified namespace.</p>
<p>The
following instructions were written for the Resource perspective, but they
will also work in many other perspectives.</p>
-<p>To add an <samp class="codeph">any</samp> element,
-follow these steps:</p>
+<p>To add an <samp class="codeph">any</samp> element:</p>
</div>
<ol>
@@ -55,17 +54,36 @@
<li class="stepexpand"><span>Select the new <samp class="codeph">any</samp> element.</span></li>
-<li class="stepexpand"><span>In the Properties view of the schema editor, for a <strong>namespace</strong> value,
-you can select <strong>##any</strong> (this allows any well-formed XML from any namespace), <strong>##local </strong> (this
-allows any well-formed XML that is not declared to be in a namespace), <strong>##other </strong> (this
-allows any well-formed XML that is not from the target namespace of the type
-being defined) or <strong>##targetNamespace </strong> (which is shorthand for the target
-namespace of the type being defined). </span></li>
+<li class="stepexpand"><span>In the Properties view of the schema editor, for a <span class="uicontrol">namespace</span> value,
+you can select:</span>
+<ul>
+<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li>
-<li class="stepexpand"><span>For a <span class="uicontrol">processContents</span> value, you can select <strong>skip</strong> (the
-XML processor will not validate the content at all), <strong>lax</strong> (the XML processor
-will validate the content as much as it can), or <strong>strict </strong> (the XML processor
-will validate all the content).</span></li>
+<li><strong>##local </strong>. This allows any well-formed XML that is not declared
+to be in a namespace.</li>
+
+<li><strong>##other </strong>. This allows any well-formed XML that is not from
+the target namespace of the type being defined.</li>
+
+<li><strong>##targetNamespace</strong>. This is shorthand for the target namespace
+of the type being defined.</li>
+
+</ul>
+
+</li>
+
+<li class="stepexpand"><span>For a <span class="uicontrol">processContents</span> value, you can select:</span>
+<ul>
+<li><strong>skip</strong>. The XML processor will not validate the content at all.</li>
+
+<li><strong>lax</strong>. The XML processor will validate the content as much as
+it can.</li>
+
+<li><strong>strict</strong>. The XML processor will validate all the content.</li>
+
+</ul>
+
+</li>
<li class="stepexpand"><span>The <span class="uicontrol">minOccurs</span> value is the number of times
the <samp class="codeph">any</samp> element must appear in an instance document. You
@@ -80,9 +98,12 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this element.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
</ol>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html
index 857c9ba..1e0afe1 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html
@@ -13,6 +13,10 @@
<meta name="description" content="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance." />
<meta content="XML schema editor, adding, content models, XML schema files, content models, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, content models, XML schema files, content models, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddanye.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddelm.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddelmr.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddgrpr.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddcmod" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -56,13 +60,13 @@
</div>
<ol>
-<li class="stepexpand"><span>In the Graph view, select your complex type, or group:</span>
+<li class="stepexpand"><span>In the Design view, select your complex type, or group:</span>
<ul>
<li>If you selected a complex type, you can right-click it and click <span class="uicontrol">Add
Sequence</span>, or <span class="uicontrol">Add Choice</span> to add the type
of content model you want to your complex type. If you wish to use the <span class="uicontrol">all</span> content
-model, you can change the model by clicking the model in the Graph view, and
-in properties, select <span class="uicontrol">all</span> as the <span class="uicontrol">Kind</span>.
+model, you can change the model by clicking the model in the Design view,
+and in properties, select <span class="uicontrol">all</span> as the <span class="uicontrol">Kind</span>.
Your content model is automatically added as a child of your complex type
- expand in the Outline view to see it. <strong>Note:</strong> These options will not
appear if you have set a base type for your complex type. You can either set
@@ -79,9 +83,9 @@
</li>
<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MinOccurs</span> field.</span>
- This is the number of times the content model must appear. If you want
-the content model to be optional, select <span class="uicontrol">0</span>. Otherwise,
-select <span class="uicontrol">1</span>. </li>
+ This is the minimum number of times the content model must appear. If
+you want the content model to be optional, select <span class="uicontrol">0</span>.
+Otherwise, select <span class="uicontrol">1</span>. </li>
<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MaxOccurs</span> field.</span>
This is the maximum number of times a content model can appear. You
@@ -90,10 +94,14 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this content model.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
+is used for human readable material, such as a description.
</li>
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
+
</ol>
<div class="section"><p>You can add the following items to a content object model. </p>
@@ -119,6 +127,13 @@
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddanye.html" title="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax.">Adding an any element</a></div>
+<div><a href="../topics/taddelm.html" title="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements.">Adding elements</a></div>
+<div><a href="../topics/taddelmr.html" title="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration.">Adding element references</a></div>
+<div><a href="../topics/taddgrpr.html" title="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration.">Adding group references</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html
index d4a5997..6204c40 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html
@@ -13,6 +13,7 @@
<meta name="description" content="A complex type allows elements in its content and can carry attributes. Complex types can be used to help determine the appropriate content for any instance documents generated from or associated with your XML schema." />
<meta content="XML schema editor, adding, complex types, XML schema files, complex types, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, complex types, XML schema files, complex types, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddcmxt" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -42,74 +43,60 @@
<ol>
<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li>
-<li class="stepexpand"><span>Right-click the Types category in the Graph view, and click <span class="uicontrol">Add
+<li class="stepexpand"><span>Right-click the Types category in the Design view, and click <span class="uicontrol">Add
Complex Type</span>.</span></li>
<li class="stepexpand"><span>In the Properties view, type a new name for the complex type in
the <span class="uicontrol">Name</span> field.</span></li>
-<li class="stepexpand"><span>Click the <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="Browse icon" /> button to select a base type for your complex
-type.</span> You can either set a base type for your complex type, or
-you can add a content model to it (which represents any data that can be contained
-inside an element), but you cannot do both. For more information about content
-models, refer to the related tasks.</li>
+<li class="stepexpand"><span>Click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="Browse icon" /> to select a base type for your complex type.</span>
+ You can either set a base type for your complex type, or you can add
+a content model to it (which represents any data that can be contained inside
+an element), but you cannot do both. For more information about content models,
+refer to the related tasks.</li>
<li class="stepexpand"><span>Select <span class="uicontrol">restriction</span> or <span class="uicontrol">extension</span> from
the <span class="uicontrol">Inherited by</span> list.</span> This specifies whether
your type is derived from its base type by restriction or extension.
</li>
-<li class="stepexpand"><span>The Graph view will display the attributes within the complex type.</span>
- You can also use this view to add attributes to your complex type. An
-attribute associates an attribute name with a specific type and value.
-<ol type="a">
-<li><span>To add an attribute, in the graph view, right click your complex
-type and select <span class="uicontrol">Add Attribute</span>.</span></li>
-
-</ol>
-
+<li class="stepexpand"><span>The Design view will display the attributes within the complex
+type.</span> You can also use this view to add attributes to your complex
+type. An attribute associates an attribute name with a specific type and value.
<ul>
-<li><span class="uicontrol">name</span>. In the Graph view, click the name of
-the attribute to make a change.</li>
+<li>To add an attribute, in the Design view, right click your complex
+type and select <span class="uicontrol">Add Attribute</span>.<ul>
+<li><span class="uicontrol">name</span>. In the Design view, click the name of the
+attribute to make a change.</li>
-<li><span class="uicontrol">type</span>. In the Graph view, click the type of
-the attribute to make a change. The drop-down menu provides commonly used
-types. For more options, simply select <span class="uicontrol">Browse</span> from
-the menu.</li>
+<li><span class="uicontrol">type</span>. In the Design view, click the type of the
+attribute to make a change. The drop-down menu provides commonly used types.
+For more options, simply select <span class="uicontrol">Browse</span> from the menu.</li>
+
+</ul>
+</li>
</ul>
</li>
<li class="stepexpand"><span>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, in the Graph view, right-click the complex
+To add an attribute reference, in the Design view, right-click the complex
type containing the element, and click <span class="uicontrol">Add Attribute Ref</span>.</span>
A declaration that references a global attribute enables the referenced
attribute to appear in the instance document in the context of the referencing
-declaration.
-<ol type="a">
-<li><span>Select the reference, then select the attribute group you want
-it to reference in the Properties view, from the<span class="uicontrol">Ref</span> menu.</span>
-</li>
-
-</ol>
-
+declaration. Select the reference, then select the attribute group you want
+it to reference in the Properties view, from the<span class="uicontrol"> Ref</span> menu.
</li>
<li class="stepexpand"><span>An attribute group reference provides a reference to an attribute
-group. To add an attribute group reference, in the Graph view, right-click
+group. To add an attribute group reference, in the Design view, right-click
the complex type containing the element, and click <span class="uicontrol">Add Attribute
Group Ref</span>.</span> A declaration that references an attribute
group enables the referenced attribute group to appear in the instance document
-in the context of the referencing declaration.
-<ol type="a">
-<li><span>Select the reference, then select the attribute group you want
-it to reference in the Properties view, from the<span class="uicontrol">Ref</span> menu.</span>
-</li>
-
-</ol>
-
-</li>
+in the context of the referencing declaration. Select the reference, then
+select the attribute group you want it to reference in the Properties view,
+from the<span class="uicontrol"> Ref</span> menu.</li>
<li class="stepexpand"><span>An <samp class="codeph">any</samp> element enables element content according
to namespaces, and the corresponding <samp class="codeph">any</samp> attribute element
@@ -117,17 +104,33 @@
right-click in the complex type header, and click <span class="uicontrol">Add Any Attribute</span>.</span>
You can specify the following values for an <samp class="codeph">any</samp> attribute:
<ul>
-<li>For a <strong>namespace</strong> value, you can select <strong>##any</strong> (this allows
-any well-formed XML from any namespace), <strong>##local </strong> (this allows any
-well-formed XML that is not declared to be in a namespace, <strong>##other </strong> (this
-allows any well-formed XML that is not from the target namespace of the type
-being defined) or <strong>##targetNamespace </strong> (which is shorthand for the target
-namespace of the type being defined). </li>
+<li>For a <span class="uicontrol">namespace</span> value, you can
+select:<ul>
+<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li>
-<li>For a <span class="uicontrol">processContents</span> value, you can select <strong>skip</strong> (the
-XML processor will not validate the attribute content at all), <strong>lax</strong>(the
-XML processor will validate the attribute content as much as it can), or <strong>strict </strong> (the
-XML processor will validate all the attribute content).</li>
+<li><strong>##local </strong>. This allows any well-formed XML that is not declared
+to be in a namespace.</li>
+
+<li><strong>##other</strong>. This allows any well-formed XML that is not from the target
+namespace of the type being defined.</li>
+
+<li><strong>##targetNamespace </strong>. This is shorthand for the target namespace
+of the type being defined.</li>
+
+</ul>
+</li>
+
+<li>For a <span class="uicontrol">processContents</span> value, you can select:<ul>
+<li><strong>skip</strong>. The XML processor will not validate the attribute content
+at all.</li>
+
+<li><strong>lax</strong>. The XML processor will validate the attribute content as much
+as it can.</li>
+
+<li><strong>strict</strong>. The XML processor will validate all the attribute content.</li>
+
+</ul>
+</li>
</ul>
@@ -135,14 +138,21 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this complex type.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
</ol>
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html
index 7b62b7a..f669f1c 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html
@@ -9,10 +9,14 @@
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta content="task" name="DC.Type" />
<meta name="DC.Title" content="Adding elements" />
-<meta name="abstract" content="Elements are fundamental building blocks in XML. Element declarations provide value constraints, and a description that can be used for validation, as well as establishing constraining relationships between related elements and attributes, and controlling substitution of elements." />
-<meta name="description" content="Elements are fundamental building blocks in XML. Element declarations provide value constraints, and a description that can be used for validation, as well as establishing constraining relationships between related elements and attributes, and controlling substitution of elements." />
+<meta name="abstract" content="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements." />
+<meta name="description" content="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements." />
<meta content="XML schema editor, adding, elements, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, elements, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddelmr.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddanye.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddglba.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddelm" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -28,26 +32,25 @@
<div><p>Elements are fundamental building blocks in XML. Element declarations
-provide value constraints, and a description that can be used for validation,
-as well as establishing constraining relationships between related elements
-and attributes, and controlling substitution of elements.</p>
+provide value constraints, provide a description that can be used for validation,
+establish constraining relationships between related elements and attributes,
+and control the substitution of elements.</p>
<div class="section"><p>The following instructions were written for the Resource perspective,
but they will also work in many other perspectives.</p>
-<p>To add an element,
-follow these steps:</p>
+<p>To add an element:</p>
</div>
<ol>
-<li class="stepexpand"><span>To add an element, in the Graph view, right-click the content model
-you want to work with and click <span class="uicontrol">Add Element</span>.</span>
- The element appears attached to the content model in the Graph view.
+<li class="stepexpand"><span>To add an element, in the Design view, right-click the content
+model you want to work with and click <span class="uicontrol">Add Element</span>.</span>
+ The element appears attached to the content model in the Design view.
<ol type="a">
-<li class="substepexpand"><span>Select the element, and in the Graph view, click the current
+<li class="substepexpand"><span>In the Design view, select the element, and click the current
(default) name of the element, which puts you in direct editing mode, then
-type the new <span class="uicontrol">Name</span> and hit enter.</span></li>
+type the new <span class="uicontrol">Name</span> and press enter.</span></li>
-<li class="substepexpand"><span>In the Graph view, click the current (default) element type
+<li class="substepexpand"><span>In the Design view, click the current (default) element type
and select a type from the menu. Alternately, you can select browse to invoke
the Set Type dialog for more options.</span> The Set Type dialog lists
all built-in and user-defined types currently available. You can change the <span class="uicontrol">Scope</span> of
@@ -72,21 +75,24 @@
</li>
<li class="stepexpand"><span>(Optional) In the Properties view, select the appropriate value
-in the <span class="uicontrol">MinOccurs</span> field.</span> This is the minimum
-number of times the element can appear in an instance document. If you want
-the element to be optional, select <span class="uicontrol">0</span>. Otherwise, select <span class="uicontrol">1</span>.
+in the <span class="uicontrol">MinOccurs</span> field.</span> This is the number
+of times the element can appear in an instance document. If you want the element
+to be optional, select <span class="uicontrol">0</span>. Otherwise, select <span class="uicontrol">1</span>.
</li>
<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MaxOccurs</span> field.</span>
This is the maximum number of times the element can appear in an instance
-document. You can select <span class="uicontrol">unbounded</span> to indicate there
-is no maximum number of occurrences.</li>
+document. Select <span class="uicontrol">unbounded</span> to indicate there is no
+maximum number of occurrences.</li>
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this element.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
</ol>
@@ -96,6 +102,13 @@
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div>
+<div><a href="../topics/taddelmr.html" title="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration.">Adding element references</a></div>
+<div><a href="../topics/taddanye.html" title="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax.">Adding an any element</a></div>
+<div><a href="../topics/taddglba.html" title="A global attribute is an attribute that can be recognized anywhere in a document. Once declared, a global attribute can be referenced in one or more declarations using an attribute reference.">Adding global attributes</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html
index 5384282..40177eb 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html
@@ -13,6 +13,10 @@
<meta name="description" content="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration." />
<meta content="XML schema editor, adding, element references, XML schema files, element references, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, element references, XML schema files, element references, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddglem.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddelm.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddanye.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddglba.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddelmr" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -35,24 +39,24 @@
<div class="section"><p>The following instructions were written for the Resource perspective,
but they will also work in many other perspectives.</p>
<p>To add an element
-reference, follow these steps:</p>
+reference:</p>
</div>
<ol>
-<li class="stepexpand"><span>In the Graph view, right-click the content model you want to work
+<li class="stepexpand"><span>In the Design view, right-click the content model you want to work
with and click <span class="uicontrol">Add Element Ref</span>.</span> If
no global element is defined in the document, a new global element is created
for you, and the element reference will point to it.</li>
-<li class="stepexpand"><span>Select the element reference. You can specify the following values
-for an element reference:</span>
+<li class="stepexpand"><span>Select the element reference. To specify values for an element
+reference:</span>
<ul>
-<li><span class="uicontrol">name</span>. Click the name of the element reference
-in the Graph view. Enter the name of the element reference.</li>
+<li>Click the name of the element reference in the Design view. Enter
+the name of the element reference.</li>
-<li><span class="uicontrol">type</span>. Click the element reference type in the
-Graph view. Select a type from the menu, or select <span class="uicontrol">Browse</span> for
-more options.</li>
+<li>Click the element reference type in the Design view.
+Select a type from the menu, or select <span class="uicontrol">Browse</span> for more
+options.</li>
</ul>
@@ -70,14 +74,24 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this element reference.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
</ol>
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddglem.html" title="A global element is an element with a global scope. It is one that has been declared as part of the main schema rather than as part of a content model.">Adding global elements</a></div>
+<div><a href="../topics/taddelm.html" title="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements.">Adding elements</a></div>
+<div><a href="../topics/taddanye.html" title="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax.">Adding an any element</a></div>
+<div><a href="../topics/taddglba.html" title="A global attribute is an attribute that can be recognized anywhere in a document. Once declared, a global attribute can be referenced in one or more declarations using an attribute reference.">Adding global attributes</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html
index 07ab203..29b0abf 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html
@@ -34,24 +34,24 @@
<div class="section"><p>The following instructions were written for the Resource perspective,
but they will also work in many other perspectives.</p>
<p>To add a global
-attribute, follow these steps:</p>
+attribute:</p>
</div>
<ol>
<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li>
-<li class="stepexpand"><span>In the Graph view, right click in the <strong>Attributes</strong> section
+<li class="stepexpand"><span>In the Design view, right-click in the <strong>Attributes</strong> section
and click <span class="uicontrol">Add Attribute</span>.</span></li>
-<li class="stepexpand"><span>In the Properties view, type the attribute <span class="uicontrol">Name</span>.</span>
+<li class="stepexpand"><span>In the Properties view, enter a name for the attribute in the <span class="uicontrol">Name</span> field.</span>
</li>
<li class="stepexpand"><span>In the Properties view, you can select the attribute <span class="uicontrol">Type</span> from
the predefined list in the menu next to the <span class="uicontrol">Type</span> field.</span>
- <p>Alternately, you can select <span class="uicontrol">Browse</span> from the
-list for more options. </p>
-<div class="p">The Set Type dialog will appear, and lists all
-built-in and user-defined types currently available. You can change the <span class="uicontrol">Scope</span> of
+ <p>Alternatively, you can select <span class="uicontrol">Browse</span> from
+the list for more options. </p>
+<div class="p">The Set Type dialog will appear, and lists
+all built-in and user-defined types currently available. You can change the <span class="uicontrol">Scope</span> of
the list by selecting one of the following options:<ul>
<li><span class="uicontrol">Workspace</span>. Lists all of the types available in
your workspace. </li>
@@ -73,9 +73,12 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this global attribute.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
</ol>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html
index 74378da..f38c0d5 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html
@@ -13,6 +13,8 @@
<meta name="description" content="A global element is an element with a global scope. It is one that has been declared as part of the main schema rather than as part of a content model." />
<meta content="XML schema editor, adding, global elements, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, global elements, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddelmr.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddglem" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -34,29 +36,30 @@
<div class="section"><p>The following instructions were written for the Resource perspective,
but they will also work in many other perspectives.</p>
<p>To add a global
-element, follow these steps:</p>
+element:</p>
</div>
<ol>
<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li>
<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire
-schema and its contents should be displayed in the Graph view.</li>
+schema and its contents are displayed in the Design view.</li>
-<li class="stepexpand"><span>In the Graph view, right click in the <strong>Elements</strong> section and
-click <span class="uicontrol">Add Element</span>.</span></li>
+<li class="stepexpand"><span>In the Design view, right-click in the <strong>Elements</strong> section
+and click <span class="uicontrol">Add Element</span>.</span></li>
<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">General</span> tab,
and type a new name for the global element in the <span class="uicontrol">Name</span> field.</span>
</li>
-<li class="stepexpand"><span>In the Properties view, you can select the attribute <span class="uicontrol">Type</span> from
+<li class="stepexpand"><span>In the Properties view, you can select the attribute type from
the predefined list in the menu next to the <span class="uicontrol">Type</span> field.</span>
- <p>Alternately, you can select <span class="uicontrol">Browse</span> from the
-list for more options. </p>
-<div class="p">The Set Type dialog will appear, and lists all
-built-in and user-defined types currently available. You can change the <span class="uicontrol">Scope</span> of
-the list by selecting one of the following options:<ul>
+ <p>Alternatively, you can select <span class="uicontrol">Browse</span> from
+the list for more options. </p>
+<div class="p">The <span class="uicontrol">Set Type</span> dialog
+box appears, and lists all built-in and user-defined types currently available.
+You can change the <span class="uicontrol">Scope</span> of the list by selecting one
+of the following options:<ul>
<li><span class="uicontrol">Workspace</span>. Lists all of the types available in
your workspace. </li>
@@ -89,15 +92,15 @@
<li><span class="uicontrol">final</span>. This field determines whether this global
element may be derived from.</li>
-<li><span class="uicontrol">fixed/default</span>. Click the <span class="uicontrol">Browse</span> button
-and select the <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> radio
-button and specify an appropriate value. If you select <strong>Fixed</strong>, the global
-element has a fixed value, which cannot be changed. If you select <strong>Default</strong>,
+<li><span class="uicontrol">fixed/default</span>. Click <span class="uicontrol">Browse</span> and
+select <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> and
+specify an appropriate value. If you select <strong>Fixed</strong>, the global element
+has a fixed value, which cannot be changed. If you select <strong>Default</strong>,
the element has a default value.</li>
<li><span class="uicontrol">form</span>. Use this field to indicate if the appearance
-of this global element in an instance of the XML schema (that is, an XML file
-associated with the XML schema) must be qualified by a namespace.</li>
+of this global element in an instance of the XML schema (an XML file associated
+with the XML schema) must be qualified by a namespace.</li>
<li><span class="uicontrol">nillable</span>. Select <strong>true</strong> if you do not
want the global element to be able to have any child elements, only attributes. </li>
@@ -109,7 +112,7 @@
</li>
-<li class="stepexpand"><span>Click the <span class="uicontrol">Attributes</span> tab</span> You
+<li class="stepexpand"><span>Click the <span class="uicontrol">Attributes</span> tab.</span> You
can use this page to add attributes, attribute references, attributes group
references, and <samp class="codeph">any</samp> attributes to your global element.
</li>
@@ -117,13 +120,13 @@
<li class="stepexpand"><span>An attribute associates an attribute name with a specific type
and value. To add an attribute, right-click in the Attributes page, and click <span class="uicontrol">Add
Attribute</span>.</span> You can specify the following values for
-an attribute
+an attribute:
<ul>
-<li><span class="uicontrol">fixed/default</span>. Click the <span class="uicontrol">Browse</span> button
-and select the <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> radio
-button and specify an appropriate value. If you select <strong>Fixed</strong>, the attribute
-has a fixed value, which cannot be changed. If you select <strong>Default</strong>,
-the attribute has a default value.</li>
+<li><span class="uicontrol">fixed/default</span>. Click <span class="uicontrol">Browse</span> and
+select <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> and
+specify an appropriate value. If you select <strong>Fixed</strong>, the attribute has
+a fixed value, which cannot be changed. If you select <strong>Default</strong>, the
+attribute has a default value.</li>
<li><span class="uicontrol">form</span>. Use this field to indicate if the appearance
of this attribute in an instance of the XML schema must be qualified by a
@@ -131,16 +134,15 @@
<li><span class="uicontrol">name</span>. Enter the name of the attribute.</li>
-<li><span class="uicontrol">type</span>. Click the <span class="uicontrol">Browse</span> button
-and select the type of the attribute. </li>
+<li><span class="uicontrol">type</span>. Click <span class="uicontrol">Browse</span> and
+select the type of the attribute. </li>
<li><span class="uicontrol">use</span>. This field indicates how an attribute
-can be used in an instance document. If you select <strong>optional</strong>, the attribute
-can appear once, but it does not have to. If you select <strong>required</strong>, the
-attribute must appear once. If you select <strong>prohibited</strong>, the attribute
-must not appear. <strong>Note</strong>: If you selected the <span class="uicontrol">Default</span> radio
-button, you must select <strong>optional</strong> in this field, otherwise the default
-value will not be valid.</li>
+can be used in an instance document. If you select optional, the attribute
+can appear once, but it does not have to. If you select required, the attribute
+must appear once. If you select prohibited, the attribute must not appear. <strong>Note</strong>:
+If you selected <span class="uicontrol">Default</span>, you must select <strong>optional</strong> in
+this field, otherwise the default value will not be valid.</li>
</ul>
@@ -152,14 +154,8 @@
attribute enables the referenced attribute to appear in the instance document
in the context of the referencing declaration. The menu option to add an attribute
reference only appears if there are global attributes defined elsewhere in
-the document.
-<ol type="a">
-<li><span>Select the reference, then select the global attribute you want
-it to reference from the <span class="uicontrol">ref</span> list.</span></li>
-
-</ol>
-
-</li>
+the document. Select the reference, then select the global attribute you want
+it to reference from the <span class="uicontrol">ref</span> list.</li>
<li class="stepexpand"><span>An attribute group reference provides a reference to an attribute
group. To add an attribute group reference, right-click in the Attributes
@@ -167,13 +163,8 @@
declaration that references an attribute group enables the referenced attribute
group to appear in the instance document in the context of the referencing
declaration. The menu option to add an attribute group reference only appears
-if there are attribute groups defined elsewhere in the document.
-<ol type="a">
-<li><span>Select the reference, then select the attribute group you want
-it to reference from the <span class="uicontrol">ref</span> list.</span></li>
-
-</ol>
-
+if there are attribute groups defined elsewhere in the document. Select the
+reference, then select the attribute group you want it to reference from the <span class="uicontrol">ref</span> list.
</li>
<li class="stepexpand"><span>An <samp class="codeph">any</samp> element enables element content according
@@ -182,17 +173,33 @@
right-click in the Attributes page and click <span class="uicontrol">Add Any Attribute</span>.</span>
You can specify the following values for an <samp class="codeph">any</samp> attribute:
<ul>
-<li>For a <strong>namespace</strong> value, you can select <strong>##any</strong> (this allows
-any well-formed XML from any namespace), <strong>##local </strong> (this allows any
-well-formed XML that is not declared to be in a namespace), <strong>##other </strong> (this
-allows any well-formed XML that is not from the target namespace of the type
-being defined) or <strong>##targetNamespace </strong> (which is shorthand for the target
-namespace of the type being defined). </li>
+<li>For a <span class="uicontrol">namespace</span> value, you can
+select:<ul>
+<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li>
-<li>For a <span class="uicontrol">processContents</span> value, you can select <strong>skip</strong> (the
-XML processor will not validate the attribute content at all), <strong>lax</strong> (the
-XML processor will validate the attribute content as much as it can), or <strong>strict</strong> (the
-XML processor will validate all the attribute content).</li>
+<li><strong>##local </strong>. This allows any well-formed XML that is not declared
+to be in a namespace.</li>
+
+<li><strong>##other</strong>. This allows any well-formed XML that is not from the target
+namespace of the type being defined.</li>
+
+<li><strong>##targetNamespace </strong>. This is shorthand for the target namespace
+of the type being defined.</li>
+
+</ul>
+</li>
+
+<li>For a <span class="uicontrol">processContents</span> value, you can select:<ul>
+<li><strong>skip</strong>. The XML processor will not validate the attribute content
+at all.</li>
+
+<li><strong>lax</strong>. The XML processor will validate the attribute content as much
+as it can.</li>
+
+<li><strong>strict</strong>. The XML processor will validate all the attribute content.</li>
+
+</ul>
+</li>
</ul>
@@ -200,9 +207,12 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this global element.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
</ol>
@@ -212,6 +222,11 @@
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div>
+<div><a href="../topics/taddelmr.html" title="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration.">Adding element references</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html
index cc5b0d0..130e49a 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html
@@ -13,6 +13,7 @@
<meta name="description" content="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration." />
<meta content="XML schema editor, adding, group references, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, group references, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddgrup.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddgrpr" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -39,7 +40,7 @@
</div>
<ol>
-<li class="stepexpand"><span>In the Graph view, right-click the content model you want to work
+<li class="stepexpand"><span>In the Design view, right-click the content model you want to work
with and select <span class="uicontrol">Add Group Ref</span>.</span></li>
<li class="stepexpand"><span>Select the new group reference.</span></li>
@@ -49,14 +50,22 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this group reference.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
+is used for human readable material, such as a description.
</li>
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
+
</ol>
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddgrup.html" title="When you create a group, it automatically contains a content model. The content model is a representation of any data that can be grouped together by the group, such as elements, element references, and group references.">Adding groups</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html
index 66a4a04..b8141ed 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html
@@ -13,6 +13,8 @@
<meta name="description" content="When you create a group, it automatically contains a content model. The content model is a representation of any data that can be grouped together by the group, such as elements, element references, and group references." />
<meta content="XML schema editor, adding, groups, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, groups, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddgrpr.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddgrup" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -49,9 +51,12 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this group element.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to
+specify the schema and add XML content to your annotations.</li>
<li class="stepexpand"><span>In the Outline view, expand the <span class="uicontrol">Groups</span> folder
and your new group.</span></li>
@@ -65,6 +70,11 @@
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddgrpr.html" title="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration.">Adding group references</a></div>
+<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html
index 2c24703..d6946ec 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html
@@ -13,6 +13,9 @@
<meta name="description" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema." />
<meta content="XML schema editor, adding, import elements, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, import elements, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddincl.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddrdfn.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/rnmspc.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddimpt" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -48,18 +51,19 @@
<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li>
<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire
-schema and its contents should be displayed in the Graph view.</li>
+schema and its contents should be displayed in the Design view.</li>
-<li class="stepexpand"><span>In the Graph view, right click in the <strong>Directives</strong> section
+<li class="stepexpand"><span>In the Design view, right click in the <strong>Directives</strong> section
and click <span class="uicontrol">Add Import</span>.</span></li>
-<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click
-the <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> button to the right of the <span class="uicontrol">Schema
-location</span> field.</span></li>
+<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> to
+the right of the <span class="uicontrol">Schema location</span> field.</span></li>
-<li class="stepexpand"><span>If you want to import an XML schema located in the workbench, select
-the <span class="uicontrol">Workbench projects</span> radio button and click <span class="uicontrol">Next</span>. </span>
+<li class="stepexpand"><span>If you want to import an XML schema located in the workbench:</span>
<ol type="a">
+<li><span>Select <span class="uicontrol">Workbench projects</span> and click <span class="uicontrol">Next</span>. </span>
+</li>
+
<li><span>Select the schema you want to import and click <span class="uicontrol">Finish</span>.</span>
</li>
@@ -67,9 +71,11 @@
</li>
-<li class="stepexpand"><span>If you want to import an XML schema located on the Web, select
-the <span class="uicontrol">HTTP</span> radio button and click <span class="uicontrol">Next</span>.</span>
+<li class="stepexpand"><span>If you want to import an XML schema located on the Web:</span>
<ol type="a">
+<li class="substepexpand"><span>Select <span class="uicontrol">HTTP</span> and click <span class="uicontrol">Next</span>.</span>
+</li>
+
<li class="substepexpand"><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>.</span>
<div class="note"><span class="notetitle">Note:</span> A local copy of the schema will not be stored in the workbench.
Every time you validate your schema, the schema's contents will be checked
@@ -89,9 +95,12 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this import element.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
</ol>
@@ -106,6 +115,14 @@
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema.">Adding include elements</a></div>
+<div><a href="../topics/taddrdfn.html" title="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. When you redefine a component, you are modifying its contents.">Adding redefine elements</a></div>
+</div>
+<div class="relref"><strong>Related reference</strong><br />
+<div><a href="../topics/rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html
index 6a31986..7abba83 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html
@@ -9,10 +9,13 @@
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta content="task" name="DC.Type" />
<meta name="DC.Title" content="Adding include elements" />
-<meta name="abstract" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to brings in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." />
-<meta name="description" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to brings in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." />
+<meta name="abstract" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." />
+<meta name="description" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." />
<meta content="XML schema editor, adding, include elements, XML schema files, include elements, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, include elements, XML schema files, include elements, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddimpt.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddrdfn.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/rnmspc.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddincl" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -30,9 +33,9 @@
<div><p>As schemas become larger, it is often desirable to divide their
content among several schema documents for purposes such as ease of maintenance,
reuse, and readability. You can use the <samp class="codeph">include</samp> element to
-brings in definitions and declarations from the included schema into the current
-schema. The included schema must be in the same target namespace as the including
-schema. </p>
+bring in definitions and declarations from the included schema
+into the current schema. The included schema must be in the same target namespace
+as the including schema. </p>
<div class="section"><p>The following instructions were written for the XML perspective,
but they will also work in many other perspectives.</p>
@@ -44,34 +47,26 @@
<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li>
<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire
-schema and its contents should be displayed in the Graph view.</li>
+schema and its contents are displayed in the Design view.</li>
-<li class="stepexpand"><span>In the Graph view, right click in the <strong>Directives</strong> section
+<li class="stepexpand"><span>In the Design view, right-click in the <strong>Directives</strong> section
and click <span class="uicontrol">Add Include</span>.</span></li>
-<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click
-the <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> button to the right of the <span class="uicontrol">Schema
-location</span> field.</span> The XML schema file you select must
-have the same namespace as the current schema.</li>
-
-<li class="stepexpand"><span>If you want to select an XML schema located in the workbench, select
-the <span class="uicontrol">Workbench projects</span> radio button and click <span class="uicontrol">Next</span>. </span>
-<ol type="a">
-<li><span>Select the schema you want to include and click <span class="uicontrol">Finish</span>.</span>
+<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> to
+the right of the <span class="uicontrol">Schema location</span> field.</span> The
+XML schema file you select must have the same namespace as the current schema.
</li>
-</ol>
+<li class="stepexpand"><span>If you want to select an XML schema located in the workbench, select <span class="uicontrol">Workbench
+projects</span> and click <span class="uicontrol">Next</span>. </span></li>
+<li class="stepexpand"><span>Select the schema you want to include and click <span class="uicontrol">Finish</span>.</span>
</li>
-<li class="stepexpand"><span>If you want to select an XML schema located on the Web, select
-the <span class="uicontrol">HTTP</span> radio button and click <span class="uicontrol">Next</span>.</span>
-<ol type="a">
-<li><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>. </span>
-</li>
+<li class="stepexpand"><span>If you want to select an XML schema located on the Web, select <span class="uicontrol">HTTP</span> and
+click <span class="uicontrol">Next</span>.</span></li>
-</ol>
-
+<li class="stepexpand"><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>.</span>
<div class="note"><span class="notetitle">Note:</span> A local copy of the schema will not be stored in the workbench.
Every time you validate your schema, the schema's contents will be checked
from the URL you specify.</div>
@@ -84,9 +79,12 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this include element.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
</ol>
@@ -113,6 +111,14 @@
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema.">Adding import elements</a></div>
+<div><a href="../topics/taddrdfn.html" title="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. When you redefine a component, you are modifying its contents.">Adding redefine elements</a></div>
+</div>
+<div class="relref"><strong>Related reference</strong><br />
+<div><a href="../topics/rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html
index b84e4f6..d7820c8 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html
@@ -13,6 +13,9 @@
<meta name="description" content="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. When you redefine a component, you are modifying its contents." />
<meta content="XML schema editor, adding, redefine elements, XML schema files, redefine elements, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, redefine elements, XML schema files, redefine elements, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddimpt.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddincl.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/rnmspc.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddrdfn" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -38,41 +41,33 @@
<p>The following instructions were written for the Resource
perspective, but they will also work in many other perspectives.</p>
<p>To
-add a redefine element , follow these steps:</p>
+add a redefine element:</p>
</div>
<ol>
<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li>
<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire
-schema and its contents should be displayed in the Graph view.</li>
+schema and its contents are displayed in the Design view.</li>
-<li class="stepexpand"><span>In the Graph view, right-click in the <strong>Directives</strong> section
+<li class="stepexpand"><span>In the Design view, right-click in the <strong>Directives</strong> section
and click <span class="uicontrol">Add Redefine</span>.</span></li>
-<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click
-the <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> button to the right of the <span class="uicontrol">Schema
-location</span> field.</span> The XML schema file you select must
-have the same namespace as the current schema.</li>
+<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> to
+the right of the <span class="uicontrol">Schema location</span> field.</span>
+ The XML schema file you select must have the same namespace as the current
+schema.</li>
-<li class="stepexpand"><span>If you want to select an XML schema located in the workbench, select
-the <span class="uicontrol">Workbench projects</span> radio button and click <span class="uicontrol">Next.</span></span>
-<ol type="a">
-<li><span> Select the schema you want to include and click <span class="uicontrol">Finish</span>.</span>
+<li class="stepexpand"><span>If you want to select an XML schema located in the workbench, select <span class="uicontrol">Workbench
+projects</span> and click <span class="uicontrol">Next.</span></span></li>
+
+<li class="stepexpand"><span>Select the schema you want to include and click <span class="uicontrol">Finish</span>.</span>
</li>
-</ol>
+<li class="stepexpand"><span>If you want to select an XML schema located on the Web, select <span class="uicontrol">HTTP</span> and
+click <span class="uicontrol">Next</span>.</span></li>
-</li>
-
-<li class="stepexpand"><span>If you want to select an XML schema located on the Web, select
-the <span class="uicontrol">HTTP</span> radio button and click <span class="uicontrol">Next</span>.</span>
-<ol type="a">
-<li><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>.
- </span></li>
-
-</ol>
-
+<li class="stepexpand"><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>.</span>
<div class="note"><span class="notetitle">Note:</span> A local copy of the schema will not be stored in the workbench.
Every time you validate your schema, the schema's contents will be checked
from the URL you specify.</div>
@@ -85,9 +80,12 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this redefine element.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
</ol>
@@ -98,6 +96,14 @@
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema.">Adding import elements</a></div>
+<div><a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema.">Adding include elements</a></div>
+</div>
+<div class="relref"><strong>Related reference</strong><br />
+<div><a href="../topics/rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html
index 3d831cd..2a0c07a 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html
@@ -13,6 +13,7 @@
<meta name="description" content="A pattern facet can be used to constrain the value of a type's lexical space (the set of string literals that represent the values of a type), which indirectly constrains the value space." />
<meta content="XML schema editor, adding, pattern facets, XML schema files, pattern facets, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, pattern facets, XML schema files, pattern facets, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddsmpt.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddreg" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -34,50 +35,65 @@
<div class="section"><p> The value of the pattern is called a regular expression. You
can specify it using the <span class="uicontrol">Regular Expression</span> wizard.</p>
<p>To
-add a pattern to a simple type, follow these steps:</p>
+add a pattern to a simple type:</p>
</div>
<ol>
-<li class="stepexpand"><span>In the Graph view, select the simple type you want to work with.</span>
+<li class="stepexpand"><span>In the Design view, select the simple type you want to work with.</span>
</li>
<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">Constraints</span> tab,
-then the <span class="uicontrol">Patterns</span> radio button.</span></li>
+then <span class="uicontrol">Patterns</span>.</span></li>
-<li class="stepexpand"><span>Click <span class="uicontrol">Add...</span>.</span> The Regular Expression
-Wizard opens.</li>
+<li class="stepexpand"><span>Click <span class="uicontrol">Add</span>.</span> The Regular Expression
+wizard opens.</li>
<li class="stepexpand"><span>Select the token you want to add to the expression.</span></li>
<li class="stepexpand"><span>Indicate how often you want the token to appear in order for a
-match to succeed.</span> If you want the token to repeat, click <span class="uicontrol">Repeat</span> and
-specify the number of times the token must appear. If you want to specify
-a minimum and maximum number of times the token can appear, click <span class="uicontrol">Range</span> and
-enter a minimum and maximum value.</li>
+match to succeed:</span>
+<ul>
+<li>If you want the token to repeat, click <span class="uicontrol">Repeat</span> and
+specify the number of times the token must appear.</li>
-<li class="stepexpand"><span>Click <span class="uicontrol">Add</span> to add the token to the regular
-expression.</span></li>
+</ul>
-<li class="stepexpand"><span>Repeat the previous three steps as necessary to create the entire
-expression.</span></li>
+<ul>
+<li> If you want to specify a minimum and maximum number of times the
+token can appear, click <span class="uicontrol">Range</span> and enter a minimum and
+maximum value.</li>
+
+</ul>
+
+</li>
+
+<li class="stepexpand"><span>To add the token to the regular expression, click <span class="uicontrol">Add</span>. </span>
+</li>
+
+<li class="stepexpand"><span>To create the entire expression, repeat steps 4 - 6 as necessary.</span>
+</li>
<li class="stepexpand"><span>When you are finished, click <span class="uicontrol">Next</span>.</span>
</li>
-<li class="stepexpand"><span>(Optional) Enter some sample text to test against the regular expression
-and see if a match occurs. </span></li>
+<li class="stepexpand"><span>(Optional) To test against the regular expression and see if a
+match occurs, enter sample text.</span></li>
-<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li>
+<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span> The regular
+expression will appear in the Patterns page. <div class="tip"><span class="tiptitle">Tip:</span> To edit an
+existing pattern, select it in the Patterns page and click <span class="uicontrol">Edit</span>.
+To delete an existing pattern, select it in the Patterns page and click <span class="uicontrol">Delete</span>. </div>
+
+</li>
</ol>
-<div class="section">The regular expression will appear in the Patterns page.</div>
-
-<div class="section">To edit an existing pattern, select it in the Patterns page and click <span class="uicontrol">Edit</span>.
-To delete an existing pattern, select it in the Patterns page and click <span class="uicontrol">Delete</span>. </div>
-
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddsmpt.html" title="Simple types are used to create derived datatypes. They provide a set of constraints on the value space (a set of values) and the lexical space (a set of valid literals) of a datatype.">Adding simple types</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html
index ebcf58c..f699167 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html
@@ -9,10 +9,11 @@
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta content="task" name="DC.Type" />
<meta name="DC.Title" content="Adding simple types" />
-<meta name="abstract" content="Simple types are used to created derived datatypes. They provide a set of constraints on the value space (that is, a set of values) and the lexical space (that is, a set of valid literals) of a datatype." />
-<meta name="description" content="Simple types are used to created derived datatypes. They provide a set of constraints on the value space (that is, a set of values) and the lexical space (that is, a set of valid literals) of a datatype." />
+<meta name="abstract" content="Simple types are used to create derived datatypes. They provide a set of constraints on the value space (a set of values) and the lexical space (a set of valid literals) of a datatype." />
+<meta name="description" content="Simple types are used to create derived datatypes. They provide a set of constraints on the value space (a set of values) and the lexical space (a set of valid literals) of a datatype." />
<meta content="XML schema editor, adding, simple types, XML schema files" name="DC.subject" />
<meta content="XML schema editor, adding, simple types, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddreg.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="taddsmpt" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -27,18 +28,17 @@
-<div><p>Simple types are used to created derived datatypes. They provide
-a set of constraints on the value space (that is, a set of values) and the
-lexical space (that is, a set of valid literals) of a datatype.</p>
+<div><p>Simple types are used to create derived datatypes.
+They provide a set of constraints on the value space (a set of values) and
+the lexical space (a set of valid literals) of a datatype.</p>
<div class="section"><p>A simple type cannot have element content and cannot carry attributes.
Elements that contain numbers (and strings, and dates, and so on) but do not
-contain any sub-elements are said to have a simple type.</p>
-<p>The following
-instructions were written for the Resource perspective, but they will also
-work in many other perspectives.</p>
-<p>To add a simple type, follow these
-steps:</p>
+contain any sub-elements have a simple type.</p>
+<p>The following instructions
+were written for the Resource perspective, but they will also work in many
+other perspectives.</p>
+<p>To add a simple type:</p>
</div>
<ol>
@@ -47,9 +47,13 @@
<li class="stepexpand"><span>In the Outline view, right-click <strong>Types</strong>, and click <span class="uicontrol">Add
Simple Type</span>.</span></li>
-<li class="stepexpand"><span>In the Outline view, select the new simple type, and in the Properties
-view, click the <span class="uicontrol">General</span> tab. Then type a new name for
-the simple type in the <span class="uicontrol">Name</span> field.</span></li>
+<li class="stepexpand"><span>In the Outline view, select the new simple type.</span></li>
+
+<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">General</span> tab.</span>
+</li>
+
+<li class="stepexpand"><span>Type a new name for the simple type in the <span class="uicontrol">Name</span> field.</span>
+</li>
<li class="stepexpand"><span>You can select the following options from the <span class="uicontrol">Variety</span> list:</span>
<ul>
@@ -68,12 +72,12 @@
</li>
-<li class="stepexpand"><span>If you selected <span class="uicontrol">atomic</span> from the <span class="uicontrol">Variety</span> drop
-down list, click the <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> button next to the <span class="uicontrol">Base
-type</span> field to specify a base type for the simple type.</span> The
-Set Type dialog lists all built-in and user-defined types currently available.
-You can change the <span class="uicontrol">Scope</span> of the list by selecting one
-of the following options:<ul>
+<li class="stepexpand"><span>If you selected <span class="uicontrol">atomic</span> from the <span class="uicontrol">Variety</span> list,
+click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> next to the <span class="uicontrol">Base type</span> field
+to specify a base type for the simple type.</span> The Set Type dialog
+box lists all built-in and user-defined types currently available. You can
+change the <span class="uicontrol">Scope</span> of the list by selecting one of the
+following options:<ul>
<li><span class="uicontrol">Workspace</span>. Lists all of the types available in
your workspace. </li>
@@ -89,12 +93,12 @@
</ul>
</li>
-<li class="stepexpand"><span>If you selected <span class="uicontrol">list</span> from the <span class="uicontrol">Variety</span> drop
-down list, click the <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> button next to the <span class="uicontrol">Item
-type</span> field to specify a item type for the simple type.</span> The
-Set Type dialog lists all built-in and user-defined types currently available.
-You can change the <span class="uicontrol">Scope</span> of the list by selecting one
-of the following options:<ul>
+<li class="stepexpand"><span>If you selected <span class="uicontrol">list</span> from the <span class="uicontrol">Variety</span> list,
+click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> next to the <span class="uicontrol">Item type</span> field
+to specify a item type for the simple type.</span> The Set Type dialog
+box lists all built-in and user-defined types currently available. You can
+change the <span class="uicontrol">Scope</span> of the list by selecting one of the
+following options:<ul>
<li><span class="uicontrol">Workspace</span>. Lists all of the types available in
your workspace. </li>
@@ -110,10 +114,10 @@
</ul>
</li>
-<li class="stepexpand"><span>If you selected <span class="uicontrol">union</span> from the <span class="uicontrol">Variety</span> drop
-down list, click the <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> button next to the <span class="uicontrol">Member
-types</span> field to specify the member types for the simple type.</span>
- You can select to add both <span class="uicontrol">Built-in simple types</span> and <span class="uicontrol">User-defined
+<li class="stepexpand"><span>If you selected <span class="uicontrol">union</span> from the <span class="uicontrol">Variety</span> list,
+click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> next to the <span class="uicontrol">Member types</span> field
+to specify the member types for the simple type.</span> You can select
+to add both <span class="uicontrol">Built-in simple types</span> and <span class="uicontrol">User-defined
simple types</span> to the member types value list. </li>
<li class="stepexpand"><span>Click the <span class="uicontrol">Constraints</span> tab.</span> From
@@ -125,14 +129,13 @@
in the instance document. You can either add one enumeration or several enumerations
at a time:</span> <ul>
<li>To add one enumeration at a time, under <span class="uicontrol">Specific constraint
-values</span>, select the <span class="uicontrol">Enumerations</span> radio button
-and click the <span class="uicontrol">Add</span> button and specify a value for the
-enumeration.</li>
+values</span>, select <span class="uicontrol">Enumerations</span> and click <span class="uicontrol">Add</span> and
+specify a value for the enumeration.</li>
<li>To add several enumerations at one time, follow these steps:<ol type="i">
-<li>Select the <span class="uicontrol">Enumerations</span> radio button.</li>
+<li>Select <span class="uicontrol">Enumerations</span>.</li>
-<li>Click the <span class="uicontrol">Add...</span> button.</li>
+<li>Click <span class="uicontrol">Add</span>.</li>
<li>Enter the value of each enumeration. Each value must be separated by the <span class="uicontrol">Delimiter
character</span>. For example: <samp class="codeph">First, Second</samp> will create
@@ -140,9 +143,9 @@
<li>Select the <span class="uicontrol">Preserve leading and trailing whitespace</span> check
box if you want any white space around your enumeration values to be preserved.
-If, for example, you select this check box, the values of <samp class="codeph">First, Second</samp> will
+If you select this check box, the values of <samp class="codeph">First, Second</samp> will
show up as "First" and " Second" (there is a space before Second) because
-you put a space before "Second" when entered the value.</li>
+you put a space before "Second" when entering the value.</li>
<li>Click <span class="uicontrol">OK</span>. Your enumerations will be created and
appear in the Properties view.</li>
@@ -157,9 +160,9 @@
values.</span> For example, you could restrict the field to only accept
input which follows the pattern "five digits followed by two upper-case ASCII
letters". To set a pattern constraint:<ol type="i">
-<li>Select the <span class="uicontrol">Patterns</span> radio button.</li>
+<li>Select <span class="uicontrol">Patterns</span>.</li>
-<li>Click the <span class="uicontrol">Add...</span> button.</li>
+<li>Click <span class="uicontrol">Add</span>.</li>
<li>Create the regular expression pattern you wish to use as your constraint
using the <span class="uicontrol">Regular Expression</span> wizard.</li>
@@ -175,14 +178,21 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this simple type.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
</ol>
</div>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddreg.html" title="A pattern facet can be used to constrain the value of a type's lexical space (the set of string literals that represent the values of a type), which indirectly constrains the value space.">Adding pattern facets to simple types</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html
index de416ef..9aec932 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html
@@ -13,6 +13,9 @@
<meta name="description" content="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations." />
<meta content="XML schema files, creating" name="DC.subject" />
<meta content="XML schema files, creating" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/tvdtschm.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="tcxmlsch" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -53,7 +56,14 @@
</div>
-<div />
+<div><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div>
+<div><a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html
index 8f90c35..a4cc200 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html
@@ -13,6 +13,7 @@
<meta name="description" content="If you have created any XML schema components you no longer need, you can delete them." />
<meta content="XML schema editor, deleting, components, XML schema files" name="DC.subject" />
<meta content="XML schema editor, deleting, components, XML schema files" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/rrefintg.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="tdelscmp" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -53,6 +54,10 @@
</div>
+<div><div class="relref"><strong>Related reference</strong><br />
+<div><a href="../topics/rrefintg.html" title="The XML schema editor has a built-in mechanism to handle referential integrity issues. When you delete certain nodes, clean up for any nodes affected will automatically occur.">Referential integrity in the XML schema editor</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html
index d2a26cb..840ef3a 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html
@@ -41,7 +41,7 @@
Navigator view.</span> It will automatically open in the XML schema editor.
</li>
-<li class="stepexpand"><span>In the Outline view, click <span class="uicontrol">Directives</span></span>
+<li class="stepexpand"><span>In the Outline view, click <span class="uicontrol">Directives</span>.</span>
</li>
<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">General</span> tab.</span>
@@ -58,9 +58,12 @@
<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
to provide any information about this XML schema.</span> The <span class="uicontrol">Documentation</span> page
-is used for human readable material, such as a description, and the <span class="uicontrol">App
-Info</span> page can be used to provide information for applications.
-</li>
+is used for human readable material, such as a description.</li>
+
+<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to
+add application information elements to your annotations of schema components.</span>
+ The <span class="uicontrol">Extensions</span> page allows you to specify the
+schema and add XML content to your annotations.</li>
</ol>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html
index d42f1b8..8726a2c 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html
@@ -13,6 +13,11 @@
<meta name="description" content="If you want to work with XML schema files that you created outside of the product, you can import them into the workbench and open them in the XML schema editor. The XML schema editor provides you with a structured view of the XML schema." />
<meta content="XML schema files, importing" name="DC.subject" />
<meta content="XML schema files, importing" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/tvdtschm.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddimpt.html" />
+<meta scheme="URI" name="DC.Relation" content="../topics/taddincl.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="timpschm" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -35,7 +40,7 @@
<div class="section"><p>The following instructions were written for the Resource perspective,
but they will also work in many other perspectives.</p>
<p>To import an XML
-schema into the workbench, follow these steps:</p>
+schema into the workbench:</p>
</div>
<ol>
@@ -56,7 +61,16 @@
</div>
-<div />
+<div><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div>
+</div>
+<div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div>
+<div><a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div>
+<div><a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema.">Adding import elements</a></div>
+<div><a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema.">Adding include elements</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html
index 835b556..582def5 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html
@@ -13,6 +13,7 @@
<meta name="description" content="When you are working in the Source view, you can use F3 to navigate through the file by placing your cursor in the appropriate item and clicking F3 to jump to the item it refers to." />
<meta content="XML schema files, navigating" name="DC.subject" />
<meta content="XML schema files, navigating" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" />
<meta content="XHTML" name="DC.Format" />
<meta content="tnavsrc" name="DC.Identifier" />
<meta content="en-us" name="DC.Language" />
@@ -70,6 +71,10 @@
</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div>
+</div>
+</div>
</body>
</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.html
index 1aaab0c..ceb881d 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.html
@@ -49,8 +49,8 @@
<ol type="a">
<li class="substepexpand"><span>Type in the new name of the artifact.</span></li>
-<li class="substepexpand"><span><strong><em>Optional:</em></strong> Click Preview.</span> A window will
-open indicating all of the changes which will take place due to the refactoring.
+<li class="substepexpand"><span>(Optional) Click <strong>Preview</strong>.</span> A window
+will open indicating all of the changes which will take place due to the refactoring.
</li>
<li class="substepexpand"><span>Click <span class="uicontrol">OK.</span></span></li>
@@ -66,20 +66,20 @@
<div class="example"><strong><u>Component References in XML Schema</u></strong><table summary="" cellspacing="0" cellpadding="4" border="1" class="simpletableborder">
<tr>
-<th valign="bottom" align="left" id="N100EE">Global named components</th>
+<th valign="bottom" align="left" id="N100EB">Global named components</th>
-<th valign="bottom" align="left" id="N100F4">Reference</th>
+<th valign="bottom" align="left" id="N100F1">Reference</th>
</tr>
<tr>
-<td valign="top" headers="N100EE"><ul>
+<td valign="top" headers="N100EB"><ul>
<li><element name="foo"></li>
</ul>
</td>
-<td valign="top" headers="N100F4"><ul>
+<td valign="top" headers="N100F1"><ul>
<li><element ref="foo"></li>
<li><element substitutionGroup="foo"</li>
@@ -90,13 +90,13 @@
</tr>
<tr>
-<td valign="top" headers="N100EE"><ul>
+<td valign="top" headers="N100EB"><ul>
<li><simple/complexType name="foo"></li>
</ul>
</td>
-<td valign="top" headers="N100F4"><ul>
+<td valign="top" headers="N100F1"><ul>
<li><element type="foo"></li>
<li><attribute type="foo"></li>
@@ -111,13 +111,13 @@
</tr>
<tr>
-<td valign="top" headers="N100EE"><ul>
+<td valign="top" headers="N100EB"><ul>
<li><attribute name="foo"></li>
</ul>
</td>
-<td valign="top" headers="N100F4"><ul>
+<td valign="top" headers="N100F1"><ul>
<li><attribute ref="foo"></li>
</ul>
@@ -126,13 +126,13 @@
</tr>
<tr>
-<td valign="top" headers="N100EE"><ul>
+<td valign="top" headers="N100EB"><ul>
<li><attributeGroup name="foo"></li>
</ul>
</td>
-<td valign="top" headers="N100F4"><ul>
+<td valign="top" headers="N100F1"><ul>
<li><attributeGroup ref="foo"></li>
</ul>
@@ -141,13 +141,13 @@
</tr>
<tr>
-<td valign="top" headers="N100EE"><ul>
+<td valign="top" headers="N100EB"><ul>
<li><group name="foo"></li>
</ul>
</td>
-<td valign="top" headers="N100F4"><ul>
+<td valign="top" headers="N100F1"><ul>
<li><group ref="foo"></li>
</ul>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html
index 923a247..b684af6 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html
@@ -13,6 +13,7 @@
<meta name="description" content="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view." />
<meta content="XML schema files, validating" name="DC.subject" />
<meta content="XML schema files, validating" name="keywords" />
+<meta scheme="URI" name="DC.Relation" content="../topics/tcxmlsch.html" />
<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html" />
<meta scheme="URI" name="DC.Relation" content="http://www.w3.org/TR/xmlschema-1" />
<meta scheme="URI" name="DC.Relation" content="http://www.w3.org/TR/xmlschema-2" />
@@ -37,7 +38,7 @@
<div class="section"><p>The following instructions were written for the Resource perspective,
but they will also work in many other perspectives.</p>
<p>To validate an XML
-schema, follow these steps:</p>
+schema:</p>
</div>
<ol>
@@ -48,8 +49,8 @@
view to see what problems were logged. </span> <div class="note"><span class="notetitle">Note:</span> If you receive an
error message indicating that the Problems view is full, you can increase
the number of error messages allowed by selecting <span class="menucascade"><span class="uicontrol">Properties
-> Validation</span></span> from the project's pop-up menu and
-specifying the maximum number of error messages allowed.</div>
+> Validation</span></span> and specifying the maximum
+number of error messages allowed.</div>
</li>
</ol>
@@ -74,7 +75,10 @@
</div>
-<div><div class="relinfo"><strong>Related information</strong><br />
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations.">Creating XML schemas</a></div>
+</div>
+<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html" title="General validation information">../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html</a></div>
<div><a href="http://www.w3.org/TR/xmlschema-1" target="_blank" title="See the W3C Web site for more information on XML Schema specifications">XML
Schema Part 1: Structures</a></div>
