Proposed requirements are organized into categories. Some requirements
occur in more than one category in the future.
Each requirement has a number. Underneath the number is a "hardness"
and "status".
12. hard approved
|
The parser shall support SAX2.
See also:
13
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Tue Jul 11 2000 - 23:42:10 MEST)
Re: parser-next-gen goals, plan, and requirements Arnaud Le Hors (Wed Jul 12 2000 - 02:49:04 MEST)
|
14. hard approved
|
The parser shall validate XML 1.0.
Re: parser-next-gen goals, plan, and requirements Arnaud Le Hors (Wed Jul 12 2000 - 02:49:04 MEST)
|
15. hard approved
|
The parser shall support namespaces.
Re: parser-next-gen goals, plan, and requirements Arnaud Le Hors (Wed Jul 12 2000 - 02:49:04 MEST)
|
18. hard approved
|
The parser shall support XML Schema.
Re: parser-next-gen goals, plan, and requirements Eric Ye (Wed Jul 12 2000 - 02:48:42 MEST)
Re: parser-next-gen goals, plan, and requirements Arnaud Le Hors (Wed Jul 12 2000 - 02:49:04 MEST)
|
19. hard approved
|
The parser shall support XPath.
Re: parser-next-gen goals, plan, and requirements Donald Ball (Wed Jul 12 2000 - 02:57:59 MEST)
Re: parser-next-gen goals, plan, and requirements Brett McLaughlin (Wed Jul 12 2000 - 16:07:32 MEST)
Re: parser-next-gen goals, plan, and requirements Eduardo Pelegri--Llopart (Wed Jul 12 2000 - 19:31:22 MEST)
Re: parser-next-gen goals, plan, and requirements Jeffrey Rodriguez (Wed Jul 12 2000 - 19:38:42 MEST)
Re: parser-next-gen goals, plan, and requirements Stefano Mazzocchi (Thu Jul 13 2000 - 01:11:58 MEST)
Re: XRI requirements Jeffrey Rodriguez (Wed Jul 12 2000 - 09:59:50 MEST)
|
20. soft unevaluated
|
The parser should support XInclude.
"[+1]"
Re: parser-next-gen goals, plan, and requirements Donald Ball (Wed Jul 12 2000 - 02:57:59 MEST)
"[+1]"
Re: parser-next-gen goals, plan, and requirements Stefano Mazzocchi (Wed Jul 12 2000 - 15:02:47 MEST)
"[+1]"
Re: parser-next-gen goals, plan, and requirements Jeffrey Rodriguez (Wed Jul 12 2000 - 19:38:42 MEST)
|
22. hard unevaluated
|
The parser shall support grammar access for both DTD and Schema.
See also:
13
Re: parser-next-gen goals, plan, and requirements Eric Ye (Wed Jul 12 2000 - 02:48:42 MEST)
|
30. hard rejected
|
The parse shall support SAX 1
"[-1]"
Re: parser-next-gen goals, plan, and requirements Brett McLaughlin (Wed Jul 12 2000 - 03:07:59 MEST)
"[-1]"
Re: parser-next-gen goals, plan, and requirements N. Sean Timm (Wed Jul 12 2000 - 05:59:47 MEST)
"[-1]"
Re: parser-next-gen goals, plan, and requirements Stefano Mazzocchi (Wed Jul 12 2000 - 15:02:47 MEST)
|
32. hard rejected
|
The parser shall support Java 1.1
"[-1]"
Re: parser-next-gen goals, plan, and requirements Brett McLaughlin (Wed Jul 12 2000 - 03:07:59 MEST)
"[-1]"
Re: parser-next-gen goals, plan, and requirements N. Sean Timm (Wed Jul 12 2000 - 05:59:47 MEST)
"[-1]"
Re: parser-next-gen goals, plan, and requirements Stefano Mazzocchi (Wed Jul 12 2000 - 15:02:47 MEST)
"[+1]"
Re: REDOM Design discussion. Jeffrey Rodriguez (Fri Jul 14 2000 - 18:47:28 MEST)
"[+-0]"
Re: REDOM Design discussion. James Duncan Davidson (Fri Jul 14 2000 - 19:22:19 MEST)
|
34. hard unevaluated
|
The parser shall support the XML Information Set.
"[+1]"
Re: [Xerces2] Requirements list; 'Xerces2'?; cross-posting Arnaud Le Hors (Wed Jul 12 2000 - 20:46:38 MEST)
"[+1]"
Re: [Xerces2] Requirements list; 'Xerces2'?; cross-posting Stefano Mazzocchi (Thu Jul 13 2000 - 01:13:00 MEST)
|
13a. soft unevaluated
|
Read-only, memory conservative, high performance DOM subset. In some ways, this is optional, since the alternative is that the XSLT processor implement it's own DOM, as it does today. But it would be neat and simpler if only one DOM implementation needed to exist. a) Document-order indexes or API as a DOM extension. I know of few or no conformant XSLT processors that can do without this. b) [optional] isWhite() method as a DOM extensions (pure telling of whether or not the text contains non-whitespace), for performance reasons. c) Some sort of weak reference, where nodes could be released if not referenced, and then rebuilt if requested. For performance and memory footprint.
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Tue Jul 11 2000 - 23:42:10 MEST)
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Wed Jul 12 2000 - 19:59:46 MEST)
|
13b. soft unevaluated
|
parse-next function, with added control over buffer size.
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Tue Jul 11 2000 - 23:42:10 MEST)
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Wed Jul 12 2000 - 19:59:46 MEST)
|
13c. soft unevaluated
|
Some sort of way to tell if a SAX char buffer is going to be overwritten, so data doesn't have to be copied until this occurs.
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Tue Jul 11 2000 - 23:42:10 MEST)
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Wed Jul 12 2000 - 19:59:46 MEST)
|
13d. soft unevaluated
|
Serialization support, as is currently in Assaf's classes.
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Tue Jul 11 2000 - 23:42:10 MEST)
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Wed Jul 12 2000 - 19:59:46 MEST)
|
13e. soft unevaluated
|
Schema data-type support, which will be needed for XSLT2, and Xalan 2.0 extensions.
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Tue Jul 11 2000 - 23:42:10 MEST)
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Wed Jul 12 2000 - 19:59:46 MEST)
|
13f. soft unevaluated
|
Small core footprint for standalone, compiled stylesheet capability, for use on small devices. This would need to include the Serializer. I'm not sure if this should really be a separate micro-parser?
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Tue Jul 11 2000 - 23:42:10 MEST)
Re: parser-next-gen goals, plan, and requirements Scott Boag/CAM/Lotus (Wed Jul 12 2000 - 19:59:46 MEST)
|
16. hard approved
|
The parser shall support DOM Level 2.
Re: parser-next-gen goals, plan, and requirements Arnaud Le Hors (Wed Jul 12 2000 - 02:49:04 MEST)
|
21. soft unevaluated
|
The parser should support write validation of a DOM tree or revalidation.
Re: parser-next-gen goals, plan, and requirements Eric Ye (Wed Jul 12 2000 - 02:48:42 MEST)
|
28. soft unevaluated
|
Xerces Native API. The parser should provide a reasonable core API (fast!) upon which to layer other API's. Examples of such API's include SAX2, DOM, and JDOM.
See also:
10
Re: parser-next-gen goals, plan, and requirements Brett McLaughlin (Wed Jul 12 2000 - 00:28:32 MEST)
"[JDOM is an important up and coming API that already has established a large and rapidly growing groundswell of support and in the developer community.]"
Re: parser-next-gen goals, plan, and requirements James Duncan Davidson (Wed Jul 12 2000 - 01:15:59 MEST)
|
31. soft unevaluated
|
The core parser should not directly support any tree model.
See also:
10
"[My understanding of the design, which I think is good, is that the "core" actually doesn't directly support any tree model. ] API Layer JDOM DOM SAX2 Core Layer Java parser code "
Re: [spinnaker] Announce Arnaud Le Hors (Tue Jul 11 2000 - 03:41:05 MEST)
Re: parser-next-gen goals, plan, and requirements Jason Hunter (Wed Jul 12 2000 - 07:51:22 MEST)
Re: parser-next-gen goals, plan, and requirements Tim Bray (Thu Jul 13 2000 - 02:33:14 MEST)
[spinnaker] Design discussion James Duncan Davidson (Mon Jul 10 2000 - 08:04:29 MEST)
Re: [spinnaker] Design discussion costin@eng.sun.com (Mon Jul 10 2000 - 20:40:06 MEST)
Re: [spinnaker] Design discussion Edwin Goei (Tue Jul 11 2000 - 00:48:20 MEST)
Re: ?? Design discussion - xerces-design-dev new list Arnaud Le Hors (Tue Jul 11 2000 - 06:51:24 MEST)
[Xerces2] What is CORE? Ed Staub (Fri Jul 14 2000 - 23:34:45 MEST)
Re: [Xerces2] What is CORE? Brett McLaughlin (Fri Jul 14 2000 - 23:52:26 MEST)
Re: [Xerces2] What is CORE? Arved Sandstrom (Sat Jul 15 2000 - 01:08:07 MEST)
|
33. soft unevaluated
|
The parser should support loading and validating only certainrequested portions of a document -- a useful feature when dealing with large xml databases, for example. See the W3C XML Fragement Interchange Working Draft.
RE: XRI requirements James Snell (Wed Jul 12 2000 - 07:25:50 MEST)
|
35. soft unevaluated
|
The parser should support pull model parsing.
Microsoft XML stuff Scott Boag/CAM/Lotus (Wed Jul 12 2000 - 21:46:16 MEST)
Re: Microsoft XML stuff Ted Leung (Thu Jul 13 2000 - 02:08:55 MEST)
Re: Microsoft XML stuff Ted Leung (Thu Jul 13 2000 - 06:46:09 MEST)
Re: Microsoft XML stuff Eric Hodges (Thu Jul 13 2000 - 09:15:49 MEST)
RE: Microsoft XML stuff Scott Boag/CAM/Lotus (Thu Jul 13 2000 - 06:29:25 MEST)
|
37. soft unevaluated
|
The DOM should emit events to interested listeners when changes are made to the DOM
Re: ?? Design discussion - xerces-design-dev new list Kelly Campbell (Tue Jul 11 2000 - 03:08:57 MEST)
|
38. soft unevaluated
|
The parser should support RELAX .
|
39. soft unevaluated
|
The parser should allow for automatic detection of compressed/encrypted documents.
|