Problem Statement : with the xml-dom-rss repositories being vogue on the web viz. 3-tier architecture,

                    while there are many a parsers to handle xml-dom-data

                    ...ability to handle ( or treat) xml-dom-[rss] data repositories (feeds or streams)
                    through a database interface  ...either as synchronous or asychronous data steams.

                    while there are many a programatic interfaces to handle the equivalent of sax(in java)
                    in many a 3rd generation languages or at a bit higher level those that support OOP.



Opportunity a):     Perl/java/c++/python/vb... support properitary to many 3rd party XML-DOM parsers 

                  Ability to handle XML-DOM-(RSS) repositories/feeds ...through a DBH(database handler ...
                  MS context ado/rdo/dao ...) interface ...presuming or assuming a standardized parser as a
                  DBD(database driver).

Opportunity b):   A XML-DTD-DOM complaint document's in conjuction with a handler (xml-parser and query) ...as
                  a RPC (remote procedure call) ...can give and also makes a ideal substitute to LDAP based
                  databases ...can be used on 3-tier or 2-tier architechtures.

                  for backward compatibility with LDAP ...the XML-DOM can be mapped with cannonical or cname,
                  the LDAP query ...could well be the variable transmitted for a query in get or post on a
                  http based service.
                  
                  thus user-authentication databases in OS context ...can substitute all use-case scenarios
                  where LDAP can be envisaged.

                  LDAP/XML-DOM compliant document can be used to enumerate or simulate the ASN MIB databases
                  used in conjuction with SNMP.

                  In this it may be presumed the DTD is either flexible or loose ...while adhering to the specifications
                  of XML, nomenclature of a valid DTD and can modified or defined or extended anytime much like the
                  ability to define or extend the schema of a LDAP repository or when multiple schema's are definable
                  then multpile DTD's i.e. a new DTD for each schema is created.

 
                  ability or flexibility of multiple user's modifying the repository...at a time need's to be modeled 
                   eg: user-data or end-user-personal-profile  when stored in such a repository


Opportunity c):  Ability to encode a XML-DOM ...object model into a perl Hash based 'sequence or series of anonymous-hash-refs',
                 ...thus ability to export or dump between XML-DOM compliant object model and vice versa i.e. import.

                 ideally packagable as perl module and package manager.


Opportunity d): deriving from c) ...ability to process or parse ...streaming content in perl over tcp/ip,
                expect, lwp ...etc.

                explore the potential addressability of the streaming context using in compliance with the AJAX.   


Opportunity e:) deriving from above use-case's product architecture's of most software's usually server centric,
                can be re-architected or redesigned and put through another cycle of development viz. RAD
                
                specificially ERP's ....CRM's ...most [en]visible or product's that can be envisaged can eXploit 
                database and AJax model  ...except that ability include a server-side downloadable script in case
                of java-script be included in the XML-DOM- ...optionally DTD complaint stream.

                Given that DHTML-or-ajax on the client-side is lite weight ...for usually server centric product
                architectures!! ....accommodating logic.
r
Opportunity f:) ability to innovatively evolve a client side java/java-script engine executable xml-dom-dtd-[rss]
                stream a evolvement of AJax .               



Note: The above problem statement having been encountered in various scenarios
      and detailed in various 'Proof of concepts' as mentioned in 
      
       http://uk.geocities.com/ravivenkatus/projects.pdf
       http://ravishankarkv.tripod.com/projects.pdf
        ....apply appropriate
      'use-case' modeling and arrive at a workable and feasible solution both
       commercially and techinically viable.

----------------------------------------------------------------------------------------------
