Problem Statement :  Data-formats ...client-side validation , server-side validation

                     client-side validation of data-format's is potentially prone for compromise and reliability,

                     server-side validation is reliable ...but can make the server-slow if sufficient processing
                     power is not provisioned.

                  eg scenario: online sales-tax filing for maharastra state government,

                               a client-side data format of  MS-excel was choosen ...and validation performed on client
                               as reliable.

                     also read through "opportunity_XML_RSS_exploitation.txt",
                                       "Opportunity_ticketing_reservation_systems.txt",
                                       "opportunity_crm_othersoftwaresystems[erp]_xmlRSS_http_channel_Push_notification_mechanism.txt",
                                       "opportunity_datastorage_mediums_data_access_views.txt",
                                       "opportunity_dynamic_virtualization_storage_blueprint.txt",
                                       "opportunity_email_embedded_forms_communication_data_transport_layer.txt'


                    user-input,presentation framework, data-validation-layer ...both expressed in XML.... Client-side and server-side
                    programs/frame-works that work or take these XML as input.


Opportunity : A document with embedded script that is executable or validated on client-side ...for convinence of the end-users.

              ...ideally ...validating such data ...on the server-side for doubly assuring there is no compromise on the data
              or validation-code in critical environments.

              for instance by opening a process thread or shell on the server-side which re-validates or re-executes the document in a
              embedded environment as in the client by populating the data-recieved from the client into a template on the 
              server with-out relying on the client-side-validation of the data,  XML ideally offer's most viable data-format for
              this kind of scenario viz. marshall or ship the data in concise or most portable format between client to server.

              Eg: windows offer's or let's running a client-side program in a ...server-side shell , leverage processing or infrastructure
                  architechture's that can leverage server-side-processing powers.

              ...ability to apply a template on the data on the client-side ...and revalidate the data on the server-side by
                 applying a server-side validatable template ...that can be executed in threaded version on server-side validation
                 program....given the context ...data needs to adhere to a XML-DTD-DOM...data marshalling needs to be in set's of
                 XML documents....given or applying OOP ...classes/interfaces are re-usable ...those that can be used or instantiated
                 for use on client-side and server-side.

                 here-in it is presumed that just the data is marshalled  from the client to the server ...not the formatting and 
                 validation ...when data gather from a end-user is trasmitted back to the server, keeping it lite-weight,by seperating
                 the presentation layer ....with the validation-layer ...ability to apply the validation frame-work(ideally much like
                 the presentation-layer the validation part expressed in XML ...the same XML input document when used on the client-side ,
                 the client-side validation program takes into account the user-interface and input from end-user, while the server-side
                 validation program taking or picking from the XML-input for data validation just re-validates the data)  on the data 
                 on the server-side when revalidation of data on server-side is required.

              presuming data-format used for marshalling is XML ...leveraging Ajax or client-side validation tools XSLT or CSS 
              or for that matter MS-Exel(ability to import into a template with embedded validations ...of excel 2003 version) on 
              the client-side

              and many a server-side XML compatible architechtures (perl/php/java/.net...etc) can be applied on such data on the server-side.

       
              The advantage of such a data format being that apart from http-protocol ...data-marshaling ...transactions over other protocols
              including passive such as email can be leveraged.
             

                               
 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, rationalize and arrive at a workable and feasible 
       solution both commercially and techinically viable.