remove more emf'ness
diff --git a/docs/dev-plans/xsd_project_plan_2.5.html b/docs/dev-plans/xsd_project_plan_2.5.html
index ba9282e..d276bba 100644
--- a/docs/dev-plans/xsd_project_plan_2.5.html
+++ b/docs/dev-plans/xsd_project_plan_2.5.html
@@ -9,7 +9,6 @@
<link rel="stylesheet" href="http://www.eclipse.org/default_style.css" type="text/css" />
- <!-- <link rel="stylesheet" href="http://www.eclipse.org/emf/docs/book.css" type="text/css" /> -->
</head>
<body lang="EN-US" xml:lang="EN-US">
@@ -19,7 +18,7 @@
<br />
Draft 2.5.0 Plans</h1>
- <p>Last revised <tt>$Date: 2008/07/11 17:33:10 $</tt> (
+ <p>Last revised <tt>$Date: 2008/07/11 17:40:53 $</tt> (
<img width="12" height="12" src="../../../images/green-box.gif"
border="0" />
@@ -332,15 +331,6 @@
for information about how to write compliant plug-ins.</p>
- <p>Almost the entire XSD code is available in non-internal packages and are
- assumed to be used and extended by users. The main exception is extending the Ecore
- model itself directly (i.e., extending or implementing <tt>org.eclipse.emf.ecore.EModelElement</tt>). There are
- no guarantees that these extensions won't be broken by changes in XSD. If you are not sure that your code has
- such extensions, please send a question to the
- <a href="mailto:mdt-xsd.dev@eclipse.org">xsd.dev@eclipse.org</a> developer mailing list or to the
- <a href="news://news.eclipse.org/eclipse.technology.xsd">eclipse.technology.xsd</a> newsgroup.</p>
-
-
<h3>
<a name="MigrationGuide">
