| 
| Abstract Schema [message #927] | Fri, 13 September 2002 16:58  |  | 
| Eclipse User  |  |  |  |  | Originally posted by: troynet+web.ugcs.net 
 What is going to be the relationship between the IBM (soon to be Eclipse)
 XML Schema Infoset API with the DOM 3 Abstract Schemas?
 
 I could be completely misunderstanding everything, but it seems to me that
 they overlap in purpose and functionality with Abstract Schemas offering a
 superset.
 |  |  |  | 
| 
| Re: Abstract Schema [message #957 is a reply to message #927] | Fri, 13 September 2002 18:07  |  | 
| Eclipse User  |  |  |  |  | Originally posted by: merks.ca.ibm.com 
 --------------5D348A7CBD532D09FAA71C38
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 Troy,
 
 I take your question to indicate that you weren't aware of this announcement?
 
 http://lists.w3.org/Archives/Public/www-dom/2002JulSep/0010. html
 
 It wasn't so easy to spot among all the links...
 
 The DOM work is focusing mainly on supporting PSVI and supporting both DTD and
 XML Schema.  Editing support for XML Schema is not a stated goal.
 
 XSD fills this spacious niche by supporting the full abstract component model
 of parts 1 and 2 of the Spec, in all it's carefully authored detail.  It also
 provides a rich editing model for representing the XML concrete syntax of XML
 Schema and for supporting bottom up construction of abstract components.  The
 intent is to complement the DOM work.
 
 
 Troy Bridoux wrote:
 
 > What is going to be the relationship between the IBM (soon to be Eclipse)
 > XML Schema Infoset API with the DOM 3 Abstract Schemas?
 >
 > I could be completely misunderstanding everything, but it seems to me that
 > they overlap in purpose and functionality with Abstract Schemas offering a
 > superset.
 
 --------------5D348A7CBD532D09FAA71C38
 Content-Type: text/html; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 <html>
 Troy,
 <p>I take your question to indicate that you weren't aware of this announcement?
 <blockquote><a href=" http://lists.w3.org/Archives/Public/www-dom/2002JulSep/0010. html"> http://lists.w3.org/Archives/Public/www-dom/2002JulSep/0010. html</a></blockquote>
 It wasn't so easy to spot among all the links...
 <p>The DOM work is focusing mainly on supporting PSVI and supporting both
 DTD and XML Schema.  Editing support for XML Schema is not a stated
 goal.
 <p>XSD fills this spacious niche by supporting the full abstract component
 model of parts 1 and 2 of the Spec, in all it's carefully authored detail. 
 It also provides a rich editing model for representing the XML concrete
 syntax of XML Schema and for supporting bottom up construction of abstract
 components.  The intent is to complement the DOM work.
 <br> 
 <p>Troy Bridoux wrote:
 <blockquote TYPE=CITE>What is going to be the relationship between the
 IBM (soon to be Eclipse)
 <br>XML Schema Infoset API with the DOM 3 Abstract Schemas?
 <p>I could be completely misunderstanding everything, but it seems to me
 that
 <br>they overlap in purpose and functionality with Abstract Schemas offering
 a
 <br>superset.</blockquote>
 </html>
 
 --------------5D348A7CBD532D09FAA71C38--
 |  |  |  | 
| 
| Re: Abstract Schema [message #562425 is a reply to message #927] | Fri, 13 September 2002 18:07  |  | 
| Eclipse User  |  |  |  |  | --------------5D348A7CBD532D09FAA71C38 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 Troy,
 
 I take your question to indicate that you weren't aware of this announcement?
 
 http://lists.w3.org/Archives/Public/www-dom/2002JulSep/0010. html
 
 It wasn't so easy to spot among all the links...
 
 The DOM work is focusing mainly on supporting PSVI and supporting both DTD and
 XML Schema.  Editing support for XML Schema is not a stated goal.
 
 XSD fills this spacious niche by supporting the full abstract component model
 of parts 1 and 2 of the Spec, in all it's carefully authored detail.  It also
 provides a rich editing model for representing the XML concrete syntax of XML
 Schema and for supporting bottom up construction of abstract components.  The
 intent is to complement the DOM work.
 
 
 Troy Bridoux wrote:
 
 > What is going to be the relationship between the IBM (soon to be Eclipse)
 > XML Schema Infoset API with the DOM 3 Abstract Schemas?
 >
 > I could be completely misunderstanding everything, but it seems to me that
 > they overlap in purpose and functionality with Abstract Schemas offering a
 > superset.
 
 --------------5D348A7CBD532D09FAA71C38
 Content-Type: text/html; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 <html>
 Troy,
 <p>I take your question to indicate that you weren't aware of this announcement?
 <blockquote><a href=" http://lists.w3.org/Archives/Public/www-dom/2002JulSep/0010. html"> http://lists.w3.org/Archives/Public/www-dom/2002JulSep/0010. html</a></blockquote>
 It wasn't so easy to spot among all the links...
 <p>The DOM work is focusing mainly on supporting PSVI and supporting both
 DTD and XML Schema.  Editing support for XML Schema is not a stated
 goal.
 <p>XSD fills this spacious niche by supporting the full abstract component
 model of parts 1 and 2 of the Spec, in all it's carefully authored detail. 
 It also provides a rich editing model for representing the XML concrete
 syntax of XML Schema and for supporting bottom up construction of abstract
 components.  The intent is to complement the DOM work.
 <br> 
 <p>Troy Bridoux wrote:
 <blockquote TYPE=CITE>What is going to be the relationship between the
 IBM (soon to be Eclipse)
 <br>XML Schema Infoset API with the DOM 3 Abstract Schemas?
 <p>I could be completely misunderstanding everything, but it seems to me
 that
 <br>they overlap in purpose and functionality with Abstract Schemas offering
 a
 <br>superset.</blockquote>
 </html>
 
 --------------5D348A7CBD532D09FAA71C38--
 |  |  |  | 
Powered by 
FUDForum. Page generated in 5.94684 seconds