Skip to main content

This CGIT instance is deprecated, and repositories have been moved to Gitlab or Github. See the repository descriptions for specific locations.

summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html')
-rw-r--r--docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html57
1 files changed, 0 insertions, 57 deletions
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 bac41e2c42..0000000000
--- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html
+++ /dev/null
@@ -1,57 +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>Importing XML schemas</title>
-</head>
-<body id="timpschm"><a name="timpschm"><!-- --></a>
-
-<h1 class="topictitle1">Importing XML schemas</h1>
-<div>
- <div>
- <div>
- If you want to work with XML schema files that you created outside
- of the product, you can import them into the workbench and open them
- in the XML schema editor. The XML schema editor provides you with a
- structured view of the XML schema.</div>
- </div>
- <div class="skipspace"><p>The following instructions were written for the
- Resource perspective, but they will also work in many other
- perspectives.</p>
-<p>To import
-an XML schema into the workbench, follow these steps:</p>
-</div>
-<ol><li class="skipspace"><span>Click <b> <span class="menucascade"><span class="uicontrol">File &gt; Import</span></span></b>.</span></li>
-<li class="skipspace"><span>Select the import source.</span> Click <b> <span class="uicontrol">Next</span></b>.</li>
-<li class="skipspace"><span>Fill in the fields in the Import wizard as necessary.</span> When
-you are finished, click <b> <span class="uicontrol">Finish</span></b>.</li>
-</ol>
-<div class="skipspace"><p>The imported schema now appears in the Navigator view. Double-click
-it to open it in the XML schema editor.</p>
-</div>
-</div>
-
-<div><p><b class="relconceptshd">Related concepts</b><br />
-<a href="../topics/cxmlsced.html" title="XML schemas are an XML language for describing and constraining the content of XML files.?">XML schema editor</a><br />
-</p>
-<p><b class="reltaskshd">Related tasks</b><br />
-<a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a><br />
-<a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating an XML schema</a><br />
-<a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. XML schema defines two constructs to support this: include and import. The include element brings in definitions and declarations from the included schema into the current schema. It requires the included schema to be in the same target namespace as the including schema. The import element behaves in a similar way, with the exception that the imported schema can come from a different namespace.">Adding an import element</a><br />
-<a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. XML schema defines two constructs to support this: include and import. The include element brings in definitions and declarations from the included schema into the current schema. It requires the included schema to be in the same target namespace as the including schema. The import element behaves in a similar way, with the exception that the imported schema can come from a different namespace.">Adding an include element</a><br />
-</p>
-</div>
-</body>
-</html> \ No newline at end of file

Back to the top