blob: da0ae94b546d46cdb99bb3dd18b70edd0b4c05f6 [file] [log] [blame]
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="../../../..//default_style.css" type="text/css">
<link rel="stylesheet" href="../../../..//webtools/wtp.css" type="text/css">
<title>XML Component Overview</title>
</head>
<body>
<table width="100%" cellspacing="5" cellpadding="2" border="0">
<tbody>
<tr>
<td width="60%" align="left"><font class="indextop">XML Component</font>
<br>
<font class="indexsub">XML Component Overview</font></td><td width="40%"><img width="120" hspace="50" height="86" align="middle" src="../../../..//images/Idea.jpg"></td>
</tr>
</tbody>
</table>
<table width="100%" cellspacing="5" cellpadding="2" border="0">
<col width="16">
<col width="*">
<tbody>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<p>Last modified March 27, 2005</p>
</td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<p>
<i>
[This document is a work in progress. It is an attempt
to capture the key concepts of the WTP XML Component.
Note that the concepts presented here may differ from
what is found in the currently released code. This
document describes the architecture, or "end goal", of
the component. Once this document is finalized, the
intent is to bring the code and its specs into line with
this document.]
</i>
</p>
</td>
</tr>
<tr>
<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">XML UI</font></b></td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<p>
There is a UI Component to XML. The UI component has little
API and ....
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../..//images/Adarrow.gif"></td><td>Editor related IDs</td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<p>
Some of these IDs are literally used in WTP 1.0, some are
considered reserved for future use.
</p>
</td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<h4>Source page</h4>
</td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<h4>Context menus [etc]</h4>
</td>
</tr>
<tr>
<td valign="top" bgcolor="#0080c0" align="left" colspan="2"><b><font face="Arial,Helvetica" color="#ffffff">XML Core</font></b></td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<p>
The more substantial contribution of XML is its core APIs.
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../..//images/Adarrow.gif"></td><td>XML Catalog and XML Resolution</td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<p>[Craig to provide]</p>
</td>
</tr>
<tr>
<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../..//images/Adarrow.gif"></td><td>DOM Parser</td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<p>
This DOM parser complies in general terms to the Base DOM
APIs Version 2.0. Plus it has a number of other features
that go beyond the w3c specified APIs.
</p>
</td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<p>
One thing that's very important to note, though, it that
this DOM Parser is specifically made to work with ill formed
text. This is important for "editing" sorts of function
since the DOM is often invalid while typing. We use
heuristics to do the best job of parsing it to what we think
is expected. Clients need to be aware however, this makes
this DOM Parser inappropriate to use for other things, since
most specs call for the parser to fail on ill formed text.
</p>
</td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<p>
In addition to the w3c standard base DOM API methods, our
DOM provides
<ul>
<li>
Each Node implements SSE's IIndexedRegion so its
expected it can report back its exact source
locations.
</li>
<li>
There are some "read-only" APIs that allow nodes be
made read-only with respect to their data,
attributes or children.
</li>
<li>
The Nodes implement SSE's INodeNotifier so
INodeAdapters can be added to specific Nodes, so the
adapters can be notified when ever there is a
change.
</li>
<li>
We have introduced the concept of a "comment
element". In many development situations, clients
want to introduce a "custom element" which in other
contexts are treated as a simple comment.
</li>
</ul>
</p>
</td>
</tr>
<tr>
<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../..//images/Adarrow.gif"></td><td>Content types and encoding</td>
</tr>
<tr>
<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../..//images/Adarrow.gif"></td><td>Content Models</td>
</tr>
<tr>
<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../..//images/Adarrow.gif"></td><td>Formatting</td>
</tr>
<tr>
<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../..//images/Adarrow.gif"></td><td>List of StructuredDocument regions</td>
</tr>
<tr>
<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../..//images/Adarrow.gif"></td><td>List of Partition Types</td>
</tr>
<tr>
<td valign="top" align="right"><img width="16" height="16" border="0" src="../../../..//images/Adarrow.gif"></td><td>Extension Points</td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<h4>Comment Elements</h4>
</td>
</tr>
<tr>
<td valign="top" align="right">&nbsp;</td><td valign="top">
<h4>document types</h4>
</td>
</tr>
</tbody>
</table>
</body>
</html>