Abstract: Systems and methods for trusted provisioning and authentication for networked devices in a cloud-based IoT/M2M platform is disclosed. In one embodiment, a fully qualified domain name and public key is registered in a domain name server for each networked device during device configuration. A network device establishes its trustworthiness to a data collection and processing server by providing credentials to the data collection and processing server. The data collection and processing server deduces the username, the device's fully qualified domain name, and encrypted password from the credentials. The domain name server is queried for the fully qualified domain name and the public key is returned. The encrypted password is decrypted using the public key and an attempt is made to verify the password. When the password is verified, the username is provided to the data collection and processing server to authorize a network connection between the networked device and the data collection and processing server.

Abstract: Systems, methods, and other embodiments associated with secure cloud based multi-tier provisioning are described. In one embodiment, a method includes storing, in server-side computer storage medium, an activation key for a networked device and a set of configuration parameter values associated with an application to be run by the networked device. The method includes managing access to the computer storage medium such that access to the activation key and the configuration parameter values by unauthorized entities is prevented. Upon receiving the activation key from an authorized installation entity, the method includes identifying a configuration for the networked device comprising the set of configuration parameter values. A network connection is made with the networked device and the configuration is transmitted to the networked device, such that the configuration is not provided to the authorized installation entity.

Abstract: Systems and methods for trusted provisioning and authentication for networked devices in a cloud-based IoT/M2M platform is disclosed. In one embodiment, a fully qualified domain name and public key is registered in a domain name server for each networked device during device configuration. A network device establishes its trustworthiness to a data collection and processing server by providing credentials to the data collection and processing server. The data collection and processing server deduces the username, the device's fully qualified domain name, and encrypted password from the credentials. The domain name server is queried for the fully qualified domain name and the public key is returned. The encrypted password is decrypted using the public key and an attempt is made to verify the password. When the password is verified, the username is provided to the data collection and processing server to authorize a network connection between the networked device and the data collection and processing server.

Abstract: Systems, methods, and other embodiments associated with secure cloud based multi-tier provisioning are described. In one embodiment, a method includes storing, in server-side computer storage medium, an activation key for a networked device and a set of configuration parameter values associated with an application to be run by the networked device. The method includes managing access to the computer storage medium such that access to the activation key and the configuration parameter values by unauthorized entities is prevented. Upon receiving the activation key from an authorized installation entity, the method includes identifying a configuration for the networked device comprising the set of configuration parameter values. A network connection is made with the networked device and the configuration is transmitted to the networked device, such that the configuration is not provided to the authorized installation entity.

Abstract: Systems, methods, and other embodiments associated with generating social networks are described. In one embodiment, a method includes generating recommendations for expanding a social network for a user based at least in part on the user's membership to a workspace and other members of the workspace.

Abstract: Systems, methods, and other embodiments associated with an artifact type neutral container are described. This artifact type neutral container is achieved through an artifact type neutral architecture that is managed using a central type neutral registration mechanism. Queries are executed on type neutral registration tables to return data stores that store the artifacts found within a given artifact type neutral container. The data stores are queried to return the artifacts in the artifact type neutral container. The artifact type neutral container can be used in systems in which the artifact type neutral container and artifact data are stored in the same database as well as in systems in which the artifact type neutral container and artifact data are stored in different databases.

Abstract: Systems, methods, and other embodiments associated with generating social networks are described. In one embodiment, a method includes generating recommendations for expanding a social network for a user based at least in part on the user's membership to a workspace and other members of the workspace.

Abstract: Systems, methods, and other embodiments associated with providing non-linear navigation in a discussion forum are described. One method embodiment includes maintaining a location data that identifies a thread or message to which a user has navigated. The method also includes manipulating a navigation control in a graphical user interface based on actions taken by the user and/or other users of the system. The navigation control facilitates a user moving to points not traditionally reachable in a single vertical navigation step in a discussion forum interface.

Abstract: Systems, methods, and other embodiments associated with thread-based conversation management are described. One system embodiment includes a conversation manager that provides access to communication applications, that provides lifecycle management for an electronic conversation carried on over the communication applications, and that organizes conversation elements belonging to a conversation carried on using the communication applications. The conversation lifecycle may include pausing and resuming a conversation carried on, at least in part, over a synchronous, online, real-time, communication application. The system embodiment may also include a thread manager to provide thread-based storage for conversation elements.

Abstract: Systems, methods, and media associated with coordinating a discussion forum application and an email application are described. One example system includes a data store and a coordination logic. The data store may store a discussion forum message in a data structure accessible to both an email logic and a discussion forum logic. The coordination logic may provide access to the discussion forum message for the email logic and the discussion forum logic. The coordination logic may also maintain read status consistency for the discussion forum message and cause threading information associated with the discussion forum message to be honored.

Abstract: Systems, methods, and other embodiments associated with artifact type neutral change management are described. One example method includes maintaining an access table for each artifact in a collaborative software environment that records a most recent access of an artifact on a per user basis. An artifact type registration table is also maintained that maps each artifact type to the access table that records access information for artifacts of the given type and to a data store that stores artifacts of that type. For a given user, artifact pair, queries on the type registration table, access table, and data store are generated to return the last modification time for the artifact and the user's last access time for the artifact. This information is used to determine a change status of the artifact for the given user. This common framework can be used for artifacts of any type that are registered in the type registration table.

Abstract: Systems, methods, media, and other embodiments associated with effort based relevance in discussion forums are described. One example method includes receiving activity data concerning messages associated with electronic discussion forum topics. The activity data may include a view count (Vw), a book mark count (Bf), a reference count (Rf), and a reply count (Rp). The effort based relevance may be computed from Vw and one or more of, Bf, Rf, and Rp. Topics may be logically ordered using the effort based relevance.

Abstract: Systems, methods, and other embodiments associated with collaborative draft forum-messages are described. One example method includes receiving draft forum-message data from a drafter. The draft forum-message data may identify a set of entities to whom the drafter seeks to grant edit privileges. The example method may also include providing a portion of the draft forum-message data to one of the identified entities and allowing them to view and/or modify the draft forum-message data.

Abstract: Systems, methods, and other embodiments associated with an artifact type neutral container are described. This artifact type neutral container is achieved through an artifact type neutral architecture that is managed using a central type neutral registration mechanism. Queries are executed on type neutral registration tables to return data stores that store the artifacts found within a given artifact type neutral container. The data stores are queried to return the artifacts in the artifact type neutral container. The artifact type neutral container can be used in systems in which the artifact type neutral container and artifact data are stored in the same database as well as in systems in which the artifact type neutral container and artifact data are stored in different databases.

Abstract: Systems, methods, and other embodiments associated with artifact type neutral change management are described. One example method includes maintaining an access table for each artifact in a collaborative software environment that records a most recent access of an artifact on a per user basis. An artifact type registration table is also maintained that maps each artifact type to the access table that records access information for artifacts of the given type and to a data store that stores artifacts of that type. For a given user, artifact pair, queries on the type registration table, access table, and data store are generated to return the last modification time for the artifact and the user's last access time for the artifact. This information is used to determine a change status of the artifact for the given user. This common framework can be used for artifacts of any type that are registered in the type registration table.

Abstract: A syndicator for disseminating Web services and other resources from service and content providers to service consumers and for establishing and implementing subscription agreements specifying the terms upon which digital assets are provided to subscribers. A registration database stores a service description for each of a plurality of different Web services and other resources. Each stored service description contains an input processing specification, an output processing specification, and the specification of the business terms upon which the described service or resource is offered by its provider to subscribers. A subscription manager conducts a negotiation with a prospective subscriber and receives from the subscriber an acceptance of the business terms upon which a specified Web service or resource is offered to establish a subscription agreement. Event tracking records information describing the performance of each service on behalf of each subscriber to perform subscription accounting functions.

Abstract: A dynamic services infrastructure accepts data describing data resources and stores that data in a relational database from which it may be retrieved to handle service requests issued by application programs. The database stores Service Definition data which is initially supplied in the form of XML Service Descriptor documents which are then mapped into the database from which they may be accessed. Each Service Definition includes an input specification which identifies the address of a resource as well as the nature of the input data to be supplied to the resource with the request, and further includes an output specification which describes the nature of the output information which is supplied by the resource in response to the request.

Abstract: Systems, methods, and other embodiments associated with providing non-linear navigation in a discussion forum are described. One method embodiment includes maintaining a location data that identifies a thread or message to which a user has navigated. The method also includes manipulating a navigation control in a graphical user interface based on actions taken by the user and/or other users of the system. The navigation control facilitates a user moving to points not traditionally reachable in a single vertical navigation step in a discussion forum interface.

Abstract: Systems, methods, and other embodiments associated with thread-based conversation management are described. One system embodiment includes a conversation manager that provides access to communication applications, that provides lifecycle management for an electronic conversation carried on over the communication applications, and that organizes conversation elements belonging to a conversation carried on using the communication applications. The conversation lifecycle may include pausing and resuming a conversation carried on, at least in part, over a synchronous, online, real-time, communication application. The system embodiment may also include a thread manager to provide thread-based storage for conversation elements.

Abstract: A system for storing and dynamically updating data represented in the Extensible Markup Language (XML) which separates the data values in at least some of the elements of an XML document and places those data values in relational database tables where they may be processed using conventional RDBMS techniques. The hierarchical structure of the XML document is saved separately in an XML skeleton object from which element data other than primary key values has been removed. The XML documents document type definition (DTD) is stored, along with additional property data used the RDBMS, in an XML Definition object.