Ethan Quach wrote: > > > Jack Schwartz wrote: >> Hi Ethan. >> >> >>>> >>>> >>>> General: >>>> >>>> In general, the parser places the requirement on the derived >>>> profiles project that the format of the tags be in an easily >>>> searchable format, for example that they contain a common prefix >>>> which can be searched for. >>> >>> Its not clear to me that we're going to be using the >>> parser to do syntactical validation of the base manifest >>> on the server. I will note this possibility though. >> OK, but there are other reasons too. In addition to use for >> validation, this will allow you to easily search for the items you >> want to process. Since they can be anywhere in the tree, the ability >> to use some kind of wildcard to find all items will be useful. > > That's a good point; tough, doesn't the document need > to qualify to meet the given schema before the parser > can even read and serve the document to searches for > a consumer? > My understanding is that with the new parser, when it finished "initializing", it just loads your XML file into memory. No validation what-so-ever is done at that point. The syntactic validation with the schema doesn't happen until the client program calls a parser's function to do that.
--Karen
