populating wst user doc folder
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/.project b/docs/org.eclipse.wst.xsdeditor.doc.user/.project
new file mode 100644
index 0000000..82170b5
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/.project
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>org.eclipse.wst.xsdeditor.doc.user</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ <buildCommand>
+ <name>org.eclipse.pde.ManifestBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ <buildCommand>
+ <name>org.eclipse.pde.SchemaBuilder</name>
+ <arguments>
+ </arguments>
+ </buildCommand>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.pde.PluginNature</nature>
+ </natures>
+</projectDescription>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.xml b/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.xml
new file mode 100644
index 0000000..2373ca6
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.xml
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<toc label="XML schemas" topic="topics/tcxmlsch.html">
+ <topic label="Working with XML schemas (XSDs)">
+ <topic label="Creating XML schemas" href="topics/tcxmlsch.html">
+ <topic label="Generating an XML schema file from an XML file" href="topics/tcxsdxml.html"/>
+ <topic label="Generating an XML schema file from a relational table" href="topics/txmlfddl.html"/>
+ <topic label="Generating an XML schema from a DTD file" href="../com.ibm.dtdeditor.doc/topics/tgenxmls.html"/>
+ </topic>
+ <topic label="Importing an XML schema" href="topics/timpschm.html"/>
+ <topic label="Navigating XML schemas" href="topics/tnavsrc.html"/>
+ <topic label="Editing XML schema properties" href="topics/tedtschm.html">
+ <topic label="XML schema editor" href="topics/cxmlsced.html">
+ <topic label="Editing XML schema editor preferences" href="topics/tedtpref.html"/>
+ </topic>
+ <topic label="Adding an attribute group" href="topics/taddagrp.html"/>
+ <topic label="Adding a complex type" href="topics/taddcmxt.html"/>
+ <topic label="Adding a content model" href="topics/taddcmod.html">
+ <topic label="Adding an any element" href="topics/taddanye.html"/>
+ <topic label="Adding an element" href="topics/taddelm.html"/>
+ <topic label="Adding an element reference" href="topics/taddelmr.html"/>
+ <topic label="Adding a group reference" href="topics/taddgrpr.html"/>
+ </topic>
+ <topic label="Adding a global attribute" href="topics/taddglba.html"/>
+ <topic label="Adding a global element" href="topics/taddglem.html"/>
+ <topic label="Adding a group" href="topics/taddgrup.html"/>
+ <topic label="Adding an import element" href="topics/taddimpt.html"/>
+ <topic label="Adding an include element" href="topics/taddincl.html"/>
+ <topic label="Adding a notation" href="topics/taddnot.html"/>
+ <topic label="Adding a redefine element" href="topics/taddrdfn.html"/>
+ <topic label="Adding a simple type" href="topics/taddsmpt.html">
+ <topic label="Adding a pattern facet to a simple type" href="topics/taddreg.html"/>
+ </topic>
+ </topic>
+ <topic label="Icons used in the XML schema editor" href="topics/rxsdicons.html"/>
+ <topic label="Deleting XML schema components" href="topics/tdelscmp.html">
+ <topic label="Referential integrity in the XML schema editor" href="topics/rrefintg.html"/>
+ </topic>
+ <topic label="Validating an XML schema" href="topics/tvdtschm.html"/>
+ <!-- <topic label="Generating files from XML schemas">
+ <topic label="Generating Java beans" href="topics/twrpbens.html">
+ <topic label="Data binding rules for Java beans from XML schema files" href="topics/rbndrule.html"/>
+ </topic>
+ <topic label="Generating HTML documentation" href="topics/tgenhtml.html"/>
+ <topic label="Generating a relational table definition" href="topics/tgendll.html"/>
+ </topic>-->
+ <topic label="XML namespaces" href="topics/rnmspc.html"/>
+ </topic>
+</toc>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/about.html b/docs/org.eclipse.wst.xsdeditor.doc.user/about.html
new file mode 100644
index 0000000..301d11b
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/about.html
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
+<html>
+<head>
+<title>About</title>
+<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+</head>
+<body>
+<h2>About This Content</h2>
+
+<p>20th June, 2002</p>
+<h3>License</h3>
+<p>Eclipse.org makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the
+Common Public License Version 1.0 ("CPL"). A copy of the CPL is available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>.
+For purposes of the CPL, "Program" will mean the Content.</p>
+
+<h3>Contributions</h3>
+
+<p>If this Content is licensed to you under the terms and conditions of the CPL, any Contributions, as defined in the CPL, uploaded, submitted, or otherwise
+made available to Eclipse.org, members of Eclipse.org and/or the host of Eclipse.org web site, by you that relate to such
+Content are provided under the terms and conditions of the CPL and can be made available to others under the terms of the CPL.</p>
+
+<p>If this Content is licensed to you under license terms and conditions other than the CPL ("Other License"), any modifications, enhancements and/or
+other code and/or documentation ("Modifications") uploaded, submitted, or otherwise made available to Eclipse.org, members of Eclipse.org and/or the
+host of Eclipse.org, by you that relate to such Content are provided under terms and conditions of the Other License and can be made available
+to others under the terms of the Other License. In addition, with regard to Modifications for which you are the copyright holder, you are also
+providing the Modifications under the terms and conditions of the CPL and such Modifications can be made available to others under the terms of
+the CPL.</p>
+
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAll.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAll.gif
new file mode 100644
index 0000000..6d74e80
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAll.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAny.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAny.gif
new file mode 100644
index 0000000..a39f93c
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAny.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAnyAttribute.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAnyAttribute.gif
new file mode 100644
index 0000000..5280cc2
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAnyAttribute.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttribute.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttribute.gif
new file mode 100644
index 0000000..79d49d0
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttribute.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroup.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroup.gif
new file mode 100644
index 0000000..648462f
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroup.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroupRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroupRef.gif
new file mode 100644
index 0000000..a89fa8f
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroupRef.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeRef.gif
new file mode 100644
index 0000000..8365af2
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeRef.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDChoice.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDChoice.gif
new file mode 100644
index 0000000..89ba825
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDChoice.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDComplexType.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDComplexType.gif
new file mode 100644
index 0000000..007f852
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDComplexType.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElement.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElement.gif
new file mode 100644
index 0000000..dd45f08
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElement.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElementRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElementRef.gif
new file mode 100644
index 0000000..749acfc
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElementRef.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalAttribute.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalAttribute.gif
new file mode 100644
index 0000000..79d49d0
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalAttribute.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalElement.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalElement.gif
new file mode 100644
index 0000000..dd45f08
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalElement.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroup.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroup.gif
new file mode 100644
index 0000000..555ef53
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroup.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroupRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroupRef.gif
new file mode 100644
index 0000000..3621342
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroupRef.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDImport.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDImport.gif
new file mode 100644
index 0000000..9e44ce5
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDImport.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDInclude.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDInclude.gif
new file mode 100644
index 0000000..b26c527
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDInclude.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDRedefine.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDRedefine.gif
new file mode 100644
index 0000000..56964c1
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDRedefine.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSequence.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSequence.gif
new file mode 100644
index 0000000..8bf3f97
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSequence.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleEnum.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleEnum.gif
new file mode 100644
index 0000000..11d7958
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleEnum.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimplePattern.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimplePattern.gif
new file mode 100644
index 0000000..a113cf4
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimplePattern.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleType.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleType.gif
new file mode 100644
index 0000000..75f33c2
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleType.gif
Binary files differ
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.properties b/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.properties
new file mode 100644
index 0000000..45279a5
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.properties
@@ -0,0 +1 @@
+Plugin.name = XML schema editor
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.xml b/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.xml
new file mode 100644
index 0000000..aa37537
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.xml
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.0"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<plugin
+ name = "%Plugin.name"
+ id = "org.eclipse.wst.xsdeditor.doc.user"
+ version = "0.7.0"
+ provider-name = "Eclipse.org">
+
+ <extension point="org.eclipse.help.toc">
+
+ <toc file="XSDeditormap_toc.xml"/>
+
+ <toc file="xsdeditor_reference_toc.xml"/>
+
+
+ </extension>
+
+</plugin>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html
new file mode 100644
index 0000000..039e497
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html
@@ -0,0 +1,72 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>XML schema editor</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<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>
+<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>
+<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
+editor:<ul><li>Graph - the Graph view provides a graphical way to edit your schema</li>
+<li>Outline - the Outline view shows you the main components in your XML schema.
+You can use this view to add and remove certain components.</li>
+<li>Properties - the Properties view enables you to edit the properties of
+your XML schema components</li>
+<li>Source - the Source view enables you to edit your source code directly</li>
+</ul>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Status of the XML schema</h4><p></p>
+<p>Three status indicators
+for the schema are available. They are in the bottom right corner:</p>
+<ul><li> <span class="uicontrol">Writable</span> or <span class="uicontrol">Read Only</span>. </li>
+<li> (Source view only) <span class="uicontrol">Smart Insert</span> or <span class="uicontrol">Overwrite</span>.
+To toggle between these modes, press the <span class="uicontrol">Insert</span> button
+on your keyboard.</li>
+<li> <span class="uicontrol">Line</span> and <span class="uicontrol">column</span> number. </li>
+</ul>
+</div>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor.">Creating XML schemas</a><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 />
+<a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating an XML schema</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html
new file mode 100644
index 0000000..be48e8b
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html
@@ -0,0 +1,248 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>XML namespaces</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="rnmspc"><a name="rnmspc"><!-- --></a>
+
+<h1 class="topictitle1">XML namespaces</h1>
+<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
+performance reasons. In order to resolve this conflict, the W3C namespace
+recommendation defines an attribute xmlns which can amend any XML element.
+If it is present in an element, it identifies the namespace for this element.</div>
+<div class="skipspace"><p>The xmlns attribute has the following syntax:</p>
+<p><samp class="codeph"> xmlns: <var class="varname">prefix</var>:namespace</samp> </p>
+<p>where <samp class="codeph">namespace</samp> is a unique URI (such as www.ibm.com) and where <samp class="codeph"><var class="varname">prefix</var></samp> represents
+the namespace and provides a pointer to it.</p>
+<p>In the following customer
+element definition, an accounting namespace is defined in order to be able
+to distinguish the element tags from those appearing in customer records created
+by other business applications:</p>
+<div class="p"><pre><acct:customer xmlns:acct="http://www.my.com/acct-REV10">
+ <acct:name>Corporation</acct:name>
+ <acct:order acct:ref="5566"/>
+ <acct:status>invoice</acct:status>
+</acct:customer> </pre>
+ </div>
+<p>The <i>namespace definition</i> in
+the first line assigns the namespace <i>http://www.my.com/acct-REV10</i> to
+the prefix. This prefix is used on the element names such as name in order
+to attach them to the namespace. A second application, for example, a fulfillment
+system, can assign a different namespace to its customer elements:</p>
+<div class="p"><pre><ful:customer xmlns:ful="http://www.your.com/ful">
+ <ful:name>Corporation</ful:name>
+ <ful:order ful:ref="A98756"/>
+ <ful:status>shipped</ful:status>
+ </ful:customer></pre>
+ </div>
+<p>An application processing both data
+structures is now able to treat the accounting and the fulfillment data differently.
+There is a default namespace. It is set if no local name is assigned in the
+namespace definition:</p>
+<div class="p"><pre><acct:customer xmlns="http://www.my.com/acct-REV10" xmlns:acct="http://www.my.com/acct-REV10 ">
+<name>Corporation</name>
+<order acct:ref="5566"/>
+<status>invoice</status>
+</customer></pre>
+</div>
+<p>In this example, all tags in the customer
+record are qualified to reside in the namespace <i>http://www.my.com/acct-REV10.</i> No
+explicit prefix is needed because the default namespace is used. Note that
+the default namespace applies to any attributes definitions.</p>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">XML schemas and namespaces</h4><p>In the XML schema below,
+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"?>
+<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">
+ <minInclusive value="10000"/>
+ <maxInclusive value="99999"/>
+</restriction>
+ </simpleType>
+ <!--element definitions skipped -->
+</schema> </pre>
+</div>
+<p>Assuming that the XML schema defined above
+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"?>
+<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>
+ <x:street>x:Vangerowstrasse</x:street>
+ <x:zipCode>69115</x:zipCode>
+ <x:city>x:Heidelberg</x:city>
+ </x:address>
+ <x:address>
+<x:street>x:Bernal Road</x:street>
+<x:zipCode>90375</x:zipCode>
+ <x:city>x:San Jose</x:city>
+ </x:address>
+</x:addressList> </pre>
+</div>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Target namespace</h4><p> The target namespace serves to
+identify the namespace within which the association between the element and
+its name exists. In the case of declarations, this association determines
+the namespace of the elements in XML files conforming to the schema. An XML
+file importing a schema must reference its target namespace in the schemaLocation
+attribute. Any mismatches between the target and the actual namespace of an
+element are reported as schema validation errors. In our example, the target
+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>
+</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"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com">
+<complexType name="AddressType">
+<sequence>
+<element name="name" type="string"></element>
+</sequence>
+</complexType>
+<element name="MyAddress" type="x:AddressType"></element>
+</schema> </pre>
+ </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"?>
+<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>
+</div>
+<p>When local elements (such as the <i>"name"</i> element)
+and attributes are unqualified in an XML file, then only the root element
+is qualified. So, in this example, the <i>"x"</i> namespace prefix is assigned
+to the root element <i>"MyAddress"</i>, associating it with the namespace <i>"http://www.ibm.com",</i> but
+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"?>
+<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>
+<element name="name" type="string"></element>
+</sequence>
+</complexType>
+<element name="MyAddress" type="x:AddressType"></element>
+ </schema> </pre>
+</div>
+<p>A valid XML instance document created from
+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"?>
+ <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>
+ </x:MyAddress></pre>
+ </div>
+<p>In this example, the <i>"x"</i> namespace
+prefix is assigned to both the root element <i>"MyAddress"</i> and the local
+element <i>"name"</i>, associating them with the namespace <i>"http://www.ibm.com",</i>.</p>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Sample 3 - Schema with target Namespace, and explicitly defines
+xmlns:xsd</h4><p>This XML schema adds this attribute: </p>
+<samp class="codeph">xmlns:xsd="http://www.w3.org/2001/XMLSchema </samp><p>What
+this means is that each of the constructs that are defined by the XML schema
+language will need to be qualified with the <var class="varname">"xsd"</var> prefix.
+For example, xsd:complexType and xsd:string</p>
+<p>. Note that you can chose
+any other prefixes such as <var class="varname">"xs"</var> or <var class="varname">"foobar"</var> in
+your declaration and usage.</p>
+<p>You can specify this prefix in the XML Schema
+preferences page. For more information, refer to the related tasks below.</p>
+<p>All
+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"?>
+<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:sequence>
+ </xsd:complexType>
+ <xsd:element name="MyAddress" type="x:AddressType"></xsd:element>
+</xsd:schema></pre>
+ </div>
+<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"?>
+ <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>
+</div>
+</div>
+<div class="skipspace"><h4 class="sectiontitle">Sample 4 - Schema with undeclared target Namespace that explicitly
+defines xmlns:xsd</h4><p>This XML schema has no target namespace for itself.
+In this case, it is highly recommended that all XML schema constructs be explicitly
+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"?>
+<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
+<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:element name="name" type="xsd:string"></xsd:element>
+</xsd:sequence>
+</xsd:complexType>
+<xsd:element name="MyAddress" type="AddressType"></xsd:element>
+</xsd:schema> </pre>
+</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"?>
+<MyAddress xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="x.xsd">
+<name>name</name>
+</MyAddress></pre>
+ </div>
+</div>
+<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"?>
+ <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>
+<xsd:element name="name" type="xsd:string"></xsd:element>
+</xsd:sequence>
+</xsd:complexType>
+ <xsd:element name="MyAddress" type="AddressType"></xsd:element>
+ </xsd:schema> </pre>
+ </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"?>
+<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>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</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
new file mode 100644
index 0000000..f35a240
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html
@@ -0,0 +1,105 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Referential integrity</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="rrefintg"><a name="rrefintg"><!-- --></a>
+
+<h1 class="topictitle1">Referential integrity in the XML schema editor</h1>
+<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>
+</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>
+<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>
+</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
+to the <tt class="sysout">string</tt> type.</li>
+<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
+to the <tt class="sysout">string</tt> type.</li>
+<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
+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
+will be reset using the algorithm similar to the one described earlier for
+deleted global elements.</li>
+</ol>
+</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>
+<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>
+</div>
+</div>
+
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</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
new file mode 100644
index 0000000..64c898a
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html
@@ -0,0 +1,90 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding an attribute group</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="taddagrp"><a name="taddagrp"><!-- --></a>
+
+<h1 class="topictitle1">Adding an attribute group</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>
+<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
+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>
+<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>
+</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
+attribute enables the referenced attribute to appear in the instance document
+in the context of the referencing declaration. The menu option to add
+an attribute reference only appears if there are global attributes defined
+elsewhere in the document.<ol type="a"><li><span>Select the reference (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>
+</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
+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>
+</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
+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
+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>
+</ol>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html
new file mode 100644
index 0000000..d56771e
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html
@@ -0,0 +1,70 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding an any element</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="taddanye"><a name="taddanye"><!-- --></a>
+
+<h1 class="topictitle1">Adding an any element</h1>
+<div><p>You can use the <samp class="codeph">any</samp> element to provide something
+similar to a DTD's ANY content model, however, it must be done in conjunction
+with namespaces. This enables you to include any well-formed XML content,
+such as an HTML Web page that conforms to XHTML 1.0 syntax.</p><div class="skipspace"><p>For example:</p>
+<div class="p"><pre><element name = "MyWebPage">
+<complexType>
+<any namespace ="http://www.w3.org/1999/xhtml>
+ < minOccurs="1" maxOccurs="unbounded" processContents="skip"/>
+</complexType>
+</element></pre>
+</div>
+<p>The above 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>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>
+<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
+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). </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
+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
+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>
+</ol>
+<div class="skipspace"><p>(c) Copyright 2001, World Wide Web (Massachusetts Institute of
+Technology, Institut National de Recherche en Informatique et en Automatique,
+Keio University).</p>
+</div>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html
new file mode 100644
index 0000000..82ae2ee
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html
@@ -0,0 +1,88 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding a content model</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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
+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
+can appear in an instance of the XML schema.</li>
+<li><b>All</b>, which means that all of the content model's children can appear
+once or not at all, and they may appear in any order. If you select this option,
+all of the contents model's children must be individual elements and no element
+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>To add a content
+model, to a 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
+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
+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
+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
+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
+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
+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>
+</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
+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>
+<li>An element reference, which provides a reference to a global element.
+This menu option only appears if there are global elements defined elsewhere
+in the document.</li>
+<li>An <samp class="codeph">any</samp> element. You can use an <samp class="codeph">any</samp> element
+to extend your content model by any elements belonging to a specified namespace.</li>
+</ul>
+</div>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</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
new file mode 100644
index 0000000..5e5151b
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html
@@ -0,0 +1,130 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding a complex type</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+<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>
+<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
+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
+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
+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
+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
+(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
+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
+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
+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 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
+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
+attribute enables the referenced attribute to appear in the instance document
+in the context of the referencing declaration. The menu option to add
+an attribute reference only appears if there are global attributes defined
+elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the global attribute you want
+it to reference from the <span class="uicontrol">ref</span> 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
+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>
+</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
+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
+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
+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>
+
+<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 />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html
new file mode 100644
index 0000000..9cbabc1
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html
@@ -0,0 +1,136 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding an element</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+<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
+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
+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
+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
+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
+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
+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
+attribute enables the referenced attribute to appear in the instance document
+in the context of the referencing declaration. The menu option to add
+an attribute reference only appears if there are global attributes defined
+elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the global attribute you want
+it to reference from the<span class="uicontrol">ref</span> 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
+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>
+</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
+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
+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 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">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
+about working with content models, refer to the related tasks.</div>
+</div>
+
+<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 />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html
new file mode 100644
index 0000000..9477dd3
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html
@@ -0,0 +1,115 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding an element reference</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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
+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
+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>
+<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>
+<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.
+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
+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
+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
+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
+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
+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
+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
+attribute enables the referenced attribute to appear in the instance document
+in the context of the referencing declaration. The menu option to add
+an attribute reference only appears if there are global attributes defined
+elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the global attribute you want
+it to reference from the <span class="uicontrol">ref</span> 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
+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>
+</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
+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
+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 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>
+</ol>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddglem.html" title="A global element is an element with a global scope. It is one that has been declared as part of the main schema rather than as part of a complex type definition.">Adding a global element</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html
new file mode 100644
index 0000000..f32e9f3
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html
@@ -0,0 +1,48 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding a global attribute</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+<p>To add a global
+attribute, 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>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
+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>
+</ol>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html
new file mode 100644
index 0000000..ce72029
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html
@@ -0,0 +1,120 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding a global element</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+<p>To add a global
+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>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
+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
+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
+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
+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
+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
+attribute enables the referenced attribute to appear in the instance document
+in the context of the referencing declaration. The menu option to add
+an attribute reference only appears if there are global attributes defined
+elsewhere in the document.<ol type="a"><li><span>Select the reference, then select the global attribute you want
+it to reference from the <span class="uicontrol">ref</span> 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
+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>
+</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
+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
+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 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>
+</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
+about working with content models, refer to the related tasks.</div>
+</div>
+
+<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 />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html
new file mode 100644
index 0000000..d7227bd
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html
@@ -0,0 +1,45 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding a group reference</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+<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>
+<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
+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>
+</ol>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddgrup.html" title="A group consists of element declarations, wildcards, and other content model groups. When you create a group, it automatically contains a content model.">Adding a group</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html
new file mode 100644
index 0000000..3e11beb
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html
@@ -0,0 +1,53 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding a group</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+<p>To
+add a group, 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>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
+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
+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
+inside the group. For more information about working with content models,
+refer to the related tasks.</li>
+</ol>
+</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/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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html
new file mode 100644
index 0000000..cd29f15
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html
@@ -0,0 +1,87 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding an import element</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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
+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
+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.
+Every time you validate your schema, the schema's contents will be checked
+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 <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
+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>
+<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 />
+<a href="../topics/taddrdfn.html" title="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. 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.">Adding a redefine element</a><br />
+</p>
+<p><b class="relrefhd">Related reference</b><br />
+<a href="../topics/rnmspc.html" title="">XML namespaces</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html
new file mode 100644
index 0000000..0c52ca1
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html
@@ -0,0 +1,94 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding an include element</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+<p>To
+add an include 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 Include</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
+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>
+</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>
+</ol>
+ <div class="note"><span class="notetitle">Note: </span> A local copy of the schema will not be stored in the workbench.
+Every time you validate your schema, the schema's contents will be checked
+from the URL you specify.</div>
+</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
+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>
+</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
+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>
+<p>For example, if Address.xsd has the
+following content:</p>
+<pre><complexType name="Address">
+ <sequence>
+ <element name="name" type="string">
+ <element name="street" type="string">
+ </sequence>
+</complexType></pre>
+and you have an XML schema called PurchaseOrder.xsd that has added
+an include for Address.xsd, then when defining a new element in PurchaseOrder,
+you can select Address as its type. <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>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. 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 import element</a><br />
+<a href="../topics/taddrdfn.html" title="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. 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.">Adding a redefine element</a><br />
+</p>
+<p><b class="relrefhd">Related reference</b><br />
+<a href="../topics/rnmspc.html" title="">XML namespaces</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html
new file mode 100644
index 0000000..dc60454
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html
@@ -0,0 +1,48 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding a notation</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="taddnot"><a name="taddnot"><!-- --></a>
+
+<h1 class="topictitle1">Adding a notation</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>
+<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
+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>
+</ol>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html
new file mode 100644
index 0000000..68566ef
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html
@@ -0,0 +1,78 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding a redefine element</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+<p>To
+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
+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 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
+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>
+</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>
+</ol>
+ <div class="note"><span class="notetitle">Note: </span>A local copy of the schema will not be stored in the workbench.
+Every time you validate your schema, the schema's contents will be checked
+from the URL you specify.</div>
+</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
+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>
+</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>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. 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 import element</a><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 />
+</p>
+<p><b class="relrefhd">Related reference</b><br />
+<a href="../topics/rnmspc.html" title="">XML namespaces</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html
new file mode 100644
index 0000000..cf615dd
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html
@@ -0,0 +1,53 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding a pattern facet to a simple type</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="taddreg"><a name="taddreg"><!-- --></a>
+
+<h1 class="topictitle1">Adding a pattern facet to a simple type</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>
+<p>To
+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
+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
+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
+specify the number of times the token must appear. If you want to specify
+a minimum and maximum number of times the token can appear, click <span class="uicontrol">Range</span> and
+enter a minimum and maximum value.</li>
+<li class="skipspace"><span>Click <span class="uicontrol">Add</span> 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>(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>
+</ol>
+<div class="skipspace">The regular expression will appear in the Pattern page.</div>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</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
new file mode 100644
index 0000000..7a3921d
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html
@@ -0,0 +1,109 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Adding a simple type</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+</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>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
+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>
+</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
+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
+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
+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
+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
+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
+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
+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>
+<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,
+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>
+</ol>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</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
new file mode 100644
index 0000000..46ce3c3
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html
@@ -0,0 +1,49 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Creating XML schemas</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tcxmlsch"><a name="tcxmlsch"><!-- --></a>
+
+<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>
+<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
+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>
+</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 />
+</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 />
+<a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating an XML schema</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html
new file mode 100644
index 0000000..f5849e8
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html
@@ -0,0 +1,38 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Deleting XML schema components</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<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>
+<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>
+</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>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html
new file mode 100644
index 0000000..9e125b3
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html
@@ -0,0 +1,48 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing XML schema editor preferences</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+</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
+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,
+type the prefix you want applied to XML Schema language constructs in your
+XML schema.</span> The prefix <span class="uicontrol">xsd</span> 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
+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
+for any new XML schema files created.</li>
+<li class="skipspace"><span>Click <span class="uicontrol">OK</span>.</span></li>
+</ol>
+<div class="skipspace"></div>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html
new file mode 100644
index 0000000..beca9a8
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html
@@ -0,0 +1,67 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Editing XML schema properties</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tedtschm"><a name="tedtschm"><!-- --></a>
+
+<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>
+</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
+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
+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
+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
+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
+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
+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
+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
+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
+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>
+</ol>
+</div>
+<p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html
new file mode 100644
index 0000000..7f9e906
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html
@@ -0,0 +1,48 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Importing an XML schema</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+<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>
+<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>
+</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>
+</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>
+<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 />
+<a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating an XML schema</a><br />
+<a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. 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 import element</a><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 />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html
new file mode 100644
index 0000000..82a26f1
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html
@@ -0,0 +1,60 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Navigating XML schemas</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></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>
+<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>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> <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
+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><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</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
new file mode 100644
index 0000000..39c3497
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html
@@ -0,0 +1,64 @@
+<?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>
+<link rel="stylesheet" type="text/css" href="../../com.ibm.help.doc/swg_info_common.css" />
+<title>Validating an XML schema</title>
+<script language="JavaScript">
+ function popup_window( url, id, width, height )
+ {
+ popup = window.open( url, id, 'toolbar=no,scrollbars=no,location=no,statusbar=no,menubar=no,resizable=no,width=' + width + ',height=' + height + ',left=,top=' );
+ popup.focus();
+ }
+</script><script language="JavaScript" src="help/liveHelp.js"></script></head>
+<body id="tvdtschm"><a name="tvdtschm"><!-- --></a>
+
+<h1 class="topictitle1">Validating an XML schema</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>
+<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
+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
+indicating that the Problems view is full, you can increase the number of
+error messages allowed by selecting <span class="menucascade"><span class="uicontrol">Properties >
+Validation</span></span> from the project's pop-up menu and specifying
+the maximum number of error messages allowed.</div>
+</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>
+<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.
+For example, if you receive an error message with this text: <tt class="sysout">ct-props-correct.2,</tt> and
+you searched in the Structure document for the text, you would find that it
+is for the section "Schema Component Constraint: Complex Type Definition Properties
+Correct". The <tt class="sysout">.2</tt> means the 2nd constraint, which
+reads: "2. If the {base type definition} is a simple type definition, the
+{derivation method} must be extension."</p>
+<p>You can set up a project's properties
+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>
+</div>
+</div>
+
+<div><p><b class="reltaskshd">Related tasks</b><br />
+<a href="../topics/tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor.">Creating XML schemas</a><br />
+</p>
+</div><p>
+ (C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.
+</p>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/xsdeditor_reference_toc.xml b/docs/org.eclipse.wst.xsdeditor.doc.user/xsdeditor_reference_toc.xml
new file mode 100644
index 0000000..4844214
--- /dev/null
+++ b/docs/org.eclipse.wst.xsdeditor.doc.user/xsdeditor_reference_toc.xml
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- /*******************************************************************************
+ * 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
+ *******************************************************************************/ -->
+<toc label="XML schema editor reference files" topic="topics/rxsdicons.html">
+ <topic label="XML schema editor reference">
+ <!-- <topic label="Icons used in the XML schema editor" href="topics/rxsdicons.html"/>-->
+ <topic label="Referential integrity in the XML schema editor" href="topics/rrefintg.html"/>
+ <!-- <topic label="Data binding rules for Java beans from XML schema files" href="topics/rbndrule.html"/>-->
+ <topic label="XML namespaces" href="topics/rnmspc.html"/>
+ </topic>
+</toc>
