| <html><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><link type="text/css" href="../../../..//default_style.css" rel="stylesheet"><link type="text/css" href="../../../..//webtools/wtp.css" rel="stylesheet"><title>XML Component Overview</title></head><body><table border="0" cellpadding="2" cellspacing="5" width="100%"><tbody><tr><td align="left" width="60%"><font class="indextop">XML Component</font><br><font class="indexsub">XML Component Overview</font></td><td width="40%"><img src="../../../..//webtools/images/wtplogosmall.jpg" align="middle" height="129" hspace="50" width="207" alt="WTP Logo" usemap="logomap"><map id="logomap" name="logomap"><area coords="0,0,207,129" href="/webtools/" alt="WTP Home"></map></td></tr></tbody></table><table border="0" cellpadding="2" cellspacing="5" width="100%"><col width="16"><col width="*"><tbody><tr><td align="right" valign="top"> | |
| | |
| </td><td valign="top"><p>Last modified March 27, 2005</p></td></tr><tr><td align="right" valign="top"> | |
| | |
| </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 colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">XML UI</font></b></td></tr><tr><td align="right" valign="top"> | |
| | |
| </td><td valign="top"><p> | |
| There is a UI Component to XML. The UI component has little | |
| API and .... | |
| </p></td></tr><tr><td align="right" valign="top"><img src="../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td>Editor related IDs</td></tr><tr><td align="right" valign="top"> | |
| | |
| </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 align="right" valign="top"> | |
| | |
| </td><td valign="top"><h4>Source page</h4></td></tr><tr><td align="right" valign="top"> | |
| | |
| </td><td valign="top"><h4>Context menus [etc]</h4></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">XML Core</font></b></td></tr><tr><td align="right" valign="top"> | |
| | |
| </td><td valign="top"><p> | |
| The more substantial contribution of XML is its core APIs. | |
| </p></td></tr><tr><td align="right" valign="top"><img src="../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td>XML Catalog and XML Resolution</td></tr><tr><td align="right" valign="top"> | |
| | |
| </td><td valign="top"><p>[Craig to provide]</p></td></tr><tr><td align="right" valign="top"><img src="../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td>DOM Parser</td></tr><tr><td align="right" valign="top"> | |
| | |
| </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 align="right" valign="top"> | |
| | |
| </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 align="right" valign="top"> | |
| | |
| </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 align="right" valign="top"><img src="../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td>Content types and encoding</td></tr><tr><td align="right" valign="top"><img src="../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td>Content Models</td></tr><tr><td align="right" valign="top"><img src="../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td>Formatting</td></tr><tr><td align="right" valign="top"><img src="../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td>List of StructuredDocument regions</td></tr><tr><td align="right" valign="top"><img src="../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td>List of Partition Types</td></tr><tr><td align="right" valign="top"><img src="../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td>Extension Points</td></tr><tr><td align="right" valign="top"> | |
| | |
| </td><td valign="top"><h4>Comment Elements</h4></td></tr><tr><td align="right" valign="top"> | |
| | |
| </td><td valign="top"><h4>document types</h4></td></tr></tbody></table></body></html> |