docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html - sourceediting/webtools.sourceediting - Gitiles

 <?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 brings in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." />
 <meta name="description" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to brings in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." />
 <meta 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 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
 brings in definitions and declarations from the included schema into the current
 schema. The included schema must be in the same target namespace as the including
 schema. </p>

 <div class="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 should be displayed in the Graph view.</li>

 <li class="stepexpand"><span>In the Graph view, right click in the <strong>Directives</strong> section
 and click <span class="uicontrol">Add Include</span>.</span></li>

 <li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click
 the <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This&#10;graphic is the Browse button" /> button to the right of the <span class="uicontrol">Schema
 location</span> field.</span> The XML schema file you select must
 have the same namespace as the current schema.</li>

 <li class="stepexpand"><span>If you want to select an XML schema located in the workbench, select
 the <span class="uicontrol">Workbench projects</span> radio button and click <span class="uicontrol">Next</span>. </span>
 <ol type="a">
 <li><span>Select the schema you want to include and click <span class="uicontrol">Finish</span>.</span>
 </li>

 </ol>

 </li>

 <li class="stepexpand"><span>If you want to select an XML schema located on the Web, select
 the <span class="uicontrol">HTTP</span> radio button and click <span class="uicontrol">Next</span>.</span>
 <ol type="a">
 <li><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>. </span>
 </li>

 </ol>

  <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, and the <span class="uicontrol">App
 Info</span> page can be used to provide information for applications.
 </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>&lt;complexType name="Address"&gt;
     &lt;sequence&gt;
         &lt;element name="name" type="string"&gt;
         &lt;element name="street" type="string"&gt;
     &lt;/sequence&gt;
 &lt;/complexType&gt;
 </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>


 </body>
 </html>
	<?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 brings in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." />
	<meta name="description" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to brings in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." />
	<meta 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 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
	brings in definitions and declarations from the included schema into the current
	schema. The included schema must be in the same target namespace as the including
	schema. </p>

	<div class="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 should be displayed in the Graph view.</li>

	<li class="stepexpand"><span>In the Graph view, right click in the <strong>Directives</strong> section
	and click <span class="uicontrol">Add Include</span>.</span></li>

	<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click
	the <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> button to the right of the <span class="uicontrol">Schema
	location</span> field.</span> The XML schema file you select must
	have the same namespace as the current schema.</li>

	<li class="stepexpand"><span>If you want to select an XML schema located in the workbench, select
	the <span class="uicontrol">Workbench projects</span> radio button and click <span class="uicontrol">Next</span>. </span>
	<ol type="a">
	<li><span>Select the schema you want to include and click <span class="uicontrol">Finish</span>.</span>
	</li>

	</ol>

	</li>

	<li class="stepexpand"><span>If you want to select an XML schema located on the Web, select
	the <span class="uicontrol">HTTP</span> radio button and click <span class="uicontrol">Next</span>.</span>
	<ol type="a">
	<li><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>. </span>
	</li>

	</ol>

	<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, and the <span class="uicontrol">App
	Info</span> page can be used to provide information for applications.
	</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>


	</body>
	</html>