Abstract: Encrypted poll responses from a group of users are validated homomorphically in an online polling system. Mathematical operations are performed on encrypted poll responses to produce validated encrypted results. The operations, when applied to plaintext of the encrypted poll response, normalize the plaintext when the poll response is valid, and nullify the plaintext when the poll response is invalid. The validated encrypted poll responses can be analyzed, without decryption, to provide a variety of results in encrypted format. The analysis may include summing the validated poll responses to produce a tally and may also be analyzed in accordance with associated cleartext metadata. Multiple sets of encrypted poll responses to multiple poll queries can be analyzed to determine relationships with respect to each other, in encrypted form, as well as in conjunction with cleartext parameters.

Abstract: An entity-centric approach has been proposed to provide a consistent user experience in accessing a unified software applications suite effortlessly. Entities are connected with one another. The entities and the connectivity between them are reflected in all three functional layers of 3-tier client-server architecture. Every entity has a set of attributes and each attribute represents a data item or record of a particular type. The data items or records are represented in the form of card(s) as determined by contextualization and access control engines. The connection between two or more entities in the context of communication/interaction, collaboration and productivity, can be referred to as an activity. The activities of the entities can be represented in a timeline or swimlane mode. The timeline mode represents the recent activities between two entities as a vertical timeline chart, in reverse chronological order. The swimlane mode represents activities of multiple entities, in parallel.

Abstract: Techniques for generating a proper agenda with a desired outcome in a predicted workflow within an organization. A template is generated and an asset synthesis instance that includes an agenda is designed to advance a task. The template is generated with the asset synthesis instances building upon one another over time by accessing meeting minutes, persona ratings, resource contribution ratings, transcripts, file histories, or the like of a first asset synthesis instance for a task when creating an agenda for a second asset synthesis instance for the task.

Abstract: A cloud marketplace includes a network of data centers that collectively allow users to search for and purchase products, including applications and extensions to applications. Each data center supports a marketplace module that executes on computing resources to offer users the products and receive and send product metadata descriptive of the products. The marketplace module in each data center, on receiving user feedback related to one of the products, updates the product metadata with the user feedback, and updates a database in the data center using database management system protocols. The marketplace module also passes the user feedback to an agent module within the data center that is separate from the database management system. The agent module passes the user feedback to agent modules of other data centers so that the user feedback can be synchronized across data centers before the database management systems of the data centers synchronize with each other.

Abstract: An effective strategy provides an intuitive starting point for an enterprise network agent to resolve issues before the issues increase the probability of an outage. Being able to predict whether and when a current anomalous state will transform into an outage is valuable to an enterprise network agent tasked with network administration, including monitoring the network; configuring the network; recommending software or hardware licenses, updates, or additions; obtaining software or hardware licenses or devices; generating reports and alerts; and launching countermeasures in association with the enterprise network.

Abstract: Live-custom recording functionality is described. Live-custom recording can help a teleconferencing participant overcome situations where the participant may, for example, not have been attentive and therefore may have missed what was communicated. Another example of a situation that can be overcome with techniques described in this paper is one in which the participant cannot hear the speaker due to inadequate or low bandwidth and network connectivity issues. An enhanced conference recording functionality such as the live-custom recording functionality proposed and described herein is designed to capture applicable segments or clips of the teleconference meeting.

Abstract: Described are methods and systems that watermark text files in document or image formats using efficient encoding schemes. A unique identifier is encoded into a document by perturbing typographical properties of document elements, such as the lengths and widths of words, lines, or spaces, to encode multiple bits per element. Perturbations to the rendered dimensions of elements create patterns, digital watermarks, that can be decoded to recover the unique identifier, which can in turn be used to identify a user who disclosed or was otherwise responsible for a leaked document.

Abstract: An entity-centric approach has been proposed to provide a consistent user experience in accessing a unified software applications suite effortlessly. Entities are connected with one another. The entities and the connectivity between them are reflected in all three functional layers of 3-tier client-server architecture. Every entity has a set of attributes and each attribute represents a data item or record of a particular type. The data items or records are represented in the form of card(s) as determined by contextualization and access control engines. The contextualization engine determines the origin of the user. The access control engine determines the access permission of every user.

Abstract: Construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A DEACTIVATE tag conveys a request to a compiler to deactivate an associated construct, as well as to find and deactivate dependencies of the construct. A DEACTIVATE tag may incorporate properties, permissions, and generate notifications, including a condition for evaluation, the deactivation conditionally responsive to the result of the condition evaluation. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: A set of construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. Tags may incorporate properties, permissions, and generate notifications. Example tags include IGNORE, DEACTIVATE, OPTIMIZE, FIX, ALTERNATE, PROTOTYPE, REQUESTREVIEW, REVIEWED, CANDIDATE, and BESTCANDIDATE. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: Construct-modified tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A REQUESTREVIEW tag conveys a request to a compiler to notify a reviewer that source code is ready for review. A REVIEWED tag indicates a review has been performed and may signify code acceptance. Alternatively, a FIX or OPTIMIZE tag may be used to identify further code development requirement. These tags may incorporate properties, permissions, and generate notifications. Methods may facilitate code review and feedback in other aspects. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: Construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A FIX or OPTIMIZE tag identifies a construct to be altered. An ALTERNATE tag identifies an alternate construct to be compiled while ignoring a FIX or OPTIMIZE tagged construct of the same name. The alternate construct may be marked for ignoring once the other tagged construct of the name is fixed or optimized. Each tag may incorporate properties, permissions, and generate notifications. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: Construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A CANDIDATE tag conveys a request to a compiler to identify multiple candidate constructs, compile each set of candidates or sets of multiple candidates into executables, and profile the compiled executables. Results of the profiling can be compared and a best candidate or set of candidates selected based on one or more of various criteria. A CANDIDATE tag may incorporate properties, permissions, and generate notifications. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: Construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A hierarchy of developers and associated permissions is maintained. A tag may be associated with one or more developers as well as one or more permissions. Notifications associated with tags may be issued to one or more developers in response to a conveyed compiler request. General messages to all the developers and personalized messages to one or more developers indicate the presence of tags and need to resolve issues before the software development process enters the production phase.

Abstract: The disclosed badge creation systems and methods aim at reducing queuing time at badge preparation and distribution. The invention discloses creating a pre-printed badge with locally printed label, a partially locally printed badge, a fully locally printed badge, or a combination of these; determining privacy policy compliance for a selected badge type; and specifying a compliant dataset that is privacy policy compliant in accordance with the privacy compliance determination.

Abstract: Described are methods and systems for parsing unstructured or semi-structured text to extract named entities, data types defined to include semantic fields. Fields are constrained to sets of potential field values. These sets can overlap, leading to ambiguous parses. For example, the text string “3-4-2023” parsed as a date can yield Mar. 4, 2023 or Apr. 3, 2023. Potential field values in alternative parses are scored and the scores used to select and disambiguate the resultant value parses.

Abstract: An entity-centric approach has been proposed to provide a consistent user experience in accessing a unified software applications suite effortlessly. Entities are connected with one another. The entities and the connectivity between them are reflected in all three functional layers of 3-tier client-server architecture. Every entity has a set of attributes and each attribute represents a data item or record of a particular type. The data items or records are represented in the form of card(s) as determined by contextualization and access control engines. Interactions capture entity communications across the unified software suite. The entities can communicate or interact across various channels like mail, call, messages, webinar, etc. Interaction across each channel is possible by one or more software applications. The interactions trends can be represented by channel and by entity. When interactions are filtered by channel, a channel-wise list for each type of interaction, e.g., mail, chat, call, etc.

Abstract: A compile-time link type manager is defined to facilitate development of source code with disciplined link type object management at run-time. In one aspect, when a compile-time link type manager encounters a link type object management construct in source code, it will emit code for a runtime object management engine that processes generic link type object management instructions at runtime. It will also compile type-specific instructions from the link type object management construct for accessing the generic instructions in the runtime object management engine for affecting a link type object at runtime. A runtime object management engine may perform various checks, referred to as link-type criteria, at runtime prior to executing a link type object management instruction. When defined link-type criteria are satisfied for a link type object management instruction for an object at runtime, the instruction is carried out.

Abstract: A compile-time link type manager is defined to facilitate development of source code with disciplined link type object management at runtime. In one aspect, the link type manager ensures that all link type object management constructs have associated event handlers. Additionally, an event handler can be evaluated at compile time to ensure that it meets certain conditions for the particular link type, referred to as link-type criteria.

Abstract: Extension of built-in object management functions such as create, update, and delete are illustrated. The developer can extend any of these functions for management of objects for a type within its type definition in source code. In one aspect, an object management function is extended to accept one or more additional arguments to capture one or more parameters, stored as metadata associated with the object, and accessible for use with further object management as well as other functions. In another aspect, one or more constraints are defined to implement control over management of an object of the extended type. At runtime, a constraint is evaluated, and, when the constraint evaluates to a predefined value, the object management function is prevented from completing.