Problem Statement: Directory servers are used for varying purposes traditionally

                   exploit their usage for news-groups(NNTp)...email ...blogging ...chronological-tracking-logging 
                   used in customer-care (CRM),ITIL-kind frame work complaint ...

                                  ...using simple plain old file-system ...directory...mime viz. text-files...attachments 

                      coupled with a user-accounting mechanism [ldap]

 Opportunity a:     while ability to integrate news-groups and blogging would be a great idea....

                   they share a lot in between them ....blogs could potentially be implemented using
                   database in the back-end 
'
                   ....a solution centered around the the 'problem statement' offers a viable , feasible and
                   a scalable solution ...by using a structure nomenclature.

                   In the context may refer to the document projects.pdf ...regard some contract work performed
                   for fapco for its client Alghanim ...the outline of the concept and schema can be made
                   analogical or applied to be implemented in a filesystem instead or inlieu of a database
                   driven application.


                   also read through "opportunity_datastorage_mediums_data_access_views.txt"


                  eg: market propositions as a software product that can do all or part of the following jobs based
                      based as configurable options ...as email ...nntp ...blog ...etc ...with interfaces to handle
                      or interact over web, email and with properitary clients to such servers.


Opportunity b: deriving from the current implementation's of blogging ....implemented using either of directory/fileserver/database driven systems

              a innovative online discussion ....forum ....a modified version of blogging ??

              in a blog ...some-user post's a comment or reply ...ability to send a notification or reply to a user responding in the discussin-form,

              as also ability to moderate these replies by the host ...as either public or private , ability to synchronize multiple views to a 
              discussion ...chronological as in a blog ...ability for each participant to view or see the feedback on a 'topic or discussion'
              he/she participated ...i.e. a personalized view to the participant users.


              with the ideal combination being that of ability to club the directory or NNTP with blog-discussion based views,,

              ability to subscribe and post using a choice of means email/xml-rss-im-or-other-clients/web-interfaced-cleint
              and ability to see the complete picture or whole view on a web-interface i.e. synchronized view.


             eg usages: all industries or domains ...where regular updates are available


Opportunity c: specifications for a lite-weight CRM product orchestrization or product architecture.
               -------------------------------------------------------------------------------------

               Implement a lite-weight CRM ...over or atop a file-system (say NAS) and mailer-daemon(send-mail or qmail) 

               Innovative data-hashing [optionally refer to perl data::dumper , perl anonymous-hash'es ... a product that can be wrapped over by
               embedding perl or embedded-perl]
               

               also read through the document "opportunity_datastorage_mediums_data_access_views.txt"

               
               chronological retrival or tracking the history or case-sheet of or documents of a specific entity ....a lite-weight CRM/e-CRM/ 

               essentially create a directory for every incident or trackable event-id.

                     mail daemon deliver's all relevant information -exchangable for the incident or trackable-event-id into the folder or directory.

                     a simple SQL-engine atop a file-system ...enable what is termed as 'Free text search'

                     (mySql/postGRESQL) kind of a daemon ...that is container based or directory based organization of
                     information for quicker-query or easier interface for retrival of information.

                     [  user's of the product thus qmail and a database-engine both residing on a LDAP  ]

                     a file is essentially inter-linked (linked-list in pure programming sense) or connected blocks of information in a file-system,
                     thus ...any information saved or retrieved using a GUI based front-end ...can be easily ...sequentially or synchronized information
                     that can be stored on to a file-system.

                  'dirty-logging' used in combination with,  a flag or attribute on the directory or folder or file(priority of mail) in a file-system 
                  in a operating system context can be used to track the status of a incident or trackable event (say open,close,pending with customer)


           {   A email-client [optionally-customized-view] with IMAP(potentially extending the protocol or building upon the protocol) offering 
               the data transport layers interacting with the Server

               or

               A web-based-interface as-usual...thus http layer being the data-transfer-layer offering the essential front-end with which the user
               interacts with the CRM and CRM-repository.
           }
               deriving from how a directory, file-system in the context of OS work, how Qmail and most container or directory based information
               organized databases work (eg mysql or many a DBMS) ....a superior lite-weight ...CRM solution can be built.       


           read through the document 'opportunity_email_embedded_forms_communication_data_transport_layer.txt' , Ajax

                   using XML-namespace-schema, XSLT or CSS for html based input forms ... based customized template,
                   downloadable from server .
   

                      


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.
