diff options
Diffstat (limited to 'docs/org.eclipse.wst.xsdeditor.doc.user/topics')
60 files changed, 0 insertions, 5571 deletions
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.dita deleted file mode 100644 index 60b1bfa322..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.dita +++ /dev/null @@ -1,29 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<?Pub Inc?>
-<concept id="workingwithxmlschemas" xml:lang="en-us">
-<title>Working with XML schemas</title>
-<shortdesc>XML schemas are an XML language for describing and constraining
-the content of XML files.</shortdesc>
-<conbody>
-<p>This sections contains information on the following:</p><?Pub Caret1?>
-</conbody>
-<related-links>
-<link href="tcxmlsch.dita"><linktext>Creating XML schemas</linktext></link>
-<link href="timpschm.dita"><linktext>Importing XML schemas</linktext></link>
-<link href="tnavsrc.dita"><linktext>Navigating XML schemas</linktext></link>
-<link href="trefactrXSD.dita"><linktext>Refactoring in XML schemas</linktext>
-</link>
-<link href="tedtpref.dita"><linktext>Editing XML schema file preferences</linktext>
-</link>
-<link href="rxsdicons.dita"><linktext>Icons used in the XML schema editor</linktext>
-</link>
-<link href="tdelscmp.dita"><linktext>Deleting XML schema components</linktext>
-</link>
-<link href="tvdtschm.dita"><linktext>Validating XML schemas</linktext></link>
-<link href="rnmspc.dita"><linktext>XML namespaces</linktext></link>
-</related-links>
-</concept>
-<?Pub *0000001267?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html deleted file mode 100644 index 45f35b6650..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html +++ /dev/null @@ -1,58 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Working with XML schemas" /> -<meta name="abstract" content="XML schemas are an XML language for describing and constraining the content of XML files." /> -<meta name="description" content="XML schemas are an XML language for describing and constraining the content of XML files." /> -<meta scheme="URI" name="DC.Relation" content="tcxmlsch.html" /> -<meta scheme="URI" name="DC.Relation" content="timpschm.html" /> -<meta scheme="URI" name="DC.Relation" content="tnavsrc.html" /> -<meta scheme="URI" name="DC.Relation" content="trefactrXSD.html" /> -<meta scheme="URI" name="DC.Relation" content="tedtpref.html" /> -<meta scheme="URI" name="DC.Relation" content="rxsdicons.html" /> -<meta scheme="URI" name="DC.Relation" content="tdelscmp.html" /> -<meta scheme="URI" name="DC.Relation" content="tvdtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="rnmspc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="workingwithxmlschemas" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Working with XML schemas</title> -</head> -<body id="workingwithxmlschemas"><a name="workingwithxmlschemas"><!-- --></a> - - -<h1 class="topictitle1">Working with XML schemas</h1> - - -<div><p>XML schemas are an XML language for describing and constraining -the content of XML files.</p> - -<p>This sections contains information on the following:</p> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations.">Creating XML schemas</a></div> -<div><a href="timpschm.html" title="If you want to work with XML schema files that you created outside of the product, you can import them into the workbench and open them in the XML schema editor. The XML schema editor provides you with a structured view of the XML schema.">Importing XML schemas</a></div> -<div><a href="tnavsrc.html" title="When you are working in the Source view, you can use F3 to navigate through the file by placing your cursor in the appropriate item and clicking F3 to jump to the item it refers to.">Navigating XML schemas</a></div> -<div><a href="trefactrXSD.html" title="Within an XML Schema file, refactoring allows authors to make a single artifact change, and have that change implemented throughout all other dependant artifacts.">Refactoring in XML schemas</a></div> -<div><a href="tedtpref.html" title="You can set various preferences for XML schema files such as the default target namespace and XML Schema language constructs prefix used.">Editing XML schema file preferences</a></div> -<div><a href="tdelscmp.html" title="If you have created any XML schema components you no longer need, you can delete them.">Deleting XML schema components</a></div> -<div><a href="tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div> -</div> -<div class="relref"><strong>Related reference</strong><br /> -<div><a href="rxsdicons.html" title="The following XML schema editor icons appear in the Outline, Design, and Properties view.">Icons used in the XML schema editor</a></div> -<div><a href="rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.dita deleted file mode 100644 index 60b4ae471c..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.dita +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cxmlsced" xml:lang="en-us">
-<title>XML schema editor</title>
-<titlealts>
-<searchtitle>XML schema editor</searchtitle>
-</titlealts>
-<shortdesc>This product provides an XML schema editor for creating, viewing,
-and validating XML schemas. X<?Pub Caret1?>ML schemas are a formal specification
-of element names that indicates which elements are allowed in an XML file,
-and in which combinations. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>A schema is functionally equivalent to a DTD, but is written in XML; a
-schema also provides for extended functionality such as data typing, inheritance,
-and presentation rules.</p>
-<p>For more information on XML schema, refer to:</p>
-<ul>
-<li> <xref format="html" href="http://www.w3.org/TR/xmlschema-0/" scope="external">http://www.w3.org/TR/xmlschema-0/</xref> </li>
-<li> <xref format="html" href="http://www.w3.org/TR/xmlschema-1/" scope="external">http://www.w3.org/TR/xmlschema-1/</xref> </li>
-<li> <xref format="html" href="http://www.w3.org/TR/xmlschema-2/" scope="external">http://www.w3.org/TR/xmlschema-2/</xref> </li>
-</ul>
-<p>Using the XML schema editor, you can:</p>
-<ul>
-<li>Create and delete XML schema components such as complex types, simple
-types, elements, attributes, attribute groups, and groups.</li>
-<li>Edit XML schemas.</li>
-<li>Import existing XML schemas for structured viewing.</li>
-</ul>
-<p>The XML Schema specification from the W3C Web site is used for validation.</p>
-<section><title>XML schema editor views - Design, Outline, Properties, and
-Source</title>There are four main views you can work with in the XML schema
-editor:<ul>
-<li>Design - the Design view provides a graphical way to edit your schema</li>
-<li>Outline - the Outline view shows you the main components in your XML schema.
-You can use this view to add and remove certain components.</li>
-<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></section>
-<section><title>Status of the XML schema</title><p></p><p>Three status indicators
-for the schema are available. They are in the bottom right corner:</p><ul>
-<li> <uicontrol>Writable</uicontrol> or <uicontrol>Read Only</uicontrol>. </li>
-<li> (Source view only) <uicontrol>Smart Insert</uicontrol> or <uicontrol>Overwrite</uicontrol>.
-To toggle between these modes, press the <uicontrol>Insert</uicontrol> button
-on your keyboard.</li>
-<li> <uicontrol>Line</uicontrol> and <uicontrol>column</uicontrol> number. </li>
-</ul></section>
-</conbody>
-</concept>
-<?Pub *0000002883?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html deleted file mode 100644 index 869ad39d40..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html +++ /dev/null @@ -1,108 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="XML schema editor" /> -<meta name="abstract" content="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations." /> -<meta name="description" content="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations." /> -<meta content="XML schema editor, overview" name="DC.subject" /> -<meta content="XML schema editor, overview" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcxmlsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tvdtschm.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cxmlsced" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML schema editor</title> -</head> -<body id="cxmlsced"><a name="cxmlsced"><!-- --></a> - - -<h1 class="topictitle1">XML schema editor</h1> - - - - -<div><p>This product provides an XML schema editor for creating, viewing, -and validating XML schemas. XML schemas are a formal specification -of element names that indicates which elements are allowed in an XML file, -and in which combinations. </p> - -<p>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>Using the XML schema editor, you can:</p> - -<ul> -<li>Create and delete XML schema components such as complex types, simple -types, elements, attributes, attribute groups, and groups.</li> - -<li>Edit XML schemas.</li> - -<li>Import existing XML schemas for structured viewing.</li> - -</ul> - -<p>The XML Schema specification from the W3C Web site is used for validation.</p> - -<div class="section"><h4 class="sectiontitle">XML schema editor views - Design, Outline, Properties, and -Source</h4>There are four main views you can work with in the XML schema -editor:<ul> -<li>Design - the Design view provides a graphical way to edit your schema</li> - -<li>Outline - the Outline view shows you the main components in your XML schema. -You can use this view to add and remove certain components.</li> - -<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="section"><h4 class="sectiontitle">Status of the XML schema</h4><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><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations.">Creating XML schemas</a></div> -<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div> -<div><a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.dita deleted file mode 100644 index e50260d98d..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.dita +++ /dev/null @@ -1,20 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="rlimitations_slushXSD" xml:lang="en-us">
-<title>Limitations of XML schema editor</title>
-<titlealts>
-<searchtitle>Limitations of XML schema editor</searchtitle>
-</titlealts>
-<shortdesc>This section describes known product aspect limitations and workarounds.</shortdesc>
-<refbody>
-<!--Use this template to single source the readme information. The content for the readme information is maintained in this topic and is inserted into the related topic using the conref attribute. This file will not be surfaced in your navigation.-->
-<section><title>Hebrew Logical encoding</title><p id="encoding"><!--There is no defect associated with this entry. It is from the 5.1 readme.-->When
-Hebrew Logical (ISO-8859-8-I) encoding is selected as a preference for encoding
-of HTML files (<menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML Files</uicontrol><uicontrol>HTML files</uicontrol>
-</menucascade> in the "When creating files" section), the HTML documentation
-files generated from an XML schema file will still have a UTF-8 encoding.
-This is a known problem.</p></section>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.html deleted file mode 100644 index 1a5cc5429d..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.html +++ /dev/null @@ -1,43 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Limitations of XML schema editor" /> -<meta name="abstract" content="This section describes known product aspect limitations and workarounds." /> -<meta name="description" content="This section describes known product aspect limitations and workarounds." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rlimitations_slushXSD" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Limitations of XML schema editor</title> -</head> -<body id="rlimitations_slushXSD"><a name="rlimitations_slushXSD"><!-- --></a> - - -<h1 class="topictitle1">Limitations of XML schema editor</h1> - - - -<div><p>This section describes known product aspect limitations and workarounds.</p> - - -<div class="section"><h4 class="sectiontitle">Hebrew Logical encoding</h4><p id="rlimitations_slushXSD__encoding"><a name="rlimitations_slushXSD__encoding"><!-- --></a>When -Hebrew Logical (ISO-8859-8-I) encoding is selected as a preference for encoding -of HTML files (<span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML Files</span> > <span class="uicontrol">HTML files</span> -</span> in the "When creating files" section), the HTML documentation -files generated from an XML schema file will still have a UTF-8 encoding. -This is a known problem.</p> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.dita deleted file mode 100644 index 0237e988f7..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.dita +++ /dev/null @@ -1,189 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="rnmspc" xml:lang="en-us">
-<title>XML namespaces</title>
-<titlealts>
-<searchtitle>XML namespaces</searchtitle>
-</titlealts>
-<shortdesc>An XML namespace is a collection of names, identified by a URI
-reference, which are used in XML documents as element types and attribute
-names.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML namespaces<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<refbody>
-<section>XML namespaces are defined by a W3C recommendation, dating 14 January
-1999, called <xref format="html" href="http://www.w3.org/TR/REC-xml-names/"
-scope="external">Namespaces in XML</xref>. 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 <b>xmlns</b> which
-can amend any XML element. If it is present in an element, it identifies the
-namespace for this element.</section>
-<section><p>The xmlns attribute has the following syntax:</p><p><codeph>xmlns:<varname>prefix</varname>=namespace</codeph> </p><p>where <codeph>namespace</codeph
-> is a unique URI (such as www.ibm.com) and where <codeph><varname>prefix</varname></codeph> 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><p><codeblock><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> </codeblock> </p><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><p><codeblock><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></codeblock> </p><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><p><codeblock><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></codeblock></p><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></section>
-<section><title>XML schemas and namespaces</title><p>In the following XML
-schema, 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><p><codeblock><?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> </codeblock></p><p>Assuming that the preceding XML schema is
-saved as <filepath>C:\temp\TestSchema.xsd</filepath>, a sample XML file that
-validates against this schema is:</p><p><codeblock><?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> </codeblock></p></section>
-<section><title>Target namespace</title><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 examples
-show how target namespaces and namespace prefixes work in XML schemas and
-their corresponding XML instance documents.</p></section>
-<section><title>Sample 1 - A schema with both a default and target namespace
-and unqualified locals</title><p>The XML schema: </p><p><codeblock><?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> </codeblock> </p><p>A valid XML instance document created from
-this schema looks like this. Local elements and attributes are <i>unqualified</i>.</p><p><codeblock><?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> </codeblock></p><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></section>
-<section><title>Sample 2 - A schema with both a default and target namespace
-and qualified locals</title><p><codeblock><?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> </codeblock></p><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><p><codeblock><?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></codeblock> </p><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></section>
-<section><title>Sample 3 - Schema with target Namespace, and explicitly defines
-xmlns:xsd</title><p>This XML schema adds this attribute: </p><codeph>xmlns:xsd="http://www.w3.org/2001/XMLSchema </codeph><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 <varname>"xsd"</varname> prefix.
-For example, xsd:complexType and xsd:string</p><p>. Note that you can chose
-any other prefixes such as <varname>"xs"</varname> or <varname>"foobar"</varname> 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.</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><p><codeblock><?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></codeblock> </p><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><p><codeblock><?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></codeblock></p></section>
-<section><title>Sample 4 - Schema with undeclared target Namespace that explicitly
-defines xmlns:xsd</title><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><p><codeblock><?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> </codeblock></p><p>A valid XML instance document created
-from the schema looks like this. All elements are <i>unqualified</i>.</p><p><codeblock><?xml version="1.0"?>
-<MyAddress xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="x.xsd">
-<name>name</name>
-</MyAddress></codeblock> </p></section>
-<section><title>Sample 5 - A schema where the target namespace is the default
-namespace</title><p>This is an XML schema where the target namespace is the
-default namespace. As well, the namespace has no namespace prefix.</p><p><codeblock><?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> </codeblock> </p><p>A valid XML instance document created
-from the schema looks like this:</p><p><codeblock><?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> </codeblock> </p></section>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html deleted file mode 100644 index f4a0b4f53d..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html +++ /dev/null @@ -1,272 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="XML namespaces" /> -<meta name="abstract" content="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names." /> -<meta name="description" content="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names." /> -<meta content="XML namespaces, overview" name="DC.subject" /> -<meta content="XML namespaces, overview" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rnmspc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML namespaces</title> -</head> -<body id="rnmspc"><a name="rnmspc"><!-- --></a> - - -<h1 class="topictitle1">XML namespaces</h1> - - - - -<div><p>An XML namespace is a collection of names, identified by a URI -reference, which are used in XML documents as element types and attribute -names.</p> - -<div class="section">XML namespaces are defined by a W3C recommendation, dating 14 January -1999, called <a href="http://www.w3.org/TR/REC-xml-names/" target="_blank">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 <strong>xmlns</strong> which -can amend any XML element. If it is present in an element, it identifies the -namespace for this element.</div> - -<div class="section"><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 <em>namespace definition</em> in -the first line assigns the namespace <em>http://www.my.com/acct-REV10</em> 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 <em>http://www.my.com/acct-REV10.</em> 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="section"><h4 class="sectiontitle">XML schemas and namespaces</h4><p>In the following XML -schema, the default namespace for the schema is defined as the standard XML -schema namespace <em>http://www.w3.org/2001/XMLSchem</em>a; there is also a -schema specific namespace <em>http://www.ibm.com</em>.</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 preceding XML schema 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="section"><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 examples -show how target namespaces and namespace prefixes work in XML schemas and -their corresponding XML instance documents.</p> -</div> - -<div class="section"><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 <em>unqualified</em>.</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 <em>"name"</em> element) -and attributes are unqualified in an XML file, then only the root element -is qualified. So, in this example, the <em>"x"</em> namespace prefix is assigned -to the root element <em>"MyAddress"</em>, associating it with the namespace <em>"http://www.ibm.com",</em> but -the<em>"x"</em> prefix is not assigned to the local element <em>"name"</em>.</p> -</div> - -<div class="section"><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 <em>qualified</em> 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 <em>"x"</em> namespace -prefix is assigned to both the root element <em>"MyAddress"</em> and the local -element <em>"name"</em>, associating them with the namespace <em>"http://www.ibm.com",</em>.</p> -</div> - -<div class="section"><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.</p> -<p>All -user defined types belong to the namespace http://www.ibm.com as defined -by the targetNamespace attribute, and the prefix is <em>"x"</em> 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 <em>unqualified</em>. -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="section"><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 <em>"xsd"</em>. The definitions and declarations -from this schema such as <em>AddressType</em> 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 <em>unqualified</em>.</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="section"><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> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.dita deleted file mode 100644 index 97d9893195..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.dita +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="rrefintg" xml:lang="en-us">
-<title>Referential integrity in the XML schema editor</title>
-<titlealts>
-<searchtitle>Referential integrity</searchtitle>
-</titlealts>
-<shortdesc>The XML schema editor has a built-in mechanism to handle referential
-integrity issues. When you delete certain nodes, clean up for any nodes affected
-will automatically occur.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>referential integrity</indexterm></indexterm>
-<indexterm>XML schema editor<indexterm>clean up in</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<refbody>
-<section>When you define a complex type, you can add a content model to it
-and reference a global element. <p>For example:<codeblock><schema>
- <element name="comment" type="string">
- <complexType name="Items">
- <sequence>
- <element ref="comment">
- </sequence>
- </complexType>
-</schema></codeblock></p><p>If the global element (comment) was deleted,
-all references to it would be in error. However, when you delete the global
-element, the XML schema editor will clean up using the following algorithm:</p><ul>
-<li>If there are one or more global elements in the schema, it will change
-all existing references to the first global element.</li>
-<li>If there is no global element, then it will delete the element reference
-from the content model.</li>
-</ul></section>
-<section><title>Deleting included and imported schema</title><p>If an included
-or imported schema is deleted, you must manually reset the following type
-references as appropriate: <ul>
-<li>Global element and element's type</li>
-<li>Attribute type</li>
-<li>Complex type derivation</li>
-<li>Simple type derivation </li>
-</ul>They will not automatically be reset if an included or imported schema
-is deleted.</p></section>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html deleted file mode 100644 index e319a3bdd8..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html +++ /dev/null @@ -1,88 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Referential integrity in the XML schema editor" /> -<meta name="abstract" content="The XML schema editor has a built-in mechanism to handle referential integrity issues. When you delete certain nodes, clean up for any nodes affected will automatically occur." /> -<meta name="description" content="The XML schema editor has a built-in mechanism to handle referential integrity issues. When you delete certain nodes, clean up for any nodes affected will automatically occur." /> -<meta content="XML schema editor, referential integrity, clean up in" name="DC.subject" /> -<meta content="XML schema editor, referential integrity, clean up in" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tdelscmp.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rrefintg" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Referential integrity</title> -</head> -<body id="rrefintg"><a name="rrefintg"><!-- --></a> - - -<h1 class="topictitle1">Referential integrity in the XML schema editor</h1> - - - - -<div><p>The XML schema editor has a built-in mechanism to handle referential -integrity issues. When you delete certain nodes, clean up for any nodes affected -will automatically occur.</p> - -<div class="section">When you define a complex type, you can add a content model to it -and reference a global element. <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. However, when you delete the global -element, the XML schema editor will clean up using the following algorithm:</p> -<ul> -<li>If there are one or more global elements in the schema, it will change -all existing references to the first global element.</li> - -<li>If there is no global element, then it will delete the element reference -from the content model.</li> - -</ul> -</div> - -<div class="section"><h4 class="sectiontitle">Deleting included and imported schema</h4><div class="p">If an included -or imported schema is deleted, you must manually reset the following type -references as appropriate: <ul> -<li>Global element and element's type</li> - -<li>Attribute type</li> - -<li>Complex type derivation</li> - -<li>Simple type derivation </li> - -</ul> -They will not automatically be reset if an included or imported schema -is deleted.</div> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div> -<div><a href="../topics/tdelscmp.html" title="If you have created any XML schema components you no longer need, you can delete them.">Deleting XML schema components</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.dita deleted file mode 100644 index 284014b314..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.dita +++ /dev/null @@ -1,140 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
- "reference.dtd">
-<reference id="ricons" xml:lang="en-us"><?Pub Caret1?>
-<title>Icons used in the XML schema editor</title>
-<titlealts>
-<searchtitle>XML schema editor icons</searchtitle>
-</titlealts>
-<shortdesc>The following XML schema editor icons appear in the Outline, Design,
-and Properties view.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>icons</indexterm></indexterm>
-<indexterm>Icons<indexterm>XML schema editor</indexterm></indexterm></keywords>
-</metadata></prolog>
-<refbody>
-<section></section>
-<table>
-<tgroup cols="2"><colspec colname="COLSPEC0"/><colspec colname="COLSPEC1"/>
-<tbody>
-<row>
-<entry colname="COLSPEC0" valign="bottom"><b>Icon</b></entry>
-<entry colname="COLSPEC1" valign="bottom"><b>Description</b></entry>
-</row>
-<row>
-<entry><image href="../images/XSDAnyAttribute.gif"><alt>This graphic is the
-any attribute icon </alt></image></entry>
-<entry><codeph>any</codeph> attribute</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAny.gif"><alt>This graphic is the any element
-icon </alt></image></entry>
-<entry><codeph>any</codeph> element</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAttribute.gif"><alt>This graphic is the attribute
-icon </alt></image></entry>
-<entry>attribute</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAttributeGroup.gif"><alt>This graphic is
-the attribute group icon </alt></image></entry>
-<entry>attribute group</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAttributeGroupRef.gif"><alt>This graphic
-is the attribute group reference icon </alt></image></entry>
-<entry>attribute group reference</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAttributeRef.gif"><alt>This graphic is the
-attribute reference icon </alt></image></entry>
-<entry>attribute reference</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAll.gif"><alt>This graphic is the content
-model - all icon </alt></image></entry>
-<entry>content model - all</entry>
-</row>
-<row>
-<entry colname="COLSPEC0"><image href="../images/XSDChoice.gif"><alt>This
-graphic is the content model - choice icon </alt></image></entry>
-<entry colname="COLSPEC1">content model - choice</entry>
-</row>
-<row>
-<entry colname="COLSPEC0"><image href="../images/XSDSequence.gif"><alt>This
-graphic is the content model - sequence icon </alt></image></entry>
-<entry colname="COLSPEC1">content model - sequence</entry>
-</row>
-<row>
-<entry><image href="../images/XSDComplexType.gif"><alt>This graphic is the
-any element icon </alt></image></entry>
-<entry>complex type</entry>
-</row>
-<row>
-<entry><image href="../images/XSDElement.gif"><alt>This graphic is the element
-icon </alt></image></entry>
-<entry>element</entry>
-</row>
-<row>
-<entry><image href="../images/XSDElementRef.gif"><alt>This graphic is the
-element reference icon </alt></image></entry>
-<entry>element reference</entry>
-</row>
-<row>
-<entry><image href="../images/XSDSimpleEnum.gif"><alt>This graphic is the
-enumeration icon </alt></image></entry>
-<entry>enumeration</entry>
-</row>
-<row>
-<entry><image href="../images/XSDGlobalAttribute.gif"><alt>This graphic is
-the global attribute icon </alt></image></entry>
-<entry>global attribute</entry>
-</row>
-<row>
-<entry> <image href="../images/XSDGlobalElement.gif"><alt>This graphic is
-the global element icon </alt></image></entry>
-<entry>global element</entry>
-</row>
-<row>
-<entry> <image href="../images/XSDGroup.gif"><alt>This graphic is the group
-icon </alt></image></entry>
-<entry>group</entry>
-</row>
-<row>
-<entry><image href="../images/XSDGroupRef.gif"><alt>This graphic is the group
-reference icon </alt></image></entry>
-<entry>group reference</entry>
-</row>
-<row>
-<entry><image href="../images/XSDImport.gif"><alt>This graphic is the import
-icon </alt></image></entry>
-<entry>import</entry>
-</row>
-<row>
-<entry><image href="../images/XSDInclude.gif"><alt>This graphic is the include
-icon </alt></image></entry>
-<entry>include</entry>
-</row>
-<row>
-<entry><image href="../images/XSDSimplePattern.gif"><alt>This graphic is the
-pattern icon </alt></image></entry>
-<entry>pattern</entry>
-</row>
-<row>
-<entry><image href="../images/XSDRedefine.gif"><alt>This graphic is the redefine
-icon </alt></image></entry>
-<entry>redefine</entry>
-</row>
-<row>
-<entry><image href="../images/XSDSimpleType.gif"><alt>This graphic is the
-simple type icon </alt></image></entry>
-<entry>simple type</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-</refbody>
-</reference>
-<?Pub *0000004581?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html deleted file mode 100644 index 92f68a6e8b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html +++ /dev/null @@ -1,209 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Icons used in the XML schema editor" /> -<meta name="abstract" content="The following XML schema editor icons appear in the Outline, Design, and Properties view." /> -<meta name="description" content="The following XML schema editor icons appear in the Outline, Design, and Properties view." /> -<meta content="XML schema editor, icons, Icons" name="DC.subject" /> -<meta content="XML schema editor, icons, Icons" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ricons" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML schema editor icons</title> -</head> -<body id="ricons"><a name="ricons"><!-- --></a> - - -<h1 class="topictitle1">Icons used in the XML schema editor</h1> - - - - -<div><p>The following XML schema editor icons appear in the Outline, Design, -and Properties view.</p> - -<div class="section" /> - - -<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> -<tbody> -<tr> -<td valign="bottom"><strong>Icon</strong></td> - -<td valign="bottom"><strong>Description</strong></td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAnyAttribute.gif" alt="This graphic is the any attribute icon " /></td> - -<td valign="top"><samp class="codeph">any</samp> attribute</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAny.gif" alt="This graphic is the any element icon " /></td> - -<td valign="top"><samp class="codeph">any</samp> element</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAttribute.gif" alt="This graphic is the attribute icon " /></td> - -<td valign="top">attribute</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAttributeGroup.gif" alt="This graphic is the attribute group icon " /></td> - -<td valign="top">attribute group</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAttributeGroupRef.gif" alt="This graphic is the attribute group reference icon " /></td> - -<td valign="top">attribute group reference</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAttributeRef.gif" alt="This graphic is the attribute reference icon " /></td> - -<td valign="top">attribute reference</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAll.gif" alt="This graphic is the content model - all icon " /></td> - -<td valign="top">content model - all</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDChoice.gif" alt="This graphic is the content model - choice icon " /></td> - -<td valign="top">content model - choice</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDSequence.gif" alt="This graphic is the content model - sequence icon " /></td> - -<td valign="top">content model - sequence</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDComplexType.gif" alt="This graphic is the any element icon " /></td> - -<td valign="top">complex type</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDElement.gif" alt="This graphic is the element icon " /></td> - -<td valign="top">element</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDElementRef.gif" alt="This graphic is the element reference icon " /></td> - -<td valign="top">element reference</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDSimpleEnum.gif" alt="This graphic is the enumeration icon " /></td> - -<td valign="top">enumeration</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDGlobalAttribute.gif" alt="This graphic is the global attribute icon " /></td> - -<td valign="top">global attribute</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/XSDGlobalElement.gif" alt="This graphic is the global element icon " /></td> - -<td valign="top">global element</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/XSDGroup.gif" alt="This graphic is the group icon " /></td> - -<td valign="top">group</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDGroupRef.gif" alt="This graphic is the group reference icon " /></td> - -<td valign="top">group reference</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDImport.gif" alt="This graphic is the import icon " /></td> - -<td valign="top">import</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDInclude.gif" alt="This graphic is the include icon " /></td> - -<td valign="top">include</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDSimplePattern.gif" alt="This graphic is the pattern icon " /></td> - -<td valign="top">pattern</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDRedefine.gif" alt="This graphic is the redefine icon " /></td> - -<td valign="top">redefine</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDSimpleType.gif" alt="This graphic is the simple type icon " /></td> - -<td valign="top">simple type</td> - -</tr> - -</tbody> - -</table> -</div> - -</div> - -<div /> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.dita deleted file mode 100644 index 17c19b2b8a..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.dita +++ /dev/null @@ -1,103 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="taddagrp" xml:lang="en-us">
-<title>Adding attribute groups</title>
-<titlealts>
-<searchtitle>Adding attribute groups</searchtitle>
-</titlealts>
-<shortdesc>An attribute group definition is an association between a name
-and a set of attribute declarations. Named groups of attribute declarations
-can greatly facilitate the maintenance and reuse of common attribute declarations
-in an XML schema.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>attribute
-groups</indexterm></indexterm></indexterm><indexterm>XML schema editor<indexterm>attributes
-groups<indexterm>adding</indexterm></indexterm></indexterm><indexterm>XML
-schema files<indexterm>adding<indexterm>attribute groups</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>attributes groups<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><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></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, right-click the <uicontrol>Attribute Groups</uicontrol> folder
-and click <uicontrol>Add Attribute Group</uicontrol>.</cmd><info>It appears
-in the <uicontrol>Attribute Groups</uicontrol> folder.</info></step>
-<step><cmd>Select your new group, and in the Design view, right-click the
-attribute group and select <menucascade><uicontrol>Refactor</uicontrol><uicontrol>Rename</uicontrol>
-</menucascade>. In the <uicontrol>New Name</uicontrol> field, type a name
-for the attribute group.</cmd></step>
-<step><cmd>To add an attribute, right-click your attribute group in the Outline
-view, click <uicontrol>Add Attribute</uicontrol>.</cmd><info>The attribute
-appears below the attribute group in the Outline view.</info>
-<substeps>
-<substep><cmd>Select the attribute, and in the Design view, click the current
-(default) name of the attribute, then type the new <uicontrol>Name</uicontrol>.</cmd>
-</substep>
-<substep><cmd>In the Design view, click the current (default) attribute type
-and select a type from the menu. Alternately, you can select browse to invoke
-the Set Type menu for more options.</cmd><info>The Set Type dialog lists all
-built-in and user-defined types currently available. You can change the <uicontrol>Scope</uicontrol> of
-the list by selecting one of the following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace. </li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file. </li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></info></substep>
-</substeps>
-</step>
-<step><cmd>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, in the Design view, right-click the complex
-type containing the element, and click <uicontrol>Add Attribute Ref</uicontrol>.</cmd>
-<info>A declaration that references a global attribute enables the referenced
-attribute to appear in the instance document in the context of the referencing
-declaration. Select the reference, then select the attribute group you want
-it to reference in the Properties view, from the<uicontrol>Ref</uicontrol> menu.</info>
-</step>
-<step><cmd>An attribute group reference provides a reference to an attribute
-group. To add an attribute group reference, in the Design view, right-click
-the complex type containing the element, and click <uicontrol>Add Attribute
-Group Ref</uicontrol>.</cmd><info>A declaration that references a global attribute
-enables the referenced attribute to appear in the instance document in the
-context of the referencing declaration. Select the reference, then select
-the attribute group you want it to reference in the Properties view, from
-the<uicontrol>Ref</uicontrol> menu.</info></step>
-<step><cmd>An <codeph>any</codeph> element enables element content according
-to namespaces, and the corresponding <codeph>any</codeph> attribute element
-enables attributes to appear in elements. To add an <codeph>any</codeph> attribute,
-right-click your attribute group and click <uicontrol>Add Any Attribute</uicontrol>.</cmd>
-<info>The <codeph>any</codeph> appears below the attribute group in the Outline
-view. You can specify the following values for an <codeph>any</codeph> attribute:</info>
-<choices>
-<choice>For a <uicontrol>namespace</uicontrol><?Pub Caret?> value, you can
-select:<ul>
-<li><b>##any</b>. This allows any well-formed XML from any namespace.</li>
-<li><b>##local </b>. This allows any well-formed XML that is not declared
-to be in a namespace.</li>
-<li><b>##other</b>. This allows any well-formed XML that is not from the target
-namespace of the type being defined.</li>
-<li><b>##targetNamespace </b>. This is shorthand for the target namespace
-of the type being defined.</li>
-</ul></choice>
-<choice>For a <uicontrol>processContents</uicontrol> value, you can select:<ul>
-<li><b>skip</b>. The XML processor will not validate the attribute content
-at all.</li>
-<li><b>lax</b>. The XML processor will validate the attribute content as much
-as it can.</li>
-<li><b>strict</b>. The XML processor will validate all the attribute content.</li>
-</ul></choice>
-</choices>
-</step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000005769?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html deleted file mode 100644 index 500b3b01b8..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html +++ /dev/null @@ -1,148 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding attribute groups" /> -<meta name="abstract" content="An attribute group definition is an association between a name and a set of attribute declarations. Named groups of attribute declarations can greatly facilitate the maintenance and reuse of common attribute declarations in an XML schema." /> -<meta name="description" content="An attribute group definition is an association between a name and a set of attribute declarations. Named groups of attribute declarations can greatly facilitate the maintenance and reuse of common attribute declarations in an XML schema." /> -<meta content="XML schema editor, adding, attribute groups, attributes groups, XML schema files, attribute groups, XML schema files, attributes groups" name="DC.subject" /> -<meta content="XML schema editor, adding, attribute groups, attributes groups, XML schema files, attribute groups, XML schema files, attributes groups" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddagrp" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding attribute groups</title> -</head> -<body id="taddagrp"><a name="taddagrp"><!-- --></a> - - -<h1 class="topictitle1">Adding attribute groups</h1> - - - - -<div><p>An attribute group definition is an association between a name -and a set of attribute declarations. Named groups of attribute declarations -can greatly facilitate the maintenance and reuse of common attribute declarations -in an XML schema.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add an attribute -group to an XML schema, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, right-click the <span class="uicontrol">Attribute Groups</span> folder -and click <span class="uicontrol">Add Attribute Group</span>.</span> It appears -in the <span class="uicontrol">Attribute Groups</span> folder.</li> - -<li class="stepexpand"><span>Select your new group, and in the Design view, right-click the -attribute group and select <span class="menucascade"><span class="uicontrol">Refactor</span> > <span class="uicontrol">Rename</span> -</span>. In the <span class="uicontrol">New Name</span> field, type a name -for the attribute group.</span></li> - -<li class="stepexpand"><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="substepexpand"><span>Select the attribute, and in the Design view, click the current -(default) name of the attribute, then type the new <span class="uicontrol">Name</span>.</span> -</li> - -<li class="substepexpand"><span>In the Design view, click the current (default) attribute type -and select a type from the menu. Alternately, you can select browse to invoke -the Set Type menu for more options.</span> The Set Type dialog lists all -built-in and user-defined types currently available. You can change the <span class="uicontrol">Scope</span> of -the list by selecting one of the following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace. </li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file. </li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>An attribute reference provides a reference to a global attribute. -To add an attribute reference, in the Design view, right-click the complex -type containing the element, and click <span class="uicontrol">Add Attribute Ref</span>.</span> - A declaration that references a global attribute enables the referenced -attribute to appear in the instance document in the context of the referencing -declaration. Select the reference, then select the attribute group you want -it to reference in the Properties view, from the<span class="uicontrol">Ref</span> menu. -</li> - -<li class="stepexpand"><span>An attribute group reference provides a reference to an attribute -group. To add an attribute group reference, in the Design view, right-click -the complex type containing the element, and click <span class="uicontrol">Add Attribute -Group Ref</span>.</span> A declaration that references a global attribute -enables the referenced attribute to appear in the instance document in the -context of the referencing declaration. Select the reference, then select -the attribute group you want it to reference in the Properties view, from -the<span class="uicontrol">Ref</span> menu.</li> - -<li class="stepexpand"><span>An <samp class="codeph">any</samp> element enables element content according -to namespaces, and the corresponding <samp class="codeph">any</samp> attribute element -enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute, -right-click 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 <span class="uicontrol">namespace</span> value, you can -select:<ul> -<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li> - -<li><strong>##local </strong>. This allows any well-formed XML that is not declared -to be in a namespace.</li> - -<li><strong>##other</strong>. This allows any well-formed XML that is not from the target -namespace of the type being defined.</li> - -<li><strong>##targetNamespace </strong>. This is shorthand for the target namespace -of the type being defined.</li> - -</ul> -</li> - -<li>For a <span class="uicontrol">processContents</span> value, you can select:<ul> -<li><strong>skip</strong>. The XML processor will not validate the attribute content -at all.</li> - -<li><strong>lax</strong>. The XML processor will validate the attribute content as much -as it can.</li> - -<li><strong>strict</strong>. The XML processor will validate all the attribute content.</li> - -</ul> -</li> - -</ul> - -</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.dita deleted file mode 100644 index 702582d1b2..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.dita +++ /dev/null @@ -1,78 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddanye" xml:lang="en-us">
-<title>Adding an any element</title>
-<titlealts>
-<searchtitle>Adding an any element</searchtitle>
-</titlealts>
-<shortdesc>You can use the <codeph>any</codeph> element in a similar way as
-a DTD's ANY content model, however, it must be done in conjunction with namespaces.
-This enables you to include any well-formed XML content, such as an HTML Web
-page that conforms to XHTML 1.0 syntax.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>an any element</indexterm></indexterm></indexterm>
-<indexterm>XML schema editor<indexterm>an any element<indexterm>adding</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>adding<indexterm>an any element</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>an any element<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>For example:</p><p><codeblock><element name = "MyWebPage">
-<complexType>
-<any namespace ="http://www.w3.org/1999/xhtml>
- < minOccurs="1" maxOccurs="unbounded" processContents="skip"/>
-</complexType>
-</element></codeblock></p><p>The preceding schema fragment allows a <codeph><MyWebPage></codeph> 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 <codeph>any</codeph> element:</p></context>
-<steps>
-<step><cmd>In the Outline view, right-click the content model that you want
-to work with and click <uicontrol>Add Any</uicontrol>. </cmd></step>
-<step><cmd>Select the new <codeph>any</codeph> element.</cmd></step>
-<step><cmd>In the Properties view of the schema editor, for a <uicontrol>namespace</uicontrol> <?Pub Caret1?>value,
-you can select:</cmd>
-<choices>
-<choice><b>##any</b>. This allows any well-formed XML from any namespace.</choice>
-<choice><b>##local </b>. This allows any well-formed XML that is not declared
-to be in a namespace.</choice>
-<choice><b>##other </b>. This allows any well-formed XML that is not from
-the target namespace of the type being defined.</choice>
-<choice><b>##targetNamespace</b>. This is shorthand for the target namespace
-of the type being defined.</choice>
-</choices>
-</step>
-<step><cmd>For a <uicontrol>processContents</uicontrol> value, you can select:</cmd>
-<choices>
-<choice><b>skip</b>. The XML processor will not validate the content at all.</choice>
-<choice><b>lax</b>. The XML processor will validate the content as much as
-it can.</choice>
-<choice><b>strict</b>. The XML processor will validate all the content.</choice>
-</choices>
-</step>
-<step><cmd>The <uicontrol>minOccurs</uicontrol> value is the number of times
-the <codeph>any</codeph> element must appear in an instance document. You
-can select <uicontrol>0</uicontrol> if you want the element to be optional;
-otherwise, select <uicontrol>1</uicontrol>. </cmd></step>
-<step><cmd>The <uicontrol>maxOccurs</uicontrol> value is the maximum number
-of times an <codeph>any</codeph> element can appear in an instance document.
-You can select <uicontrol>0</uicontrol>, <uicontrol>1</uicontrol>, or, to
-indicate there is no maximum number of occurrences, <uicontrol>unbounded</uicontrol>.</cmd>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<postreq><p>(c) Copyright 2001, World Wide Web (Massachusetts Institute of
-Technology, Institut National de Recherche en Informatique et en Automatique,
-Keio University).</p></postreq>
-</taskbody>
-</task>
-<?Pub *0000004291?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html deleted file mode 100644 index 8540ecb118..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html +++ /dev/null @@ -1,119 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding an any element" /> -<meta name="abstract" content="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax." /> -<meta name="description" content="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax." /> -<meta content="XML schema editor, adding, an any element, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, an any element, XML schema files" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddanye" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding an any element</title> -</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 in a similar way as -a DTD's ANY content model, however, it must be done in conjunction with namespaces. -This enables you to include any well-formed XML content, such as an HTML Web -page that conforms to XHTML 1.0 syntax.</p> - -<div class="section"><p>For example:</p> -<div class="p"><pre><element name = "MyWebPage"> -<complexType> -<any namespace ="http://www.w3.org/1999/xhtml> - < minOccurs="1" maxOccurs="unbounded" processContents="skip"/> -</complexType> -</element></pre> -</div> -<p>The preceding schema fragment allows a <samp class="codeph"><MyWebPage></samp> element -to contain any well-formed XHTML data that appears in the specified namespace.</p> -<p>The -following instructions were written for the Resource perspective, but they -will also work in many other perspectives.</p> -<p>To add an <samp class="codeph">any</samp> element:</p> -</div> - -<ol> -<li class="stepexpand"><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="stepexpand"><span>Select the new <samp class="codeph">any</samp> element.</span></li> - -<li class="stepexpand"><span>In the Properties view of the schema editor, for a <span class="uicontrol">namespace</span> value, -you can select:</span> -<ul> -<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li> - -<li><strong>##local </strong>. This allows any well-formed XML that is not declared -to be in a namespace.</li> - -<li><strong>##other </strong>. This allows any well-formed XML that is not from -the target namespace of the type being defined.</li> - -<li><strong>##targetNamespace</strong>. This is shorthand for the target namespace -of the type being defined.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>For a <span class="uicontrol">processContents</span> value, you can select:</span> -<ul> -<li><strong>skip</strong>. The XML processor will not validate the content at all.</li> - -<li><strong>lax</strong>. The XML processor will validate the content as much as -it can.</li> - -<li><strong>strict</strong>. The XML processor will validate all the content.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>The <span class="uicontrol">minOccurs</span> value is the number of times -the <samp class="codeph">any</samp> element must appear in an instance document. You -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="stepexpand"><span>The <span class="uicontrol">maxOccurs</span> value is the maximum number -of times an <samp class="codeph">any</samp> element can appear in an instance document. -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="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section"><p>(c) Copyright 2001, World Wide Web (Massachusetts Institute of -Technology, Institut National de Recherche en Informatique et en Automatique, -Keio University).</p> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.dita deleted file mode 100644 index e283139f24..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.dita +++ /dev/null @@ -1,90 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddcmod" xml:lang="en-us">
-<title>Adding content models</title>
-<titlealts>
-<searchtitle>Adding content models</searchtitle>
-</titlealts>
-<shortdesc>A content model is the representation of any data that can be contained
-inside an element, global element, complex type, or group. It is a formal
-description of the structure and permissible content of an element, global
-element, complex type, or group, which may be used to validate a document
-instance.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>content
-models</indexterm></indexterm></indexterm><indexterm>XML schema editor<indexterm>content
-models<indexterm>adding</indexterm></indexterm></indexterm><indexterm>XML
-schema files<indexterm>adding<indexterm>content models</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>content models<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><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 can 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 can appear more than once.</li>
-</ul></p><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To add a content
-model to an element, global element, complex type, or group, follow these
-steps:</p></context>
-<steps>
-<step><cmd>In the Design view, select your complex type, or group:</cmd>
-<choices>
-<choice>If you selected a complex type, you can right-click it and click <uicontrol>Add
-Sequence</uicontrol>, or <uicontrol>Add Choice</uicontrol> to add the type
-of content model you want to your complex type. If you wish to use the <uicontrol>all</uicontrol> content
-model, you can change the model by clicking the model in the Design view,
-and in properties, select <uicontrol>all</uicontrol> as the <uicontrol>Kind</uicontrol>.
-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.</choice>
-<choice>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 <uicontrol>choice</uicontrol> or <uicontrol>all</uicontrol> content
-model by selecting these options from the <uicontrol>Kind</uicontrol> menu.</choice>
-</choices>
-</step>
-<step><cmd>(Optional) Select the appropriate value in the <uicontrol>MinOccurs</uicontrol> field.</cmd>
-<info>This is the minimum number of times the content model must appear. If
-you want the content model to be optional, select <uicontrol>0</uicontrol>.
-Otherwise, select <uicontrol>1</uicontrol>. </info></step>
-<step><cmd>(Optional) Select the appropriate value in the <uicontrol>MaxOccurs</uicontrol> field.</cmd>
-<info>This is the maximum number of times a content model can appear. You
-can select <uicontrol>unbounded</uicontrol> to indicate there is no maximum
-number of occurrences.</info></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this content model.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.<?Pub Caret?></info>
-</step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<postreq><p>You can add the following items 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 <codeph>any</codeph> element. You can use an <codeph>any</codeph> element
-to extend your content model by any elements belonging to a specified namespace.</li>
-</ul></postreq>
-</taskbody>
-</task>
-<?Pub *0000005317?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html deleted file mode 100644 index 1e0afe1e3b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html +++ /dev/null @@ -1,139 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding content models" /> -<meta name="abstract" content="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance." /> -<meta name="description" content="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance." /> -<meta content="XML schema editor, adding, content models, XML schema files, content models, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, content models, XML schema files, content models, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddanye.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddelm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddelmr.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddgrpr.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddcmod" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding content models</title> -</head> -<body id="taddcmod"><a name="taddcmod"><!-- --></a> - - -<h1 class="topictitle1">Adding content models</h1> - - - - -<div><p>A content model is the representation of any data that can be contained -inside an element, global element, complex type, or group. It is a formal -description of the structure and permissible content of an element, global -element, complex type, or group, which may be used to validate a document -instance.</p> - -<div class="section"><div class="p">There are three different kinds of content models:<ul> -<li><strong>Sequence</strong>, which means that all the content model's children can -appear in an instance of the XML schema. They must, however, appear in the -order they are listed in the content model.</li> - -<li><strong>Choice</strong>, which means that only one of the content model's children -can appear in an instance of the XML schema.</li> - -<li><strong>All</strong>, which means that all of the content model's children can appear -once or not at all, and they can 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 can 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 an element, global element, complex type, or group, follow these -steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, select your complex type, or group:</span> -<ul> -<li>If you selected a complex type, you can right-click it and click <span class="uicontrol">Add -Sequence</span>, or <span class="uicontrol">Add Choice</span> to add the type -of content model you want to your complex type. If you wish to use the <span class="uicontrol">all</span> content -model, you can change the model by clicking the model in the Design view, -and in properties, select <span class="uicontrol">all</span> as the <span class="uicontrol">Kind</span>. -Your content model is automatically added as a child of your complex type -- expand in the Outline view to see it. <strong>Note:</strong> These options will not -appear if you have set a base type for your complex type. You can either set -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> menu.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MinOccurs</span> field.</span> - This is the minimum number of times the content model must appear. If -you want the content model to be optional, select <span class="uicontrol">0</span>. -Otherwise, select <span class="uicontrol">1</span>. </li> - -<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MaxOccurs</span> field.</span> - This is the maximum number of times a content model can appear. You -can select <span class="uicontrol">unbounded</span> to indicate there is no maximum -number of occurrences.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this content model.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description. -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section"><p>You can add the following items to a content object model. </p> -<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> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddanye.html" title="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax.">Adding an any element</a></div> -<div><a href="../topics/taddelm.html" title="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements.">Adding elements</a></div> -<div><a href="../topics/taddelmr.html" title="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration.">Adding element references</a></div> -<div><a href="../topics/taddgrpr.html" title="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration.">Adding group references</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.dita deleted file mode 100644 index 3d1f73f467..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.dita +++ /dev/null @@ -1,108 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddcmxt" xml:lang="en-us">
-<title>Adding complex types</title>
-<titlealts>
-<searchtitle>Adding complex types</searchtitle>
-</titlealts>
-<shortdesc>A complex type allows elements in its content and can carry attributes.
-Complex types can be used to help determine the appropriate content for any
-instance documents generated from or associated with your XML schema.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>complex
-types</indexterm></indexterm></indexterm><indexterm>XML schema editor<indexterm>complex
-types<indexterm>adding</indexterm></indexterm></indexterm><indexterm>XML schema
-files<indexterm>adding<indexterm>complex types</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>complex types<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>You can add as many complex types as you want to an XML schema.</p><p>The
-following instructions were written for the Resource perspective, but they
-will also work in many other perspectives.</p><p>To add a complex type to
-an XML schema, follow these steps:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>Right-click the Types category in the Design view, and click <uicontrol>Add
-Complex Type</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, type a new name for the complex type in
-the <uicontrol>Name</uicontrol> field.</cmd></step>
-<step><cmd>Click <uicontrol>Browse</uicontrol> <image href="../images/Browse.gif">
-<alt>Browse icon</alt></image> to select a base type for your complex type.</cmd>
-<info>You can either set a base type for your complex type, or you can add
-a content model to it (which represents any data that can be contained inside
-an element), but you cannot do both. For more information about content models,
-refer to the related tasks.</info></step>
-<step><cmd>Select <uicontrol>restriction</uicontrol> or <uicontrol>extension</uicontrol> from
-the <uicontrol>Inherited by</uicontrol> list.</cmd><info>This specifies whether
-your type is derived from its base type by restriction or extension.</info>
-</step>
-<step><cmd>The Design view will display the attributes within the complex
-type.</cmd><info>You can also use this view to add attributes to your complex
-type. An attribute associates an attribute name with a specific type and value.</info>
-<choices>
-<choice>To add an attribute, in the Design view, right click your complex
-type and select <uicontrol>Add Attribute</uicontrol>.<ul>
-<li><uicontrol>name</uicontrol>. In the Design view, click the name of the
-attribute to make a change.</li>
-<li><uicontrol>type</uicontrol>. In the Design view, click the type of the
-attribute to make a change. The drop-down menu provides commonly used types.
-For more options, simply select <uicontrol>Browse</uicontrol> from the menu.</li>
-</ul></choice>
-</choices>
-</step>
-<step><cmd>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, in the Design view, right-click the complex
-type containing the element, and click <uicontrol>Add Attribute Ref</uicontrol>.</cmd>
-<info>A declaration that references a global attribute enables the referenced
-attribute to appear in the instance document in the context of the referencing
-declaration. Select the reference, then select the attribute group you want
-it to reference in the Properties view, from the<uicontrol> Ref</uicontrol> menu.</info>
-</step>
-<step><cmd>An attribute group reference provides a reference to an attribute
-group. To add an attribute group reference, in the Design view, right-click
-the complex type containing the element, and click <uicontrol>Add Attribute
-Group Ref</uicontrol>.</cmd><info>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. Select the reference, then
-select the attribute group you want it to reference in the Properties view,
-from the<uicontrol> Ref</uicontrol> menu.</info></step>
-<step><cmd>An <codeph>any</codeph> element enables element content according
-to namespaces, and the corresponding <codeph>any</codeph> attribute element
-enables attributes to appear in elements. To add an <codeph>any</codeph> attribute,
-right-click in the complex type header, and click <uicontrol>Add Any Attribute</uicontrol>.</cmd>
-<info>You can specify the following values for an <codeph>any</codeph> attribute:</info>
-<choices>
-<choice>For a <uicontrol>namespace</uicontrol> <?Pub Caret1?>value, you can
-select:<ul>
-<li><b>##any</b>. This allows any well-formed XML from any namespace.</li>
-<li><b>##local </b>. This allows any well-formed XML that is not declared
-to be in a namespace.</li>
-<li><b>##other</b>. This allows any well-formed XML that is not from the target
-namespace of the type being defined.</li>
-<li><b>##targetNamespace </b>. This is shorthand for the target namespace
-of the type being defined.</li>
-</ul></choice>
-<choice>For a <uicontrol>processContents</uicontrol> value, you can select:<ul>
-<li><b>skip</b>. The XML processor will not validate the attribute content
-at all.</li>
-<li><b>lax</b>. The XML processor will validate the attribute content as much
-as it can.</li>
-<li><b>strict</b>. The XML processor will validate all the attribute content.</li>
-</ul></choice>
-</choices>
-<info></info></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this complex type.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000006207?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html deleted file mode 100644 index 6204c408fd..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html +++ /dev/null @@ -1,158 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding complex types" /> -<meta name="abstract" content="A complex type allows elements in its content and can carry attributes. Complex types can be used to help determine the appropriate content for any instance documents generated from or associated with your XML schema." /> -<meta name="description" content="A complex type allows elements in its content and can carry attributes. Complex types can be used to help determine the appropriate content for any instance documents generated from or associated with your XML schema." /> -<meta content="XML schema editor, adding, complex types, XML schema files, complex types, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, complex types, XML schema files, complex types, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddcmxt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding complex types</title> -</head> -<body id="taddcmxt"><a name="taddcmxt"><!-- --></a> - - -<h1 class="topictitle1">Adding complex types</h1> - - - - -<div><p>A complex type allows elements in its content and can carry attributes. -Complex types can be used to help determine the appropriate content for any -instance documents generated from or associated with your XML schema.</p> - -<div class="section"><p>You can add as many complex types as you want to an XML schema.</p> -<p>The -following instructions were written for the Resource perspective, but they -will also work in many other perspectives.</p> -<p>To add a complex type to -an XML schema, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>Right-click the Types category in the Design view, and click <span class="uicontrol">Add -Complex Type</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, type a new name for the complex type in -the <span class="uicontrol">Name</span> field.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="Browse icon" /> to select a base type for your complex type.</span> - You can either set a base type for your complex type, or you can add -a content model to it (which represents any data that can be contained inside -an element), but you cannot do both. For more information about content models, -refer to the related tasks.</li> - -<li class="stepexpand"><span>Select <span class="uicontrol">restriction</span> or <span class="uicontrol">extension</span> from -the <span class="uicontrol">Inherited by</span> list.</span> This specifies whether -your type is derived from its base type by restriction or extension. -</li> - -<li class="stepexpand"><span>The Design view will display the attributes within the complex -type.</span> You can also use this view to add attributes to your complex -type. An attribute associates an attribute name with a specific type and value. -<ul> -<li>To add an attribute, in the Design view, right click your complex -type and select <span class="uicontrol">Add Attribute</span>.<ul> -<li><span class="uicontrol">name</span>. In the Design view, click the name of the -attribute to make a change.</li> - -<li><span class="uicontrol">type</span>. In the Design view, click the type of the -attribute to make a change. The drop-down menu provides commonly used types. -For more options, simply select <span class="uicontrol">Browse</span> from the menu.</li> - -</ul> -</li> - -</ul> - -</li> - -<li class="stepexpand"><span>An attribute reference provides a reference to a global attribute. -To add an attribute reference, in the Design view, right-click the complex -type containing the element, and click <span class="uicontrol">Add Attribute Ref</span>.</span> - A declaration that references a global attribute enables the referenced -attribute to appear in the instance document in the context of the referencing -declaration. Select the reference, then select the attribute group you want -it to reference in the Properties view, from the<span class="uicontrol"> Ref</span> menu. -</li> - -<li class="stepexpand"><span>An attribute group reference provides a reference to an attribute -group. To add an attribute group reference, in the Design view, right-click -the complex type containing the element, and click <span class="uicontrol">Add Attribute -Group Ref</span>.</span> A declaration that references an attribute -group enables the referenced attribute group to appear in the instance document -in the context of the referencing declaration. Select the reference, then -select the attribute group you want it to reference in the Properties view, -from the<span class="uicontrol"> Ref</span> menu.</li> - -<li class="stepexpand"><span>An <samp class="codeph">any</samp> element enables element content according -to namespaces, and the corresponding <samp class="codeph">any</samp> attribute element -enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute, -right-click in the complex type header, and click <span class="uicontrol">Add Any Attribute</span>.</span> - You can specify the following values for an <samp class="codeph">any</samp> attribute: -<ul> -<li>For a <span class="uicontrol">namespace</span> value, you can -select:<ul> -<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li> - -<li><strong>##local </strong>. This allows any well-formed XML that is not declared -to be in a namespace.</li> - -<li><strong>##other</strong>. This allows any well-formed XML that is not from the target -namespace of the type being defined.</li> - -<li><strong>##targetNamespace </strong>. This is shorthand for the target namespace -of the type being defined.</li> - -</ul> -</li> - -<li>For a <span class="uicontrol">processContents</span> value, you can select:<ul> -<li><strong>skip</strong>. The XML processor will not validate the attribute content -at all.</li> - -<li><strong>lax</strong>. The XML processor will validate the attribute content as much -as it can.</li> - -<li><strong>strict</strong>. The XML processor will validate all the attribute content.</li> - -</ul> -</li> - -</ul> - - </li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this complex type.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.dita deleted file mode 100644 index 1a0099942e..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.dita +++ /dev/null @@ -1,71 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddelm" xml:lang="en-us">
-<title>Adding elements</title>
-<titlealts>
-<searchtitle>Adding elements</searchtitle>
-</titlealts>
-<shortdesc>Elements are fundamental building blocks in XML. Element declarations
-provide value constraints, provide a description that can be used for validation,
-establish constraining relationships between related elements and attributes,
-and control the substitution of elements.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>elements</indexterm></indexterm></indexterm>
-<indexterm>XML schema editor<indexterm>elements<indexterm>adding</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>adding<indexterm>elements</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>elements<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><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:</p></context>
-<steps>
-<step><cmd>To add an element, in the Design view, right-click the content
-model you want to work with and click <uicontrol>Add Element</uicontrol>.</cmd>
-<info>The element appears attached to the content model in the Design view.</info>
-<substeps>
-<substep><cmd>In the Design view, select the element, and click the current
-(default) name of the element, which puts you in direct editing mode, then
-type the new <uicontrol>Name</uicontrol> and press enter.</cmd></substep>
-<substep><cmd>In the Design view, click the current (default) element type
-and select a type from the menu. Alternately, you can select browse to invoke
-the Set Type dialog for more options.</cmd><info>The Set Type dialog lists
-all built-in and user-defined types currently available. You can change the <uicontrol>Scope</uicontrol> of
-the list by selecting one of the following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace. </li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file. </li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></info></substep>
-</substeps>
-</step>
-<step><cmd>(Optional) In the Properties view, select the appropriate value
-in the <uicontrol>MinOccurs</uicontrol> field.</cmd><info>This is the <?Pub Caret?>number
-of times the element can appear in an instance document. If you want the element
-to be optional, select <uicontrol>0</uicontrol>. Otherwise, select <uicontrol>1</uicontrol>. </info>
-</step>
-<step><cmd>(Optional) Select the appropriate value in the <uicontrol>MaxOccurs</uicontrol> field.</cmd>
-<info>This is the maximum number of times the element can appear in an instance
-document. Select <uicontrol>unbounded</uicontrol> to indicate there is no
-maximum number of occurrences.</info></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<postreq>You can add a content model to an element, which is the representation
-of any data that can be contained inside the element. For more information
-about working with content models, refer to the related tasks.</postreq>
-</taskbody>
-</task>
-<?Pub *0000004079?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html deleted file mode 100644 index f669f1ce02..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html +++ /dev/null @@ -1,114 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding elements" /> -<meta name="abstract" content="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements." /> -<meta name="description" content="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements." /> -<meta content="XML schema editor, adding, elements, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, elements, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddelmr.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddanye.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddglba.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddelm" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding elements</title> -</head> -<body id="taddelm"><a name="taddelm"><!-- --></a> - - -<h1 class="topictitle1">Adding elements</h1> - - - - -<div><p>Elements are fundamental building blocks in XML. Element declarations -provide value constraints, provide a description that can be used for validation, -establish constraining relationships between related elements and attributes, -and control the substitution of elements.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add an element:</p> -</div> - -<ol> -<li class="stepexpand"><span>To add an element, in the Design view, right-click the content -model you want to work with and click <span class="uicontrol">Add Element</span>.</span> - The element appears attached to the content model in the Design view. -<ol type="a"> -<li class="substepexpand"><span>In the Design view, select the element, and click the current -(default) name of the element, which puts you in direct editing mode, then -type the new <span class="uicontrol">Name</span> and press enter.</span></li> - -<li class="substepexpand"><span>In the Design view, click the current (default) element type -and select a type from the menu. Alternately, you can select browse to invoke -the Set Type dialog for more options.</span> The Set Type dialog lists -all built-in and user-defined types currently available. You can change the <span class="uicontrol">Scope</span> of -the list by selecting one of the following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace. </li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file. </li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>(Optional) In the Properties view, select the appropriate value -in the <span class="uicontrol">MinOccurs</span> field.</span> This is the number -of times the element can appear in an instance document. If you want the element -to be optional, select <span class="uicontrol">0</span>. Otherwise, select <span class="uicontrol">1</span>. -</li> - -<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MaxOccurs</span> field.</span> - This is the maximum number of times the element can appear in an instance -document. Select <span class="uicontrol">unbounded</span> to indicate there is no -maximum number of occurrences.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section">You can add a content model to an element, which is the representation -of any data that can be contained inside the element. For more information -about working with content models, refer to the related tasks.</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div> -<div><a href="../topics/taddelmr.html" title="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration.">Adding element references</a></div> -<div><a href="../topics/taddanye.html" title="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax.">Adding an any element</a></div> -<div><a href="../topics/taddglba.html" title="A global attribute is an attribute that can be recognized anywhere in a document. Once declared, a global attribute can be referenced in one or more declarations using an attribute reference.">Adding global attributes</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.dita deleted file mode 100644 index f2d6675c01..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.dita +++ /dev/null @@ -1,60 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddelmr" xml:lang="en-us">
-<title>Adding element references</title>
-<titlealts>
-<searchtitle>Adding element references</searchtitle>
-</titlealts>
-<shortdesc>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.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>element
-references</indexterm></indexterm></indexterm><indexterm>XML schema editor<indexterm>element
-references<indexterm>adding</indexterm></indexterm></indexterm><indexterm>XML
-schema files<indexterm>adding<indexterm>element references</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>element references<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><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:</p></context>
-<steps>
-<step><cmd>In the Design view, right-click the content model you want to work
-with and click <uicontrol>Add Element Ref</uicontrol>.</cmd><stepresult>If
-no global element is defined in the document, a new global element is created
-for you, and the element reference will point to it.</stepresult></step>
-<step><cmd>Select the element reference. To specify values for an element
-reference:</cmd>
-<choices>
-<choice>Click the name of the element reference in the Design view. Enter
-the name of the element reference.</choice>
-<choice>Click the element reference type in the Design<?Pub Caret?> view.
-Select a type from the menu, or select <uicontrol>Browse</uicontrol> for more
-options.</choice>
-</choices>
-</step>
-<step><cmd>(Optional) Select the appropriate value in the <uicontrol>MinOccurs</uicontrol> field.</cmd>
-<info>This is the number of times the global element referenced can appear
-in an instance document. If you want the element to be optional, select <uicontrol>0</uicontrol>.
-Otherwise, select <uicontrol>1</uicontrol>. </info></step>
-<step><cmd>(Optional) Select the appropriate value in the <uicontrol>MaxOccurs</uicontrol> field.</cmd>
-<info>This is the maximum number of times the global element referenced can
-appear. You can select <uicontrol>unbounded</uicontrol> to indicate there
-is no maximum number of occurrences.</info></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this element reference.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000003232?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html deleted file mode 100644 index 40177eb6a0..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html +++ /dev/null @@ -1,97 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding element references" /> -<meta name="abstract" content="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration." /> -<meta name="description" content="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration." /> -<meta content="XML schema editor, adding, element references, XML schema files, element references, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, element references, XML schema files, element references, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddglem.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddelm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddanye.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddglba.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddelmr" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding element references</title> -</head> -<body id="taddelmr"><a name="taddelmr"><!-- --></a> - - -<h1 class="topictitle1">Adding element references</h1> - - - - -<div><p>An element reference provides a reference to a global element. -A declaration that references a global element enables the referenced global -element to appear in the instance document in the context of the referencing -declaration.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add an element -reference:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, right-click the content model you want to work -with and click <span class="uicontrol">Add Element Ref</span>.</span> If -no global element is defined in the document, a new global element is created -for you, and the element reference will point to it.</li> - -<li class="stepexpand"><span>Select the element reference. To specify values for an element -reference:</span> -<ul> -<li>Click the name of the element reference in the Design view. Enter -the name of the element reference.</li> - -<li>Click the element reference type in the Design view. -Select a type from the menu, or select <span class="uicontrol">Browse</span> for more -options.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MinOccurs</span> field.</span> - This is the number of times the global element referenced can appear -in an instance document. If you want the element to be optional, select <span class="uicontrol">0</span>. -Otherwise, select <span class="uicontrol">1</span>. </li> - -<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MaxOccurs</span> field.</span> - This is the maximum number of times the global element referenced can -appear. You can select <span class="uicontrol">unbounded</span> to indicate there -is no maximum number of occurrences.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this element reference.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddglem.html" title="A global element is an element with a global scope. It is one that has been declared as part of the main schema rather than as part of a content model.">Adding global elements</a></div> -<div><a href="../topics/taddelm.html" title="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements.">Adding elements</a></div> -<div><a href="../topics/taddanye.html" title="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax.">Adding an any element</a></div> -<div><a href="../topics/taddglba.html" title="A global attribute is an attribute that can be recognized anywhere in a document. Once declared, a global attribute can be referenced in one or more declarations using an attribute reference.">Adding global attributes</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.dita deleted file mode 100644 index f975e1cceb..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.dita +++ /dev/null @@ -1,57 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddglba" xml:lang="en-us">
-<title>Adding global attributes</title>
-<titlealts>
-<searchtitle>Adding global attributes</searchtitle>
-</titlealts>
-<shortdesc>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.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>global attributes</indexterm></indexterm></indexterm>
-<indexterm>XML schema editor<indexterm>global attributes<indexterm>adding</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>adding<indexterm>global attributes</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>global attributes<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><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:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Design view, right-click in the <b>Attributes</b> section
-and click <uicontrol>Add Attribute</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, enter a name for the attribute in the <uicontrol>Name</uicontrol> field.</cmd>
-</step>
-<step><cmd>In the Properties view, you can select the attribute <uicontrol>Type</uicontrol> from
-the predefined list in the menu next to the <uicontrol>Type</uicontrol> field.</cmd>
-<info><p>Alternatively<?Pub Caret?>, you can select <uicontrol>Browse</uicontrol> from
-the list for more options. </p><p>The Set Type dialog will appear, and lists
-all built-in and user-defined types currently available. You can change the <uicontrol>Scope</uicontrol> of
-the list by selecting one of the following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace. </li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file. </li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></p><p>Select the type you want in the type list, then click <uicontrol>OK</uicontrol>. </p></info>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this global attribute.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000003230?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html deleted file mode 100644 index 29b0abfecf..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html +++ /dev/null @@ -1,89 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding global attributes" /> -<meta name="abstract" content="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." /> -<meta name="description" content="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." /> -<meta content="XML schema editor, adding, global attributes, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, global attributes, XML schema files" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddglba" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding global attributes</title> -</head> -<body id="taddglba"><a name="taddglba"><!-- --></a> - - -<h1 class="topictitle1">Adding global attributes</h1> - - - - -<div><p>A global attribute is an attribute that can be recognized anywhere -in a document. Once declared, a global attribute can be referenced in one -or more declarations using an attribute reference.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add a global -attribute:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Design view, right-click in the <strong>Attributes</strong> section -and click <span class="uicontrol">Add Attribute</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, enter a name for the attribute in the <span class="uicontrol">Name</span> field.</span> -</li> - -<li class="stepexpand"><span>In the Properties view, you can select the attribute <span class="uicontrol">Type</span> from -the predefined list in the menu next to the <span class="uicontrol">Type</span> field.</span> - <p>Alternatively, you can select <span class="uicontrol">Browse</span> from -the list for more options. </p> -<div class="p">The Set Type dialog will appear, and lists -all built-in and user-defined types currently available. You can change the <span class="uicontrol">Scope</span> of -the list by selecting one of the following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace. </li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file. </li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</div> -<p>Select the type you want in the type list, then click <span class="uicontrol">OK</span>. </p> - -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this global attribute.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.dita deleted file mode 100644 index 6e0139d351..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.dita +++ /dev/null @@ -1,159 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddglem" xml:lang="en-us">
-<title>Adding global elements</title>
-<titlealts>
-<searchtitle>Adding global elements</searchtitle>
-</titlealts>
-<shortdesc>A global element is an element with a global scope. It is one that
-has been declared as part of the main schema rather than as part of a content
-model.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>global elements</indexterm></indexterm></indexterm>
-<indexterm>XML schema editor<indexterm>global elements<indexterm>adding</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>adding<indexterm>global elements</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>global elements<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><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:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, select your schema.</cmd><info>The entire
-schema and its contents are displayed in the Design view.</info></step>
-<step><cmd>In the Design view, right-click in the <b>Elements</b> section
-and click <uicontrol>Add Element</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, click the <uicontrol>General</uicontrol> tab,
-and type a new name for the global element in the <uicontrol>Name</uicontrol> field.</cmd>
-</step>
-<step><cmd>In the Properties view, you can select the attribute type from
-the predefined list in the menu next to the <uicontrol>Type</uicontrol> field.</cmd>
-<info><p>Alternatively, you can select <uicontrol>Browse</uicontrol> from
-the list for more options. </p><p>The <uicontrol>Set Type</uicontrol> dialog
-box appears, and lists all built-in and user-defined types currently available.
-You can change the <uicontrol>Scope</uicontrol> of the list by selecting one
-of the following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace. </li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file. </li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></p><p>Select the type you want in the type list, then click <uicontrol>OK</uicontrol>. </p></info>
-</step>
-<step><cmd>(Optional) Click the <uicontrol>Other</uicontrol> tab.</cmd><info>In
-this page, you can specify the following various values for the global element: </info>
-<choices>
-<choice><uicontrol>abstract</uicontrol>. Click <b>true </b>if you want the
-global element to be abstract. When a global element is declared to be abstract,
-it cannot be used in an instance document. Instead, a member of that global
-element's substitution group must appear in the instance document.</choice>
-<choice><uicontrol>block</uicontrol>. This field determines whether the global
-element may be replaced by an element derived from it.</choice>
-<choice><uicontrol>final</uicontrol>. This field determines whether this global
-element may be derived from.</choice>
-<choice><uicontrol>fixed/default</uicontrol>. Click <uicontrol>Browse</uicontrol> and
-select <uicontrol>Fixed</uicontrol> or <uicontrol>Default</uicontrol> and
-specify an appropriate value. If you select <b>Fixed</b>, the global element
-has a fixed value, which cannot be changed. If you select <b>Default</b>,
-the element has a default value.</choice>
-<choice><uicontrol>form</uicontrol>. Use this field to indicate if the appearance
-of this global element in an instance of the XML schema (an XML file associated
-with the XML schema) must be qualified by a namespace.</choice>
-<choice><uicontrol>nillable</uicontrol>. Select <b>true</b> if you do not
-want the global element to be able to have any child elements, only attributes. </choice>
-<choice><uicontrol>substitutionGroup</uicontrol>. A substitution group allows
-elements to be substituted for other elements.</choice>
-</choices>
-</step>
-<step><cmd>Click the <uicontrol>Attributes</uicontrol> tab.</cmd><info>You
-can use this page to add attributes, attribute references, attributes group
-references, and <codeph>any</codeph> attributes to your global element.</info>
-</step>
-<step><cmd>An attribute associates an attribute name with a specific type
-and value. To add an attribute, right-click in the Attributes page, and click <uicontrol>Add
-Attribute</uicontrol>.</cmd><info>You can specify the following values for
-an attribute:</info>
-<choices>
-<choice><uicontrol>fixed/default</uicontrol>. Click <uicontrol>Browse</uicontrol> and
-select <uicontrol>Fixed</uicontrol> or <uicontrol>Default</uicontrol> 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.</choice>
-<choice><uicontrol>form</uicontrol>. Use this field to indicate if the appearance
-of this attribute in an instance of the XML schema must be qualified by a
-namespace.</choice>
-<choice><uicontrol>name</uicontrol>. Enter the name of the attribute.</choice>
-<choice><uicontrol>type</uicontrol>. Click <uicontrol>Browse</uicontrol> and
-select the type of the attribute. </choice>
-<choice><uicontrol>use</uicontrol>. This field indicates how an attribute
-can be used in an instance document. If you select optional, the attribute
-can appear once, but it does not have to. If you select required, the attribute
-must appear once. If you select prohibited, the attribute must not appear. <b>Note</b>:
-If you selected <uicontrol>Default</uicontrol>, you must select <b>optional</b> in
-this field, otherwise the default value will not be valid.</choice>
-</choices>
-</step>
-<step><cmd>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, right-click in the Attributes page, and click <uicontrol>Add
-Attribute Ref</uicontrol>.</cmd><info>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. Select the reference, then select the global attribute you want
-it to reference from the <uicontrol>ref</uicontrol> list.</info></step>
-<step><cmd>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 <uicontrol>Add Attribute Group Ref</uicontrol>.</cmd><info>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. Select the
-reference, then select the attribute group you want it to reference from the <uicontrol>ref</uicontrol> list.</info>
-</step>
-<step><cmd>An <codeph>any</codeph> element enables element content according
-to namespaces, and the corresponding <codeph>any</codeph> attribute element
-enables attributes to appear in elements. To add an <codeph>any</codeph> attribute,
-right-click in the Attributes page and click <uicontrol>Add Any Attribute</uicontrol>.</cmd>
-<info>You can specify the following values for an <codeph>any</codeph> attribute:</info>
-<choices>
-<choice>For a <uicontrol>namespace</uicontrol> <?Pub Caret1?>value, you can
-select:<ul>
-<li><b>##any</b>. This allows any well-formed XML from any namespace.</li>
-<li><b>##local </b>. This allows any well-formed XML that is not declared
-to be in a namespace.</li>
-<li><b>##other</b>. This allows any well-formed XML that is not from the target
-namespace of the type being defined.</li>
-<li><b>##targetNamespace </b>. This is shorthand for the target namespace
-of the type being defined.</li>
-</ul></choice>
-<choice>For a <uicontrol>processContents</uicontrol> value, you can select:<ul>
-<li><b>skip</b>. The XML processor will not validate the attribute content
-at all.</li>
-<li><b>lax</b>. The XML processor will validate the attribute content as much
-as it can.</li>
-<li><b>strict</b>. The XML processor will validate all the attribute content.</li>
-</ul></choice>
-</choices>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this global element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<postreq>You can add a content model to a global element, which is the representation
-of any data that can be contained inside the global element. For more information
-about working with content models, refer to the related tasks.</postreq>
-</taskbody>
-</task>
-<?Pub *0000009579?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html deleted file mode 100644 index f38c0d5eec..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html +++ /dev/null @@ -1,232 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding global elements" /> -<meta name="abstract" content="A global element is an element with a global scope. It is one that has been declared as part of the main schema rather than as part of a content model." /> -<meta name="description" content="A global element is an element with a global scope. It is one that has been declared as part of the main schema rather than as part of a content model." /> -<meta content="XML schema editor, adding, global elements, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, global elements, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddelmr.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddglem" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding global elements</title> -</head> -<body id="taddglem"><a name="taddglem"><!-- --></a> - - -<h1 class="topictitle1">Adding global elements</h1> - - - - -<div><p>A global element is an element with a global scope. It is one that -has been declared as part of the main schema rather than as part of a content -model.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add a global -element:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire -schema and its contents are displayed in the Design view.</li> - -<li class="stepexpand"><span>In the Design view, right-click in the <strong>Elements</strong> section -and click <span class="uicontrol">Add Element</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">General</span> tab, -and type a new name for the global element in the <span class="uicontrol">Name</span> field.</span> -</li> - -<li class="stepexpand"><span>In the Properties view, you can select the attribute type from -the predefined list in the menu next to the <span class="uicontrol">Type</span> field.</span> - <p>Alternatively, you can select <span class="uicontrol">Browse</span> from -the list for more options. </p> -<div class="p">The <span class="uicontrol">Set Type</span> dialog -box appears, and lists all built-in and user-defined types currently available. -You can change the <span class="uicontrol">Scope</span> of the list by selecting one -of the following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace. </li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file. </li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</div> -<p>Select the type you want in the type list, then click <span class="uicontrol">OK</span>. </p> - -</li> - -<li class="stepexpand"><span>(Optional) Click the <span class="uicontrol">Other</span> tab.</span> In -this page, you can specify the following various values for the global element: -<ul> -<li><span class="uicontrol">abstract</span>. Click <strong>true </strong>if you want the -global element to be abstract. When a global element is declared to be abstract, -it cannot be used in an instance document. Instead, a member of that global -element's substitution group must appear in the instance document.</li> - -<li><span class="uicontrol">block</span>. This field determines whether the global -element may be replaced by an element derived from it.</li> - -<li><span class="uicontrol">final</span>. This field determines whether this global -element may be derived from.</li> - -<li><span class="uicontrol">fixed/default</span>. Click <span class="uicontrol">Browse</span> and -select <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> and -specify an appropriate value. If you select <strong>Fixed</strong>, the global element -has a fixed value, which cannot be changed. If you select <strong>Default</strong>, -the element has a default value.</li> - -<li><span class="uicontrol">form</span>. Use this field to indicate if the appearance -of this global element in an instance of the XML schema (an XML file associated -with the XML schema) must be qualified by a namespace.</li> - -<li><span class="uicontrol">nillable</span>. Select <strong>true</strong> if you do not -want the global element to be able to have any child elements, only attributes. </li> - -<li><span class="uicontrol">substitutionGroup</span>. A substitution group allows -elements to be substituted for other elements.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Attributes</span> tab.</span> You -can use this page to add attributes, attribute references, attributes group -references, and <samp class="codeph">any</samp> attributes to your global element. -</li> - -<li class="stepexpand"><span>An attribute associates an attribute name with a specific type -and value. To add an attribute, right-click in the Attributes page, and click <span class="uicontrol">Add -Attribute</span>.</span> You can specify the following values for -an attribute: -<ul> -<li><span class="uicontrol">fixed/default</span>. Click <span class="uicontrol">Browse</span> and -select <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> and -specify an appropriate value. If you select <strong>Fixed</strong>, the attribute has -a fixed value, which cannot be changed. If you select <strong>Default</strong>, the -attribute has a default value.</li> - -<li><span class="uicontrol">form</span>. Use this field to indicate if the appearance -of this attribute in an instance of the XML schema must be qualified by a -namespace.</li> - -<li><span class="uicontrol">name</span>. Enter the name of the attribute.</li> - -<li><span class="uicontrol">type</span>. Click <span class="uicontrol">Browse</span> and -select the type of the attribute. </li> - -<li><span class="uicontrol">use</span>. This field indicates how an attribute -can be used in an instance document. If you select optional, the attribute -can appear once, but it does not have to. If you select required, the attribute -must appear once. If you select prohibited, the attribute must not appear. <strong>Note</strong>: -If you selected <span class="uicontrol">Default</span>, you must select <strong>optional</strong> in -this field, otherwise the default value will not be valid.</li> - -</ul> - -</li> - -<li class="stepexpand"><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. Select the reference, then select the global attribute you want -it to reference from the <span class="uicontrol">ref</span> list.</li> - -<li class="stepexpand"><span>An attribute group reference provides a reference to an attribute -group. To add an attribute group reference, right-click in the Attributes -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. Select the -reference, then select the attribute group you want it to reference from the <span class="uicontrol">ref</span> list. -</li> - -<li class="stepexpand"><span>An <samp class="codeph">any</samp> element enables element content according -to namespaces, and the corresponding <samp class="codeph">any</samp> attribute element -enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute, -right-click in the Attributes page and click <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 <span class="uicontrol">namespace</span> value, you can -select:<ul> -<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li> - -<li><strong>##local </strong>. This allows any well-formed XML that is not declared -to be in a namespace.</li> - -<li><strong>##other</strong>. This allows any well-formed XML that is not from the target -namespace of the type being defined.</li> - -<li><strong>##targetNamespace </strong>. This is shorthand for the target namespace -of the type being defined.</li> - -</ul> -</li> - -<li>For a <span class="uicontrol">processContents</span> value, you can select:<ul> -<li><strong>skip</strong>. The XML processor will not validate the attribute content -at all.</li> - -<li><strong>lax</strong>. The XML processor will validate the attribute content as much -as it can.</li> - -<li><strong>strict</strong>. The XML processor will validate all the attribute content.</li> - -</ul> -</li> - -</ul> - -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this global element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section">You can add a content model to a global element, which is the representation -of any data that can be contained inside the global element. For more information -about working with content models, refer to the related tasks.</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div> -<div><a href="../topics/taddelmr.html" title="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration.">Adding element references</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.dita deleted file mode 100644 index 841870d300..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.dita +++ /dev/null @@ -1,43 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddgrpr" xml:lang="en-us">
-<title>Adding group references</title>
-<titlealts>
-<searchtitle>Adding group references</searchtitle>
-</titlealts>
-<shortdesc>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.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>group references</indexterm></indexterm></indexterm>
-<indexterm>XML schema editor<indexterm>group references<indexterm>adding</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>adding<indexterm>group references</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>group references<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>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></context>
-<steps>
-<step><cmd>In the Design view, right-click the content model you want to work
-with and select <uicontrol>Add Group Ref</uicontrol>.</cmd></step>
-<step><cmd>Select the new group reference.</cmd></step>
-<step><cmd>In the Properties view, select the group you want to refer to in
-the <uicontrol>ref</uicontrol> list.</cmd></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this group reference.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.<?Pub Caret?></info>
-</step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000002277?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html deleted file mode 100644 index 130e49adbb..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html +++ /dev/null @@ -1,71 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding group references" /> -<meta name="abstract" content="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration." /> -<meta name="description" content="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration." /> -<meta content="XML schema editor, adding, group references, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, group references, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddgrup.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddgrpr" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding group references</title> -</head> -<body id="taddgrpr"><a name="taddgrpr"><!-- --></a> - - -<h1 class="topictitle1">Adding group references</h1> - - - - -<div><p>A group reference is a declaration that references a group. It -enables the referenced group to appear in the instance document in the context -of the referencing declaration.</p> - -<div class="section">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="stepexpand"><span>In the Design view, right-click the content model you want to work -with and select <span class="uicontrol">Add Group Ref</span>.</span></li> - -<li class="stepexpand"><span>Select the new group reference.</span></li> - -<li class="stepexpand"><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="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this group reference.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description. -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddgrup.html" title="When you create a group, it automatically contains a content model. The content model is a representation of any data that can be grouped together by the group, such as elements, element references, and group references.">Adding groups</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.dita deleted file mode 100644 index 215cf4adb4..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.dita +++ /dev/null @@ -1,46 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="taddgrup" xml:lang="en-us">
-<title>Adding groups</title>
-<titlealts>
-<searchtitle>Adding groups</searchtitle>
-</titlealts>
-<shortdesc>When you create a group, it automatically contains a content model.
-The content model is a representation of any data that can be grouped together
-by the group, such as elements, element references, and group references.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>groups</indexterm></indexterm></indexterm>
-<indexterm>XML schema editor<indexterm>groups<indexterm>adding</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>adding<indexterm>groups</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>groups<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><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></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, right-click <b>Groups</b>, and click <uicontrol>Add
-Group</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, type a new name for the group in the <uicontrol>Name</uicontrol> field.</cmd>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this group element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol><?Pub Caret?> page allows you to
-specify the schema and add XML content to your annotations.</info></step>
-<step><cmd>In the Outline view, expand the <uicontrol>Groups</uicontrol> folder
-and your new group.</cmd></step>
-<step><cmd>Your group automatically contains a content model. </cmd><info>A
-group's content model is the representation of any data that can be contained
-inside the group. For more information about working with content models,
-refer to the related tasks.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000002502?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html deleted file mode 100644 index b8141ed975..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html +++ /dev/null @@ -1,80 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding groups" /> -<meta name="abstract" content="When you create a group, it automatically contains a content model. The content model is a representation of any data that can be grouped together by the group, such as elements, element references, and group references." /> -<meta name="description" content="When you create a group, it automatically contains a content model. The content model is a representation of any data that can be grouped together by the group, such as elements, element references, and group references." /> -<meta content="XML schema editor, adding, groups, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, groups, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddgrpr.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddgrup" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding groups</title> -</head> -<body id="taddgrup"><a name="taddgrup"><!-- --></a> - - -<h1 class="topictitle1">Adding groups</h1> - - - - -<div><p>When you create a group, it automatically contains a content model. -The content model is a representation of any data that can be grouped together -by the group, such as elements, element references, and group references.</p> - -<div class="section"><p /> -<p>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="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, right-click <strong>Groups</strong>, and click <span class="uicontrol">Add -Group</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, type a new name for the group in the <span class="uicontrol">Name</span> field.</span> -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this group element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to -specify the schema and add XML content to your annotations.</li> - -<li class="stepexpand"><span>In the Outline view, expand the <span class="uicontrol">Groups</span> folder -and your new group.</span></li> - -<li class="stepexpand"><span>Your group automatically contains a content model. </span> A -group's content model is the representation of any data that can be contained -inside the group. For more information about working with content models, -refer to the related tasks.</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddgrpr.html" title="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration.">Adding group references</a></div> -<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.dita deleted file mode 100644 index c8f253e22e..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.dita +++ /dev/null @@ -1,78 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddimpt" xml:lang="en-us">
-<title>Adding import elements</title>
-<titlealts>
-<searchtitle>Adding import elements</searchtitle>
-</titlealts>
-<shortdesc>As schemas become larger, it is often desirable to divide their
-content among several schema documents for purposes such as ease of maintenance,
-reuse, and readability. You can use an <codeph>import</codeph> element to
-bring in definitions and declarations from an imported schema into the current
-schema. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>import elements</indexterm></indexterm></indexterm>
-<indexterm>XML schema editor<indexterm>import elements<indexterm>adding</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>adding<indexterm>import elements</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>import elements<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The imported schema can come from a different namespace than the
-current schema does.</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>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></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, select your schema.</cmd><info>The entire
-schema and its contents should be displayed in the Design view.</info></step>
-<step><cmd>In the Design view, right click in the <b>Directives</b> section
-and click <uicontrol>Add Import</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, click the <b>General</b> tab and click <uicontrol>Browse</uicontrol> <image
-href="../images/Browse.gif"><alt>This graphic is the Browse button</alt></image> to
-the right of the <uicontrol>Schema location</uicontrol> field.</cmd></step>
-<step><cmd>If you want to import an XML schema located in the workbench:</cmd>
-<substeps>
-<substep><cmd>Select <uicontrol>Workbench projects</uicontrol> and click <uicontrol>Next</uicontrol>. </cmd>
-</substep>
-<substep><cmd>Select the schema you want to import and click <uicontrol>Finish</uicontrol>.</cmd>
-</substep>
-</substeps>
-</step>
-<step><cmd>If you want to import an XML schema located on the Web:<?Pub Caret?></cmd>
-<substeps>
-<substep><cmd>Select <uicontrol>HTTP</uicontrol> and click <uicontrol>Next</uicontrol>.</cmd>
-</substep>
-<substep><cmd>Type the URL of the XML schema and click <uicontrol>Finish</uicontrol>.</cmd>
-<info><note>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.</note></info></substep>
-</substeps>
-</step>
-<step><cmd>The XML schema editor will retrieve the namespace for the imported
-XML schema file and display it as read-only in the <uicontrol>Namespace</uicontrol> field.</cmd>
-</step>
-<step><cmd>If necessary, type a unique prefix for this namespace in the <uicontrol>Prefix</uicontrol> field.</cmd>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this import element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<result><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 <uicontrol>Type</uicontrol> list for the element,
-attribute, complex or simple type.</p></result>
-<postreq></postreq>
-</taskbody>
-</task>
-<?Pub *0000004340?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html deleted file mode 100644 index d6946ec368..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html +++ /dev/null @@ -1,128 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding import elements" /> -<meta name="abstract" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema." /> -<meta name="description" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema." /> -<meta content="XML schema editor, adding, import elements, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, import elements, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddincl.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddrdfn.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/rnmspc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddimpt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding import elements</title> -</head> -<body id="taddimpt"><a name="taddimpt"><!-- --></a> - - -<h1 class="topictitle1">Adding import elements</h1> - - - - -<div><p>As schemas become larger, it is often desirable to divide their -content among several schema documents for purposes such as ease of maintenance, -reuse, and readability. You can use an <samp class="codeph">import</samp> element to -bring in definitions and declarations from an imported schema into the current -schema. </p> - -<div class="section"><p>The imported schema can come from a different namespace than the -current schema does.</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>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="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire -schema and its contents should be displayed in the Design view.</li> - -<li class="stepexpand"><span>In the Design view, right click in the <strong>Directives</strong> section -and click <span class="uicontrol">Add Import</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> to -the right of the <span class="uicontrol">Schema location</span> field.</span></li> - -<li class="stepexpand"><span>If you want to import an XML schema located in the workbench:</span> -<ol type="a"> -<li><span>Select <span class="uicontrol">Workbench projects</span> and click <span class="uicontrol">Next</span>. </span> -</li> - -<li><span>Select the schema you want to import and click <span class="uicontrol">Finish</span>.</span> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>If you want to import an XML schema located on the Web:</span> -<ol type="a"> -<li class="substepexpand"><span>Select <span class="uicontrol">HTTP</span> and click <span class="uicontrol">Next</span>.</span> -</li> - -<li class="substepexpand"><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>.</span> - <div class="note"><span class="notetitle">Note:</span> A local copy of the schema will not be stored in the workbench. -Every time you validate your schema, the schema's contents will be checked -from the URL you specify.</div> -</li> - -</ol> - -</li> - -<li class="stepexpand"><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="stepexpand"><span>If necessary, type a unique prefix for this namespace in the <span class="uicontrol">Prefix</span> field.</span> -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this import element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section"><p>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="section" /> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema.">Adding include elements</a></div> -<div><a href="../topics/taddrdfn.html" title="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. When you redefine a component, you are modifying its contents.">Adding redefine elements</a></div> -</div> -<div class="relref"><strong>Related reference</strong><br /> -<div><a href="../topics/rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.dita deleted file mode 100644 index d52b8325a4..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.dita +++ /dev/null @@ -1,80 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddincl" xml:lang="en-us">
-<title>Adding include elements</title>
-<titlealts>
-<searchtitle>Adding include elements</searchtitle>
-</titlealts>
-<shortdesc>As schemas become larger, it is often desirable to divide their
-content among several schema documents for purposes such as ease of maintenance,
-reuse, and readability. You can use the <codeph>include</codeph> element to
-bring<?Pub Caret?> in definitions and declarations from the included schema
-into the current schema. The included schema must be in the same target namespace
-as the including schema. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>include
-elements</indexterm></indexterm></indexterm><indexterm>XML schema editor<indexterm>include
-elements<indexterm>adding</indexterm></indexterm></indexterm><indexterm>XML
-schema files<indexterm>adding<indexterm>include elements</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>include elements<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><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></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, select your schema.</cmd><info>The entire
-schema and its contents are displayed in the Design view.</info></step>
-<step><cmd>In the Design view, right-click in the <b>Directives</b> section
-and click <uicontrol>Add Include</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, click the <b>General</b> tab and click <uicontrol>Browse</uicontrol> <image
-href="../images/Browse.gif"><alt>This graphic is the Browse button</alt></image> to
-the right of the <uicontrol>Schema location</uicontrol> field.</cmd><info>The
-XML schema file you select must have the same namespace as the current schema.</info>
-</step>
-<step><cmd>If you want to select an XML schema located in the workbench, select <uicontrol>Workbench
-projects</uicontrol> and click <uicontrol>Next</uicontrol>. </cmd></step>
-<step><cmd>Select the schema you want to include and click <uicontrol>Finish</uicontrol>.</cmd>
-</step>
-<step><cmd>If you want to select an XML schema located on the Web, select <uicontrol>HTTP</uicontrol> and
-click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>Type the URL of the XML schema and click <uicontrol>Finish</uicontrol>.</cmd>
-<info><note> 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.</note></info></step>
-<step><cmd>The XML schema editor will retrieve the location of the included
-XML schema file, and display it in the <uicontrol>Schema location</uicontrol> field.
-This field can be edited at any time to reflect the location of the XML schema
-file.</cmd></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this include element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<result><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 <uicontrol>Type</uicontrol> list for the element,
-attribute, complex or simple type.</p><p>For example, if Address.xsd has the
-following content:</p><codeblock><complexType name="Address">
- <sequence>
- <element name="name" type="string">
- <element name="street" type="string">
- </sequence>
-</complexType>
-</codeblock>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></result>
-</taskbody>
-</task>
-<?Pub *0000004728?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html deleted file mode 100644 index 7abba83f41..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html +++ /dev/null @@ -1,124 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding include elements" /> -<meta name="abstract" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." /> -<meta name="description" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." /> -<meta content="XML schema editor, adding, include elements, XML schema files, include elements, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, include elements, XML schema files, include elements, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddimpt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddrdfn.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/rnmspc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddincl" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding include elements</title> -</head> -<body id="taddincl"><a name="taddincl"><!-- --></a> - - -<h1 class="topictitle1">Adding include elements</h1> - - - - -<div><p>As schemas become larger, it is often desirable to divide their -content among several schema documents for purposes such as ease of maintenance, -reuse, and readability. You can use the <samp class="codeph">include</samp> element to -bring in definitions and declarations from the included schema -into the current schema. The included schema must be in the same target namespace -as the including schema. </p> - -<div class="section"><p>The following instructions were written for the XML perspective, -but they will also work in many other perspectives.</p> -<p>To add an include -element, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire -schema and its contents are displayed in the Design view.</li> - -<li class="stepexpand"><span>In the Design view, right-click in the <strong>Directives</strong> section -and click <span class="uicontrol">Add Include</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> to -the right of the <span class="uicontrol">Schema location</span> field.</span> The -XML schema file you select must have the same namespace as the current schema. -</li> - -<li class="stepexpand"><span>If you want to select an XML schema located in the workbench, select <span class="uicontrol">Workbench -projects</span> and click <span class="uicontrol">Next</span>. </span></li> - -<li class="stepexpand"><span>Select the schema you want to include and click <span class="uicontrol">Finish</span>.</span> -</li> - -<li class="stepexpand"><span>If you want to select an XML schema located on the Web, select <span class="uicontrol">HTTP</span> and -click <span class="uicontrol">Next</span>.</span></li> - -<li class="stepexpand"><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>.</span> - <div class="note"><span class="notetitle">Note:</span> A local copy of the schema will not be stored in the workbench. -Every time you validate your schema, the schema's contents will be checked -from the URL you specify.</div> -</li> - -<li class="stepexpand"><span>The XML schema editor will retrieve the location of the included -XML schema file, and display it in the <span class="uicontrol">Schema location</span> field. -This field can be edited at any time to reflect the location of the XML schema -file.</span></li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this include element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section"><p>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><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema.">Adding import elements</a></div> -<div><a href="../topics/taddrdfn.html" title="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. When you redefine a component, you are modifying its contents.">Adding redefine elements</a></div> -</div> -<div class="relref"><strong>Related reference</strong><br /> -<div><a href="../topics/rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.dita deleted file mode 100644 index ee680ef6f0..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.dita +++ /dev/null @@ -1,53 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddnot" xml:lang="en-us">
-<title>Adding notations</title>
-<titlealts>
-<searchtitle>Adding notations</searchtitle>
-</titlealts>
-<shortdesc>A notation is a means of associating a binary description with
-an entity or attribute. The most common uses of notations are to include familiar
-types of binary references, such as GIFs and JPGs, in an XML file.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>notations</indexterm></indexterm></indexterm>
-<indexterm>XML schema editor<indexterm>notations<indexterm>adding</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>adding<indexterm>notations</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>notations<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>For example, you are making a catalogue of your clothing and want
-to include an image of one of your shirts. You would have to create a notation
-like this: <userinput><notation name="My_Shirt" system="GIF"></notation></userinput> which
-defines a notation for a GIF image.</p><p>The following instructions were
-written for the Resource perspective, but they will also work in many other
-perspectives.</p><p>To create a notation, follow these steps:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, right-click your XML schema and click <uicontrol>Add
-Notation</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, type the name of the notation in the <uicontrol>Name</uicontrol> field.</cmd>
-</step>
-<step><cmd>Click the <uicontrol>Other</uicontrol> tab.</cmd></step>
-<step><cmd>In the <uicontrol>public</uicontrol> field, type a public identifier.</cmd>
-<info> This is optional if you enter a value in the <uicontrol>system</uicontrol> field.</info>
-</step>
-<step><cmd>In the <uicontrol>system</uicontrol> field, type a URI reference.</cmd>
-<info> This is optional if you enter a value in the <uicontrol>public</uicontrol> field.</info>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this notation.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description. <uicontrol>App
-Info</uicontrol> page can be used to provide information for applications.</info>
-</step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info><?Pub Caret?></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000002959?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html deleted file mode 100644 index 75078b0b7f..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html +++ /dev/null @@ -1,52 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> -<title>Adding notations</title> -</head> -<body id="taddnot"><a name="taddnot"><!-- --></a> - -<h1 class="topictitle1">Adding notations</h1> -<div><p>A notation is a means of associating a binary description with -an entity or attribute. The most common uses of notations are to include familiar -types of binary references, such as GIFs and JPGs, in an XML file.</p> -<div class="section"><p>For example, you are making a catalogue of your clothing and want -to include an image of one of your shirts. You would have to create a notation -like this: <kbd class="userinput"><notation name="My_Shirt" system="GIF"></notation></kbd> which -defines a notation for a GIF image.</p> -<p>The following instructions were written for the Resource perspective, but -they will also work in many other perspectives.</p> -<p>To -create a notation, follow these steps:</p> -</div> -<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li> -<li class="skipspace"><span>In the Outline view, right-click your XML schema and click -<b> <span class="uicontrol">Add -Notation</span></b>.</span></li> -<li class="skipspace"><span>In the Properties view, type the name of the notation in the -<b> <span class="uicontrol">Name</span></b> field.</span></li> -<li class="skipspace"><span>Click the <b> <span class="uicontrol">Other</span></b> tab.</span></li> -<li class="skipspace"><span>In the <b> <span class="uicontrol">public</span></b> field, type a public identifier.</span> This is optional if you enter a value in the -<b> <span class="uicontrol">system</span></b> field.</li> -<li class="skipspace"><span>In the <b> <span class="uicontrol">system</span></b> field, type a URI reference.</span> This is optional if you enter a value in the -<b> <span class="uicontrol">public</span></b> field.</li> -<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want -to provide any information about this notation.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description, and the <span class="uicontrol">App -Info</span> page can be used to provide information for applications.</li> -</ol> -</div> -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.dita deleted file mode 100644 index 00e7b41b60..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.dita +++ /dev/null @@ -1,67 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddrdfn" xml:lang="en-us">
-<title>Adding redefine elements</title>
-<titlealts>
-<searchtitle>Adding redefine elements</searchtitle>
-</titlealts>
-<shortdesc>You can use the <codeph>redefine</codeph> mechanism to redefine
-simple and complex types, groups, and attribute groups obtained from external
-schema files. When you redefine a component, you are modifying its contents.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>redefine
-elements</indexterm></indexterm></indexterm><indexterm>XML schema editor<indexterm>redefine
-elements<indexterm>adding</indexterm></indexterm></indexterm><indexterm>XML
-schema files<indexterm>adding<indexterm>redefine elements</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>redefine elements<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>Like the <codeph>include</codeph> mechanism, <codeph>redefine</codeph> 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><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:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, select your schema.</cmd><info>The entire
-schema and its contents are displayed in the Design view.</info></step>
-<step><cmd>In the Design view, right-click in the <b>Directives</b> section
-and click <uicontrol>Add Redefine</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, click the <b>General</b> tab and click <uicontrol>Browse</uicontrol> <image
-href="../images/Browse.gif"><alt>This graphic is the Browse button</alt></image> to
-<?Pub Caret?>the right of the <uicontrol>Schema location</uicontrol> field.</cmd>
-<info>The XML schema file you select must have the same namespace as the current
-schema.</info></step>
-<step><cmd>If you want to select an XML schema located in the workbench, select <uicontrol>Workbench
-projects</uicontrol> and click <uicontrol>Next.</uicontrol></cmd></step>
-<step><cmd>Select the schema you want to include and click <uicontrol>Finish</uicontrol>.</cmd>
-</step>
-<step><cmd>If you want to select an XML schema located on the Web, select <uicontrol>HTTP</uicontrol> and
-click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>Type the URL of the XML schema and click <uicontrol>Finish</uicontrol>.</cmd>
-<info> <note>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.</note></info></step>
-<step><cmd>The XML schema editor will retrieve the location of the included
-XML schema file, and display it in the <uicontrol>Schema location</uicontrol> field.
-This field can be edited at any time to reflect the location of the XML schema
-file.</cmd></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this redefine element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<result><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></result>
-</taskbody>
-</task>
-<?Pub *0000004055?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html deleted file mode 100644 index d7820c8d36..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html +++ /dev/null @@ -1,109 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding redefine elements" /> -<meta name="abstract" content="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. When you redefine a component, you are modifying its contents." /> -<meta name="description" content="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. When you redefine a component, you are modifying its contents." /> -<meta content="XML schema editor, adding, redefine elements, XML schema files, redefine elements, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, redefine elements, XML schema files, redefine elements, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddimpt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddincl.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/rnmspc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddrdfn" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding redefine elements</title> -</head> -<body id="taddrdfn"><a name="taddrdfn"><!-- --></a> - - -<h1 class="topictitle1">Adding redefine elements</h1> - - - - -<div><p>You can use the <samp class="codeph">redefine</samp> mechanism to redefine -simple and complex types, groups, and attribute groups obtained from external -schema files. When you redefine a component, you are modifying its contents.</p> - -<div class="section"><p>Like the <samp class="codeph">include</samp> mechanism, <samp class="codeph">redefine</samp> requires -the external components to be in the same target namespace as the redefining -schema, although external components from schemas that have no namespace can -also be redefined.</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:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire -schema and its contents are displayed in the Design view.</li> - -<li class="stepexpand"><span>In the Design view, right-click in the <strong>Directives</strong> section -and click <span class="uicontrol">Add Redefine</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> to -the right of the <span class="uicontrol">Schema location</span> field.</span> - The XML schema file you select must have the same namespace as the current -schema.</li> - -<li class="stepexpand"><span>If you want to select an XML schema located in the workbench, select <span class="uicontrol">Workbench -projects</span> and click <span class="uicontrol">Next.</span></span></li> - -<li class="stepexpand"><span>Select the schema you want to include and click <span class="uicontrol">Finish</span>.</span> -</li> - -<li class="stepexpand"><span>If you want to select an XML schema located on the Web, select <span class="uicontrol">HTTP</span> and -click <span class="uicontrol">Next</span>.</span></li> - -<li class="stepexpand"><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>.</span> - <div class="note"><span class="notetitle">Note:</span> A local copy of the schema will not be stored in the workbench. -Every time you validate your schema, the schema's contents will be checked -from the URL you specify.</div> -</li> - -<li class="stepexpand"><span>The XML schema editor will retrieve the location of the included -XML schema file, and display it in the <span class="uicontrol">Schema location</span> field. -This field can be edited at any time to reflect the location of the XML schema -file.</span></li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this redefine element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section"><p>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> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema.">Adding import elements</a></div> -<div><a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema.">Adding include elements</a></div> -</div> -<div class="relref"><strong>Related reference</strong><br /> -<div><a href="../topics/rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.dita deleted file mode 100644 index a0fc73b722..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.dita +++ /dev/null @@ -1,61 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="taddreg" xml:lang="en-us">
-<title>Adding pattern facets to simple types</title>
-<titlealts>
-<searchtitle>Adding pattern facets to simple types</searchtitle>
-</titlealts>
-<shortdesc>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.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>pattern
-facets</indexterm></indexterm></indexterm><indexterm>XML schema editor<indexterm>pattern
-facets<indexterm>adding</indexterm></indexterm></indexterm><indexterm>XML
-schema files<indexterm>adding<indexterm>pattern facets</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>pattern facets<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p> The value of the pattern is called a regular expression. You
-can specify it using the <uicontrol>Regular Expression</uicontrol> wizard.</p><p>To
-add a pattern to a simple type:</p></context>
-<steps>
-<step><cmd>In the Design view, select the simple type you want to work with.</cmd>
-</step>
-<step><cmd>In the Properties view, click the <uicontrol>Constraints</uicontrol> tab,
-then <uicontrol>Patterns</uicontrol>.</cmd></step>
-<step><cmd>Click <uicontrol>Add</uicontrol>.</cmd><info>The Regular Expression
-wizard opens.</info></step>
-<step><cmd>Select the token you want to add to the expression.</cmd></step>
-<step><cmd>Indicate how often you want the token to appear in order for a
-match to succeed:</cmd>
-<choices>
-<choice>If you want the token to repeat, click <uicontrol>Repeat</uicontrol> and
-specify the number of times the token must appear.</choice>
-</choices>
-<choices>
-<choice> If you want to specify a minimum and maximum number of times the
-token can appear, click <uicontrol>Range</uicontrol> and enter a minimum and
-maximum value.</choice>
-</choices>
-</step>
-<step><cmd>To add the token to the regular expression, click <uicontrol>Add</uicontrol>. </cmd>
-</step>
-<step><cmd>To create the entire expression, repeat steps 4 - 6 as necessary.</cmd>
-</step>
-<step><cmd>When you are finished, click <uicontrol>Next</uicontrol>.</cmd>
-</step>
-<step><cmd>(Optional) To test against the regular expression and see if a
-match occurs, enter sample text.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd><stepresult> The regular
-expression will appear in the Patterns page. <note type="tip"> To edit an
-existing pattern, select it in the Patterns page and click <uicontrol>Edit</uicontrol>.
-To delete an existing pattern, select it in the Patterns page and click <uicontrol>Delete</uicontrol>. <?Pub Caret?></note></stepresult>
-</step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000002952?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html deleted file mode 100644 index 2a0c07aa9e..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html +++ /dev/null @@ -1,99 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding pattern facets to simple types" /> -<meta name="abstract" content="A pattern facet can be used to constrain the value of a type's lexical space (the set of string literals that represent the values of a type), which indirectly constrains the value space." /> -<meta name="description" content="A pattern facet can be used to constrain the value of a type's lexical space (the set of string literals that represent the values of a type), which indirectly constrains the value space." /> -<meta content="XML schema editor, adding, pattern facets, XML schema files, pattern facets, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, pattern facets, XML schema files, pattern facets, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddsmpt.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddreg" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding pattern facets to simple types</title> -</head> -<body id="taddreg"><a name="taddreg"><!-- --></a> - - -<h1 class="topictitle1">Adding pattern facets to simple types</h1> - - - - -<div><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.</p> - -<div class="section"><p> The value of the pattern is called a regular expression. You -can specify it using the <span class="uicontrol">Regular Expression</span> wizard.</p> -<p>To -add a pattern to a simple type:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, select the simple type you want to work with.</span> -</li> - -<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">Constraints</span> tab, -then <span class="uicontrol">Patterns</span>.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Add</span>.</span> The Regular Expression -wizard opens.</li> - -<li class="stepexpand"><span>Select the token you want to add to the expression.</span></li> - -<li class="stepexpand"><span>Indicate how often you want the token to appear in order for a -match to succeed:</span> -<ul> -<li>If you want the token to repeat, click <span class="uicontrol">Repeat</span> and -specify the number of times the token must appear.</li> - -</ul> - -<ul> -<li> If you want to specify a minimum and maximum number of times the -token can appear, click <span class="uicontrol">Range</span> and enter a minimum and -maximum value.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>To add the token to the regular expression, click <span class="uicontrol">Add</span>. </span> -</li> - -<li class="stepexpand"><span>To create the entire expression, repeat steps 4 - 6 as necessary.</span> -</li> - -<li class="stepexpand"><span>When you are finished, click <span class="uicontrol">Next</span>.</span> -</li> - -<li class="stepexpand"><span>(Optional) To test against the regular expression and see if a -match occurs, enter sample text.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span> The regular -expression will appear in the Patterns page. <div class="tip"><span class="tiptitle">Tip:</span> To edit an -existing pattern, select it in the Patterns page and click <span class="uicontrol">Edit</span>. -To delete an existing pattern, select it in the Patterns page and click <span class="uicontrol">Delete</span>. </div> - -</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddsmpt.html" title="Simple types are used to create derived datatypes. They provide a set of constraints on the value space (a set of values) and the lexical space (a set of valid literals) of a datatype.">Adding simple types</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.dita deleted file mode 100644 index 5321111b12..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.dita +++ /dev/null @@ -1,134 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddsmpt" xml:lang="en-us">
-<title>Adding simple types</title>
-<titlealts>
-<searchtitle>Adding simple types</searchtitle>
-</titlealts>
-<shortdesc>Simple types are used to create<?Pub Caret?> derived datatypes.
-They provide a set of constraints on the value space (a set of values) and
-the lexical space (a set of valid literals) of a datatype.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding<indexterm>simple types</indexterm></indexterm></indexterm>
-<indexterm>XML schema editor<indexterm>simple types<indexterm>adding</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>adding<indexterm>simple types</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>simple types<indexterm>adding</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>A simple type cannot have element content and cannot carry attributes.
-Elements that contain numbers (and strings, and dates, and so on) but do not
-contain any sub-elements have a simple type.</p><p>The following instructions
-were written for the Resource perspective, but they will also work in many
-other perspectives.</p><p>To add a simple type:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, right-click <b>Types</b>, and click <uicontrol>Add
-Simple Type</uicontrol>.</cmd></step>
-<step><cmd>In the Outline view, select the new simple type.</cmd></step>
-<step><cmd>In the Properties view, click the <uicontrol>General</uicontrol> tab.</cmd>
-</step>
-<step><cmd>Type a new name for the simple type in the <uicontrol>Name</uicontrol> field.</cmd>
-</step>
-<step><cmd>You can select the following options from the <uicontrol>Variety</uicontrol> list:</cmd>
-<choices>
-<choice><uicontrol>atomic</uicontrol>. Atomic types are all the simple types
-built into the XML schema language.</choice>
-<choice><uicontrol>list</uicontrol>. List types are comprised of sequences
-of atomic types. They have values that are comprised of finite-length sequences
-of atomic values. </choice>
-<choice><uicontrol>union</uicontrol>. 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.</choice>
-</choices>
-</step>
-<step><cmd>If you selected <uicontrol>atomic</uicontrol> from the <uicontrol>Variety</uicontrol> list,
-click <uicontrol>Browse</uicontrol> <image href="../images/Browse.gif"><alt>This
-graphic is the Browse button</alt></image> next to the <uicontrol>Base type</uicontrol> field
-to specify a base type for the simple type.</cmd><info>The Set Type dialog
-box lists all built-in and user-defined types currently available. You can
-change the <uicontrol>Scope</uicontrol> of the list by selecting one of the
-following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace. </li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file. </li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></info></step>
-<step><cmd>If you selected <uicontrol>list</uicontrol> from the <uicontrol>Variety</uicontrol> list,
-click <uicontrol>Browse</uicontrol> <image href="../images/Browse.gif"><alt>This
-graphic is the Browse button</alt></image> next to the <uicontrol>Item type</uicontrol> field
-to specify a item type for the simple type.</cmd><info>The Set Type dialog
-box lists all built-in and user-defined types currently available. You can
-change the <uicontrol>Scope</uicontrol> of the list by selecting one of the
-following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace. </li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file. </li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></info></step>
-<step><cmd>If you selected <uicontrol>union</uicontrol> from the <uicontrol>Variety</uicontrol> list,
-click <uicontrol>Browse</uicontrol> <image href="../images/Browse.gif"><alt>This
-graphic is the Browse button</alt></image> next to the <uicontrol>Member types</uicontrol> field
-to specify the member types for the simple type.</cmd><info>You can select
-to add both <uicontrol>Built-in simple types</uicontrol> and <uicontrol>User-defined
-simple types</uicontrol> to the member types value list. </info></step>
-<step><cmd>Click the <uicontrol>Constraints</uicontrol> tab.</cmd><info>From
-here you will be able to set specific constraint values including length constraints,
-enumerations, and patterns. </info>
-<substeps>
-<substep><cmd>Enumerations help you to define a set of valid values for simple
-types. They are the actual values the simple type can take as valid values
-in the instance document. You can either add one enumeration or several enumerations
-at a time:</cmd><info><ul>
-<li>To add one enumeration at a time, under <uicontrol>Specific constraint
-values</uicontrol>, select <uicontrol>Enumerations</uicontrol> and click <uicontrol>Add</uicontrol> and
-specify a value for the enumeration.</li>
-<li>To add several enumerations at one time, follow these steps:<ol>
-<li>Select <uicontrol>Enumerations</uicontrol>.</li>
-<li>Click <uicontrol>Add</uicontrol>.</li>
-<li>Enter the value of each enumeration. Each value must be separated by the <uicontrol>Delimiter
-character</uicontrol>. For example: <codeph>First, Second</codeph> will create
-two enumerations, one with the value "First" and one with the value "Second".</li>
-<li>Select the <uicontrol>Preserve leading and trailing whitespace</uicontrol> check
-box if you want any white space around your enumeration values to be preserved.
-If you select this check box, the values of <codeph>First, Second</codeph> will
-show up as "First" and " Second" (there is a space before Second) because
-you put a space before "Second" when entering the value.</li>
-<li>Click <uicontrol>OK</uicontrol>. Your enumerations will be created and
-appear in the Properties view.</li>
-</ol></li>
-</ul></info></substep>
-<substep><cmd>Patterns help you to place certain constraints regarding allowable
-values.</cmd><info>For example, you could restrict the field to only accept
-input which follows the pattern "five digits followed by two upper-case ASCII
-letters". To set a pattern constraint:<ol>
-<li>Select <uicontrol>Patterns</uicontrol>.</li>
-<li>Click <uicontrol>Add</uicontrol>.</li>
-<li>Create the regular expression pattern you wish to use as your constraint
-using the <uicontrol>Regular Expression</uicontrol> wizard.</li>
-<li>Click <uicontrol>Finish</uicontrol>.</li>
-</ol></info></substep>
-</substeps>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this simple type.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000007829?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html deleted file mode 100644 index f6991670b3..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html +++ /dev/null @@ -1,198 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding simple types" /> -<meta name="abstract" content="Simple types are used to create derived datatypes. They provide a set of constraints on the value space (a set of values) and the lexical space (a set of valid literals) of a datatype." /> -<meta name="description" content="Simple types are used to create derived datatypes. They provide a set of constraints on the value space (a set of values) and the lexical space (a set of valid literals) of a datatype." /> -<meta content="XML schema editor, adding, simple types, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, simple types, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddreg.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddsmpt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding simple types</title> -</head> -<body id="taddsmpt"><a name="taddsmpt"><!-- --></a> - - -<h1 class="topictitle1">Adding simple types</h1> - - - - -<div><p>Simple types are used to create derived datatypes. -They provide a set of constraints on the value space (a set of values) and -the lexical space (a set of valid literals) of a datatype.</p> - -<div class="section"><p>A simple type cannot have element content and cannot carry attributes. -Elements that contain numbers (and strings, and dates, and so on) but do not -contain any sub-elements have a simple type.</p> -<p>The following instructions -were written for the Resource perspective, but they will also work in many -other perspectives.</p> -<p>To add a simple type:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, right-click <strong>Types</strong>, and click <span class="uicontrol">Add -Simple Type</span>.</span></li> - -<li class="stepexpand"><span>In the Outline view, select the new simple type.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">General</span> tab.</span> -</li> - -<li class="stepexpand"><span>Type a new name for the simple type in the <span class="uicontrol">Name</span> field.</span> -</li> - -<li class="stepexpand"><span>You can select the following options from the <span class="uicontrol">Variety</span> list:</span> -<ul> -<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="stepexpand"><span>If you selected <span class="uicontrol">atomic</span> from the <span class="uicontrol">Variety</span> list, -click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> next to the <span class="uicontrol">Base type</span> field -to specify a base type for the simple type.</span> The Set Type dialog -box lists all built-in and user-defined types currently available. You can -change the <span class="uicontrol">Scope</span> of the list by selecting one of the -following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace. </li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file. </li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</li> - -<li class="stepexpand"><span>If you selected <span class="uicontrol">list</span> from the <span class="uicontrol">Variety</span> list, -click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> next to the <span class="uicontrol">Item type</span> field -to specify a item type for the simple type.</span> The Set Type dialog -box lists all built-in and user-defined types currently available. You can -change the <span class="uicontrol">Scope</span> of the list by selecting one of the -following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace. </li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file. </li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</li> - -<li class="stepexpand"><span>If you selected <span class="uicontrol">union</span> from the <span class="uicontrol">Variety</span> list, -click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> next to the <span class="uicontrol">Member types</span> field -to specify the member types for the simple type.</span> You can select -to add both <span class="uicontrol">Built-in simple types</span> and <span class="uicontrol">User-defined -simple types</span> to the member types value list. </li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Constraints</span> tab.</span> From -here you will be able to set specific constraint values including length constraints, -enumerations, and patterns. -<ol type="a"> -<li class="substepexpand"><span>Enumerations help you to define a set of valid values for simple -types. They are the actual values the simple type can take as valid values -in the instance document. You can either add one enumeration or several enumerations -at a time:</span> <ul> -<li>To add one enumeration at a time, under <span class="uicontrol">Specific constraint -values</span>, select <span class="uicontrol">Enumerations</span> and click <span class="uicontrol">Add</span> and -specify a value for the enumeration.</li> - -<li>To add several enumerations at one time, follow these steps:<ol type="i"> -<li>Select <span class="uicontrol">Enumerations</span>.</li> - -<li>Click <span class="uicontrol">Add</span>.</li> - -<li>Enter the value of each enumeration. Each value must be separated by the <span class="uicontrol">Delimiter -character</span>. For example: <samp class="codeph">First, Second</samp> will create -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 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 entering the value.</li> - -<li>Click <span class="uicontrol">OK</span>. Your enumerations will be created and -appear in the Properties view.</li> - -</ol> -</li> - -</ul> -</li> - -<li class="substepexpand"><span>Patterns help you to place certain constraints regarding allowable -values.</span> For example, you could restrict the field to only accept -input which follows the pattern "five digits followed by two upper-case ASCII -letters". To set a pattern constraint:<ol type="i"> -<li>Select <span class="uicontrol">Patterns</span>.</li> - -<li>Click <span class="uicontrol">Add</span>.</li> - -<li>Create the regular expression pattern you wish to use as your constraint -using the <span class="uicontrol">Regular Expression</span> wizard.</li> - -<li>Click <span class="uicontrol">Finish</span>.</li> - -</ol> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this simple type.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddreg.html" title="A pattern facet can be used to constrain the value of a type's lexical space (the set of string literals that represent the values of a type), which indirectly constrains the value space.">Adding pattern facets to simple types</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.dita deleted file mode 100644 index bde45d16a4..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.dita +++ /dev/null @@ -1,31 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tcxmlsch" xml:lang="en-us">
-<title>Creating XML schemas</title>
-<titlealts>
-<searchtitle>Creating XML schemas</searchtitle>
-</titlealts>
-<shortdesc>You can create an XML schema and then edit it using the XML schema
-editor. Using the XML schema editor, you can specify element names that indicates
-which elements are allowed in an XML file, and in which combinations.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema files<indexterm>creating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>To create an XML schema, follow these steps:</context>
-<steps>
-<step><cmd>Create a project to contain the XML schema.</cmd></step>
-<step><cmd>In the workbench, select <menucascade><uicontrol>File > New >
-Other > XML > XML Schema</uicontrol></menucascade> and click <uicontrol>Next</uicontrol>.</cmd>
-</step>
-<step><cmd>Select the project or folder that will contain the XML schema.
-In the </cmd><info><uicontrol>File name</uicontrol> field, type the name of
-the XML schema, for example <userinput>MyXMLSchema.xsd</userinput>. The name
-of your XML schema must end in <systemoutput>.xsd</systemoutput>.</info></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-<result>The XML schema opens in the XML schema editor. </result>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html deleted file mode 100644 index 9aec93283d..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html +++ /dev/null @@ -1,69 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating XML schemas" /> -<meta name="abstract" content="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations." /> -<meta name="description" content="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations." /> -<meta content="XML schema files, creating" name="DC.subject" /> -<meta content="XML schema files, creating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tvdtschm.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcxmlsch" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating XML schemas</title> -</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. Using the XML schema editor, you can specify element names that indicates -which elements are allowed in an XML file, and in which combinations.</p> - -<div class="section">To create an XML schema, follow these steps:</div> - -<ol> -<li class="stepexpand"><span>Create a project to contain the XML schema.</span></li> - -<li class="stepexpand"><span>In the workbench, select <span class="menucascade"><span class="uicontrol">File > New > -Other > XML > XML Schema</span></span> and click <span class="uicontrol">Next</span>.</span> -</li> - -<li class="stepexpand"><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="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li> - -</ol> - -<div class="section">The XML schema opens in the XML schema editor. </div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div> -<div><a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.dita deleted file mode 100644 index 1ed3d1bd00..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.dita +++ /dev/null @@ -1,30 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tdelscmp" xml:lang="en-us">
-<title>Deleting XML schema components</title>
-<titlealts>
-<searchtitle>Deleting XML schema components</searchtitle>
-</titlealts>
-<shortdesc>If you have created any XML schema components you no longer need,
-you can delete them.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>deleting<indexterm>components</indexterm></indexterm></indexterm>
-<indexterm>XML schema files<indexterm>deleting<indexterm>components</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><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></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, click the item to delete.</cmd></step>
-<step><cmd>Right-click the item, and, from its pop-up menu, click <uicontrol>Delete</uicontrol>.</cmd>
-</step>
-</steps>
-<result><p>The XML schema editor has a built-in mechanism to handle referential
-integrity issues. When you delete certain components, cleanup will automatically
-occur.</p></result>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html deleted file mode 100644 index a4cc20057b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html +++ /dev/null @@ -1,63 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Deleting XML schema components" /> -<meta name="abstract" content="If you have created any XML schema components you no longer need, you can delete them." /> -<meta name="description" content="If you have created any XML schema components you no longer need, you can delete them." /> -<meta content="XML schema editor, deleting, components, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, deleting, components, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/rrefintg.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tdelscmp" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Deleting XML schema components</title> -</head> -<body id="tdelscmp"><a name="tdelscmp"><!-- --></a> - - -<h1 class="topictitle1">Deleting XML schema components</h1> - - - - -<div><p>If you have created any XML schema components you no longer need, -you can delete them.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To delete an XML -schema component, follow these steps:</p> -</div> - -<ol> -<li><span>Open your XML schema in the XML schema editor.</span></li> - -<li><span>In the Outline view, click the item to delete.</span></li> - -<li><span>Right-click the item, and, from its pop-up menu, click <span class="uicontrol">Delete</span>.</span> -</li> - -</ol> - -<div class="section"><p>The XML schema editor has a built-in mechanism to handle referential -integrity issues. When you delete certain components, cleanup will automatically -occur.</p> -</div> - -</div> - -<div><div class="relref"><strong>Related reference</strong><br /> -<div><a href="../topics/rrefintg.html" title="The XML schema editor has a built-in mechanism to handle referential integrity issues. When you delete certain nodes, clean up for any nodes affected will automatically occur.">Referential integrity in the XML schema editor</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.dita deleted file mode 100644 index 856072ad20..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.dita +++ /dev/null @@ -1,43 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtpref" xml:lang="en-us">
-<title>Editing XML schema file preferences</title>
-<titlealts>
-<searchtitle>Editing XML schema file preferences</searchtitle>
-</titlealts>
-<shortdesc>You can set various preferences for XML schema files such as the
-default target namespace and XML Schema language constructs prefix used.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema files<indexterm>defining<indexterm>default
-target namespace</indexterm></indexterm></indexterm><indexterm>XML schema
-files<indexterm>defining<indexterm>schema prefix</indexterm></indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To define XML schema file preferences, follow these steps:</p></context>
-<steps>
-<step><cmd>Select <menucascade><uicontrol>Window > Preferences > Web and
-XML > XML Schema Files</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Select the <uicontrol>Qualify XML schema language constructs</uicontrol> check
-box if you want a prefix applied to all XML Schema language constructs in
-your XML schema.</cmd></step>
-<step><cmd>In the <uicontrol>XML schema language constructs prefix</uicontrol> field,
-type the prefix you want applied to XML Schema language constructs in your
-XML schema.</cmd><info> The prefix <uicontrol>xsd</uicontrol> 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. <note>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 <uicontrol>Apply</uicontrol>. Any schemas that already
-exist will have the prefix specified in the schema applied to the XML schema
-language constructs.</note></info></step>
-<step><cmd>You can change the <uicontrol>Default Target Namespace</uicontrol> value.</cmd>
-<info>The value specified in this field will be the default target namespace
-for any new XML schema files created.</info></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<result></result>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html deleted file mode 100644 index fe76430875..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html +++ /dev/null @@ -1,71 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing XML schema file preferences" /> -<meta name="abstract" content="You can set various preferences for XML schema files such as the default target namespace and XML Schema language constructs prefix used." /> -<meta name="description" content="You can set various preferences for XML schema files such as the default target namespace and XML Schema language constructs prefix used." /> -<meta content="XML schema files, defining, default target namespace, XML schema files, schema prefix" name="DC.subject" /> -<meta content="XML schema files, defining, default target namespace, XML schema files, schema prefix" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtpref" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing XML schema file preferences</title> -</head> -<body id="tedtpref"><a name="tedtpref"><!-- --></a> - - -<h1 class="topictitle1">Editing XML schema file preferences</h1> - - - - -<div><p>You can set various preferences for XML schema files such as the -default target namespace and XML Schema language constructs prefix used.</p> - -<div class="section"><p>To define XML schema file preferences, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Select <span class="menucascade"><span class="uicontrol">Window > Preferences > Web and -XML > XML Schema Files</span></span>.</span></li> - -<li class="stepexpand"><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="stepexpand"><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="stepexpand"><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="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -<div class="section" /> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.dita deleted file mode 100644 index 847830e6bf..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.dita +++ /dev/null @@ -1,47 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="tedtschm" xml:lang="en-us">
-<title>Editing XML schema properties</title>
-<titlealts>
-<searchtitle>Editing XML schema properties</searchtitle>
-</titlealts>
-<shortdesc>After you create an XML schema, you can edit its various properties,
-such as its namespace and prefix.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>editing XML schemas<indexterm>simple
-types</indexterm></indexterm></indexterm><indexterm>XML schema files<indexterm>editing<indexterm>simple
-types</indexterm></indexterm></indexterm></keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To edit an XML schema's
-properties follow these steps:</p></context>
-<steps>
-<step><cmd>Create a new XML schema or double-click an existing schema in the
-Navigator view.</cmd><info> It will automatically open in the XML schema editor.</info>
-</step>
-<step><cmd>In the Outline view, click <uicontrol>Directives</uicontrol>.<?Pub Caret?></cmd>
-</step>
-<step><cmd>In the Properties view, click the <uicontrol>General</uicontrol> tab.</cmd>
-</step>
-<step><cmd>You can change the <uicontrol>Prefix</uicontrol> associated with
-the current namespace.</cmd><info>Element and attribute names that are associated
-with this namespace will be prefixed with this value.</info></step>
-<step><cmd>You can also edit the <uicontrol>Target namespace</uicontrol> for
-this schema.</cmd><info> A namespace is a URI that provides a unique name
-to associate with all the elements and type definitions in a schema.</info>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this XML schema.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000002389?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html deleted file mode 100644 index 840ef3a847..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html +++ /dev/null @@ -1,74 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing XML schema properties" /> -<meta name="abstract" content="After you create an XML schema, you can edit its various properties, such as its namespace and prefix." /> -<meta name="description" content="After you create an XML schema, you can edit its various properties, such as its namespace and prefix." /> -<meta content="XML schema editor, editing XML schemas, simple types, XML schema files, editing" name="DC.subject" /> -<meta content="XML schema editor, editing XML schemas, simple types, XML schema files, editing" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtschm" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing XML schema properties</title> -</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="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To edit an XML schema's -properties follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><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="stepexpand"><span>In the Outline view, click <span class="uicontrol">Directives</span>.</span> -</li> - -<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">General</span> tab.</span> -</li> - -<li class="stepexpand"><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="stepexpand"><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. -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this XML schema.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.dita deleted file mode 100644 index 670f5d02f2..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.dita +++ /dev/null @@ -1,34 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="timpschm" xml:lang="en-us">
-<title>Importing XML schemas</title>
-<titlealts>
-<searchtitle>Importing XML schemas</searchtitle>
-</titlealts>
-<shortdesc>If you want to work with XML schema files that you created outside
-of the product, you can import them into the workbench and open them in the
-XML schema editor. The XML schema editor provides you with a structured view
-of the XML schema.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema files<indexterm>importing</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><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<?Pub Caret?>:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>File > Import</uicontrol></menucascade>.</cmd>
-</step>
-<step><cmd>Select the import source.</cmd><info> Click <uicontrol>Next</uicontrol>.</info>
-</step>
-<step><cmd>Fill in the fields in the Import wizard as necessary.</cmd><info> When
-you are finished, click <uicontrol>Finish</uicontrol>.</info></step>
-</steps>
-<result><p>The imported schema now appears in the Navigator view. Double-click
-it to open it in the XML schema editor.</p></result>
-</taskbody>
-</task>
-<?Pub *0000001448?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html deleted file mode 100644 index 8726a2ce3b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html +++ /dev/null @@ -1,76 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Importing XML schemas" /> -<meta name="abstract" content="If you want to work with XML schema files that you created outside of the product, you can import them into the workbench and open them in the XML schema editor. The XML schema editor provides you with a structured view of the XML schema." /> -<meta name="description" content="If you want to work with XML schema files that you created outside of the product, you can import them into the workbench and open them in the XML schema editor. The XML schema editor provides you with a structured view of the XML schema." /> -<meta content="XML schema files, importing" name="DC.subject" /> -<meta content="XML schema files, importing" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tvdtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddimpt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddincl.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="timpschm" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Importing XML schemas</title> -</head> -<body id="timpschm"><a name="timpschm"><!-- --></a> - - -<h1 class="topictitle1">Importing XML schemas</h1> - - - - -<div><p>If you want to work with XML schema files that you created outside -of the product, you can import them into the workbench and open them in the -XML schema editor. The XML schema editor provides you with a structured view -of the XML schema.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To import an XML -schema into the workbench:</p> -</div> - -<ol> -<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">File > Import</span></span>.</span> -</li> - -<li class="stepexpand"><span>Select the import source.</span> Click <span class="uicontrol">Next</span>. -</li> - -<li class="stepexpand"><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="section"><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><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div> -<div><a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div> -<div><a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema.">Adding import elements</a></div> -<div><a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema.">Adding include elements</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.dita deleted file mode 100644 index c4f2a0ffd1..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.dita +++ /dev/null @@ -1,38 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tnavsrc" xml:lang="en-us">
-<title>Navigating XML schemas</title>
-<titlealts>
-<searchtitle>Navigating XML schemas</searchtitle>
-</titlealts>
-<shortdesc>When you are working in the Source view, you can use F3 to navigate
-through the file by placing your cursor in the appropriate item and clicking
-F3 to jump to the item it refers to. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema files<indexterm>navigating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>You can jump to any of the following items:</p><ul>
-<li>Element or attribute declaration's type</li>
-<li>Element references</li>
-<li>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>You must place your cursor exactly in the location of the reference
-(for example between the double quotes for <systemoutput>type = " "</systemoutput> or
- <systemoutput>base = " "</systemoutput>).</p><p>For example, if you place
-your cursor anywhere in the following text and click F3:</p><p> <systemoutput><element
-name="shipTo" type="po:USAddress"></element></systemoutput> </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 following
-text and click F3:</p><p> <systemoutput><element ref="po:ContactElement"></element></systemoutput> </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></context>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html deleted file mode 100644 index 582def5858..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html +++ /dev/null @@ -1,80 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Navigating XML schemas" /> -<meta name="abstract" content="When you are working in the Source view, you can use F3 to navigate through the file by placing your cursor in the appropriate item and clicking F3 to jump to the item it refers to." /> -<meta name="description" content="When you are working in the Source view, you can use F3 to navigate through the file by placing your cursor in the appropriate item and clicking F3 to jump to the item it refers to." /> -<meta content="XML schema files, navigating" name="DC.subject" /> -<meta content="XML schema files, navigating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tnavsrc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Navigating XML schemas</title> -</head> -<body id="tnavsrc"><a name="tnavsrc"><!-- --></a> - - -<h1 class="topictitle1">Navigating XML schemas</h1> - - - - -<div><p>When you are working in the Source view, you can use F3 to navigate -through the file by placing your cursor in the appropriate item and clicking -F3 to jump to the item it refers to. </p> - -<div class="section"><p>You can jump to any of the following items:</p> -<ul> -<li>Element or attribute declaration's type</li> - -<li>Element references</li> - -<li>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>You must place your cursor exactly in the location of the reference -(for example between the double quotes for <tt class="sysout">type = " "</tt> or - <tt class="sysout">base = " "</tt>).</p> -<p>For example, if you place -your cursor anywhere in the following text and click F3:</p> -<p> <tt class="sysout"><element -name="shipTo" type="po:USAddress"></element></tt> </p> -<p>the -cursor will automatically jump to the location in the file where the type -USAddress is defined.</p> -<p>Or, if you place your cursor anywhere in the following -text and click F3:</p> -<p> <tt class="sysout"><element ref="po:ContactElement"></element></tt> </p> -<p>the -cursor will automatically jump to the location in the file where the global -element ContactElement is defined.</p> -<p>This works across files. For example, -if the type you have selected is defined in another XML schema and you click -F3, you will automatically be taken to that file.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.dita deleted file mode 100644 index 0d1c0b0cc8..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.dita +++ /dev/null @@ -1,95 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="refactoring" xml:lang="en-us">
-<title>Refactoring in XML Schema Files</title>
-<titlealts>
-<searchtitle>Refactoring in XML Schema Files</searchtitle>
-</titlealts>
-<shortdesc>Within an XML Schema file, refactoring allows authors to make a
-single artifact change, and have that change implemented throughout all other
-dependant artifacts.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema files</indexterm><indexterm>XML schema editor</indexterm>
-<indexterm>refactoring</indexterm><indexterm>renaming</indexterm><indexterm>editing
-XML schemas</indexterm><indexterm>dependant artifacts</indexterm></keywords>
-</metadata></prolog>
-<taskbody>
-<prereq></prereq>
-<context>Refactoring eliminates the need for the tedious editing necessary
-to recover broken dependencies caused by artifact changes which cause ripple
-effects on other dependant artifacts (such as renaming an XML Schema element).</context>
-<steps>
-<step><cmd>Create a new XML schema or double-click an existing schema in the
-Navigator view.</cmd><info> It will automatically open in the XML schema editor.</info>
-</step>
-<step><cmd>To refactor an artifact, position cursor within the artifact, right-click
-the artifact, click <menucascade><uicontrol>Refactor</uicontrol><uicontrol>Rename</uicontrol>
-</menucascade></cmd><info>A popup dialog will request the entry of a new name
-for that artifact</info>
-<substeps>
-<substep><cmd>Type in the new name of the artifact.</cmd></substep>
-<substep><cmd>(Optional) Click <b>Preview</b><?Pub Caret?>.</cmd><info>A window
-will open indicating all of the changes which will take place due to the refactoring.</info>
-</substep>
-<substep><cmd>Click <uicontrol>OK.</uicontrol></cmd></substep>
-</substeps>
-</step>
-</steps>
-<result>The new name will be entered in the opened XSD source, as well as
-in all dependant artifacts</result>
-<example><b><u>Component References in XML Schema</u></b><simpletable>
-<sthead>
-<stentry>Global named components</stentry>
-<stentry>Reference</stentry>
-</sthead>
-<strow>
-<stentry><ul>
-<li><element name="foo"></li>
-</ul></stentry>
-<stentry><ul>
-<li><element ref="foo"></li>
-<li><element substitutionGroup="foo"</li>
-</ul></stentry>
-</strow>
-<strow>
-<stentry><ul>
-<li><simple/complexType name="foo"></li>
-</ul></stentry>
-<stentry><ul>
-<li><element type="foo"></li>
-<li><attribute type="foo"></li>
-<li><restriction base="foo"></li>
-<li><substitution base="foo"></li>
-</ul></stentry>
-</strow>
-<strow>
-<stentry><ul>
-<li><attribute name="foo"></li>
-</ul></stentry>
-<stentry><ul>
-<li><attribute ref="foo"></li>
-</ul></stentry>
-</strow>
-<strow>
-<stentry><ul>
-<li><attributeGroup name="foo"></li>
-</ul></stentry>
-<stentry><ul>
-<li><attributeGroup ref="foo"></li>
-</ul></stentry>
-</strow>
-<strow>
-<stentry><ul>
-<li><group name="foo"></li>
-</ul></stentry>
-<stentry><ul>
-<li><group ref="foo"></li>
-</ul></stentry>
-</strow>
-</simpletable></example>
-<postreq></postreq>
-</taskbody>
-</task>
-<?Pub *0000003131?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.html deleted file mode 100644 index ceb881d068..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.html +++ /dev/null @@ -1,168 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Refactoring in XML Schema Files" /> -<meta name="abstract" content="Within an XML Schema file, refactoring allows authors to make a single artifact change, and have that change implemented throughout all other dependant artifacts." /> -<meta name="description" content="Within an XML Schema file, refactoring allows authors to make a single artifact change, and have that change implemented throughout all other dependant artifacts." /> -<meta content="XML schema files, XML schema editor, refactoring, renaming, editing XML schemas, dependant artifacts" name="DC.subject" /> -<meta content="XML schema files, XML schema editor, refactoring, renaming, editing XML schemas, dependant artifacts" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="refactoring" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Refactoring in XML Schema Files</title> -</head> -<body id="refactoring"><a name="refactoring"><!-- --></a> - - -<h1 class="topictitle1">Refactoring in XML Schema Files</h1> - - - - -<div><p>Within an XML Schema file, refactoring allows authors to make a -single artifact change, and have that change implemented throughout all other -dependant artifacts.</p> - -<div class="p" /> - -<div class="section">Refactoring eliminates the need for the tedious editing necessary -to recover broken dependencies caused by artifact changes which cause ripple -effects on other dependant artifacts (such as renaming an XML Schema element).</div> - -<ol> -<li class="stepexpand"><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="stepexpand"><span>To refactor an artifact, position cursor within the artifact, right-click -the artifact, click <span class="menucascade"><span class="uicontrol">Refactor</span> > <span class="uicontrol">Rename</span> -</span></span> A popup dialog will request the entry of a new name -for that artifact -<ol type="a"> -<li class="substepexpand"><span>Type in the new name of the artifact.</span></li> - -<li class="substepexpand"><span>(Optional) Click <strong>Preview</strong>.</span> A window -will open indicating all of the changes which will take place due to the refactoring. -</li> - -<li class="substepexpand"><span>Click <span class="uicontrol">OK.</span></span></li> - -</ol> - -</li> - -</ol> - -<div class="section">The new name will be entered in the opened XSD source, as well as -in all dependant artifacts</div> - -<div class="example"><strong><u>Component References in XML Schema</u></strong><table summary="" cellspacing="0" cellpadding="4" border="1" class="simpletableborder"> -<tr> -<th valign="bottom" align="left" id="N100EB">Global named components</th> - -<th valign="bottom" align="left" id="N100F1">Reference</th> - -</tr> - -<tr> -<td valign="top" headers="N100EB"><ul> -<li><element name="foo"></li> - -</ul> -</td> - -<td valign="top" headers="N100F1"><ul> -<li><element ref="foo"></li> - -<li><element substitutionGroup="foo"</li> - -</ul> -</td> - -</tr> - -<tr> -<td valign="top" headers="N100EB"><ul> -<li><simple/complexType name="foo"></li> - -</ul> -</td> - -<td valign="top" headers="N100F1"><ul> -<li><element type="foo"></li> - -<li><attribute type="foo"></li> - -<li><restriction base="foo"></li> - -<li><substitution base="foo"></li> - -</ul> -</td> - -</tr> - -<tr> -<td valign="top" headers="N100EB"><ul> -<li><attribute name="foo"></li> - -</ul> -</td> - -<td valign="top" headers="N100F1"><ul> -<li><attribute ref="foo"></li> - -</ul> -</td> - -</tr> - -<tr> -<td valign="top" headers="N100EB"><ul> -<li><attributeGroup name="foo"></li> - -</ul> -</td> - -<td valign="top" headers="N100F1"><ul> -<li><attributeGroup ref="foo"></li> - -</ul> -</td> - -</tr> - -<tr> -<td valign="top" headers="N100EB"><ul> -<li><group name="foo"></li> - -</ul> -</td> - -<td valign="top" headers="N100F1"><ul> -<li><group ref="foo"></li> - -</ul> -</td> - -</tr> - -</table> -</div> - -<div class="section" /> - -</div> - -<div /> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.dita deleted file mode 100644 index 5dcffb0cb8..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.dita +++ /dev/null @@ -1,60 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tvdtschm" xml:lang="en-us">
-<title>Validating XML schemas</title>
-<titlealts>
-<searchtitle>Validating XML schemas</searchtitle>
-</titlealts>
-<shortdesc>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.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema files<indexterm>validating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><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:</p></context>
-<steps>
-<step><cmd>Right-click your file in the Navigator view and click <uicontrol>Run
-Validation</uicontrol>.</cmd></step>
-<step><cmd> If validation was not successful, you can refer to the Problems
-view to see what problems were logged. </cmd><info> <note>If you receive an
-error message indicating that the Problems view is full, you can increase
-the number of error messages allowed by selecting <menucascade><uicontrol>Properties
-> Validation</uicontrol></menucascade> <?Pub Caret?>and specifying the maximum
-number of error messages allowed.</note></info></step>
-</steps>
-<result><p>The XML schema support in the XML schema editor is based on the
-W3C XML Schema Recommendation Specification. The XML Schema specifications
-XML Schema Part 1: Structures and XML Schema Part 2: Datatypes 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 XML Schema Part 1: Structures
-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:
- <systemoutput>ct-props-correct</systemoutput> 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". </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 <uicontrol>Properties</uicontrol>,
-then select <uicontrol>Validation</uicontrol>. Any validators you can run
-against your project will be listed in the Validation page.</p></result>
-</taskbody>
-<related-links>
-<link href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.dita" scope="peer">
-<desc>General validation information</desc>
-</link>
-<link href="http://www.w3.org/TR/xmlschema-1" scope="external"><linktext>XML
-Schema Part 1: Structures</linktext>
-<desc>See the W3C Web site for more information on XML Schema specifications</desc>
-</link>
-<link href="http://www.w3.org/TR/xmlschema-2" scope="external"><linktext>XML
-Schema Part 2: Datatypes</linktext>
-<desc>See the W3C Web site for more information on XML Schema specifications</desc>
-</link>
-</related-links>
-</task>
-<?Pub *0000003124?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html deleted file mode 100644 index b684af6a7b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html +++ /dev/null @@ -1,91 +0,0 @@ -<?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 lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 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" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Validating XML schemas" /> -<meta name="abstract" content="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view." /> -<meta name="description" content="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view." /> -<meta content="XML schema files, validating" name="DC.subject" /> -<meta content="XML schema files, validating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcxmlsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html" /> -<meta scheme="URI" name="DC.Relation" content="http://www.w3.org/TR/xmlschema-1" /> -<meta scheme="URI" name="DC.Relation" content="http://www.w3.org/TR/xmlschema-2" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tvdtschm" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Validating XML schemas</title> -</head> -<body id="tvdtschm"><a name="tvdtschm"><!-- --></a> - - -<h1 class="topictitle1">Validating XML schemas</h1> - - - - -<div><p>Validating an XML schema determines whether the current state of -the XML schema file is semantically valid. Any errors will be displayed in -the Problems view.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To validate an XML -schema:</p> -</div> - -<ol> -<li class="stepexpand"><span>Right-click your file in the Navigator view and click <span class="uicontrol">Run -Validation</span>.</span></li> - -<li class="stepexpand"><span> If validation was not successful, you can refer to the Problems -view to see what problems were logged. </span> <div class="note"><span class="notetitle">Note:</span> If you receive an -error message indicating that the Problems view is full, you can increase -the number of error messages allowed by selecting <span class="menucascade"><span class="uicontrol">Properties -> Validation</span></span> and specifying the maximum -number of error messages allowed.</div> -</li> - -</ol> - -<div class="section"><p>The XML schema support in the XML schema editor is based on the -W3C XML Schema Recommendation Specification. The XML Schema specifications -XML Schema Part 1: Structures and XML Schema Part 2: Datatypes 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 XML Schema Part 1: Structures -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</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". </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><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations.">Creating XML schemas</a></div> -</div> -<div class="relinfo"><strong>Related information</strong><br /> -<div><a href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html" title="General validation information">../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html</a></div> -<div><a href="http://www.w3.org/TR/xmlschema-1" target="_blank" title="See the W3C Web site for more information on XML Schema specifications">XML -Schema Part 1: Structures</a></div> -<div><a href="http://www.w3.org/TR/xmlschema-2" target="_blank" title="See the W3C Web site for more information on XML Schema specifications">XML -Schema Part 2: Datatypes</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file |