Abstract: An approach is provided for providing separation of authentication protocols and/or authentication contexts for client-server and server-server communication in network communication. A proxy server receives a request to initiate a service session. The request includes a first authentication context. The proxy server request verification of the first authentication context from an authentication server and validates the first authentication context based, at least in part, on the verification. The proxy server implements a second authentication context based, at least in part, on the verification of the first authentication context to initiate the service session.

Abstract: An approach is presented for making the use of a mobile device more socially suitable. Remote control application programming interfaces and installation packages are specified to developers for designing applications that can be controlled via a main device (e.g., a mobile phone) and one or more accessory devices (e.g., a watch). Specifically, each application is required to have two installable components—one that resides on the main device and one that is automatically installed on an associated remote accessory device. By enabling the seamless installation of these two components, a new paradigm or ecosystem for how applications are to be created and installed is introduced. In this new paradigm, application developers will not only develop the applications, but they will also design and define a way to make their applications remotely controllable and reachable from an accessory device, thus making the associated mobile devices running such applications more socially suitable.

Abstract: An approach is presented for making the use of a mobile device more socially suitable. Remote control application programming interfaces and installation packages are specified to developers for designing applications that can be controlled via a main device (e.g., a mobile phone) and one or more accessory devices (e.g., a watch). Specifically, each application is required to have two installable components—one that resides on the main device and one that is automatically installed on an associated remote accessory device. By enabling the seamless installation of these two components, a new paradigm or ecosystem for how applications are to be created and installed is introduced. In this new paradigm, application developers will not only develop the applications, but they will also design and define a way to make their applications remotely controllable and reachable from an accessory device, thus making the associated mobile devices running such applications more socially suitable.

Abstract: An approach is provided for providing separation of authentication protocols and/or authentication contexts for client-server and server-server communication in network communication. A proxy server receives a request to initiate a service session. The request includes a first authentication context. The proxy server request verification of the first authentication context from an authentication server and validates the first authentication context based, at least in part, on the verification. The proxy server implements a second authentication context based, at least in part, on the verification of the first authentication context to initiate the service session.

Abstract: An approach is provided for providing separation of authentication protocols and/or authentication contexts for client-server and server-server communication in network communication. A proxy server receives a request to initiate a service session. The request includes a first authentication context. The proxy server request verification of the first authentication context from an authentication server and validates the first authentication context based, at least in part, on the verification. The proxy server implements a second authentication context based, at least in part, on the verification of the first authentication context to initiate the service session.

Abstract: An approach is presented for making the use of a mobile device more socially suitable. Remote control application programming interfaces and installation packages are specified to developers for designing applications that can be controlled via a main device (e.g., a mobile phone) and one or more accessory devices (e.g., a watch). Specifically, each application is required to have two installable components—one that resides on the main device and one that is automatically installed on an associated remote accessory device. By enabling the seamless installation of these two components, a new paradigm or ecosystem for how applications are to be created and installed is introduced. In this new paradigm, application developers will not only develop the applications, but they will also design and define a way to make their applications remotely controllable and reachable from an accessory device, thus making the associated mobile devices running such applications more socially suitable.

Abstract: An approach is provided for providing separation of authentication protocols and/or authentication contexts for client-server and server-server communication in network communication. A proxy server receives a request to initiate a service session. The request includes a first authentication context. The proxy server request verification of the first authentication context from an authentication server and validates the first authentication context based, at least in part, on the verification. The proxy server implements a second authentication context based, at least in part, on the verification of the first authentication context to initiate the service session.

Abstract: A device for generating semantic folder annotations is provided. The device includes a semantic folder editor which enables a user to create attribute-value pairs corresponding to a semantic folder(s). The device is capable of downloading ontolog(ies) and associated data from an ontology server which may be utilized to determine relationships between the attribute-value pairs created by the user. The device includes an annotations generator which specifies the semantic folder descriptions of the semantic folders based on attribute-value relationships determined by the ontolog(ies). The device is capable of allowing a user to insert an object(s) into a semantic folder(s) and the annotations generator assigns all attribute-value pairs corresponding to the semantic folder to the object(s). The annotations assigned to object(s) may be stored in a semantic triple store. The device further includes a search engine which may be employed by a user to search semantic folders to locate an object(s).

Abstract: A device for generating semantic folder annotations is provided. The device includes a semantic folder editor which enables a user to create attribute-value pairs corresponding to a semantic folder(s). The device is capable of downloading ontolog(ies) and associated data from an ontology server which may be utilized to determine relationships between the attribute-value pairs created by the user. The device includes an annotations generator which specifies the semantic folder descriptions of the semantic folders based on attribute-value relationships determined by the ontolog(ies). The device is capable of allowing a user to insert an object(s) into a semantic folder(s) and the annotations generator assigns all attribute-value pairs corresponding to the semantic folder to the object(s). The annotations assigned to object(s) may be stored in a semantic triple store. The device further includes a search engine which may be employed by a user to search semantic folders to locate an object(s).

Abstract: A method of facilitating a service includes receiving a description of a service, and invoking the service based on the description. In this regard, the description comprises one having been generated based on an ontology including a set of classes, instances and associated properties for describing a user interface (UI) that includes one or more fields. The set of classes, instances and associated properties include a class for describing a field of the UI, and one or more properties for describing a name of the respective field and/or a UI widget for implementing the respective field. In this regard, the description includes a UI model of the service, where the UI model includes one or more of the classes, instances and associated properties of the ontology. Invoking the service, then, includes generating a UI based on the UI model.