updated docs
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html
new file mode 100644
index 0000000..d7d715a
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2005 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Working with XML schemas</title>
+</head>
+<body id="workingwithxmlschemas"><a name="workingwithxmlschemas"><!-- --></a>
+<h1 class="topictitle1">Working with XML schemas</h1>
+<div><p>This sections contains information on the following:</p>
+</div>
+<p><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="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="timpschm.html" title="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.">Importing XML schemas</a></div>
+<div><a href="tnavsrc.html" title="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.">Navigating XML schemas</a></div>
+<div><a href="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><a href="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><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>
+</p>
+<p 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="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>
+</p></body>
+</html>
\ No newline at end of file
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 eea95e3..5697286 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html
@@ -19,28 +19,25 @@
<body id="cxmlsced"><a name="cxmlsced"><!-- --></a>
<h1 class="topictitle1">XML schema editor</h1>
-<div><p>XML schemas are an XML language for describing and constraining
-the content of XML files. </p><p>XML schemas are a proposed alternative for the document type definition
-(DTD) based on XML. They 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>
+<div><p>XML schemas are an XML language for describing and constraining the
+the content of XML files.</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>For more information on XML schema, refer to:</p>
<ul><li> <a href="http://www.w3.org/TR/xmlschema-0/" target="_blank">http://www.w3.org/TR/xmlschema-0/</a> </li>
<li> <a href="http://www.w3.org/TR/xmlschema-1/" target="_blank">http://www.w3.org/TR/xmlschema-1/</a> </li>
<li> <a href="http://www.w3.org/TR/xmlschema-2/" target="_blank">http://www.w3.org/TR/xmlschema-2/</a> </li>
</ul>
<p>This product provides an XML schema editor for creating, viewing, and validating
-XML schemas. Using the XML schema editor, you can do the following:</p>
+XML schemas. Using the XML schema editor, you can:</p>
<ul><li>Create and delete XML schema components such as complex types, simple
types, elements, attributes, attribute groups, and groups</li>
<li>Edit XML schemas</li>
<li>Import existing XML schemas for structured viewing</li>
</ul>
-<p>The XML schema support in the XML schema editor is based on the </p>
-<p><a href="http://www.w3.org/TR/xmlschema-0/" target="_blank">W3C
-XML Schema Recommendation Specification of 2 May 2001</a></p>
<p>The XML Schema specification from the W3C Web site is used for validation.</p>
<div class="skipspace"><h4 class="sectiontitle">XML schema editor views - Graph, Outline, Properties, and
Source</h4>There are four main views you can work with in the XML schema
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 a20461b..3686085 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html
@@ -19,6 +19,9 @@
<body id="rnmspc"><a name="rnmspc"><!-- --></a>
<h1 class="topictitle1">XML namespaces</h1>
+<div><p>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.</p>
<div><div class="skipspace">XML namespaces are defined by a W3C recommendation, dating 14 January
1999, called <a href="http://www.w3.org/TR/REC-xml-names/">Namespaces
in XML</a>. XML tag names should be globally unique, as well as short for
@@ -69,7 +72,7 @@
the default namespace for the schema is defined as the standard XML schema
namespace <i>http://www.w3.org/2001/XMLSchem</i>a; there is also a schema
specific namespace <i>http://www.ibm.com</i>.</p>
-<div class="p"><pre><?xml version="1.0"?>
+<div class="p"><pre><?xml version="1.0">
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:TestSchema="http://www.ibm.com">
<simpleType name="ZipCodeType">
<restriction base="integer">
@@ -80,10 +83,10 @@
<!--element definitions skipped -->
</schema> </pre>
</div>
-<p>Assuming that the XML schema defined above
+<p>Assuming that the preceding XML schema is
is saved as <span class="filepath">C:\temp\TestSchema.xsd</span>, a sample XML file
that validates against this schema is:</p>
-<div class="p"><pre><?xml version="1.0"?>
+<div class="p"><pre><?xml version="1.0">
<x:addressList xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com file:///C:/temp/TestSchema.xsd">
xsi:schemaLocation="http://www.ibm.com file:///C:/temp/TestSchema.xsd">
<x:address>
@@ -109,13 +112,13 @@
namespace is http://www.ibm.com; it is defined in the XML schema file and
referenced twice in the XML file. Any mismatch between these three occurrences
of the namespace lead to validation errors.</p>
-<p> The following are some
-examples of how target namespace and namespace prefixes work in XML schemas
-and their corresponding XML instance documents. </p>
+<p> The following examples
+show how target namespaces and namespace prefixes work in XML schemas and
+their corresponding XML instance documents.</p>
</div>
<div class="skipspace"><h4 class="sectiontitle">Sample 1 - A schema with both a default and target namespace
and unqualified locals</h4><p>The XML schema: </p>
-<div class="p"><pre><?xml version="1.0"?>
+<div class="p"><pre><?xml version="1.0">
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com">
<complexType name="AddressType">
<sequence>
@@ -127,7 +130,7 @@
</div>
<p>A valid XML instance document created from
this schema looks like this. Local elements and attributes are <i>unqualified</i>.</p>
-<div class="p"><pre><?xml version="1.0"?>
+<div class="p"><pre><?xml version="1.0">
<x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com x.xsd ">
<name>Peter Smith</name>
</x:MyAddress> </pre>
@@ -139,7 +142,7 @@
the<i>"x"</i> prefix is not assigned to the local element <i>"name"</i>.</p>
</div>
<div class="skipspace"><h4 class="sectiontitle">Sample 2 - A schema with both a default and target namespace
-and qualified locals</h4><div class="p"><pre><?xml version="1.0"?>
+and qualified locals</h4><div class="p"><pre><?xml version="1.0">
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com" elementFormDefault="qualified">
<complexType name="AddressType">
<sequence>
@@ -153,7 +156,7 @@
this schema looks like this. Local elements and attributes are <i>qualified</i> This
is because the elementFormDefault attribute is set to qualified in the XML
schema.</p>
-<div class="p"><pre><?xml version="1.0"?>
+<div class="p"><pre><?xml version="1.0">
<x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.ibm.com x.xsd ">
<x:name>Peter Smith</x:name>
@@ -178,11 +181,11 @@
user defined types belong to the namespace http://www.ibm.com as defined
by the targetNamespace attribute, and the prefix is <i>"x"</i> as defined
by the xmlns:x attribute.</p>
-<div class="p"><pre><?xml version="1.0"?>
+<div class="p"><pre><?xml version="1.0">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com">
<xsd:complexType name="AddressType">
<xsd:sequence>
- <xsd:element name="name" type="xsd:string"></xsd:element>
+ <xsd:element name="name" type="xsd:string"></xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="MyAddress" type="x:AddressType"></xsd:element>
@@ -191,7 +194,7 @@
<p>A valid XML instance document created
from this schema looks like this. Local elements and attributes are <i>unqualified</i>.
The semantics of qualification is the same as Sample 1.</p>
-<div class="p"><pre><?xml version="1.0"?>
+<div class="p"><pre><?xml version="1.0">
<x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ibm.com x.xsd ">
<name>Peter Smith</name>
</x:MyAddress></pre>
@@ -203,7 +206,7 @@
qualified with a prefix such as <i>"xsd"</i>. The definitions and declarations
from this schema such as <i>AddressType</i> are referenced without namespace
qualification since there is no namespace prefix. </p>
-<div class="p"><pre><?xml version="1.0"?>
+<div class="p"><pre><?xml version="1.0">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="AddressType">
<xsd:sequence>
@@ -217,7 +220,7 @@
</div>
<p>A valid XML instance document created
from the schema looks like this. All elements are <i>unqualified</i>.</p>
-<div class="p"><pre><?xml version="1.0"?>
+<div class="p"><pre><?xml version="1.0">
<MyAddress xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="x.xsd">
<name>name</name>
</MyAddress></pre>
@@ -226,7 +229,7 @@
<div class="skipspace"><h4 class="sectiontitle">Sample 5 - A schema where the target namespace is the default
namespace</h4><p>This is an XML schema where the target namespace is the
default namespace. As well, the namespace has no namespace prefix.</p>
-<div class="p"><pre><?xml version="1.0"?>
+<div class="p"><pre><?xml version="1.0">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns="http://www.ibm.com">
<xsd:complexType name="AddressType">
<xsd:sequence>
@@ -238,12 +241,15 @@
</div>
<p>A valid XML instance document created
from the schema looks like this:</p>
-<div class="p"><pre><?xml version="1.0" encoding="UTF-8"?>
+<div class="p"><pre><?xml version="1.0" encoding="UTF-8">
<MyAddress xmlns="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com NewXMLSchema.xsd">
<name>name</name>
</MyAddress> </pre>
</div>
</div>
</div>
-</body>
+<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 78cf364..8c33e5f 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html
@@ -19,87 +19,74 @@
<body id="rrefintg"><a name="rrefintg"><!-- --></a>
<h1 class="topictitle1">Referential integrity in the XML schema editor</h1>
+<div><p>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.</p>
<div><p>When you define a complex type, you can add a content model to
it and reference a global element. </p><div class="skipspace"><div class="p">For example:<pre><schema>
- <element name="comment" type="string">
- <complexType name="Items">
- <sequence>
- <element ref="comment">
- </sequence>
- </complexType>
+ <element name="comment" type="string">
+ <complexType name="Items">
+ <sequence>
+ <element ref="comment">
+ </sequence>
+ </complexType>
</schema></pre>
</div>
<p>If the global element (comment) was deleted,
-all references to it would be in error. To prevent this, the XML schema editor
-has a built-in mechanism to handle such referential integrity issues. When
-you delete the global element, the XML schema editor will clean up using the
-following algorithm:</p>
+all references to it would be in error. However, when you delete the global
+element, the XML schema editor will clean up using the following algorithm:</p>
<ul><li>If there are one or more global elements in the schema, it will change
all existing references to the first global element.</li>
<li>If there is no global element, then it will delete the element reference
from the content model.</li>
</ul>
<p>Similar cleanup operations are performed when other types of objects
-are deleted. The following lists describes various cleanup operations.
- </p>
-<p>Deleting a global attribute will cause the following cleanup:</p>
-<ol><li>Any content model or attribute group that references the deleted global
-attribute will be reset using the above algorithm.</li>
+are deleted. The following lists describes various cleanup operations. </p>
+<p>Deleting
+a global attribute will cause the following cleanup:</p>
+<ul><li>Any item that references the deleted global attribute will be reset using
+the preceding algorithm.</li>
</ol>
-<p>Deleting a complex type will cause the following cleanup:</p>
-<ol><li>Any element type that is set to the deleted complex type will be reset
+ </ul>
+ <p>Deleting a complex type will cause the following cleanup:</p>
+ <ul>
+ <li>Any element type that is set to the deleted complex type will be reset
to the <tt class="sysout">string</tt> type.</li>
-<li>Any complex type that derives from the deleted complex type will be reset
+ <li>Any complex type that derives from the deleted complex type will be reset
to no derivation.</li>
-</ol>
-<p>Deleting a simple type will cause the following cleanup:</p>
-<ol><li>Any attribute type that is set to the deleted simple type will be reset
+ </ul>
+ <p>Deleting a simple type will cause the following cleanup:</p>
+ <ul>
+ <li>Any attribute type that is set to the deleted simple type will be reset
to the <tt class="sysout">string</tt> type.</li>
-<li>Any element type that is set to the deleted simple type will be reset
+ <li>Any element type that is set to the deleted simple type will be reset
to the <tt class="sysout">string</tt> type.</li>
-<li>Any simple type that derives from the deleted simple type will be reset
+ <li>Any simple type that derives from the deleted simple type will be reset
to <tt class="sysout">string</tt> as its base type.</li>
-</ol>
-<p>Deleting a group or attribute group will cause the following cleanup:</p>
-<ol><li>Any complex type that references the deleted group or attribute group
+ </ul>
+ <p>Deleting a group or attribute group will cause the following cleanup:</p>
+ <ul>
+ <li>Any complex type that references the deleted group or attribute group
will be reset using the algorithm similar to the one described earlier for
deleted global elements.</li>
-</ol>
+ </ul>
</div>
-<div class="skipspace"><h4 class="sectiontitle">Deleting include and import elements</h4><p>When an <samp class="codeph">include</samp> or <samp class="codeph">import</samp> element
-is added to a schema, types from the included or imported schema become visible
-to the current schema. For example, the following schema references the Address
-type from the Address.xsd file</p>
-<div class="p"><pre><schema targetNamespace="http://www.example.com/IPO"
-xmlns="http://www.w3.org/1999/XMLSchema"
-xmlns:ipo="http://www.example.com/IPO>
-<include schemaLocation="F:\vabase\itp\workbench\B2B\Project1\Address.xsd"/>
-<complexType name="PurchaseOrder">
-<sequence>
-<element name="shipTo" type="ipo:Address">
-</sequence>
-</complexType>
-</schema> </pre>
-</div>
-<p>If the included schema is subsequently deleted,
-the <samp class="codeph">include</samp> element would be in error. To prevent this, the
-XML schema editor will perform the necessary cleanup. In this example, the
-type for the element <samp class="codeph">shipTo</samp> would be reset to the <tt class="sysout">string</tt> data
-type.</p>
-<p>The XML schema editor resets the following type references when
-an include or import element is deleted:</p>
-<ul><li>Global element and element's type</li>
+<div class="section"><h4 class="sectiontitle">Deleting included and imported schema</h4><div class="p">If an included
+or imported schema is deleted, you must manually reset the following type
+references as appropriate: <ul><li>Global element and element's type</li>
<li>Attribute type</li>
<li>Complex type derivation</li>
<li>Simple type derivation</li>
</ul>
-<p>The cleanup is similar to the other operations outlined above. The
-XML schema editor will write an information message to the Problems view to
-notify you of such operations.</p>
-<p>(c) Copyright 2001, World Wide Web Consortium
-(Massachusetts Institute of Technology, Institut National de Recherche en
-Informatique et en Automatique, Keio University) </p>
+They will not automatically be reset if an included or imported schema
+is deleted.</div>
</div>
</div>
-</body>
+<p><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files.">XML schema editor</a></div>
+</p>
+<p 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>
+</p></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
new file mode 100644
index 0000000..2d6e1c4
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html
@@ -0,0 +1,99 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2005 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Icons used in the XML schema editor</title>
+</head>
+<body id="ricons"><a name="ricons"><!-- --></a>
+<h1 class="topictitle1">Icons used in the XML schema editor</h1>
+<div><p>The following XML schema editor icons appear in the Outline, Graph,
+and Properties view.</p>
+<div class="section"></div>
+
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><tbody><tr><td valign="bottom"><strong>Icon</strong></td>
+<td valign="bottom"><strong>Description</strong></td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAnyAttribute.gif" alt="This graphic is the any attribute icon" /></td>
+<td valign="top"><samp class="codeph">any</samp> attribute</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAny.gif" alt="This graphic is the any element icon" /></td>
+<td valign="top"><samp class="codeph">any</samp> element</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAttribute.gif" alt="This graphic is the attribute icon" /></td>
+<td valign="top">attribute</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAttributeGroup.gif" alt="This graphic is the attribute group icon" /></td>
+<td valign="top">attribute group</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAttributeGroupRef.gif" alt="This graphic is the attribute group reference icon" /></td>
+<td valign="top">attribute group reference</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAttributeRef.gif" alt="This graphic is the attribute reference icon" /></td>
+<td valign="top">attribute reference</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDAll.gif" alt="This graphic is the content model - all icon" /></td>
+<td valign="top">content model - all</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDChoice.gif" alt="This graphic is the content model - choice icon" /></td>
+<td valign="top">content model - choice</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDSequence.gif" alt="This graphic is the content model - sequence icon" /></td>
+<td valign="top">content model - sequence</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDComplexType.gif" alt="This graphic is the any element icon" /></td>
+<td valign="top">complex type</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDElement.gif" alt="This graphic is the element icon" /></td>
+<td valign="top">element</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDElementRef.gif" alt="This graphic is the element reference icon" /></td>
+<td valign="top">element reference</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDSimpleEnum.gif" alt="This graphic is the enumeration icon" /></td>
+<td valign="top">enumeration</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDGlobalAttribute.gif" alt="This graphic is the global attribute icon" /></td>
+<td valign="top">global attribute</td>
+</tr>
+<tr><td valign="top"> <img src="../images/XSDGlobalElement.gif" alt="This graphic is the global element icon" /></td>
+<td valign="top">global element</td>
+</tr>
+<tr><td valign="top"> <img src="../images/XSDGroup.gif" alt="This graphic is the group icon" /></td>
+<td valign="top">group</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDGroupRef.gif" alt="This graphic is the group reference icon" /></td>
+<td valign="top">group reference</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDImport.gif" alt="This graphic is the import icon" /></td>
+<td valign="top">import</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDInclude.gif" alt="This graphic is the include icon" /></td>
+<td valign="top">include</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDSimplePattern.gif" alt="This graphic is the pattern icon" /></td>
+<td valign="top">pattern</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDRedefine.gif" alt="This graphic is the redefine icon" /></td>
+<td valign="top">redefine</td>
+</tr>
+<tr><td valign="top"><img src="../images/XSDSimpleType.gif" alt="This graphic is the simple type icon" /></td>
+<td valign="top">simple type</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div></div></body>
+</html>
\ No newline at end of file
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 00efdae..22106ed 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html
@@ -14,72 +14,82 @@
* IBM Corporation - initial API and implementation
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-<title>Adding an attribute group</title>
+<title>Adding attribute groups</title>
</head>
<body id="taddagrp"><a name="taddagrp"><!-- --></a>
-<h1 class="topictitle1">Adding an attribute group</h1>
+<h1 class="topictitle1">Adding attribute groups</h1>
<div><p>An attribute group definition is an association between a name
-and a set of attribute declarations, enabling re-use of the same set in several
-complex type definitions. Named groups of attribute declarations can greatly
-facilitate the maintenance and reuse of common attribute declarations in an
-XML schema.</p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives. </p>
+and a set of attribute declarations. Named groups of attribute declarations
+can greatly facilitate the maintenance and reuse of common attribute declarations
+in an XML schema.</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
attribute group to an XML schema, follow these steps:</p>
</div>
<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
-<li class="skipspace"><span>In the Outline view, right-click the XML schema and click <span class="uicontrol">Add
-Attribute Group</span>.</span> It appears in the <span class="uicontrol">Attribute
+<li class="skipspace"><span>In the Outline view, right-click the XML schema and click
+<b> <span class="uicontrol">Add
+Attribute Group</span></b>.</span> It appears in the <span class="uicontrol">Attribute
Groups</span> folder.</li>
<li class="skipspace"><span>Select your new group, and in the Properties view, type a name
-for the attribute group in the <span class="uicontrol">Name</span> field.</span></li>
+for the attribute group in the <b> <span class="uicontrol">Name</span></b> field.</span></li>
<li class="skipspace"><span>To add an attribute, right-click your attribute group in the Outline
-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="skipspace"><span>Select the attribute, and in the Properties view, type the <span class="uicontrol">Name</span> of
-it. </span></li>
-<li class="skipspace"><span>Click the <span class="uicontrol">More</span> button and specify the
-type for the attribute.</span> To specify that an attribute's type is
-anonymous, when the <span class="uicontrol">User-defined simple type</span> radio
-button is selected, click <span class="uicontrol">**anonymous**</span> in the type
-list. The anonymous type is added to the outline under the attribute.
-Expand the attribute to see it. You can then start adding content to the new
-anonymous type.</li>
+view, click <b> <span class="uicontrol">Add Attribute</span></b>.</span> The attribute
+appears below the attribute group in the Outline view.<ol type="a"><li class="skipspace"><span>Select the attribute, and in the Properties view, type the
+ <b> <span class="uicontrol">Name</span></b> of it.</span></li>
+<li><span>Click the <b> <span class="uicontrol">More</span></b> <img src="../images/More.gif" alt="This graphic is the More button" /> button and specify the
+type for the attribute. The</span> Set Type dialog lists all built-in and
+user-defined types currently available. You can change the <b>
+<span class="uicontrol">Scope</span></b> of the list by selecting one of the
+following options:
+<ul>
+ <li><b><span class="uicontrol">Workspace</span></b>. Lists all of the types
+ available in your workspace. </li>
+ <li><b><span class="uicontrol">Enclosing Project</span>.</b> Lists all of
+ the types available in the project that contains your file. </li>
+ <li>(Default) <b><span class="uicontrol">Current Resource</span>.</b> List
+ all of the types available in your current file.</li>
+</ul>
+ </li>
</ol>
</li>
<li class="skipspace"><span>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, right-click your attribute group, and click <span class="uicontrol">Add
-Attribute Ref</span>.</span> A declaration that references a global
+To add an attribute reference, right-click your attribute group, and click <b> <span class="uicontrol">Add
+Attribute Ref</span>.</b></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. The menu option to add
+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 (which appears below the attribute group
in the Outline view), then select the global attribute you want it to reference
-from the <span class="uicontrol">ref</span> drop down list.</span></li>
+from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
</ol>
</li>
<li class="skipspace"><span>An attribute group reference provides a reference to an attribute
group. To add an attribute group reference, right-click your attribute group,
-and click <span class="uicontrol">Add Attribute Group Ref</span>, and fill in the
+and click <span class="uicontrol"><b>Add Attribute Group Ref</b></span>, and fill in the
field values as necessary.</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. 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 (which appears below the attribute group
in the Outline view), then select the attribute group you want it to reference
-from the <span class="uicontrol">ref</span> drop down list.</span></li>
+from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
</ol>
</li>
-<li class="skipspace"><span>An <samp class="codeph">any</samp> element enables attributes to appear
-in <samp class="codeph">any</samp> elements. To add an <samp class="codeph">any</samp> attribute,
-right-click in your attribute group and click <span class="uicontrol">Add Any Attribute</span>.</span> The <samp class="codeph">any</samp> appears below the attribute group in the Outline
+<li class="skipspace"><span>An <samp class="codeph">any</samp> element enables element content according
+to namespaces, and the corresponding <samp class="codeph">any</samp> attribute
+element enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute,
+right-click your attribute group and click <b> <span class="uicontrol">Add Any Attribute</span></b>.</span> The <samp class="codeph">any</samp> attribute
+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 <b>namespace</b> value, you can select <b>##any</b> (this allows
any well-formed XML from any namespace), <b>##local </b> (this allows any
well-formed XML that is not declared to be in a namespace, <b>##other </b> (this
allows any well-formed XML that is not from the target namespace of the type
being defined) or <b>##targetNamespace </b> (which is shorthand for the target
namespace of the type being defined). </li>
-<li>For a <span class="uicontrol">processContents</span> value, you can select <b>skip</b> (the
+<li>For a <b> <span class="uicontrol">processContents</span></b> value, you can select <b>skip</b> (the
XML processor will not validate the attribute content at all), <b>lax</b> (the
XML processor will validate the attribute content as much as it can), or <b>strict </b> (the
XML processor will validate all the attribute content).</li>
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 4d58aff..a10c6b2 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html
@@ -26,20 +26,19 @@
<div class="p"><pre><element name = "MyWebPage">
<complexType>
<any namespace ="http://www.w3.org/1999/xhtml>
- < minOccurs="1" maxOccurs="unbounded" processContents="skip"/>
+ < minOccurs="1" maxOccurs="unbounded" processContents="skip"/>
</complexType>
</element></pre>
</div>
-<p>The above schema fragment allows a <var class="varname"><MyWebPage></var> element
+<p>The preceding schema fragment allows a <var class="varname"><MyWebPage></var> 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>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>
</div>
<ol><li class="skipspace"><span>In the Outline view, right-click the content model that you want
-to work with and click <span class="uicontrol">Add Any</span>. </span></li>
+to work with and click <b> <span class="uicontrol">Add Any</span></b>. </span></li>
<li class="skipspace"><span>Select the new <samp class="codeph">any</samp> element.</span></li>
<li class="skipspace"><span>In the Properties view of the schema editor, for a <b>namespace</b> value,
you can select <b>##any</b> (this allows any well-formed XML from any namespace), <b>##local </b> (this
@@ -47,20 +46,21 @@
allows any well-formed XML that is not from the target namespace of the type
being defined) or <b>##targetNamespace </b> (which is shorthand for the target
namespace of the type being defined). </span></li>
-<li class="skipspace"><span>For a <span class="uicontrol">processContents</span> value, you can select <b>skip</b> (the
-XML processor will not validate the attribute content at all), <b>lax</b>(the
-XML processor will validate the attribute content as much as it can), or <b>strict </b> (the
-XML processor will validate all the attribute content).</span></li>
-<li class="skipspace"><span>The <span class="uicontrol">minOccurs</span> value is the number of times
-the <samp class="codeph">any</samp> element must appear. You can select <span class="uicontrol">0</span> if
-you want the element to be optional; otherwise, select <span class="uicontrol">1</span>. </span></li>
-<li class="skipspace"><span>The <span class="uicontrol">maxOccurs</span>value is the maximum number
+<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 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
+can select <span class="uicontrol">0</span> if you want the element to be optional;
+otherwise, select <span class="uicontrol">1</span>. </span></li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">maxOccurs </span>value</b> is the maximum number
of times an <samp class="codeph">any</samp> element may appear. You can select <span class="uicontrol">0</span>, <span class="uicontrol">1</span>,
or, to indicate there is no maximum number of occurrences, <span class="uicontrol">unbounded</span>.</span></li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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>
+Info</span> page can be used to provide information for applications.</li>
</ol>
<div class="skipspace"><p>(c) Copyright 2001, World Wide Web (Massachusetts Institute of
Technology, Institut National de Recherche en Informatique et en Automatique,
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 df2166c..a17d228 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html
@@ -18,10 +18,13 @@
</head>
<body id="taddcmod"><a name="taddcmod"><!-- --></a>
-<h1 class="topictitle1">Adding a content model</h1>
-<div><p>You can add a content model to an element, global element, a complex
-type, or a group. A content model is the representation of any data that may
-be contained inside the element, global element, complex type, or group.</p><div class="skipspace"><div class="p">There are three different kinds of content models:<ul><li><b>Sequence</b>, which means that all the content model's children can
+<h1 class="topictitle1">Adding content models</h1>
+<div><p>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.</p>
+<div class="section"><div class="p">There are three different kinds of content models:<ul><li><strong>Sequence</strong>, which means that all the content model's children can
appear in an instance of the XML schema. They must, however, appear in the
order they are listed in the content model.</li>
<li><b>Choice</b>, which means that only one of the content model's children
@@ -32,48 +35,50 @@
in the content model may appear more than once</li>
</ul>
</div>
-<p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives. </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 content
-model, to a global element, complex type, or group, follow these steps:</p>
+model to an element, global element, complex type, or group, follow these
+steps:</p>
</div>
-<ol><li class="skipspace"><span>In the Outline view, select your global element, complex type,
-or group:</span><ul><li>If you selected an element or global element, you can right-click
-it and click <span class="uicontrol">Add Sequence</span>, <span class="uicontrol">Add Choice</span>,
-or <span class="uicontrol">Add All</span> to add the type of content model you want
+<ol><li class="stepexpand"><span>In the Outline view, select your element, global element, complex
+type, or group:</span><ul><li>If you selected an element or global element, you can right-click
+it, and click <span class="uicontrol">Add Sequence</span>, <span class="uicontrol">Add Choice</span>,
+or <b> <span class="uicontrol">Add All</span></b> to add the type of content model you want
to your element or global element. Your content model is automatically added
as a child of a local complex type - expand your element or global element
in the Outline view to see it.</li>
-<li>If you selected a complex type, you can right-click it and click <span class="uicontrol">Add
-Sequence</span>, <span class="uicontrol">Add Choice</span>, or <span class="uicontrol">Add
-All</span> to add the type of content model you want to your complex
+<li>If you selected a complex type, you can right-click it and click <b> <span class="uicontrol">Add
+Sequence</span></b>, <b> <span class="uicontrol">Add Choice</span></b>, or <b> <span class="uicontrol">Add
+All</span></b> to add the type of content model you want to your complex
type. Your content model is automatically added as a child of your complex
-type - expand in the Outline view to see it. <b>Note:</b>These
+type - expand in the Outline view to see it. <b>Note: </b>These
options will not appear if you have set a base type for your complex type.
You can either set a base type for your complex type, or you add a content
model to it, but you cannot do both.</li>
<li>Your group is automatically created with a sequence content model
child. Expand it in the Outline view to see it and select it. In the Properties
-view, you can select to change it to a <span class="uicontrol">choice</span> or <span class="uicontrol">all</span> content
-model by selecting these options from the <span class="uicontrol">Kind</span> drop
+view, you can select to change it to a <b> <span class="uicontrol">choice</span></b> or
+<b> <span class="uicontrol">all</span></b> content
+model by selecting these options from the <b> <span class="uicontrol">Kind</span></b> drop
down list.</li>
</ul>
</li>
-<li class="skipspace"><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>
-<li class="skipspace"><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 may appear. You
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b> <span class="uicontrol">MinOccurs</span></b> field.</span> This is the number of times the content model must appear. If you want
+the content model to be optional, select <b> <span class="uicontrol">0</span></b>. Otherwise,
+select <b> <span class="uicontrol">1</span></b>. </li>
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b> <span class="uicontrol">MaxOccurs</span></b> field.</span> This is the maximum number of times a content model may appear. You
can select <span class="uicontrol">unbounded</span> to indicate there is no maximum
number of occurrences.</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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. </li>
+Info</span> page can be used to provide information for applications.</li>
</ol>
<div class="skipspace"><p>You can add the following to a content object model. </p>
<ul><li>Another content model.</li>
<li>A group reference which enables the referenced group to appear in the
-instance document in the context of the referencing declaration. This
+instance document in the context of the referencing declaration. This
menu option only appears if there are global groups defined elsewhere in the
document or if groups are defined in included schemas.</li>
<li>An element, fundamental building blocks in XML.</li>
@@ -85,5 +90,11 @@
</ul>
</div>
</div>
-</body>
+<div><div class="reltasks"><strong>Related tasks</strong><br />
+<div><a href="../topics/taddanye.html" title="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.">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, 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.">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 5a5d833..a8fc3a2 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html
@@ -18,109 +18,120 @@
</head>
<body id="taddcmxt"><a name="taddcmxt"><!-- --></a>
-<h1 class="topictitle1">Adding a complex type</h1>
-<div><p>A complex type allows elements in its content and may carry attributes.
-You can add as many complex types as you want to an XML schema.</p><div class="skipspace"><p></p>
-<p>The following instructions were written for the Resource
-perspective, but they will also work in many other perspectives. </p>
+<h1 class="topictitle1">Adding complex types</h1>
+<div><p>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.</p>
+<div class="section"><p>You can add as many complex types as you want to an XML schema.</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 complex type to an XML schema, follow these steps:</p>
</div>
<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
<li class="skipspace"><span>In the Outline view, select your schema.</span></li>
<li class="skipspace"><span>In the Graph view, right click in the <b>Types</b> section and
-click <span class="uicontrol">Add Complex Type</span>.</span></li>
+click <b> <span class="uicontrol">Add Complex Type</span></b>.</span></li>
<li class="skipspace"><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="skipspace"><span>Click the <span class="uicontrol">More</span> button to select a base type
+the <b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> to select a base type
for your complex type.</span> You can either set a base type for your
complex type, or you add a content model to it (which represents any data
that may be contained inside an element), but you cannot do both. For more
information about content models, refer to the related tasks.</li>
-<li class="skipspace"><span>Select <span class="uicontrol">restriction</span> or <span class="uicontrol">extension</span> from
-the <span class="uicontrol">Derived by</span> drop down list.</span></li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Other</span> tab.</span> The following
-optional values can be specified in this page:<ol type="a"><li class="skipspace"><span>Select the appropriate value in the <span class="uicontrol">abstract</span> list.</span> When a complex type is declared abstract, it cannot be used in an instance
+<li class="stepexpand"><span>Select <span class="uicontrol">restriction</span> or <span class="uicontrol">extension</span> from
+the <span class="uicontrol">Derived by</span> list.</span> This specifies whether
+your type is derived from its base type by restriction or extension.</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Other</span></b> tab.</span> The following
+optional values can be specified in this page:<ol type="a"><li class="skipspace"><span>Select the appropriate value in the
+ <b> <span class="uicontrol">abstract</span></b> list.</span> When a complex type is declared abstract, it cannot be used in an instance
document. Click <b>true</b> if you want the complex type to be abstract; otherwise,
click <b>false</b>.</li>
-<li class="skipspace"><span>Select the appropriate value in the <span class="uicontrol">block</span> list.</span> If you select <b>#all</b>, the complex type may not be replaced by any
+<li class="skipspace"><span>Select the appropriate value in the <b> <span class="uicontrol">block</span></b> list.</span> If you select <b>#all</b>, the complex type may not be replaced by any
derivations. If you select <b>extension</b>, the complex type may not be replaced
by any type derived from it by extending it. If you select <b>restriction</b>,
the complex type may not be replaced by any type derived from it by restricting
it.</li>
-<li class="skipspace"><span> Select the appropriate value in the <span class="uicontrol">final</span> list.</span> If you select <b>#all</b>, the complex type may not be derived from
+<li class="skipspace"><span> Select the appropriate value in the <b> <span class="uicontrol">final</span></b> list.</span> If you select <b>#all</b>, the complex type may not be derived from
at all. If you select <b>extension</b>, the complex type may not be derived
from by extension. If you select <b>restriction</b>, the complex type may
not be derived from by restriction.</li>
-<li class="skipspace"><span>Select the appropriate value in the <span class="uicontrol">mixed</span> list.</span> If you click <b>true</b>, the complex type can contain mixed content
+<li class="skipspace"><span>Select the appropriate value in the <b> <span class="uicontrol">mixed</span></b> list.</span> If you click <b>true</b>, the complex type can contain mixed content
(both character data and other elements). If you click <b>false</b>, the complex
type can only contain other elements.</li>
</ol>
</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Attributes</span> tab</span> You
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Attributes</span></b> tab.</span> You
can use this page to add attributes, attribute references, attributes group
references, and <samp class="codeph">any</samp> attributes to your complex type.</li>
<li class="skipspace"><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<ul><li><span class="uicontrol">fixed/default</span>. Click the <span class="uicontrol">More</span> button
-and select the <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> radio
+and value. To add an attribute, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute</span></b>.</span> You can specify the following values for
+an attribute<ul><li><b><span class="uicontrol">fixed/default</span></b>. Click the
+ <b> <span class="uicontrol">More</span></b> button <span>
+ <img border="0" src="../images/More.gif" width="22" height="18"></span>
+and select the <b> <span class="uicontrol">Fixed</span></b> or <b> <span class="uicontrol">Default</span></b> radio
button and specify an appropriate value. If you select <b>Fixed</b>, the attribute
has a fixed value, which cannot be changed. If you select <b>Default</b>,
-the attribute has a default value.</li>
-<li><span class="uicontrol">form</span>. Use this field to indicate if the appearance
+the attribute has a default value. When an attribute has a default value,
+the value of the attribute is whatever value appears as the attribute's value
+in an instance document.</li>
+<li><b><span class="uicontrol">form</span></b>. Use this field to indicate if the appearance
of this attribute in an instance of the XML schema must be qualified by a
namespace.</li>
-<li><span class="uicontrol">name</span>Enter the name of the attribute.</li>
-<li><span class="uicontrol">type</span>Click the <span class="uicontrol">More</span> button
+<li><span class="uicontrol"><b>name</b>. </span>Enter the name of the attribute.</li>
+<li><span class="uicontrol"><b>type</b>. </span>Click the <b> <span class="uicontrol">More</span></b> button <span>
+<img border="0" src="../images/More.gif" width="22" height="18"></span>
and select the type of the attribute. </li>
-<li><span class="uicontrol">use</span>This field indicates how an attribute may
+<li><span class="uicontrol"><b>use</b>. </span>This field indicates how an attribute may
be used in an instance document. If you select <b>optional</b>, the attribute
may appear once, but it does not have to. If you select <b>required</b>, the
attribute must appear once. If you select <b>prohibited</b>, the attribute
-must not appear. <b>Note</b>: If you selected the <span class="uicontrol">Default</span> radio
+must not appear. <b>Note</b>: If you selected the <b> <span class="uicontrol">Default</span></b> radio
button, you must select <b>optional</b> in this field, otherwise the default
value will not be valid.</li>
</ul>
</li>
<li class="skipspace"><span>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, right-click in the Attributes page, and click <span class="uicontrol">Add
-Attribute Ref</span></span> A declaration that references a global
+To add an attribute reference, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute Ref</span>.</b> </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. The menu option to add
+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> drop down list.</span></li>
+it to reference from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
</ol>
</li>
<li class="skipspace"><span>An attribute group reference provides a reference to an attribute
group. To add an attribute group reference, right-click in the Attributes
-page, and click <span class="uicontrol">Add Attribute Group Ref</span></span> A
+page, and click <b> <span class="uicontrol">Add Attribute Group Ref. </span></b></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. 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> drop down list.</span></li>
+it to reference from the<span class="uicontrol"> <b>ref</b></span> drop down list.</span></li>
</ol>
</li>
-<li class="skipspace"><span>An <samp class="codeph">any</samp> element enables attributes to appear
-in <samp class="codeph">any</samp> elements. To add an <samp class="codeph">any</samp> attribute,
-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 <b>namespace</b> value, you can select <b>##any</b> (this allows
+<li class="skipspace"><span>An <samp class="codeph">any</samp> element enables element content according
+to namespaces, and the corresponding <samp class="codeph">any</samp> attribute
+element enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute,
+right-click in the Attributes page, and click <b> <span class="uicontrol">Add Any Attribute</span></b>.</span> You can specify the following values for an <samp class="codeph">any</samp> attribute:<ul><li>For a <b>namespace</b> value, you can select <b>##any</b> (this allows
any well-formed XML from any namespace), <b>##local </b> (this allows any
well-formed XML that is not declared to be in a namespace, <b>##other </b> (this
allows any well-formed XML that is not from the target namespace of the type
being defined) or <b>##targetNamespace </b> (which is shorthand for the target
namespace of the type being defined). </li>
-<li>For a <span class="uicontrol">processContents</span> value, you can select <b>skip</b> (the
-XML processor will not validate the attribute content at all), <b>lax</b>(the
+<li>For a <b> <span class="uicontrol">processContents</span></b> value, you can select <b>skip</b> (the
+XML processor will not validate the attribute content at all), <b>lax </b>(the
XML processor will validate the attribute content as much as it can), or <b>strict </b> (the
XML processor will validate all the attribute content).</li>
</ul>
</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
-to provide any information about this complext type.</span> The <span class="uicontrol">Documentation</span> page
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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>
+Info</span> page can be used to provide information for applications.</li>
</ol>
</div>
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 ba6e968..55d2288 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html
@@ -14,70 +14,99 @@
* IBM Corporation - initial API and implementation
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-<title>Adding an element</title>
+<title>Adding elements</title>
</head>
<body id="taddelm"><a name="taddelm"><!-- --></a>
-<h1 class="topictitle1">Adding an element</h1>
-<div><p>Elements are fundamental building blocks in XML - they consist
-of a start-tag, and end-tag, and any text that is contained between the two.</p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives. </p>
+<h1 class="topictitle1">Adding elements</h1>
+<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><div class="skipspace"><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>
</div>
-<ol><li class="skipspace"><span>In the Outline view, right-click the content model you want to
-work with and click <span class="uicontrol">Add Element</span>.</span></li>
-<li class="skipspace"><span>In the Properties view, type a new name for the element in the <span class="uicontrol">Name</span> field.</span></li>
-<li class="skipspace"><span>Specify its type information by clicking the <span class="uicontrol">More</span> button
-and selecting the appropriate type.</span> An element type can reference
-a complex type or a simple type. An element or attribute can define its type
-to be anonymous. You do not have to name an anonymous type since an anonymous
-type cannot be referenced directly. To specify that a global element's type
-is anonymous, when the <span class="uicontrol">User-defined simple type</span> or <span class="uicontrol">User-defined
-complex type</span> radio button is selected ,click <span class="uicontrol">**anonymous**</span> in
-the type list. </li>
-<li class="skipspace"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MinOccurs</span> field.</span> This is the number of times the element may appear. If you want the
-element to be optional, select <span class="uicontrol">0</span>. Otherwise, select <span class="uicontrol">1</span>. </li>
-<li class="skipspace"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MaxOccurs</span> field.</span> This is the maximum number of times the element may appear. You can
-select <span class="uicontrol">unbounded</span> to indicate there is no maximum number
+<ol><li class="skipspace"><span>In the Outline view, right-click the content
+ model you want to
+work with and click <b> <span class="uicontrol">Add Element</span></b>.</span></li>
+<li class="skipspace"><span>In the Properties view, type a new name for the element in the
+<b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="skipspace"><span>Specify its type information by clicking the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> and selecting the appropriate type.</span>
+The Set Type dialog lists all built-in and user-defined types currently
+available. You can change the <b><span class="uicontrol">Scope</span></b> of the
+list by selecting one of the following options:
+<div>
+ <ul>
+ <li><b><span class="uicontrol">Workspace</span></b>. Lists all of the
+ types available in your workspace. </li>
+ <li><b><span class="uicontrol">Enclosing Project</span></b>. Lists all
+ of the types available in the project that contains your file. </li>
+ <li>(Default) <b><span class="uicontrol">Current Resource</span>. </b>
+ List all of the types available in your current file. </li>
+ </ul>
+</div>
+ </li>
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b>
+<span class="uicontrol">MinOccurs</span></b> field.</span> This is the number of times the element may appear. If you want the
+element to be optional, select <b><span class="uicontrol">0</span></b>. Otherwise, select
+<b><span class="uicontrol">1</span></b>. </li>
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b> <span class="uicontrol">MaxOccurs</span></b> field.</span> This is the maximum number of times the element may appear. You can
+select <b> <span class="uicontrol">unbounded</span></b> to indicate there is no maximum number
of occurrences.</li>
-<li class="skipspace"><span>(Optional) Click the <span class="uicontrol">Other</span> tab. </span> In this page, you can specify various values for the element, such as
-, <span class="uicontrol">block</span>, <span class="uicontrol">fixed/default</span>,<span class="uicontrol">form</span>and <span class="uicontrol">nillable</span>.</li>
-<li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
-<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
-schema and its contents should be displayed in the Graph view.</li>
-<li class="skipspace"><span>In the Graph view, right click in the <b>Elements</b> section and
-click <span class="uicontrol">Add Element</span>.</span></li>
-<li class="skipspace"><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="skipspace"><span>Specify its type information by clicking the <span class="uicontrol">More</span> button
-and selecting the appropriate type.</span> An element type can reference
-a complex type or a simple type. An element or attribute can define its type
-to be anonymous. You do not have to name an anonymous type since an anonymous
-type cannot be referenced directly. To specify that a global element's type
-is anonymous, when the <span class="uicontrol">User-defined simple type</span> or <span class="uicontrol">User-defined
-complex type</span> radio button is selected ,click <span class="uicontrol">**anonymous**</span> in
-the type list. </li>
-<li class="skipspace"><span>(Optional) Click the <span class="uicontrol">Other</span> tab. </span> In this page, you can specify various values for the global element,
-such as <span class="uicontrol">abstract</span>, <span class="uicontrol">block</span>, <span class="uicontrol">final</span>, <span class="uicontrol">fixed/default</span>, <span class="uicontrol">nillable</span>, and <span class="uicontrol">substituionGroup</span>.</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Attributes</span> tab</span> You
+<li class="skipspace">
+<div>
+ (Optional) Click the <b><span class="uicontrol">Other</span></b> tab. In
+ this page, you can specify the following various values for the element:
+ <ul>
+ <li><b><span class="uicontrol">block</span></b>. This field determines
+ whether the element may be replaced by an element derived from it. </li>
+ <li><b><span class="uicontrol">fixed/default</span>.</b> Click the <b>
+ <span class="uicontrol">More</span></b> button
+ <img border="0" src="../images/More.gif" width="22" height="18"> and
+ select the <b><span class="uicontrol">Fixed</span></b> or <b>
+ <span class="uicontrol">Default</span></b> radio button and specify an
+ appropriate value. If you select <strong>Fixed</strong>, the element has
+ a fixed value, which cannot be changed. If you select <strong>Default</strong>,
+ the element has a default value. </li>
+ <li><b><span class="uicontrol">form</span></b>. Use this field to
+ indicate if the appearance of this 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>
+ <li><b><span class="uicontrol">maxOccurs</span></b>. This is the minimum
+ number of times the element can appear in an instance document. You can
+ specify this option here or in the General page. </li>
+ <li><b><span class="uicontrol">minOccurs</span></b>. This is the maximum
+ number of times the element can appear in an instance document. You can
+ specify this option here or in the General page. </li>
+ <li><b><span class="uicontrol">nillable</span></b>. Select <strong>true</strong>
+ if you do not want the element to be able to have any child elements,
+ only attributes. </li>
+ </ul>
+</div>
+ </li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Attributes</span></b> 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>
+references, and <samp class="codeph">any</samp> attributes to your element.</li>
<li class="skipspace"><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<ul><li><span class="uicontrol">fixed/default</span>.Click the <span class="uicontrol">More</span> button
-and select the <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> radio
+and value. To add an attribute, right-click in the Attributes page, and click<b> <span class="uicontrol">Add
+Attribute</span>.</b></span> You can specify the following values for
+an attribute<ul><li><b><span class="uicontrol">fixed/default</span>.</b> Click the
+ <b> <span class="uicontrol">More</span></b> button
+ <img border="0" src="../images/More.gif" width="22" height="18"> and select the
+ <b> <span class="uicontrol">Fixed</span></b> or <b> <span class="uicontrol">Default</span></b> radio
button and specify an appropriate value. If you select <b>Fixed</b>, the attribute
has a fixed value, which cannot be changed. If you select <b>Default</b>,
the attribute has a default value.</li>
-<li><span class="uicontrol">form</span>. Use this field to indicate if the appearance
+<li><b><span class="uicontrol">form</span></b>. Use this field to indicate if the appearance
of this attribute in an instance of the XML schema must be qualified by a
namespace.</li>
-<li><span class="uicontrol">name</span>. Enter the name of the attribute.</li>
-<li><span class="uicontrol">type</span>. Click the <span class="uicontrol">More</span> button
-and select the type of the attribute. </li>
-<li><span class="uicontrol">use</span>. This field indicates how an attribute
+<li><b><span class="uicontrol">name</span></b>. Enter the name of the attribute.</li>
+<li><b><span class="uicontrol">type</span></b>. Click the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> and select the type of the attribute. </li>
+<li><b><span class="uicontrol">use</span></b>. This field indicates how an attribute
may be used in an instance document. If you select <b>optional</b>, the attribute
may appear once, but it does not have to. If you select <b>required</b>, the
attribute must appear once. If you select <b>prohibited</b>, the attribute
@@ -87,43 +116,44 @@
</ul>
</li>
<li class="skipspace"><span>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, right-click in the Attributes page, and click <span class="uicontrol">Add
-Attribute Ref</span>.</span> A declaration that references a global
+To add an attribute reference, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute Ref</span></b>.</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. The menu option to add
+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> drop down list.</span></li>
+it to reference from the<span class="uicontrol"> <b>ref</b></span> drop down list.</span></li>
</ol>
</li>
<li class="skipspace"><span>An attribute group reference provides a reference to an attribute
group. To add an attribute group reference, right-click in the Attributes
-page, and click <span class="uicontrol">Add Attribute Group Ref</span>.</span> A
+page, and click <b> <span class="uicontrol">Add Attribute Group Ref</span>.</b></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. 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> drop down list.</span></li>
+it to reference from the<span class="uicontrol"> <b>ref</b></span> drop down list.</span></li>
</ol>
</li>
-<li class="skipspace"><span>An <samp class="codeph">any</samp> element enables attributes to appear
-in <samp class="codeph">any</samp> elements. To add an <samp class="codeph">any</samp> attribute,
-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 <b>namespace</b> value, you can select <b>##any</b> (this allows
+<li class="skipspace"><span>An <samp class="codeph">any</samp> element enables element content according
+to namespaces, and the corresponding <samp class="codeph">any</samp> attribute
+element enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute,
+right-click in the Attributes page and click <b> <span class="uicontrol">Add Any Attribute</span>.</b></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), <b>##local </b> (this allows any
well-formed XML that is not declared to be in a namespace, <b>##other </b> (this
allows any well-formed XML that is not from the target namespace of the type
being defined) or <b>##targetNamespace </b> (which is shorthand for the target
namespace of the type being defined). </li>
-<li>For a <span class="uicontrol">processContents</span> value, you can select <b>skip</b> (the
+<li>For a <b> <span class="uicontrol">processContents</span></b> value, you can select <b>skip</b> (the
XML processor will not validate the attribute content at all), <b>lax</b> (the
XML processor will validate the attribute content as much as it can), or <b>strict </b> (the
XML processor will validate all the attribute content).</li>
</ul>
</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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>
+Info</span> page can be used to provide information for applications.</li>
</ol>
<div class="skipspace">You can add a content model to an element, which is the representation
of any data that may be contained inside the element. For more information
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 886a26e..0893b05 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html
@@ -18,94 +18,124 @@
</head>
<body id="taddelmr"><a name="taddelmr"><!-- --></a>
-<h1 class="topictitle1">Adding an element reference</h1>
-<div><p>An element reference provides a reference to a global element.
-A declaration that references a global element enables the referenced global
+<h1 class="topictitle1">Adding element references</h1>
+<div><p>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. </p><div class="skipspace">The menu option to add an element reference only appears if there
+declaration.</p>
+<div class="section"><p>You can modify the contents of your global element directly via
+an element reference. For example, you can add attributes and attribute reference
+to an element reference, but they are actually being added to your global
+element.</p>
+The menu option to add an element reference only appears if there
are global elements defined elsewhere in the document.<p>The following instructions
were written for the Resource perspective, but they will also work in many
-other perspectives. </p>
+other perspectives.</p>
<p>To add an element reference, follow these
steps:</p>
</div>
<ol><li class="skipspace"><span>In the Outline view, right-click the content model you want to
-work with and click <span class="uicontrol">Add Element Ref</span>.</span></li>
+work with and click <b> <span class="uicontrol">Add Element Ref</span>.</b></span></li>
<li class="skipspace"><span>Select the element reference.</span></li>
<li class="skipspace"><span>In the Properties view, select the global element you want to reference
in the <span class="uicontrol">ref</span> list.</span></li>
-<li class="skipspace"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MinOccurs</span> field.</span> This is the number of times the global element referenced may appear.
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b> <span class="uicontrol">MinOccurs</span></b> field.</span> This is the number of times the global element referenced may appear.
If you want the element to be optional, select <span class="uicontrol">0</span>. Otherwise,
select <span class="uicontrol">1</span>. </li>
-<li class="skipspace"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MaxOccurs</span> field.</span> This is the maximum number of times the global element referenced may
+<li class="skipspace"><span>(Optional) Select the appropriate value in the <b> <span class="uicontrol">MaxOccurs</span></b> field.</span> This is the maximum number of times the global element referenced may
appear. You can select <span class="uicontrol">unbounded</span> to indicate there
is no maximum number of occurrences.</li>
-<li class="skipspace"><span>(Optional) Click the <span class="uicontrol">Other</span> tab. </span> In this page, you can specify various values for thel element reference,
-such as <span class="uicontrol">abstract</span>, <span class="uicontrol">block</span>, <span class="uicontrol">final</span>, <span class="uicontrol">fixed/default</span>, <span class="uicontrol">nillable</span>, and <span class="uicontrol">substituionGroup</span>.</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Attributes</span> tab</span> You
+<li class="stepexpand"><span>(Optional) Click the <b> <span class="uicontrol">Other</span></b> tab.</span> In
+this page, you can specify the following various values for the global element
+you are referencing: <ul><li><b><span class="uicontrol">abstract</span></b>. Click <strong>true </strong>if you want the
+global element to be abstract. When a global element is declared to be abstract,
+it cannot be used in an instance document. Instead, a member of that global
+element's substitution group must appear in the instance document.</li>
+<li><b><span class="uicontrol">block</span></b>. This field determines whether the global
+element may be replaced by an element derived from it.</li>
+<li><b><span class="uicontrol">final</span></b>. This field determines whether this global
+element may be derived from.</li>
+<li><b><span class="uicontrol">fixed/default</span>.</b> Click the <b> <span class="uicontrol">More</span></b> button
+and select the <b> <span class="uicontrol">Fixed</span></b> or <b> <span class="uicontrol">Default</span></b> 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>,
+the element has a default value.</li>
+<li><b><span class="uicontrol">form</span></b>. 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>
+<li><b><span class="uicontrol">nillable</span></b>. Select <strong>true</strong> if you do not
+want the global element to be able to have any child elements, only attributes. </li>
+<li><b><span class="uicontrol">substitutionGroup</span></b>. A substitution group allows
+elements to be substituted for other elements.</li>
+</ul>
+</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Attributes</span></b> tab.</span> You
can use this page to add attributes, attribute references, attributes group
references, and <samp class="codeph">any</samp> attributes to your element reference.</li>
<li class="skipspace"><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<ul><li><span class="uicontrol">fixed/default</span>. Click the <span class="uicontrol">More</span> button
-and select the <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> radio
+and value. To add an attribute, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute</span></b>.</span> You can specify the following values for
+an attribute<ul><li><b><span class="uicontrol">fixed/default</span>.</b> Click the
+ <b> <span class="uicontrol">More</span></b> button
+ <img border="0" src="../images/More.gif" width="22" height="18"> and select the
+ <b> <span class="uicontrol">Fixed</span></b> or <b> <span class="uicontrol">Default</span></b> radio
button and specify an appropriate value. If you select <b>Fixed</b>, the attribute
has a fixed value, which cannot be changed. If you select <b>Default</b>,
the attribute has a default value.</li>
-<li><span class="uicontrol">form</span>. Use this field to indicate if the appearance
+<li><b><span class="uicontrol">form</span></b>. Use this field to indicate if the appearance
of this attribute in an instance of the XML schema must be qualified by a
namespace.</li>
-<li><span class="uicontrol">name</span>. Enter the name of the attribute.</li>
-<li><span class="uicontrol">type</span>. Click the <span class="uicontrol">More</span> button
+<li><b><span class="uicontrol">name</span></b>. Enter the name of the attribute.</li>
+<li><b><span class="uicontrol">type</span></b>. Click the <span class="uicontrol">More</span> button
and select the type of the attribute. </li>
-<li><span class="uicontrol">use</span>. This field indicates how an attribute
+<li><b><span class="uicontrol">use</span></b>. This field indicates how an attribute
may be used in an instance document. If you select <b>optional</b>, the attribute
may appear once, but it does not have to. If you select <b>required</b>, the
attribute must appear once. If you select <b>prohibited</b>, the attribute
-must not appear. <b>Note</b>: If you selected the <span class="uicontrol">Default</span> radio
+must not appear. <b>Note</b>: If you selected the <b> <span class="uicontrol">Default</span></b> radio
button, you must select <b>optional</b> in this field, otherwise the default
value will not be valid.</li>
</ul>
</li>
<li class="skipspace"><span>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, right-click in the Attributes page, and click <span class="uicontrol">Add
-Attribute Ref</span>.</span> A declaration that references a global
+To add an attribute reference, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute Ref</span>.</b></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. The menu option to add
+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> drop down list.</span></li>
+it to reference from the <b> <span class="uicontrol">ref</span> </b>drop down list.</span></li>
</ol>
</li>
<li class="skipspace"><span>An attribute group reference provides a reference to an attribute
group. To add an attribute group reference, right-click in the Attributes
-page, and click <span class="uicontrol">Add Attribute Group Ref</span>.</span> A
+page, and click <b> <span class="uicontrol">Add Attribute Group Ref</span></b>.</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. 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> drop down list.</span></li>
+it to reference from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
</ol>
</li>
-<li class="skipspace"><span>An <samp class="codeph">any</samp> element enables attributes to appear
-in <samp class="codeph">any</samp> elements. To add an <samp class="codeph">any</samp> attribute,
-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 <b>namespace</b> value, you can select <b>##any</b> (this allows
+<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
+enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute,
+right-click in the Attributes page and click<b> <span class="uicontrol">Add Any Attribute</span>.</b></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), <b>##local </b> (this allows any
well-formed XML that is not declared to be in a namespace, <b>##other </b> (this
allows any well-formed XML that is not from the target namespace of the type
being defined) or <b>##targetNamespace </b> (which is shorthand for the target
namespace of the type being defined). </li>
-<li>For a <span class="uicontrol">processContents</span> value, you can select <b>skip</b> (the
-XML processor will not validate the attribute content at all), <b>lax</b>(the
+<li>For a <b> <span class="uicontrol">processContents</span></b> value, you can select <b>skip</b> (the
+XML processor will not validate the attribute content at all), <b>lax </b>(the
XML processor will validate the attribute content as much as it can), or <b>strict </b> (the
XML processor will validate all the attribute content).</li>
</ul>
</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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>
+material, such as a description, and the <span class="uicontrol">App Info</span>
+page can be used to provide information for applications.</li>
</ol>
</div>
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 dd0a9dc..fcb254c 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html
@@ -18,11 +18,12 @@
</head>
<body id="taddglba"><a name="taddglba"><!-- --></a>
-<h1 class="topictitle1">Adding a global attribute</h1>
-<div><p>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. </p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives. </p>
+<h1 class="topictitle1">Adding global attributes</h1>
+<div><p>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.</p><div class="skipspace"><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>
</div>
@@ -30,19 +31,25 @@
<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
schema and its contents should be displayed in the Graph view.</li>
<li class="skipspace"><span>In the Graph view, right click in the <b>Attributes</b> section
-and click <span class="uicontrol">Add Global Attribute</span>.</span></li>
-<li class="skipspace"><span>In the Properties view, type the attribute <span class="uicontrol">Name</span>.</span> </li>
-<li class="skipspace"><span>Click the <b>More</b> button next to the <span class="uicontrol">Type</span> field
-to launch the Available Types dialog.</span></li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Built-in simple type</span> or <span class="uicontrol">User-defined
-simple type</span> radio button, select the type you want in the type
-list, then click <span class="uicontrol">OK</span>. </span> If you want to create
-a local simple type, select the <span class="uicontrol">User-defined simple type</span> radio
-button, and select <span class="uicontrol">**anonymous**</span>.</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+and click <b> <span class="uicontrol">Add Global Attribute</span>.</b></span></li>
+<li class="skipspace"><span>In the Properties view, type the attribute <b> <span class="uicontrol">Name</span></b>.</span> </li>
+<li class="skipspace"><span>Click the <b>More</b> button next to the <b> <span class="uicontrol">Type</span></b> field
+to launch the Set Types dialog.</span></li>
+<li class="skipspace"><span>Select the type you want in the type
+list, then click <b> <span class="uicontrol">OK</span></b>. </span>The Set Type dialog lists all built-in and user-defined types currently
+available. You can change the <b> <span class="uicontrol">Scope</span></b> of the list by
+selecting one of the following options:<ul><li><b><span class="uicontrol">Workspace</span></b>. Lists all of the types available in
+your workspace. </li>
+<li><b><span class="uicontrol">Enclosing Project</span>.</b> Lists all of the types available
+in the project that contains your file. </li>
+<li>(Default) <b> <span class="uicontrol">Current Resource</span>.</b> List all of the types
+available in your current file.</li>
+</ul>
+ </li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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>
+material, such as a description, and the <span class="uicontrol">App Info</span>
+page can be used to provide information for applications.</li>
</ol>
</div>
</body>
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 05896a5..d87d4e2 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html
@@ -18,11 +18,12 @@
</head>
<body id="taddglem"><a name="taddglem"><!-- --></a>
-<h1 class="topictitle1">Adding a global element</h1>
-<div><p>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 complex
-type definition.</p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives. </p>
+<h1 class="topictitle1">Adding global elements</h1>
+<div><p>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.</p><div class="skipspace"><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>
</div>
@@ -30,37 +31,74 @@
<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
schema and its contents should be displayed in the Graph view.</li>
<li class="skipspace"><span>In the Graph view, right click in the <b>Elements</b> section and
-click <span class="uicontrol">Add Element</span>.</span></li>
-<li class="skipspace"><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="skipspace"><span>Specify its type information by clicking the <span class="uicontrol">More</span> button
-and selecting the appropriate type.</span> An element type can reference
-a complex type or a simple type. An element or attribute can define its type
-to be anonymous. You do not have to name an anonymous type since an anonymous
-type cannot be referenced directly. To specify that a global element's type
-is anonymous, when the <span class="uicontrol">User-defined simple type</span> or <span class="uicontrol">User-defined
-complex type</span> radio button is selected ,click <span class="uicontrol">**anonymous**</span> in
-the type list. </li>
-<li class="skipspace"><span>(Optional) Click the <span class="uicontrol">Other</span> tab. </span> In this page, you can specify various values for the global element,
-such as <span class="uicontrol">abstract</span>, <span class="uicontrol">block</span>, <span class="uicontrol">final</span>, <span class="uicontrol">fixed/default</span>, <span class="uicontrol">nillable</span>, and <span class="uicontrol">substituionGroup</span>.</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Attributes</span> tab</span> You
+click <b> <span class="uicontrol">Add Element</span></b>.</span></li>
+<li class="skipspace"><span>In the Properties view, click the <b> <span class="uicontrol">General</span></b> tab,
+and type a new name for the global element in the <b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="skipspace"><span>Specify its type information by clicking the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> and selecting the appropriate type.</span> The Set Type dialog lists all
+built-in and user-defined types currently available. You can change the <b> <span class="uicontrol">Scope</span></b> of
+the list by selecting one of the following options:<ul><li><b><span class="uicontrol">Workspace</span></b>. Lists all of the types available in
+your workspace. </li>
+<li><b><span class="uicontrol">Enclosing Project</span>.</b> Lists all of the types available
+in the project that contains your file. </li>
+<li>(Default) <b> <span class="uicontrol">Current Resource</span>.</b> List all of the types
+available in your current file.</li>
+</ul>
+ </li>
+<li class="skipspace">
+<div>
+ (Optional) Click the <b><span class="uicontrol">Other</span></b> tab. In
+ this page, you can specify the following various values for the global
+ element:
+ <ul>
+ <li><b><span class="uicontrol">abstract</span></b>. Click <strong>true
+ </strong>if you want the global element to be abstract. When a global
+ element is declared to be abstract, it cannot be used in an instance
+ document. Instead, a member of that global element's substitution group
+ must appear in the instance document. </li>
+ <li><b><span class="uicontrol">block</span></b>. This field determines
+ whether the global element may be replaced by an element derived from
+ it. </li>
+ <li><b><span class="uicontrol">final</span></b>. This field determines
+ whether this global element may be derived from. </li>
+ <li><b><span class="uicontrol">fixed/default</span>.</b> Click the <b>
+ <span class="uicontrol">More</span></b> button
+ <img border="0" src="../images/More.gif" width="22" height="18"> and
+ select the <b><span class="uicontrol">Fixed</span></b> or <b>
+ <span class="uicontrol">Default</span></b> 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>, the element has a default value. </li>
+ <li><b><span class="uicontrol">form</span></b>. 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>
+ <li><b><span class="uicontrol">nillable</span></b>. Select <strong>true</strong>
+ if you do not want the global element to be able to have any child
+ elements, only attributes. </li>
+ <li><b><span class="uicontrol">substitutionGroup</span></b>. A
+ substitution group allows elements to be substituted for other elements.</li>
+ </ul>
+</div>
+ </li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Attributes</span></b> 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>
<li class="skipspace"><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<ul><li><span class="uicontrol">fixed/default</span>. Click the <span class="uicontrol">More</span> button
-and select the <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> radio
+an attribute<ul><li><b><span class="uicontrol">fixed/default</span></b>. Click the <span class="uicontrol">More</span> button
+and select the <b> <span class="uicontrol">Fixed</span></b> or <b> <span class="uicontrol">Default</span></b> radio
button and specify an appropriate value. If you select <b>Fixed</b>, the attribute
has a fixed value, which cannot be changed. If you select <b>Default</b>,
the attribute has a default value.</li>
-<li><span class="uicontrol">form</span>. Use this field to indicate if the appearance
+<li><b><span class="uicontrol">form</span></b>. Use this field to indicate if the appearance
of this attribute in an instance of the XML schema must be qualified by a
namespace.</li>
-<li><span class="uicontrol">name</span>. Enter the name of the attribute.</li>
-<li><span class="uicontrol">type</span>. Click the <span class="uicontrol">More</span> button
-and select the type of the attribute. </li>
-<li><span class="uicontrol">use</span>. This field indicates how an attribute
+<li><b><span class="uicontrol">name</span></b>. Enter the name of the attribute.</li>
+<li><b><span class="uicontrol">type</span></b>. Click the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> and select the type of the attribute. </li>
+<li><b><span class="uicontrol">use</span></b>. This field indicates how an attribute
may be used in an instance document. If you select <b>optional</b>, the attribute
may appear once, but it does not have to. If you select <b>required</b>, the
attribute must appear once. If you select <b>prohibited</b>, the attribute
@@ -70,28 +108,29 @@
</ul>
</li>
<li class="skipspace"><span>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, right-click in the Attributes page, and click <span class="uicontrol">Add
-Attribute Ref</span>.</span> A declaration that references a global
+To add an attribute reference, right-click in the Attributes page, and click <b> <span class="uicontrol">Add
+Attribute Ref</span>.</b></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. The menu option to add
+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> drop down list.</span></li>
+it to reference from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
</ol>
</li>
<li class="skipspace"><span>An attribute group reference provides a reference to an attribute
group. To add an attribute group reference, right-click in the Attributes
-page, and click <span class="uicontrol">Add Attribute Group Ref</span>.</span> A
+page, and click <b> <span class="uicontrol">Add Attribute Group Ref</span></b>.</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. 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> drop down list.</span></li>
+it to reference from the <b> <span class="uicontrol">ref</span></b> drop down list.</span></li>
</ol>
</li>
-<li class="skipspace"><span>An <samp class="codeph">any</samp> element enables attributes to appear
-in <samp class="codeph">any</samp> elements. To add an <samp class="codeph">any</samp> attribute,
-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 <b>namespace</b> value, you can select <b>##any</b> (this allows
+<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
+enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute,
+right-click in the Attributes page and click <b> <span class="uicontrol">Add Any Attribute</span></b>.</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), <b>##local </b> (this allows any
well-formed XML that is not declared to be in a namespace, <b>##other </b> (this
allows any well-formed XML that is not from the target namespace of the type
@@ -103,10 +142,10 @@
XML processor will validate all the attribute content).</li>
</ul>
</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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>
+Info</span> page can be used to provide information for applications.</li>
</ol>
<div class="skipspace">You can add a content model to a global element, which is the representation
of any data that may be contained inside the global element. For more information
@@ -115,7 +154,7 @@
<div><p><b class="reltaskshd">Related tasks</b><br />
<a href="../topics/taddcmod.html" title="You can add a content model to an element, global element, a complex type, or a group. A content model is the representation of any data that may be contained inside the element, global element, complex type, or group.">Adding a content model</a><br />
-<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 an element reference</a><br />
+<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 an element reference</a><br />
</p>
</div>
</body>
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 4538784..d68bd69 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html
@@ -18,24 +18,24 @@
</head>
<body id="taddgrpr"><a name="taddgrpr"><!-- --></a>
-<h1 class="topictitle1">Adding a group reference</h1>
-<div><p>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. </p><div class="skipspace">The menu option to add a group reference only appears if there are
-groups defined elsewhere in the document.<p>The following instructions were
-written for the Resource perspective, but they will also work in many other
-perspectives. </p>
+<h1 class="topictitle1">Adding group references</h1>
+<div><p>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.</p><div class="skipspace">The menu option to add a group reference only appears if there are
+groups defined elsewhere in the document.<p>The following instructions were
+ written for the Resource perspective, but they will also work in many
+ other perspectives.</p>
<p>To add a group reference, follow these steps:</p>
</div>
<ol><li class="skipspace"><span>In the Outline view, right-click the content model you want to
-work with and select <span class="uicontrol">Add Group Ref</span>.</span></li>
+work with and select <b> <span class="uicontrol">Add Group Ref</span></b>.</span></li>
<li class="skipspace"><span>Select the new group reference.</span></li>
<li class="skipspace"><span>In the Properties view, select the group you want to refer to in
-the <span class="uicontrol">ref</span> list.</span></li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+the <b> <span class="uicontrol">ref</span></b> list.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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. </li>
+Info</span> page can be used to provide information for applications.</li>
</ol>
</div>
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 fab83e2..d9809bd 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html
@@ -18,12 +18,13 @@
</head>
<body id="taddgrup"><a name="taddgrup"><!-- --></a>
-<h1 class="topictitle1">Adding a group</h1>
-<div><p>A group consists of element declarations, wildcards, and other
-content model groups. When you create a group, it automatically contains a
-content model.</p><div class="skipspace"><p></p>
-<p>The following instructions were written for the Resource
-perspective, but they will also work in many other perspectives. </p>
+<h1 class="topictitle1">Adding groups</h1>
+<div><p>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.</p>
+<div class="section"><p></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 group, follow these steps:</p>
</div>
@@ -31,13 +32,14 @@
<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
schema and its contents should be displayed in the Graph view.</li>
<li class="skipspace"><span>In the Graph view, right click in the <b>Groups</b> section and
-click <span class="uicontrol">Add Group</span>.</span></li>
-<li class="skipspace"><span>In the Properties view, type a new name for the group in the <span class="uicontrol">Name</span> field.</span></li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+click <span class="uicontrol"><b>Add Group</b>.</span></span></li>
+<li class="skipspace"><span>In the Properties view, type a new name for the group in the
+<b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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>
-<li class="skipspace"><span>In the Outline view, expand the <span class="uicontrol">Groups</span> folder
+Info</span> page can be used to provide information for applications.</li>
+<li class="skipspace"><span>In the Outline view, expand the <b> <span class="uicontrol">Groups</span></b> folder
and your new group.</span></li>
<li class="skipspace"><span>Your group automatically contains a content model. </span> A
group's content model is the representation of any data that may be contained
@@ -47,7 +49,7 @@
</div>
<div><p><b class="reltaskshd">Related tasks</b><br />
-<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 a group reference</a><br />
+<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 a group reference</a><br />
<a href="../topics/taddcmod.html" title="You can add a content model to an element, global element, a complex type, or a group. A content model is the representation of any data that may be contained inside the element, global element, complex type, or group.">Adding a content model</a><br />
</p>
</div>
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 c50681a..a2c1e54 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html
@@ -14,68 +14,72 @@
* IBM Corporation - initial API and implementation
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-<title>Adding an import element</title>
+<title>Adding import elements</title>
</head>
<body id="taddimpt"><a name="taddimpt"><!-- --></a>
-<h1 class="topictitle1">Adding an import element</h1>
-<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. XML schema defines two constructs to support this: <i>include</i> and <i>import</i>.
-The include element brings in definitions and declarations from the included
-schema into the current schema. It requires the included schema to be in the
-same target namespace as the including schema. The import element behaves
-in a similar way, with the exception that the imported schema can come from
-a different namespace.</p><div class="skipspace"><p>In the XML schema editor, you can add an import element to an
-XML schema. Before you can do this, you must create an XML schema and open
-it in the XML schema editor (you can open an XML schema in the XML schema
-editor by double-clicking it).</p>
-<p>You can add multiple import elements
+<h1 class="topictitle1">Adding import elements</h1>
+<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 an <samp class="codeph">import</samp> element to bring
+in definitions and declarations from an imported schema into the current schema.
+</p>
+<div class="section">
+ The imported schema can come from a different namespace than the current
+ schema does.</div>
+<div class="skipspace">
+ <p>You can add multiple import elements
to an XML schema, however, prefixes and namespaces have to unique amongst
the imported schemas.</p>
-<p>An import element is always added to the top of
-the schema file, as it must appear as the first children of the schema element. </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 import element,
-follow these steps:</p>
-</div>
-<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
-<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
+ <p>The following instructions were written for the Resource perspective, but
+ they will also work in many other perspectives.</p>
+ <p>To add an import element,
+follow these steps:</p></div>
+<ol>
+ <li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
+ <li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
schema and its contents should be displayed in the Graph view.</li>
-<li class="skipspace"><span>In the Graph view, right click in the <b>Directives</b> section
-and click <span class="uicontrol">Add Import</span>.</span></li>
-<li class="skipspace"><span>In the Properties view, click the <b>General</b> tab and click
-the <span class="uicontrol">More</span> button to the right of the <span class="uicontrol">Schema
-location</span> field.</span></li>
-<li class="skipspace"><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><ol type="a"><li><span>Select the schema you want to import and click <span class="uicontrol">Finish</span>.</span></li>
-</ol>
-</li>
-<li class="skipspace"><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><ol type="a"><li class="skipspace"><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.
+ <li class="skipspace"><span>In the Graph view, right click in the <b>Directives</b> section
+and click <b><span class="uicontrol">Add Import</span></b>.</span></li>
+ <li class="skipspace"><span>In the Properties view, click the <b>General</b> tab and click
+the <b><span class="uicontrol">More</span></b> button
+ <img border="0" src="../images/More.gif" width="22" height="18"> to the right of the
+ <b><span class="uicontrol">Schema
+location</span></b> field.</span></li>
+ <li class="skipspace"><span>If you want to import an XML schema located in the workbench, select
+the <b><span class="uicontrol">Workbench projects</span></b> radio button and click
+ <b><span class="uicontrol">Next</span></b>. </span>
+ <ol type="a">
+ <li><span>Select the schema you want to import and click <b>
+ <span class="uicontrol">Finish</span></b>.</span></li>
+ </ol></li>
+ <li class="skipspace"><span>If you want to import an XML schema located on the Web, select
+the <b><span class="uicontrol">HTTP</span></b> radio button and click <b>
+ <span class="uicontrol">Next</span></b>.</span><ol type="a">
+ <li class="skipspace"><span>Type the <b>URL</b> of the XML schema and click
+ <b><span class="uicontrol">Finish</span></b>.</span>
+ <div class="note"><span class="notetitle"><b>Note</b>: </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>
-</li>
+from the URL you specify.</div></li>
+ </ol></li>
+ <li class="skipspace"><span>The XML schema editor will retrieve the namespace for the imported
+XML schema file and display it as read-only in the <b><span class="uicontrol">Namespace</span></b> field.</span></li>
+ <li class="skipspace"><span>If necessary, type a unique prefix for this namespace in the
+ <b><span class="uicontrol">Prefix</span></b> field.</span></li>
+ <li class="skipspace"><span>Click the <b><span class="uicontrol">Documentation</span></b> 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>
</ol>
-</li>
-<li class="skipspace"><span>The XML schema editor will retrieve the namespace for the imported
-XML schema file and display it as read-only in the <span class="uicontrol">Namespace</span> field.</span></li>
-<li class="skipspace"><span>If necessary, type a unique prefix for this namespace in the <span class="uicontrol">Prefix</span> field.</span></li>
-<li class="skipspace"><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>
-</ol>
-<div class="skipspace"><p>Once you have added an import element to your XML schema, when
+<div class="skipspace">
+ <p>Once you have added an import element to your XML schema, when
you define new elements, attributes, complex types, or simple types where
you can specify type information, any declarations from the included schema
-will be available in the <span class="uicontrol">Type</span> list for the element,
-attribute, complex or simple type.</p>
-</div>
+will be available in the <b><span class="uicontrol">Type</span></b> list for the element,
+attribute, complex or simple type.</p></div>
<div class="skipspace"></div>
-</div>
<div><p><b class="reltaskshd">Related tasks</b><br />
<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. XML schema defines two constructs to support this: include and import. The include element brings in definitions and declarations from the included schema into the current schema. It requires the included schema to be in the same target namespace as the including schema. The import element behaves in a similar way, with the exception that the imported schema can come from a different namespace.">Adding an include element</a><br />
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 6b31d51..dd48705 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html
@@ -14,24 +14,19 @@
* IBM Corporation - initial API and implementation
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-<title>Adding an include element</title>
+<title>Adding include elements</title>
</head>
<body id="taddincl"><a name="taddincl"><!-- --></a>
-<h1 class="topictitle1">Adding an include element</h1>
-<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. XML schema defines two constructs to support this: <i>include</i> and
- <i>import</i>. The include element brings in definitions and declarations
-from the included schema into the current schema. It requires the included
-schema to be in the same target namespace as the including schema. The import
-element behaves in a similar way, with the exception that the imported schema
-can come from a different namespace.</p><div class="skipspace"><p>In the XML schema editor, you can add an include element to an
-XML schema. Before you can do this, you must create an XML schema and open
-it in the XML schema editor (you can open an XML schema in the XML schema
-editor by double-clicking it).</p>
-<p>The following instructions were written
-for the XML perspective, but they will also work in many other perspectives. </p>
+<h1 class="topictitle1">Adding include elements</h1>
+<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><div class="skipspace">
+<p>The following instructions were written for the XML perspective, but they
+will also work in many other perspectives.</p>
<p>To
add an include element , follow these steps:</p>
</div>
@@ -39,29 +34,33 @@
<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
schema and its contents should be displayed in the Graph view.</li>
<li class="skipspace"><span>In the Graph view, right click in the <b>Directives</b> section
-and click <span class="uicontrol">Add Include</span>.</span></li>
+and click <b> <span class="uicontrol">Add Include</span>.</b></span></li>
<li class="skipspace"><span>In the Properties view, click the <b>General</b> tab and click
-the <span class="uicontrol">More</span> button to the right of the <span class="uicontrol">Schema
-location</span> field.</span> The XML schema file you select must
+the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> to the right of the
+<b> <span class="uicontrol">Schema
+location</span> </b>field.</span> The XML schema file you select must
have the same namespace as the current schema.</li>
<li class="skipspace"><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>
+workbench, select the <b> <span class="uicontrol">Workbench projects</span></b> radio button
+and click <b> <span class="uicontrol">Next</span></b>. </span><ol type="a"><li><span>Select the schema you want to include and click
+ <b> <span class="uicontrol">Finish</span></b>.</span></li>
</ol>
</li>
<li class="skipspace"><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>
+the <b> <span class="uicontrol">HTTP</span></b> radio button and click <b> <span class="uicontrol">Next</span></b>.</span><ol type="a"><li><span>Type the URL of the XML schema and click
+ <b> <span class="uicontrol">Finish</span></b>. </span></li>
</ol>
- <div class="note"><span class="notetitle">Note: </span> A local copy of the schema will not be stored in the workbench.
+ <div class="note"><span class="notetitle"><b>Note</b>: </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>
</li>
<li class="skipspace"><span>The XML schema editor will retrieve the location of the included
-XML schema file and display it as read-only in the <span class="uicontrol">Schema location</span> field.</span></li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+XML schema file and display it as read-only in the <b> <span class="uicontrol">Schema location</span></b> field.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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>
+Info</span> page can be used to provide information for applications.</li>
</ol>
<div class="skipspace"><p>Once you have added the include element to your XML schema, when
you define new elements, attributes, complex types, or simple types where
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html
index a1fb746..75078b0 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html
@@ -14,35 +14,38 @@
* IBM Corporation - initial API and implementation
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-<title>Adding a notation</title>
+<title>Adding notations</title>
</head>
<body id="taddnot"><a name="taddnot"><!-- --></a>
-<h1 class="topictitle1">Adding a notation</h1>
+<h1 class="topictitle1">Adding notations</h1>
<div><p>A notation is a means of associating a binary description with
-an entity or attribute. For example, you are making a catalogue of your clothing
-and want to include an image of one of your shirts. You would have to create
-a notation such as the following: <kbd class="userinput"><notation name="My_Shirt"
-system="GIF"></notation></kbd> which defines a notation for a GIF
-image.</p><div class="skipspace"><p>In the XML schema editor, you can add an notation element to an
-XML schema. Before you can do this, you must create an XML schema and open
-it in the XML schema editor.</p>
-<p>The following instructions were written
-for the Resource perspective, but they will also work in many other perspectives. </p>
+an entity or attribute. The most common uses of notations are to include familiar
+types of binary references, such as GIFs and JPGs, in an XML file.</p>
+<div class="section"><p>For example, you are making a catalogue of your clothing and want
+to include an image of one of your shirts. You would have to create a notation
+like this: <kbd class="userinput"><notation name="My_Shirt" system="GIF"></notation></kbd> which
+defines a notation for a GIF image.</p>
+<p>The following instructions were written for the Resource perspective, but
+they will also work in many other perspectives.</p>
<p>To
create a notation, follow these steps:</p>
</div>
<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
-<li class="skipspace"><span>In the Outline view, right-click your XML schema and click <span class="uicontrol">Add
-Notation</span>.</span></li>
-<li class="skipspace"><span>In the Properties view, type the name of the notation in the <span class="uicontrol">Name</span> field.</span></li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Other</span> tab.</span></li>
-<li class="skipspace"><span>In the <span class="uicontrol">public</span> field, type a public identifier.</span> This is optional if you enter a value in the <span class="uicontrol">system</span> field.</li>
-<li class="skipspace"><span>In the <span class="uicontrol">system</span> field, type a URI reference.</span> This is optional if you enter a value in the <span class="uicontrol">public</span> field.</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+<li class="skipspace"><span>In the Outline view, right-click your XML schema and click
+<b> <span class="uicontrol">Add
+Notation</span></b>.</span></li>
+<li class="skipspace"><span>In the Properties view, type the name of the notation in the
+<b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Other</span></b> tab.</span></li>
+<li class="skipspace"><span>In the <b> <span class="uicontrol">public</span></b> field, type a public identifier.</span> This is optional if you enter a value in the
+<b> <span class="uicontrol">system</span></b> field.</li>
+<li class="skipspace"><span>In the <b> <span class="uicontrol">system</span></b> field, type a URI reference.</span> This is optional if you enter a value in the
+<b> <span class="uicontrol">public</span></b> field.</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want
to provide any information about this notation.</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>
+Info</span> page can be used to provide information for applications.</li>
</ol>
</div>
</body>
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 d95b7b2..d056100 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html
@@ -14,21 +14,29 @@
* IBM Corporation - initial API and implementation
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-<title>Adding a redefine element</title>
+<title>Adding redefine elements</title>
</head>
<body id="taddrdfn"><a name="taddrdfn"><!-- --></a>
-<h1 class="topictitle1">Adding a redefine element</h1>
-<div><p>You can use the redefine mechanism to redefine simple and complex
-types, groups, and attribute groups obtained from external schema files. Like
-the include mechanism, redefine requires the external components to be in
-the same target namespace as the redefining schema, although external components
-from schemas that have no namespace can also be redefined.</p><div class="skipspace"><p>In the XML schema editor, you can add a redefine element to an
-XML schema.</p>
-<p>The following instructions were written for the Resource
-perspective, but they will also work in many other perspectives. </p>
+<h1 class="topictitle1">Adding redefine elements</h1>
+<div>
+ <div class="skipspace">
+ <div>
+ <div>
+ You can use the <samp class="codeph">redefine</samp> 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.<p>Like the
+ <samp class="codeph">include</samp> mechanism,
+ <samp class="codeph">redefine</samp> requires the external
+ components to be in the same target namespace as the redefining
+ schema, although external components from schemas that have no
+ namespace can also be redefined.</div>
+ </div>
+ <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, follow these steps:</p>
</div>
<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
@@ -36,35 +44,37 @@
<li class="skipspace"><span>In the Graph view, right-click in the <b>Directives</b> section
and click <span class="uicontrol">Add Redefine</span>.</span></li>
<li class="skipspace"><span>In the Properties view, click the <b>General</b> tab and click
-the <span class="uicontrol">More</span> button to the right of the <span class="uicontrol">Schema
-location</span> field.</span> The XML schema file you select must
+the <b> <span class="uicontrol">More</span></b> button
+<img border="0" src="../images/More.gif" width="22" height="18"> to the right of the
+<b> <span class="uicontrol">Schema
+location</span> </b>field.</span> The XML schema file you select must
have the same namespace as the current schema.</li>
<li class="skipspace"><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>
+the <b> <span class="uicontrol">Workbench projects</span> </b>radio button and click <span class="uicontrol">
+<b>Next</b>.</span></span><ol type="a"><li><span> Select the schema you want to include and click
+ <b> <span class="uicontrol">Finish</span></b>.</span></li>
</ol>
</li>
<li class="skipspace"><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>.
+the <b> <span class="uicontrol">HTTP</span></b> radio button and click <b> <span class="uicontrol">Next</span></b>.</span><ol type="a"><li><span>Type the URL of the XML schema and click
+ <b> <span class="uicontrol">Finish</span></b>.
</span></li>
</ol>
- <div class="note"><span class="notetitle">Note: </span>A local copy of the schema will not be stored in the workbench.
+ <div class="note"><span class="notetitle"><b>Note</b>: </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>
</li>
<li class="skipspace"><span>The XML schema editor will retrieve the location of the included
-XML schema file and display it as read-only in the <span class="uicontrol">Schema location</span> field.</span></li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+XML schema file and display it as read-only in the <b> <span class="uicontrol">Schema location</span>
+</b>field.</span></li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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>
+material, such as a description, and the <span class="uicontrol">App Info</span>
+page can be used to provide information for applications.</li>
</ol>
-<div class="skipspace"><p>Once you have added the redefine element to your XML schema, you
-can redefine any of the simple and complex types, groups, and attribute groups
-in the XML schema you selected in the redefine element. </p>
-</div>
-<div class="skipspace"><p>(c) Copyright 2001, World Wide Web Consortium (Massachusetts Institute
-of Technology, Institut National de Recherche en Informatique et en Automatique,
-Keio University).</p>
+<div class="skipspace"><p>Once you have added the redefine element to your XML
+ schema, you can redefine any of the simple and complex types, groups, and
+ attribute groups in the XML schema you selected in the redefine element. </p>
</div>
</div>
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 265a65f..9db7e77 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html
@@ -14,41 +14,50 @@
* IBM Corporation - initial API and implementation
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-<title>Adding a pattern facet to a simple type</title>
+<title>Adding pattern facets to simple types</title>
</head>
<body id="taddreg"><a name="taddreg"><!-- --></a>
-<h1 class="topictitle1">Adding a pattern facet to a simple type</h1>
+<h1 class="topictitle1">Adding pattern facets to simple types</h1>
<div><div class="skipspace"><p>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. The value of the pattern is called
-a regular expression. You can specify it using the <span class="uicontrol">Regular Expression</span> wizard.</p>
+which indirectly constrains the value space. </p>
+ <p>The value of the pattern is called
+a regular expression. You can specify it using the<b> <span class="uicontrol">Regular Expression</span></b> wizard.</p>
<p>To
-add a pattern to a simple type, follow these steps</p>
+add a pattern to a simple type, follow these steps:</p>
</div>
<ol><li class="skipspace"><span>In the Graph view, select the simple type you want to work with.</span></li>
-<li class="skipspace"><span>In the Properties view, click the <span class="uicontrol">Advanced</span> tab,
-then the <span class="uicontrol">Pattern</span> tab.</span> The <span class="uicontrol">Pattern</span> tab
+<li class="skipspace"><span>In the Properties view, click the <b> <span class="uicontrol">Advanced</span></b> tab,
+then the <b> <span class="uicontrol">Patterns</span></b> tab.</span> The <b> <span class="uicontrol">Patterns</span></b> tab
will only appear if the pattern facet is applicable to the base type of the
simple type.</li>
-<li class="skipspace"><span>Click <span class="uicontrol">Add</span>.</span> The Regular Expression
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Add</span></b>.</span> The Regular Expression
Wizard opens.</li>
<li class="skipspace"><span>Select the token you want to add to the expression.</span></li>
<li class="skipspace"><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
+match to succeed.</span> If you want the token to repeat, click <span class="uicontrol">
+<b>Repeat</b> </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
+a minimum and maximum number of times the token can appear, click <b> <span class="uicontrol">Range</span></b> and
enter a minimum and maximum value.</li>
-<li class="skipspace"><span>Click <span class="uicontrol">Add</span> to add the token to the regular
-expression. </span></li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Add</span></b> to
+add the token to the regular expression.</span></li>
<li class="skipspace"><span>Repeat the previous three steps as necessary to create the entire
expression.</span></li>
-<li class="skipspace"><span>When you are finished, click <span class="uicontrol">Next</span>.</span></li>
+<li class="skipspace"><span>When you are finished, click <b> <span class="uicontrol">Next</span></b>.</span></li>
<li class="skipspace"><span>(Optional) Enter some sample text to test against the regular expression
and see if a match occurs. </span></li>
-<li class="skipspace"><span>Click<span class="uicontrol">Finish</span>. </span></li>
+<li class="skipspace"><span>Click<span class="uicontrol"> <b>Finish</b></span>.</span></li>
</ol>
-<div class="skipspace">The regular expression will appear in the Pattern page.</div>
+<div class="skipspace">The regular expression will appear in the Patterns page.</div>
</div>
+<p>To edit an existing pattern, select it in the Patterns page and click <b>
+<span class="uicontrol">Edit</span></b>. To delete an existing pattern, select
+it in the Patterns page and click <b><span class="uicontrol">Delete</span></b>.
+</p>
+<p><b class="reltaskshd">Related tasks</b><br />
+<a 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. XML schema defines two constructs to support this: include and import. The include element brings in definitions and declarations from the included schema into the current schema. It requires the included schema to be in the same target namespace as the including schema. The import element behaves in a similar way, with the exception that the imported schema can come from a different namespace." href="taddsmpt.html">Adding
+simple types</a></p>
</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 6996580..2805cad 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html
@@ -1,110 +1,151 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
+<html lang="en-us" xml:lang="en-us">
<head>
-<!-- /*******************************************************************************
- * Copyright (c) 2000, 2005 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- *
- * Contributors:
- * IBM Corporation - initial API and implementation
- *******************************************************************************/ -->
-<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-<title>Adding a simple type</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name="copyright" content="(C) Copyright IBM Corporation 2005" />
+<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
+<meta name="security" content="public" />
+<meta name="Robots" content="index,follow" />
+<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 name="DC.Type" content="task" />
+<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="DC.subject" content="XML schema editor, adding, simple types, XML schema files" />
+<meta name="keywords" content="XML schema editor, adding, simple types, XML schema files" />
+<meta name="DC.Relation" scheme="URI" content="../topics/taddreg.html" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="taddsmpt" />
+<meta name="DC.Language" content="en-us" />
+<!-- All rights reserved. Licensed Materials Property of IBM -->
+<!-- US Government Users Restricted Rights -->
+<!-- Use, duplication or disclosure restricted by -->
+<!-- GSA ADP Schedule Contract with IBM Corp. -->
+<link rel="stylesheet" type="text/css" href="../ibmdita.css" />
+<title>Adding simple types</title>
</head>
<body id="taddsmpt"><a name="taddsmpt"><!-- --></a>
-
-<h1 class="topictitle1">Adding a simple type</h1>
-<div><p>In the XML schema editor, you can add a simple type to an XML schema.
-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 simple types. </p><div class="skipspace"><p></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>
+<h1 class="topictitle1">Adding simple types</h1>
+<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 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>
</div>
-<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li>
-<li class="skipspace"><span>In the Outline view, select your schema.</span> The entire
+<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>
-<li class="skipspace"><span>In the Graph view, right click in the <b>Types</b> section and
-click <span class="uicontrol">Add Simple Type</span>.</span></li>
-<li class="skipspace"><span>In the Properties view, click the <span class="uicontrol">General</span> tab,
-and type a new name for the simple type in the <span class="uicontrol">Name</span> field.</span></li>
-<li class="skipspace"><span>You can select the following options from the <span class="uicontrol">Variety</span> drop
-down list:</span><ul><li><span class="uicontrol">atomic</span> - atomic types are all the simple types
-built into the XML schema language</li>
-<li><span class="uicontrol">list</span> - list types are comprised of sequences
+<li class="stepexpand"><span>In the Graph view, right-click in the <strong>Types</strong> section and
+click <b> <span class="uicontrol">Add Simple Type</span></b>.</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 simple type in the <b> <span class="uicontrol">Name</span></b> field.</span></li>
+<li class="stepexpand"><span>You can select the following options from the <b> <span class="uicontrol">Variety</span></b> list:</span><ul><li>
+ <b><span class="uicontrol">atomic</span></b>. Atomic types are all the simple types
+built into the XML schema language.</li>
+<li><b><span class="uicontrol">list</span></b>. List types are comprised of sequences
of atomic types. They have values that are comprised of finite-length sequences
-of atomic values. </li>
-<li><span class="uicontrol">union</span> - a union type enables an element or
-attribute value to be one or more instances of one type drawn from the union
-of multiple atomic and list types</li>
+of atomic values. </li>
+<li><b><span class="uicontrol">union</span></b>. A union type enables an element or attribute
+value to be one or more instances of one type drawn from the union of multiple
+atomic and list types.</li>
</ul>
</li>
-<li class="skipspace"><span>If you selected <span class="uicontrol">atomic</span> from the <span class="uicontrol">Variety</span> drop
-down list, click the <span class="uicontrol">More</span> button next to the <span class="uicontrol">Base
-type</span> field to specify a base type for the simple type.</span> You
-can select either a <span class="uicontrol">Built-in simple type</span>, or <span class="uicontrol">User-defined
-simple type</span> to be the base type.</li>
-<li class="skipspace"><span>If you selected <span class="uicontrol">list</span> from the <span class="uicontrol">Variety</span> drop
-down list, click the <span class="uicontrol">More</span> button next to the <span class="uicontrol">Item
-type</span> field to specify a item type for the simple type.</span> You
-can select either a <span class="uicontrol">Built-in simple type</span>, or <span class="uicontrol">User-defined
-simple type</span> to be the item type.</li>
-<li class="skipspace"><span>If you selected <span class="uicontrol">union</span> from the <span class="uicontrol">Variety</span> drop
-down list, click the <span class="uicontrol">More</span> button next to the <span class="uicontrol">Member
-types</span> field to specify the member types for the simple type.</span> You can select both <span class="uicontrol">Built-in simple type</span>, or <span class="uicontrol">User-defined
-simple type</span> to add to the member types list.</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Enumerations</span> tab.</span> Enumerations
-help you to define a set of valid values for simple types. Enumerations are
-the actual values the simple type can take as valid values in the instance
-document. You can either add one enumeration or several enumerations at a
-time:<ol type="a"><li class="skipspace"><span>To add one enumeration at a time, click the <span class="uicontrol">Add</span> button
+<li class="stepexpand"><span>If you selected <span class="uicontrol">atomic</span> from the
+<b> <span class="uicontrol">Variety</span></b> drop
+down list, click the <b> <span class="uicontrol">More</span></b> <img src="../images/More.gif" alt="This graphic is the More button" /> button next to the
+<b> <span class="uicontrol">Base
+type</span></b> 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 <b> <span class="uicontrol">Scope</span></b> of the list by selecting one
+of the following options:<ul><li><b><span class="uicontrol">Workspace</span></b>. Lists all of the types available in
+your workspace. </li>
+<li><b><span class="uicontrol">Enclosing Project</span></b>. Lists all of the types available
+in the project that contains your file. </li>
+<li>(Default)<b> <span class="uicontrol">Current Resource</span>.</b> List all of the types
+available in your current file.</li>
+</ul>
+ </li>
+<li class="stepexpand"><span>If you selected <span class="uicontrol">list</span> from the
+<b> <span class="uicontrol">Variety</span></b> drop
+down list, click the <b> <span class="uicontrol">More</span></b> <img src="../images/More.gif" alt="This graphic is the More button" /> button next to the
+<b> <span class="uicontrol">Item
+type</span> </b>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 <b> <span class="uicontrol">Scope</span></b> of the list by selecting one
+of the following options:<ul><li><b><span class="uicontrol">Workspace</span></b>. Lists all of the types available in
+your workspace. </li>
+<li><b><span class="uicontrol">Enclosing Project</span></b>. Lists all of the types available
+in the project that contains your file. </li>
+<li>(Default) <b> <span class="uicontrol">Current Resource</span></b>. List all of the types
+available in your current file.</li>
+</ul>
+ </li>
+<li class="stepexpand"><span>If you selected <span class="uicontrol">union</span> from the
+<b> <span class="uicontrol">Variety</span></b> drop
+down list, click the <b> <span class="uicontrol">More</span></b> <img src="../images/More.gif" alt="This graphic is the More button" /> button next to the
+<b> <span class="uicontrol">Member
+types</span> </b>field to specify the member types for the simple type.</span> You can select to add both
+<b> <span class="uicontrol">Built-in simple types</span></b> and <b> <span class="uicontrol">User-defined
+simple types</span></b> to the member types value list. </li>
+<li class="stepexpand"><span>Click the <b> <span class="uicontrol">Enumerations</span></b> tab.</span> Enumerations
+help you to define a set of valid values for simple types. They are the actual
+values the simple type can take as valid values in the instance document.
+You can either add one enumeration or several enumerations at a time:<ol type="a"><li class="substepexpand"><span>To add one enumeration at a time, click the
+ <b> <span class="uicontrol">Add</span></b> button
and specify a value for the enumeration.</span></li>
-<li class="skipspace"><span>To add several enumerations at one time, follow these steps:</span> <ol><li>Click the <span class="uicontrol">Add...</span> button.</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
+<li class="substepexpand"><span>To add several enumerations at one time, follow these steps:</span> <ol type="i"><li>Click the
+ <b> <span class="uicontrol">Add...</span></b> button.</li>
+<li>Enter the value of each enumeration. Each value must be separated by the <b> <span class="uicontrol">Delimiter
+character</span></b>. For example: <samp class="codeph">First, Second</samp> will create
two enumerations, one with the value "First" and one with the value "Second".</li>
-<li>Select the <span class="uicontrol">Preserve leading and trailing whitespace</span> check
+<li>Select the <b> <span class="uicontrol">Preserve leading and trailing whitespace</span></b> 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
show up as "First" and " Second" (there is a space before Second) because
you put a space before "Second" when entered the value.</li>
-<li>Click <span class="uicontrol">OK</span>. Your enumerations will be created and
+<li>Click <b> <span class="uicontrol">OK</span></b>. Your enumerations will be created and
appear in the Properties view.</li>
</ol>
</li>
</ol>
</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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>
-<li class="skipspace"><span>Click the <span class="uicontrol">Advanced</span> tab.</span> The options
+Info</span> page can be used to provide information for applications.</li>
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Advanced</span></b> tab.</span> The options
available from this page will vary depending on what option you selected in
-the <span class="uicontrol">Variety</span> field, and the <span class="uicontrol">Base type</span>, <span class="uicontrol">Item
-type</span>, or <span class="uicontrol">Member types</span> field on the <span class="uicontrol">General</span> page.</li>
-<li class="skipspace"><span>If applicable to the type, the <span class="uicontrol">Facets</span> table
+the <b> <span class="uicontrol">Variety</span></b> field, and the <b> <span class="uicontrol">Base type</span>,</b>
+<b> <span class="uicontrol">Item
+type</span>,</b> or <b> <span class="uicontrol">Member types</span></b> field on the <span class="uicontrol">General</span> page.</li>
+<li class="skipspace"><span>If applicable to the type, the <b> <span class="uicontrol">Facets</span></b> table
will be populated with constraining facets. A constraining facet is an optional
-property that can be applied to a datatype to constrain its value.</span><ol type="a"><li><span>To change a facet's value, click its name in the <span class="uicontrol">Name</span> column,
-then click its value (or the empty cell that will contain its value) in the <span class="uicontrol">Value</span> column
-and type or select a new value</span></li>
+property that can be applied to a datatype to constrain its value.</span><ol type="a"><li><span>To change a facet's value, click its name in the
+ <b> <span class="uicontrol">Name</span></b> column,
+then click its value (or the empty cell that will contain its value) in the <b> <span class="uicontrol">Value</span></b> column
+and type or select a new value.</span></li>
<li><span> To change whether a facet's value is fixed or not, click its
-name in the Name column, then click the appropriate cell in the Fixed column,
+name in the <b>Name</b> column, then click the appropriate cell in the <b>Fixed</b> column,
and change the value to true or false.</span></li>
</ol>
</li>
-<li class="skipspace"><span>If applicable to the type, a Pattern page will be
-available. Click the <span class="uicontrol">Pattern</span> tab to switch to it.</span> A pattern 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. For more information on adding a pattern to a
-simple type, refer to the related tasks.</li>
+<li class="stepexpand"><span>If applicable to the type, a Pattern page will be available. Click
+the <b> <span class="uicontrol">Patterns</span></b> tab to switch to it.</span> A pattern
+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. For more information on adding a pattern to a simple type,
+refer to the related tasks.</li>
</ol>
-</div>
+ <p><b class="reltaskshd">Related tasks</b><br />
+ <a href="taddreg.html">Adding pattern facets to simple types</a></p>
+ <p> </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 9657746..bcd548e 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html
@@ -20,27 +20,23 @@
<h1 class="topictitle1">Creating XML schemas</h1>
<div><p>You can create an XML schema and then edit it using the XML schema
-editor.</p><div class="skipspace">To create an XML schema, follow these steps:</div>
-<ol><li class="skipspace"><span>Create a project to contain the XML schema.</span> If you intend
-to generate Java beans from your XML schema, we recommend that
-you create a Java project to contain both the schema and the beans.
-The beans must be contained in a Java project, however, the XML schema does
-not have to be. Otherwise, it does not matter what kind of project you create.</li>
-<li class="skipspace"><span>In the workbench, select <span class="menucascade"><span class="uicontrol">File > New >
-Other > XML > XML Schema</span></span>. Click <span class="uicontrol">Next</span>.</span> If you cannot see the <span class="uicontrol">XML</span> option, select the <span class="uicontrol">Show
-All Wizards</span> check box.</li>
+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.</p><div class="skipspace">To create an XML schema, follow these steps:</div>
+<ol><li class="skipspace"><span>Create a project to contain the XML schema.</span> </li>
+<li class="skipspace"><span>In the workbench, select<b> <span class="menucascade"><span class="uicontrol">File > New >
+Other > XML > XML Schema</span></span></b>. Click <b> <span class="uicontrol">Next</span></b>.</span> </li>
<li class="skipspace"><span>Select the project or folder that will contain the XML schema.
-In the </span> <span class="uicontrol">File name</span> field, type the name of
+In the </span> <b> <span class="uicontrol">File name</span></b> field, type the name of
the XML schema, for example <kbd class="userinput">MyXMLSchema.xsd</kbd>. The name
of your XML schema must end in <tt class="sysout">.xsd</tt></li>
-<li class="skipspace"><span>Click <span class="uicontrol">Finish</span>.</span></li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">Finish</span></b>.</span></li>
</ol>
<div class="skipspace">The XML schema opens in the XML schema editor. </div>
</div>
<div>
<p><b class="relconceptshd">Related concepts</b><br />
-<a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files. ">XML schema editor</a><br />
+<a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files.?">XML schema editor</a><br />
</p>
<p><b class="reltaskshd">Related tasks</b><br />
<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><br />
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 b19d23d..5215087 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html
@@ -19,20 +19,22 @@
<body id="tdelscmp"><a name="tdelscmp"><!-- --></a>
<h1 class="topictitle1">Deleting XML schema components</h1>
-<div><p>In the XML schema editor, you can delete any of the XML schema
-components that you have created.</p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives. </p>
+<div><p>If you have created any XML schema components you no longer need,
+you can delete them.</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 delete
an XML schema component, follow these steps:</p>
</div>
<ol><li><span>Open your XML schema in the XML schema editor.</span></li>
<li><span>In the Outline view, click the item to delete.</span></li>
-<li><span>Right-click the item, and, from its pop-up menu, click <span class="uicontrol">Delete</span>.</span></li>
+<li><span>Right-click the item, and, from its pop-up menu, click <b> <span class="uicontrol">Delete</span></b>.</span></li>
</ol>
-<div class="skipspace"><p>The XML schema editor has a built-in mechanism to
-handle referential integrity issues. When you delete certain components, cleanup
-will automatically occur. Refer to the related reference section below for
-more information.</p>
+<div class="skipspace"><p>The XML schema editor has a built-in mechanism to
+ handle referential integrity issues. When you delete certain components,
+ cleanup will automatically occur. </p>
+ <p><b class="reltaskshd">Related reference</b><br />
+ <a href="rrefintg.html">Referential integrity in the XML schema editor</a></p>
</div>
</div>
</body>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html
index 665780e..f137064 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html
@@ -14,34 +14,36 @@
* IBM Corporation - initial API and implementation
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-<title>Editing XML schema editor preferences</title>
+<title>Editing XML schema file preferences</title>
</head>
<body id="tedtpref"><a name="tedtpref"><!-- --></a>
-
-<h1 class="topictitle1">Editing XML schema editor preferences</h1>
-<div><p>You can set various preferences for the XML schema editor such
-as the formatter indentation style and default target namespace.</p><div class="skipspace"><p>To define XML schema preferences, follow these steps:</p>
+<h1 class="topictitle1">Editing XML schema file preferences</h1>
+<div><p>You can set various preferences for XML schema files such as the default
+ target namespace and XML Schema language constructs prefix used.</p><div class="skipspace"><p>To define XML schema preferences, follow these steps:</p>
</div>
-<ol><li class="skipspace"><span>Select <span class="menucascade"><span class="uicontrol">Window > Preferences > Web and
-XML > XML Schema Files</span></span>.</span></li>
-<li class="skipspace"><span>Select the <span class="uicontrol">Qualify XML schema language constructs </span>check
+<ol><li class="skipspace"><span>Select <b> <span class="menucascade"><span class="uicontrol">Window > Preferences > Web and
+XML > XML Schema Files</span></span></b>.</span></li>
+<li class="skipspace"><span>Select the <b> <span class="uicontrol">Qualify XML schema language constructs </span>
+</b>check
box if you want a prefix applied to all XML Schema language constructs in
your XML schema.</span></li>
-<li class="skipspace"><span>In the <span class="uicontrol">XML schema language constructs prefix</span> field,
+<li class="skipspace"><span>In the<b> <span class="uicontrol">XML schema language constructs prefix</span>
+</b>field,
type the prefix you want applied to XML Schema language constructs in your
-XML schema.</span> The prefix <span class="uicontrol">xsd</span> is
+XML schema.</span> The prefix <b> <span class="uicontrol">xsd</span></b> is
used by convention to denote the XML Schema namespace, but any prefix can
be used. The purpose of the association is to identify the elements and simple
types as belonging to the vocabulary of the XML Schema language rather than
-the vocabulary of the schema author. <div class="note"><span class="notetitle">Note: </span>This prefix will not appear in
+the vocabulary of the schema author. <div class="note"><span class="notetitle">
+ <b>Note</b>: </span>This prefix will not appear in
any schemas that currently exist - it will only appear in new schemas you
create after you type the prefix and click <span class="uicontrol">Apply</span>. Any
schemas that already exist will have the prefix specified in the schema applied
to the XML schema language constructs.</div>
</li>
-<li class="skipspace"><span>You can change the <span class="uicontrol">Default Target Namespace</span> value.</span> The value specified in this field will be the default target namespace
+<li class="skipspace"><span>You can change the <b> <span class="uicontrol">Default Target Namespace</span></b> value.</span> The value specified in this field will be the default target namespace
for any new XML schema files created.</li>
-<li class="skipspace"><span>Click <span class="uicontrol">OK</span>.</span></li>
+<li class="skipspace"><span>Click <b> <span class="uicontrol">OK</span></b>.</span></li>
</ol>
</div>
</body>
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 877cf30..789d62f 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html
@@ -20,48 +20,67 @@
<h1 class="topictitle1">Editing XML schema properties</h1>
<div><p>After you create an XML schema, you can edit its various properties,
-such as its namespace and prefix.</p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives. </p>
-<p>To edit an
-XML schemas properties follow these steps:</p>
+such as its namespace and prefix.</p><div class="skipspace"><p>The following
+ instructions were written for the Resource perspective, but they will
+ also work in many other perspectives.</p>
+<p>To edit an XML schema's
+properties follow these steps:</p>
</div>
<ol><li class="skipspace"><span>Create a new XML schema or double-click an existing schema in the
Navigator view.</span> It will automatically open in the XML schema editor.</li>
-<li class="skipspace"><span>In the Properties view, click the <span class="uicontrol">General</span> tab.</span></li>
-<li class="skipspace"><span>You can change the <span class="uicontrol">Prefix</span> associated with
+<li class="skipspace"><span>In the Properties view, click the <b> <span class="uicontrol">General</span></b> tab.</span></li>
+<li class="skipspace"><span>You can change the <b> <span class="uicontrol">Prefix</span></b> associated with
the current namespace.</span> Element and attribute names that are associated
with this namespace will be prefixed with this value.</li>
-<li class="skipspace"><span>You can also edit the <span class="uicontrol">Target namespace</span> for
+<li class="skipspace"><span>You can also edit the <b> <span class="uicontrol">Target namespace</span>
+</b>for
this schema.</span> A namespace is a URI that provides a unique name
-to associate with all the elements and type definitions in a schema.<ol type="a"><li><span>Click <span class="uicontrol">Advanced</span> if you want to add more
+to associate with all the elements and type definitions in a schema.<ol type="a"><li><span>Click
+ <b> <span class="uicontrol">Advanced</span></b> if you want to add more
namespace declarations to your XML schema.</span></li>
</ol>
</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Other</span> tab.</span> You can
-modify the following values in this page.<ol type="a"><li class="skipspace"><span>The <span class="uicontrol">attributeFormDefault</span> value. </span> Select <span class="uicontrol">qualified</span> if you want attributes in an
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Other</span></b> tab.</span> You can
+modify the following values in this page.<ol type="a"><li class="skipspace"><span>The
+ <b> <span class="uicontrol">attributeFormDefault</span></b> value. </span> Select
+ <b> <span class="uicontrol">qualified</span></b> if you want attributes in an
XML schema instance to be qualified by the prefix that is associated with
-the schema namespace; otherwise, select <span class="uicontrol">unqualified</span>.</li>
-<li class="skipspace"><span>The <span class="uicontrol">blockDefault</span> value.</span> This
+the schema namespace; otherwise, select <b> <span class="uicontrol">unqualified</span></b>.</li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">blockDefault</span></b> value.</span> This
field determines whether the types or elements in the schema may be replaced
-by elements or types derived from them.</li>
-<li class="skipspace"><span>The <span class="uicontrol">elementFormDefault</span> value.</span> Select <span class="uicontrol">qualified</span> if
+by elements or types derived from them. The effect of specifying the
+blockDefault attribute is equivalent to specifying a block attribute on every
+type definition and element declaration in the schema. You can either select
+<strong>#all</strong> (nothing may be replaced by derivations),<strong>
+extension</strong> (nothing may be replaced by derivations-by-extension),
+<strong>restriction</strong> (nothing may be replaced by
+derivations-by-restrictions ) or <strong>substitution</strong> (nothing may be
+replaced by derivations-by-substitution). </li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">elementFormDefault</span></b> value.</span> Select <span class="uicontrol">qualified</span> if
you want elements in an XML schema instance to be qualified by the prefix
that is associated with the schema namespace; otherwise, select <span class="uicontrol">unqualified</span>.</li>
-<li class="skipspace"><span>The <span class="uicontrol">finalDefault</span> value.</span> This
+<li class="skipspace"><span>The <b> <span class="uicontrol">finalDefault</span></b> value.</span> This
field determines whether the types or elements in the schema may be derived
-from.</li>
-<li class="skipspace"><span>The <span class="uicontrol">version</span> value.</span> Type the
-version number of the schema in the <span class="uicontrol">version</span> field</li>
-<li class="skipspace"><span>The <span class="uicontrol">xml:lang</span> value. </span> Type
+from. The effect of specifying the final default attribute is equivalent to
+specifying a final attribute on every type definition and element declaration in
+the schema. If you select <strong>#all</strong>, no types or elements in the
+schema may be derived from. If you select <strong>extension</strong>, no types
+or elements in the schema may be derived from using extension. If you select
+<strong>restriction</strong>, no types or elements in the schema may be derived
+from using restriction. </li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">version</span></b>
+value.</span> Type the version number of the schema in the <b> <span class="uicontrol">
+version</span></b> field.</li>
+<li class="skipspace"><span>The <b> <span class="uicontrol">xml:lang</span> </b>value. </span> Type
the appropriate ISO-IETF (for example, en-us) tag in this field. This tag
may be inserted in documents to specify the language used in the contents
and attribute values of any element in an XML file.</li>
</ol>
</li>
-<li class="skipspace"><span>Click the <span class="uicontrol">Documentation</span> tab if you want
+<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> 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>
+Info</span> page can be used to provide information for applications.</li>
</ol>
</div>
</body>
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 430d08a..bac41e2 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html
@@ -14,22 +14,29 @@
* IBM Corporation - initial API and implementation
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
-<title>Importing an XML schema</title>
+<title>Importing XML schemas</title>
</head>
<body id="timpschm"><a name="timpschm"><!-- --></a>
-<h1 class="topictitle1">Importing an XML schema</h1>
-<div><p>You can import schemas into the workbench and open them in the
-XML schema editor. Opening them in the XML schema editor provides you with
-an opportunity to have a structured view of the XML schema file.</p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives. </p>
+<h1 class="topictitle1">Importing XML schemas</h1>
+<div>
+ <div>
+ <div>
+ 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.</div>
+ </div>
+ <div class="skipspace"><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>
</div>
-<ol><li class="skipspace"><span>Click <span class="menucascade"><span class="uicontrol">File > Import</span></span>.</span></li>
-<li class="skipspace"><span>Select the import source.</span> Click <span class="uicontrol">Next</span>.</li>
+<ol><li class="skipspace"><span>Click <b> <span class="menucascade"><span class="uicontrol">File > Import</span></span></b>.</span></li>
+<li class="skipspace"><span>Select the import source.</span> Click <b> <span class="uicontrol">Next</span></b>.</li>
<li class="skipspace"><span>Fill in the fields in the Import wizard as necessary.</span> When
-you are finished, click <span class="uicontrol">Finish</span>.</li>
+you are finished, click <b> <span class="uicontrol">Finish</span></b>.</li>
</ol>
<div class="skipspace"><p>The imported schema now appears in the Navigator view. Double-click
it to open it in the XML schema editor.</p>
@@ -37,7 +44,7 @@
</div>
<div><p><b class="relconceptshd">Related concepts</b><br />
-<a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files. ">XML schema editor</a><br />
+<a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files.?">XML schema editor</a><br />
</p>
<p><b class="reltaskshd">Related tasks</b><br />
<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><br />
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 458da4d..f3e6e10 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html
@@ -17,46 +17,42 @@
<title>Navigating XML schemas</title>
</head>
<body id="tnavsrc"><a name="tnavsrc"><!-- --></a>
-
<h1 class="topictitle1">Navigating XML schemas</h1>
<div><p>When you are working in the Source view, you can use F3 to navigate
-through the file. You can place your cursor in any of the following items
-and press the F3 key to jump to the item it refers to. You must place your
-cursor exactly in the location of the reference (for example between the double
-quotes for <tt class="sysout">type = " "</tt> or <tt class="sysout">base
-= " "</tt>):</p><div class="skipspace"><ul><li>Element or attribute declaration's type</li>
-<li> Restriction (you jump to the base type it refers to) </li>
-<li> List (you jump to the type it refers to) </li>
-<li> Union (you jump to the type it refers to) </li>
+through the file by placing your cursor in the appropriate item and clicking
+F3 to jump to the item it refers to. </p>
+<div class="section"><p>You can jump to any of the following items:</p>
+<ul><li>Element or attribute declaration's type</li>
<li>Element references</li>
-<li>Key references</li>
<li>Group references</li>
<li>Attribute references</li>
<li>Attribute group references</li>
<li>Import, include, and redefine element (the external schema will open in
the XML schema editor. This only works with schemas in the workspace).</li>
</ul>
-<p>For example, if you place your cursor anywhere in the bolded text
-below and click F3:</p>
-<p> <tt class="sysout"><element name="shipTo" type="po:USAddress"></element></tt> </p>
+<p>You must place your cursor exactly in the location of the reference
+(for example between the double quotes for <tt class="sysout">type = " "</tt> or
+ <tt class="sysout">base = " "</tt>).</p>
+<p>For example,
+if you place your cursor anywhere in the following text and click F3:</p>
+<p> <tt class="sysout"><element
+name="shipTo" type="po:USAddress"></element></tt> </p>
<p>the
cursor will automatically jump to the location in the file where the type
USAddress is defined.</p>
-<p>Or, if you place your cursor anywhere in the bolded
-text below and click F3:</p>
+<p>Or, if you place your cursor anywhere in the following
+text and click F3:</p>
<p> <tt class="sysout"><element ref="po:ContactElement"></element></tt> </p>
<p>the
cursor will automatically jump to the location in the file where the global
element ContactElement is defined.</p>
<p>This works across files. For example,
-if the type you have selected is defined in another XML schema and you click
+if the type you have selected is defined in another XML schema and you click
F3, you will automatically be taken to that file.</p>
</div>
</div>
-
-<div><p><b class="relconceptshd">Related concepts</b><br />
-<a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files. ">XML schema editor</a><br />
-</p>
+<div><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files.">XML schema editor</a></div>
</div>
-</body>
+</div></body>
</html>
\ No newline at end of file
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 015300a..c1c62e3 100644
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html
@@ -18,29 +18,32 @@
</head>
<body id="tvdtschm"><a name="tvdtschm"><!-- --></a>
-<h1 class="topictitle1">Validating an XML schema</h1>
+<h1 class="topictitle1">Validating XML schemas</h1>
<div><p>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.</p><div class="skipspace"><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives. </p>
+the Problems view.</p><div class="skipspace"><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>
</div>
-<ol><li class="skipspace"><span>Right-click your file in the Navigator view and click <span class="uicontrol">Validate
-XML Schema.</span></span></li>
-<li class="skipspace"><span>You will receive a message indicating whether the XML schema file is
+<ol><li class="skipspace"><span>Right-click your file in the Navigator view and click <span class="uicontrol">
+ <b>Validate
+XML Schema</b>.</span></span></li>
+<li class="skipspace"><span>You will receive a message indicating whether the XML schema file is
valid.</span> If validation was not successful, refer to the Problems
-view to see what problems were logged. <div class="note"><span class="notetitle">Note: </span>If you receive an error message
+view to see what problems were logged. <div class="note"><span class="notetitle">
+ <b>Note</b>: </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
+error messages allowed by selecting <b> <span class="menucascade"><span class="uicontrol">Properties >
+Validation</span></span></b> from the project's pop-up menu and specifying
the maximum number of error messages allowed.</div>
</li>
</ol>
<div class="skipspace"><p>The XML schema support in the XML schema editor is
based on the W3C XML Schema Recommendation Specification of 2 May 2001. The
-XML Schema specifications <a href="http://www.w3.org/TR/xmlschema-1/" target="_blank">XML Schema Part 1: Structures</a> and <a href="http://www.w3.org/TR/xmlschema-2/" target="_blank">XML Schema Part 2: Datatypes</a> from the
-W3C Web site are used for validation. </p>
+XML Schema specifications <a href="http://www.w3.org/TR/xmlschema-1/" target="_blank">XML Schema Part 1: Structures</a> and <a href="http://www.w3.org/TR/xmlschema-2/" target="_blank">XML Schema Part 2: Datatypes</a>
+ from the W3C Web site are used for validation.</p>
<p>Certain error messages contain
a reference to the schema constraints listed in Appendix C of the <a href="http://www.w3.org/TR/xmlschema-1/" target="_blank">XML Schema Part 1: Structures</a> document.
Each constraint has a unique name that will be referenced in the error message.
@@ -54,7 +57,7 @@
so that different types of project resources are automatically validated when
you save them. From a project's pop-up menu select <span class="uicontrol">Properties</span>,
then select <span class="uicontrol">Validation</span>. Any validators you can run
-against your project will be listed in the Validation page. </p>
+against your project will be listed in the Validation page.</p>
</div>
</div>