a description will be given of embodiments of the present invention , by referring to fig3 and the subsequent drawings . fig3 is a system block diagram showing a functional structure of a composite apparatus according to an embodiment of the present invention . a composite apparatus 1200 shown in fig3 includes a plotter 1201 , a scanner 1202 , other hardware resources 1203 such as a facsimile apparatus , applications 1240 ( 1211 , 1212 , 1213 , 1214 , 100 ), control services 1250 ( 1222 , 1224 , 1225 , 1226 , 1227 , 1228 , 1229 , 1230 , 1231 ( 200 )), a system resource manager ( srm ) 1223 and an operating system ( os ) 1221 . the control services 1250 analyzes the process requests from the applications 1240 , and generate acquisition requests for the hardware resources . the system resource manager 1223 manages one or a plurality of hardware resources , and carries out an arbitration with respect to the acquisition requests from the control services 1250 . the control services 1250 are formed by a plurality of service modules , namely , a system control service ( scs ) 1222 , an engine control service ( ecs ) 1224 , a facsimile control service ( fcs ) 1225 , a memory control service ( mcs ) 1226 , a delivery control service ( dcs ) 1227 , a user control service ( ucs ) 1228 , a certification control service ( ccs ) 1229 , a log control service ( lcs ) 1230 , and a network control service ( ncs ) 1231 . the operating system 1221 is formed by a unix ( registered trademark ) operating system ( os ), for example . the system resource manager 1223 carries out the system control and the resource management together with the system control service 1222 . the system control service 1222 carries out a plurality of functions including application management , operation part control , system screen display , led display , resource management , and interrupt application control . the engine control service 1224 controls an engine part of the plotter 1201 or the like . the facsimile control service 1225 provides an application program interface ( api ) for carrying out facsimile transmission and reception using pstn / isdn networks from each application layer of a system controller , registration / reference of various facsimile data managed by a backup memory ( backup sram ), facsimile reading , facsimile reception printing , and multi - function ( composite ) transmission and reception . the memory control service 1226 carries out a memory control . the delivery control service 1227 carries out processes such as transferring stored documents ton an external server , a user &# 39 ; s personal computer ( pc ) or the like . the user control service 1228 carries out management and the like of user information and / or group information of a group to which the user belongs . the certification control service 1229 carries out user authentication or the like . the log control service 1230 carries out management and the like of logs . the network control service 1231 carries out an intervening process when distributing data received from the network by each protocol to each application , and transmitting data from the application to the network , for example . the applications 1240 include a copy application 1211 , a facsimile application 1212 , a scanner application 1213 , a printer application 1214 , and a server platform 100 . compared to the functional structure of the composite apparatus 1200 shown in fig2 , the functional structure of the composite apparatus 1200 shown in fig3 differs in that the functions related to processes via the network and implemented within the plurality of applications 1240 in fig2 are integrated and implemented within the server platform 100 in fig3 . a print shared function ( sf ) 41 , a scan shared function ( sf ) 43 and a storage shared function ( sf ) 44 shown in fig3 are not only used from each application within the composite apparatus 100 , but also used from the server platform 100 . the print sf 41 , the scan sf 43 and the storage sf 44 are not dependent upon the devices , the model , the operating system and the like that are provided in the composite apparatus 1200 , and form components that can provide an interface for macro processes in units of functions . the programs of the composite apparatus 1200 may be preinstalled in the composite apparatus 1200 or , may be provided to the composite apparatus 1200 by way of a recording medium 1 or downloaded to the composite apparatus 1200 via the network . a cpu of the composite apparatus 1200 executes processes according to the programs . fig4 is a diagram showing a functional structure of an entire framework . as shown in fig4 , the framework includes , as network services ( first functions ), an httpd 200 , an ftpd ( file transfer protocol daemon ) 210 and an smtpd ( simple mail transfer protocol daemon ) 220 . the httpd 200 , the ftpd 210 and the smtpd 220 are included within the network control service 1231 . in addition , the framework includes , as shared function ( sf ) layers or service layers ( second functions ), the print sf 41 that provides the print function , the facsimile sf 42 that provides the facsimile function , the scan sf 43 that provides the scan function , the storage sf 44 that provides the storage function , the log control service 1230 that carries out the management of the log and the like , and the system control service 1222 . the server platform 100 includes a middlewear interface part ( second interface part or means ) 30 for utilizing middlewear groups that provide various kinds of functions , a protocol interface part ( first interface part or means ) 10 for analyzing various kinds of protocols and operation sequences , and a shared function providing part ( or means ) 20 for defining the functions that are shared ( that is , used in common ) when carrying out the various kinds of functions according to the various kinds of protocols . the protocol interface part 10 provides an interface that is shared ( that is , used in common ) from the networks . for example , the protocol interface part 10 includes an html analyzing part 11 for analyzing the html ( hypertext markup language ), an upnp analyzing part 12 for analyzing the upnp ( universal plug and play ), a ws analyzing part 13 for analyzing the ws ( web service ), and a custom interface ( i / f ) analyzing part 14 for analyzing a custom i / f . the middlewear interface part 30 provides an interface that is not only shared from the networks , but also shared from the applications 1240 and the shared functions ( sfs ) within the composite apparatus 1200 . the middlewear interface part 30 provides the interface within the equipment , such as the shared function ( sf ) layer and the service layer . for example , the middlewear interface part 30 includes a print sf i / f 31 that provides an interface between the shared function providing part 20 and the print sf 41 , a facsimile sf i / f 32 that provides an interface between the shared function providing part 20 and the facsimile sf 42 , a scan sf i / f 33 that provides an interface between the shared function providing part 20 and the scan sf 43 , a storage sf i / f 34 that provides an interface between the shared function providing part 20 and the storage sf 44 , a job i / f 35 that provides an interface between the shared function providing part 20 and the log control service 1230 , and a system i / f 36 that provides an interface between the shared function providing part 20 and the system control service 1222 . by employing the functional structure of the framework shown in fig4 , the designer of the protocol interface part 10 only needs to know the interface between the protocol interface part 10 and the shared function providing part 20 in order to design the protocol interface part 10 . further , the designer of the middlewear interface part 30 only needs to know the interface between the middlewear interface part 30 and the shared function providing part 20 in order to design the middlewear interface part 30 . accordingly , in the case of the framework having the functional structure shown in fig4 , the protocol interface part 10 and the middlewear interface part 30 can be designed independently , and a design modification or the like does not affect each other . for this reason , it is possible to easily cope with situations such as the addition of a new function the use of a new protocol . next , a description will be given of a functional structure of a upnp compatible printer for a case where the framework shown in fig4 is applied to this compatible upnp printer , by referring to fig5 . fig5 is a diagram showing the functional structure of the upnp compatible printer for the case where the framework is applied to the compatible upnp printer . as shown in fig5 , the upnp compatible printer includes , as network services , an httpd 200 , an ftpd 210 and an smtpd 220 . in addition , the server platform 100 includes a protocol interface part 10 , a shared function providing part 20 and a middlewear interface part 30 . as shown in fig5 , the protocol interface part 10 includes an upnp analyzing part 12 . moreover , the middlewear interface part 30 includes a print sf i / d 31 , a job i / f 35 and a system i / f 36 , as shown in fig5 . the upnp compatible printer includes , as the sf layers or the service layers , a print sf 41 , a log control service 1230 and a system control service 1222 . as shown in fig5 , the framework shown in fig4 can also be applied to the upnp compatible printer . the programs of the upnp compatible printer may be preinstalled in the upnp compatible printer or , may be provided to the upnp compatible printer by way of a recording medium 1 or downloaded to the upnp compatible printer via the network . a cpu of the upnp compatible printer executes processes according to the programs . next , a description will be given of a functional structure of a printer capable of equipment management by a browser for a case where the framework shown in fig4 is applied to this printer capable of equipment management by the browser , by referring to fig6 . fig6 is a diagram showing the functional structure of the printer capable of equipment management by the browser for the case where the framework is applied to this printer capable of equipment management by the browser . as shown in fig6 , the printer capable of equipment management by the browser includes , as network services , an httpd 200 , an ftpd 210 and an smtpd 220 . in addition , the server platform 100 includes a protocol interface part 10 , a shared function providing part 20 and a middlewear interface part 30 . as shown in fig6 , the protocol interface part 10 includes an html analyzing part 11 and an upnp analyzing part 12 . moreover , the middlewear interface part 30 includes a print sf i / d 31 , a job i / f 35 and a system i / f 36 , as shown in fig5 . the printer capable of equipment management by the browser includes , as the sf layers or the service layers , a print sf 41 , a log control service 1230 and a system control service 1222 . as shown in fig6 , the framework shown in fig4 can also be applied to the printer capable of equipment management by the browser . the programs of the printer capable of equipment management by the browser may be preinstalled in the printer capable of equipment management by the browser or , may be provided to the printer capable of equipment management by the browser by way of a recording medium 1 or downloaded to the printer capable of equipment management by the browser via the network . a cpu of the printer capable of equipment management by the browser executes processes according to the programs . next , a description will be given of a functional structure of a web service and web browser compatible composite apparatus 1200 for a case where the framework shown in fig4 is applied to this web service and web browser compatible composite apparatus 1200 , by referring to fig7 . fig7 is a diagram showing the functional structure of the web service and web browser compatible composite apparatus 1200 for the case where the framework is applied to the web service and web browser compatible composite apparatus 1200 . as shown in fig7 , the web service and web browser compatible composite apparatus 1200 includes , as network services , an httpd 200 , an ftpd 210 and an smtpd 220 . in addition , the server platform 100 includes a protocol interface part 10 , a shared function providing part 20 and a middlewear interface part 30 . as shown in fig7 , the protocol interface part 10 includes an html analyzing part 11 , and a we analyzing part 13 . moreover , the middlewear interface part 30 includes a print sf i / d 31 , a facsimile sf i / f 32 , a scan sf i / f 33 , a storage sf i / f 34 , a job i / f 35 and a system i / f 36 , as shown in fig7 . the web service and web browser compatible composite apparatus 1200 includes , as the sf layers or the service layers , a print sf 41 , a facsimile sf 42 , a scan sf 43 , a storage sf 44 , a log control service 1230 and a system control service 1222 . as shown in fig7 , the framework shown in fig4 can also be applied to the web service and web browser compatible composite apparatus 1200 . the programs of the web service and web browser compatible composite apparatus 1200 may be preinstalled in the web service and web browser compatible composite apparatus 1200 or , may be provided to the web service and web browser compatible composite apparatus 1200 by way of a recording medium 1 or downloaded to the web service and web browser compatible composite apparatus 1200 via the network . a cpu of the web service and web browser compatible composite apparatus 1200 executes processes according to the programs . next , a description will be given of a functional structure of an exclusive client interface compatible composite apparatus 1200 for a case where the framework shown in fig4 is applied to this exclusive client interface compatible composite apparatus 1200 , by referring to fig8 . fig8 is a diagram showing the functional structure of the exclusive client interface compatible composite apparatus 1200 for the case where the framework is applied to the exclusive client interface compatible composite apparatus 1200 . as shown in fig8 , the exclusive client interface compatible composite apparatus 1200 includes , as network services , an httpd 200 , an ftpd 210 and an smtpd 220 . in addition , the server platform 100 includes a protocol interface part 10 , a shared function providing part 20 and a middlewear interface part 30 . as shown in fig8 , the protocol interface part 10 includes a custom i / f analyzing part 14 . moreover , the middlewear interface part 30 includes a print sf i / d 31 , a facsimile sf i / f 32 , a scan sf i / f 33 , a storage sf i / f 34 , a job i / f 35 and a system i / f 36 , as shown in fig8 . the exclusive client interface compatible composite apparatus 1200 includes , as the sf layers or the service layers , a print sf 41 , a facsimile sf 42 , a scan sf 43 , a storage sf 44 , a log control service 1230 and a system control service 1222 . as shown in fig8 , the framework shown in fig4 can also be applied to the exclusive client interface compatible composite apparatus 1200 . the programs of the exclusive client interface compatible composite apparatus 1200 may be preinstalled in the exclusive client interface compatible composite apparatus 1200 or , may be provided to the exclusive client interface compatible composite apparatus 1200 by way of a recording medium 1 or downloaded to the exclusive client interface compatible composite apparatus 1200 via the network . a cpu of the exclusive client interface compatible composite apparatus 1200 executes processes according to the programs . next , a description will be given of the concept of the functions related to the shared processes via the network , by referring to fig9 through 11 . fig9 is a sequence diagram for explaining a print operation . generally , the client who requests the printing sends a client authentication request to a server that is connected to the client via the network ( sequence sq 1 ). the server that receives the client authentication request from the client carries out an authentication based on data related to the authentication and included in the client authentication request , such as a user name and a password . the authenticated client ( that is , a valid client for which the authentication is successful ) sends a session start request to the server ( sequence sq 2 ). the server judges whether or not the received session start request is from the valid client , and starts a session with the client if it is judged that the session start request is received from the valid client . next , the client sends a print start request to the server ( sequence sq 3 ). the server starts printing based on the print start request , and when the printing ends , the server sends a print end notification to the client ( sequence sq 4 ). when the client receives the print end notification , the client sends a session end request to the server ( sequence sq 5 ). fig1 is a sequence diagram for explaining a document referring operation . generally , the client who requests the document referring sends a client authentication request to a server that is connected to the client via the network ( sequence sq 1 o ). the server that receives the client authentication request from the client carries out an authentication based on data related to the authentication and included in the client authentication request , such as a user name and a password . the authenticated client ( that is , a valid client for which the authentication is successful ) sends a session start request to the server ( sequence sq 11 ). the server judges whether or not the received session start request is from the valid client , and starts a session with the client if it is judged that the session start request is received from the valid client . next , the client sends a document search start request to the server ( sequence sq 12 ). the server starts document search based on the document search start request , and when the document search ends , the server sends a document search result notification to the client ( sequence sq 13 ). when the client receives the document search result notification , the client sends a document acquisition request to the server ( sequence sq 14 ). after the client acquires the document , the client sends a session end request to the server ( sequence q 15 ). fig1 is a sequence diagram for explaining a modification of user information . generally , the client who requests the modification of user information sends a client authentication request to a server that is connected to the client via the network ( sequence sq 20 ). the server that receives the client authentication request from the client carries out an authentication based on data related to the authentication and included in the client authentication request , such as a user name and a password . the authenticated client ( that is , a valid client for which the authentication is successful ) sends a session start request to the server ( sequence sq 21 ). the server judges whether or not the received session start request is from the valid client , and starts a session with the client if it is judged that the session start request is received from the valid client . next , the client sends a user information modifying instruction ( or request ) to the server ( sequence sq 22 ). when the modification of the user information ends , the client sends a session end request to the server ( sequence sq 23 ). as shown in fig9 through 11 , the portions surrounded by dotted lines that carry out processes related to the authentication and the session ( right of use ) management can be shared . a relationship of classes related to management of authentication and right of use , that is implemented in the shared function providing part 20 of the server platform 100 , is shown in fig1 . fig1 is a class diagram showing the relationship of the classes related to the management of the authentication and the right of use . as shown in fig1 , the shared function providing part 20 includes a service user class , a personal identification class , an authenticated user list ( or directory ) class , a right of use class , and usable user list ( or directory ) class . the service user class indicates users of the service ( that is , service users ). the personal identification class indicates a personal identification of the service user . the authenticated user list class indicates a list of authenticated service users . the right of use class indicates a right of use ( corresponding to a session ) of a certain service . the usable user list class indicates a list of users capable of using various kinds of services . fig1 is a diagram showing a functional structure of the server platform 100 . as shown in fig1 , the shared function providing part 20 includes an authentication and right of use managing part 111 . the authentication and right of use managing part 111 includes a service user class , a personal identification class , an authenticated user list ( or directory ) class , a right of use class , and usable user list ( or directory ) class . as shown in fig1 , the functions related to the management of the authentication and the right of use ( session ) may be shared and included in the shared function providing part 20 , within the server platform 100 . next , a description will be given of another concept of the functions related to the shared processes via the network , by referring to fig1 and 15 . fig1 is a sequence diagram showing a document referring operation . the client who requests the document referring sends a document search start request to the server ( sequence sq 30 ), similarly to the sequence sq 12 shown in fig1 . when the document search start request is received from the client , the server creates search parameters based on the information included in the document search start request ( sequence sq 31 ). then , the server supplies the created search parameters to the storage sf 44 and makes a request for a search process ( sequence sq 32 ). the storage sf 44 makes a search based on the supplied search parameters , and notifies a search result to the server ( sequence sq 33 ). the server notifies the search result received from the storage sf 44 to the client ( sequence sq 34 ). when the search result is received from the server , the client sends a document acquisition request for a specified document , for example , to the server ( sequence sq 35 ). the sever supplies the document acquisition request for the specified document , for example , to the storage sf 44 ( sequence sq 36 ). fig1 is a sequence diagram showing a user information referring operation . the user who requests the user information referring sends a user information search start request to the server ( sequence sq 40 ). when the user information search start request is received from the client , the server creates search parameters based on the information included in the user information search start request ( sequence sq 41 ). then , the server supplies the created search parameters to the user control service 1228 and makes a request for a user information search process ( sequence sq 42 ). the user control service 1228 makes a search based on the supplied search parameters , and notifies a search result to the server ( sequence sq 43 ). the server notifies the search result received from the user control service 1228 to the client ( sequence sq 44 ). when the search result is received from the server , the client sends an acquisition request for specified user information , for example , to the server ( sequence sq 45 ). the sever supplies the acquisition request for the specified user information , for example , to the user control service 1228 ( sequence sq 46 ). as shown in fig1 and 15 , the portions surrounded by dotted lines that carry out processes related to the referring of information ( or data ) can be shared . a relationship of classes related to the referring of information , that is implemented in the shared function providing part 20 of the server platform 100 , is shown in fig1 . fig1 is a class diagram showing the relationship of the classes related to the referring of information . fig1 shows a model that refers to the search result as it is . as shown in fig1 , the shared function providing part 20 includes a catalog class , a referring data class , a data storage class , and a right of use class . the catalog class indicates a sheet or paper on which the search result of the information within the equipment is to be written . the referring data class indicates the target data that are to be referred to and are written in the catalog . the data storage class indicates a location where the data are stored within the equipment . the right of use class indicates the right of use ( corresponding to the session ) of a certain service , as described above . fig1 is a class diagram showing a relationship of the classes related to the referring of information . fig1 shows a model that selects the data to be referred to from the search result . as shown in fig1 , the shared function providing part 20 includes an information referring request class , a referring data class , a data storage class , and a right of use class . the information referring request class indicates a request ( or request form ) for the information referring within the equipment . the referring data class indicates the target data that are to be referred to and are written in the catalog , as described above . the data storage class indicates a location where the data are stored within the equipment , as described above . the right of use class indicates the right of use ( corresponding to the session ) of a certain service , as described above . in the following description , it is assumed for the sake of convenience that the classes shown in fig1 are implemented in the shared function providing part 20 . fig1 is a diagram showing a functional structure of the server platform 100 . as shown in fig1 , the shared function providing part 20 includes an authentication and right of use managing part 111 and a referring part 112 . the authentication and right of use managing part 111 includes a right of use class . the referring part 112 includes a catalog class , a referring data class and a data storage class . as shown in fig1 , the functions related to the referring of the data ( or information ) within the equipment may be shared and included in the shared function providing part 20 , within the server platform 100 . next , a description will be given of another concept of the functions related to the shared processes via the network , by referring to fig1 and 20 . fig1 is a sequence diagram showing a setting of document information . the client who requests modifying of the document information sends a document information modifying request to the server ( sequence sq 50 ). when the document information modifying request is received from the client , the server creates modifying parameters based on information included in the document information modifying request ( sequence sq 51 ). then , the server supplies the created modifying parameters to the storage sf 44 and requests a modifying process ( sequence sq 52 ). fig2 is a sequence diagram showing a setting of user information . the client who requests modifying of the - user information sends a user information modifying request to the server ( sequence sq 60 ). when the user information modifying request is received from the client , the server creates modifying parameters based on information included in the user information modifying request ( sequence sq 61 ). then , the server supplies the created modifying parameters to the user control service 1228 and requests a modifying process ( sequence sq 62 ). as shown in fig1 and 20 , the portions surrounded by dotted lines that carry out processes related to the setting of information ( or data ) can be shared . a relationship of classes related to the setting of information , that is implemented in the shared function providing part 20 of the server platform 100 , is shown in fig2 . fig2 is a class diagram showing the relationship of the classes related to the setting of information . as shown in fig2 , the shared function providing part 20 includes an information setting request class , a registering data class , an information setting service class , and a right of use class . the information setting request class indicates a request ( or request form ) for setting the information within the equipment . the registering data class indicates the data to be registered within the equipment when setting the information . the information setting service class indicates a service that sets the information within the equipment . the right of use class indicates the right of use ( corresponding to the session ) of a certain service , as described above . next , a description will be given of state transitions of an information setting request object of the information setting request class , by referring to fig2 . fig2 is a state transition diagram of the information setting request . as shown in fig2 , the information setting request object assumes a requesting state when an information setting request event is generated from the client . the information setting request object makes a transition from the requesting state to a request failed state and assumes an end state , if an non - acceptable notification is received from the sf . in addition , the information setting request object makes a transition from the requesting state to a requested state and assumes the end state , if an accept complete notification is received from the sf . fig2 is a diagram showing a functional structure of the server platform 100 . as shown in fig2 , the shared function providing part 20 includes an authentication and right of use managing part 111 and a setting part 113 . the authentication and right of use managing part 111 includes a right of use class . the setting part 113 includes an information setting request class , a registering data class , and an information setting service class . as shown in fig2 , the functions related to the setting of the data ( or information ) within the equipment may be shared and included in the shared function providing part 20 , within the server platform 100 . next , a description will be given of another concept of the functions related to the shared processes via the network , by referring to fig2 and 25 . fig2 is a sequence diagram showing a print operation . similarly to the sequence sq 3 shown in fig9 , the client who requests the start of the printing sends a print start request to the server ( sequence sq 70 ). when the print start request is received from the client , the server creates print parameters based on information included in the print start request ( sequence sq 71 ). then , the server supplies the created parameters to the print sf 41 and requests a print process ( sequence sq 72 ). the print sf 41 carries out the print process based on the supplied print parameters , and notifies a print result to the server ( sequence sq 73 ). fig2 is a sequence diagram showing a scanner operation . the client who requests the start of the scanning sends a scan start request to the server ( sequence sq 80 ). when the scan start request is received from the client , the server creates scan parameters based on information included in the scan start request ( sequence sq 81 ). then , the server supplies the created scan parameters to the scan sf 43 and requests a scan process ( sequence sq 82 ). the scan sf 43 carries out the scan process based on the supplied scan parameters , and notifies a scan result to the server ( sequence sq 83 ). as shown in fig2 and 25 , the portions surrounded by dotted lines that carry out processes related to the print and scanner operations can be shared . a relationship of classes related to the print and scanner operations , that is implemented in the shared function providing part 20 of the server platform 100 , is shown in fig2 . fig2 is a class diagram showing a relationship of classes related to the print and scanner operations . as shown in fig2 , the shared function providing part 20 includes a job operation request class , an operation target class , a job operation executing service class , and a right of use class . the job operation request class indicates a request ( or request form ) for a job operation . it is assumed that a job requires time until it is completed , and that a job complete notification is separately notified from the sf layer . the operation target class indicates a target job operation . the job operation executing service class indicates a service for executing a job operation within the equipment . the right of use class indicates the right of use ( corresponding to the session ) of a certain service , as described above . next , a description will be given of state transitions of a job operation request object of the job operation request class , by referring to fig2 . fig2 is a state transition diagram of the job operation request . as shown in fig2 , the job operation request object assumes a requesting state when a job operation request event is generated from the client . the job operation request object makes a transition from the requesting state to a request failed state and assumes an end state , if an non - acceptable notification is received from the sf . in addition , the job operation request object makes a transition from the requesting state to a request executing state , if an accept complete notification is received from the sf . if an execution failed notification event is generated from the sf , the job operation request object makes a transition from the request executing state to an execution failed state and assumes an end state . further , the job operation request object makes a transition from the request executing state to a request executed state and assumes the end state , if an execution complete notification event is generated from the sf . fig2 is a diagram showing a functional structure of the server platform 100 . as shown in fig2 , the shared function providing part 20 includes an authentication and right of use managing part 111 and a job operation part 114 . the authentication and right of use managing part 111 includes a right of use class . the job operation part 114 includes a job operation request class , an operation target class , and a job operation executing service class . as shown in fig2 , the functions related to the operations with respect to the job may be shared and included in the shared function providing part 20 , within the server platform 100 . fig2 is a diagram showing an entire functional structure of the server platform 100 . as shown in fig2 , the shared function providing part 20 includes an authentication and right of use managing part 111 , a referring part 112 , a setting part 113 and a job operation part 114 . the authentication and right of use managing part 111 includes a service user class , a personal identification class , an authenticated user list class , a right of use class , and a usable user list class . the referring part 112 includes a target class , a referring data class , and a data storage class . the setting part 113 includes an information setting request class , a registering data class , and an information setting service class . the job operation part 114 includes a job operation request class , an operation target class , and a job operation executing service class . as shown in fig2 , the functions related to the processes via the network may be shared and included in the shared function providing part 20 , within the server platform 100 . by sharing the functions related to the processes via the network , it is possible to reduce the number of design steps and to reduce the code size of each application . furthermore , if an evaluation is made with respect to the shared function providing part 20 , the services having the same specifications and the same quality may be used in each application , thereby making it possible to secure a desired quality of the services . fig3 is a diagram showing a link ( or association ) of the sf and the server platform 100 . as shown in fig3 , the shared function providing part 20 of the server platform 100 includes a job operation part 114 . the job operation part 114 includes a job operation request class , an operation target class , and a job operation executing service class . a print service class that is implemented in a print sf i / f 31 of a middlewear interface part 30 inherits the job operation executing service class . in addition , a print document class that is implemented in the print sf i / f 31 of the middlewear interface part 30 inherits the operation target class . for example , when an operation executing method of the job operation executing service class is called , a print executing method of the print service class is called , and the print sf 41 is executed . fig3 is a diagram showing a link ( or association ) of the sf and the server platform 100 . as shown in fig3 , the shared function providing part 20 of the server platform 100 includes a referring part 112 . the referring part 112 includes a catalog class , a referring data class , and a data storage class . a document storage service class that is implemented in a storage sf i / f 34 of a middlewear interface part 30 inherits the data storage class . a stored document class that is implemented in the storage sf i / f 34 of the middlewear interface part 30 inherits the referring data class . for example , when a method of the data storage class is called , a method of the document storage service class is called , and the storage sf 34 is executed . fig3 is a diagram for explaining differences in interfaces of the sf layer and the service layer . as shown in fig3 , a getfilelist method , an openfile method , a getfileinfo method and a closefile method are implemented in the service layer , in correspondence with a searchdocument method of the sf layer . an openfile method , a writefile method and a closefile method are implemented in the service layer , in correspondence with a changedocument method of the sf layer . a checkscanparam method , a startscan method , an endscan method and a createfile method are implemented in the service layer , in correspondence with a scandocument method of the sf layer . a createprintdata method , a startprint method and a deleteprintdata method are implemented in the service layer , in correspondence with a printdocument method of the sf layer . an openfile method , a getfileinfo method , a closefile method , a checkprintparam method , a startprint method and an endprint method are implemented in the service layer , in correspondence with a printstoreddocument method of the sf layer . the processing unit of the methods of the sf layer is “ document ”, and the processing unit and the representation format are selected by the user . on the other hand , the processing unit of the methods of the service layer is “ file ”, and the processing unit and the representation format are selected by the machine . next , a description will be given of an entire relationship of the classes that are implemented in the shared function providing part 20 of the server platform 100 , by referring to fig3 . fig3 is a class diagram showing the entire relationship of the classes . fig3 shows the classes for a document operation which is used as one example of the job operation . as shown in fig3 , a service user class includes a personal identification and an identification examining state as attribute values , and includes an identification method , a right of use acquisition method and a right of use returning method as methods . an authenticated user class includes a number of registered users as the attribute value , and includes an identity inquiring method as the method . a personal identification class includes a user name and a password as the attribute values . a right of use class includes a usable function , a valid term ( or expiry date ) and an issued state as the attribute values , and includes an acquisition method , a return method , a valid term extension method , a right of use examining method , a service executing request method , a document operation request method , a document operation result notification method , an information setting request method , a catalog creating request method and a data referring request method as the methods . a usable user list class includes a number of registered users as the attribute value , and includes an authority examining method as the method . a catalog class includes a search condition and a search state as the attribute values , and includes a catalog creating method , a writing method and a data referring method as the methods . a referring data class includes a data type , a data content and a data referring state as the attribute values , and includes a referring method as the method . a data storage class includes a storage data type as the attribute value , and includes a writing start method and a detailed information acquisition method as the methods . an information setting request class includes a setting information type , a request result and a setting request state as the attribute values , and includes an information setting request method as the method . a registering data class includes a data type and a data content as the attribute values . an information setting service class includes an information setting item as the attribute value , and includes an information setting method as the method . a job operation request class includes an operation type , an operation parameter , an operation result and an operation request state as the attribute values , and includes an operation executing request method and an operation complete notification method as the methods . a document class includes an identifier and a storage location as the attribute values . a document operation executing service class includes a responsible operation as the attribute value , and includes an operation start method and an operation complete method as the methods . a service storage class includes a number of services as the attribute value , and includes a service list acquisition method , a responsible service determination method and a service detailed information acquisition method as the methods . in fig2 , the shared function providing part 20 is formed by the authentication and right of use managing part 111 , the referring part 112 , the setting part 113 and the job operation part 114 . however , the shared function providing part 20 may be formed by a single part as shown in fig3 . fig3 is a class diagram showing the shared function providing part 20 that is formed by a single part . as shown in fig3 , the shared function providing part 20 includes a service user class , a personal identification class , an authenticated user list class , a right of use class , a usable user list class , a request class and a service class . the service user class indicates users of the service ( that is , service users ). the personal identification class indicates the personal identification of the service user . the authenticated user list class indicates a list of authenticated service users . the right of use class indicates a right of use ( corresponding to a session ) of a certain service . the usable user list class indicates a list of users capable of using - various kinds of services . the request class indicates a request ( or request form ) of a process . the service class indicates a service that is usable by the service user . next , a description will be given of the concept of the functions related to the shared processes via the network . fig3 is a flow chart for explaining request and response operations . generally , the client who requests a process advances to a step si shown in fig3 , and sends a process request to the server that is connected to the client via the network . the server that receives the process request from the client advances to a step s 2 , and creates a request ( or request form ) having attribute values shown in fig4 which will be described later , for example . in addition , the server advances to a step s 3 and checks the right of use . if the check of the right of use in the step s 3 is ok , the server advances to a step s 4 and makes a process request in correspondence with the received process request . the server then advances to a step s 5 , and discards the request ( or request form ) created in the step s 2 . the server then advances to a step s 6 , and sends a result response to the client . on the other hand , if the check of the right of use in the step s 3 is no good ( ng ), the server advances to a step s 7 , and discards the request ( or request form ) that is created in the step s 2 . the server then advances to a step s 8 , and sends a result response to the client . fig3 is a collaboration diagram for a case where the check of the right of use in the step s 3 is ok . fig3 is a flow chart for explaining a job operation . generally , the client who requests a process advances to a step s 11 shown in fig3 , and sends a process request to the server that is connected to the client via the network . the server that receives the process request from the client advances to a step s 12 , and creates a request ( or request form ). in addition , the server advances to a step s 13 and checks the right of use . if the check of the right of use in the step s 13 is ok , the server advances to a step s 14 and makes a process request in correspondence with the received process request . the server then advances to a step s 15 , and judges whether or not a job operation is requested . if other than the job operation is requested ( no in step s 15 ), the server advances to a step s 16 and discards the request ( or request form ) created in the step s 12 . the server then advances to a step s 17 , and sends a result response to the client . on the other hand , if the check of the right of use in the step s 13 is no good ( ng ), the server advances to a step s 18 , and discards the request ( or request form ) that is created in the step s 12 . the server then advances to a step s 19 , and sends a result response to the client . on the other hand , if the job operation is requested ( yes in step s 15 ), the server advances to a step s 20 , and sends a result response to the client . the server repeats a process of a step s 21 until a process end notification is received . the step s 21 judges whether or not the process end notification is received . when the process end notification is received ( yes in step s 21 ), the server advances to a step s 22 , and discards the request ( or request form ) that is created in the step s 12 . fig3 is a collaboration diagram for a case where the job operation is requested . fig3 is a diagram showing an entire functional structure of the server platform 100 . as shown in fig3 , the shared function providing part 20 may be formed by a single part . fig4 is a class diagram showing an entire relationship of the classes that are implemented in the shared function providing part 20 of the server platform 100 shown in fig3 . next , a description will be given of a case where the framework shown in fig4 having the server platform 100 shown in fig2 is applied to other than the printer and the composite apparatus 1200 , by referring to fig4 through 44 . various daemons shown in fig4 through 44 are examples , and it is of course possible to employ structures in which some of the shown daemons are not included and / or some other daemons are additionally included . first , a description will be given of a functional structure of an audio visual ( av ) equipment for a case where the framework is applied to the av equipment , by referring to fig4 . fig4 is a diagram showing a functional structure of the av equipment for the case where the framework is applied to the av equipment . as shown in fig4 , the av equipment includes an httpd 200 , an ftpd 210 and an smtpd 220 as the network services . the server platform 100 includes a protocol interface part 10 , a shared function providing part 20 and a middlewear interface part 30 . as shown in fig4 , the protocol interface part 10 includes an html analyzing part 11 , an upnp analyzing part 12 , a ws analyzing part 13 and a custom i / f analyzing part 14 . in addition , the middlewear interface part 30 includes an image sf i / f 51 , an audio sf i / f 52 , a television ( tv ) sf i / f 53 , a storage sf i / f 54 , a telephone sf i / f 55 and a system i / f 56 , as shown in fig4 . in addition , the av equipment includes as the sf layer or the service layer , an image sf 61 that provides image functions , an audio sf 62 that provides audio functions , a tv sf 63 that provides tv functions , a storage sf 64 that provides storage functions , a telephone sf 65 that provides telephone functions , and a system control service ( scs ) 66 that provides functions related to system control of the av equipment . as shown in fig4 , the framework shown in fig4 having the server platform 100 shown in fig2 may be applied to the av equipment . the programs of the av equipment may be preinstalled in the av equipment or , may be provided to the av equipment by way of a recording medium 1 or downloaded to the av equipment via the network . a cpu of the av equipment executes processes according to the programs . next , a description will be given of a functional structure of a cooking appliance for a case where the framework is applied to the cooking appliance , by referring to fig4 . fig4 is a diagram showing a functional structure of the cooking appliance for the case where the framework is applied to the cooking appliance . as shown in fig4 , the cooking appliance includes an httpd 200 , an ftpd 210 and an smtpd 220 as the network services . the server platform 100 includes a protocol interface part 10 , a shared function providing part 20 and a middlewear interface part 30 . as shown in fig4 , the protocol interface part 10 includes an html analyzing part 11 , an upnp analyzing part 12 , a ws analyzing part 13 and a custom i / f analyzing part 14 . in addition , the middlewear interface part 30 includes a heating sf i / f 71 , a cooling sf i / f 72 , a cooking sf i / f 73 , a thawing sf i / f 74 , and a system i / f 75 , as shown in fig4 . in addition , the cooking appliance includes as the sf layer or the service layer , a heating sf 81 that provides heating functions , a cooling sf 82 that provides cooling functions , a cooking sf 83 that provides cooking functions , a thawing sf 84 that provides thawing functions , and a system control service ( scs ) 85 that provides functions related to system control of the cooking appliance . as shown in fig4 , the framework shown in fig4 having the server platform 100 shown in fig2 may be applied to the cooking appliance . the programs of the cooking appliance may be preinstalled in the cooking appliance or , may be provided to the cooking appliance by way of a recording medium 1 or downloaded to the cooking appliance via the network . a cpu of the cooking appliance executes processes according to the programs . next , a description will be given of a functional structure of an air conditioner for a case where the framework is applied to the air conditioner , by referring to fig4 . fig4 is a diagram showing a functional structure of the air conditioner for the case where the framework is applied to the air conditioner . as shown in fig4 , the air conditioner includes an httpd 200 , an ftpd 210 and an smtpd 220 as the network services . the server platform 100 includes a protocol interface part 10 , a shared function providing part 20 and a middlewear interface part 30 . as shown in fig4 , the protocol interface part 10 includes an html analyzing part 11 , an upnp analyzing part 12 , a ws analyzing part 13 and a custom i / f analyzing part 14 . in addition , the middlewear interface part 30 includes a heater sf i / f 91 , a cooler sf i / f 92 , a dehumidifier sf i / f 93 , a humidity controller sf i / f 94 , a germ eliminator sf i / f 95 and a system i / f 96 , as shown in fig4 . in addition , the air conditioner includes as the sf layer or the service layer , a heater sf 141 that provides heater functions , a cooler sf 142 that provides cooler functions , a dehumidifier sf 143 that provides dehumidifier functions , a humidity controller sf 144 that provides humidity controller functions , a germ eliminator sf i / f 145 that provides germ eliminator functions , and a system control service ( scs ) 146 that provides functions related to system control of the air conditioner . as shown in fig4 , the framework shown in fig4 having the server platform 100 shown in fig2 may be applied to the air conditioner . the programs of the air conditioner may be preinstalled in the air conditioner or , may be provided to the air conditioner by way of a recording medium 1 or downloaded to the air conditioner via the network . a cpu of the air conditioner executes processes according to the programs . next , a description will be given of a functional structure of a washing machine for a case where the framework is applied to the air conditioner , by referring to fig4 . fig4 is a diagram showing a functional structure of the washing machine for the case where the framework is applied to the washing machine . as shown in fig4 , the washing machine includes an httpd 200 , an ftpd 210 and an smtpd 220 as the network services . the server platform 100 includes a protocol interface part 10 , a shared function providing part 20 and a middlewear interface part 30 . as shown in fig4 , the protocol interface part 10 includes an html analyzing part 11 , an upnp analyzing part 12 , a ws analyzing part 13 and a custom i / f analyzing part 14 . in addition , the middlewear interface part 30 includes a water supplying sf i / f 121 , a washing sf i / f 122 , a spin - drying sf i / f 123 , a heat - drying sf i / f 124 , a germ eliminator sf i / f 125 and a system i / f 126 , as shown in fig4 . in addition , the washing machine includes as the sf layer or the service layer , a water supplying sf 131 that provides water supplying functions , a washing sf 132 that provides washing functions , a spin - drying sf 133 that provides spin - drying functions , a heat - drying sf 134 that provides heat - drying functions , a germ eliminator sf i / f 135 that provides germ eliminator functions , and a system control service ( scs ) 136 that provides functions related to system control of the washing machine . as shown in fig4 , the framework shown in fig4 having the server platform 100 shown in fig2 may be applied to the washing machine . the programs of the washing machine may be preinstalled in the washing machine or , may be provided to the washing machine by way of a recording medium 1 or downloaded to the washing machine via the network . a cpu of the washing machine executes processes according to the programs . therefore , according to the present invention , it is possible to realize service providing methods , service providing apparatuses , computer - readable storage media and computer program products that are easy to develop and can provide services having a desired quality . this application claims the benefit of japanese patent applications no . 2004 - 130211 filed apr . 26 , 2004 and no . 2005 - 117648 filed apr . 15 , 2005 , in the japanese patent office , the disclosures of which are hereby incorporated by reference . further , the present invention is not limited to these embodiments , but various variations and modifications may be made without departing from the scope of the present invention .