Abstract: Systems and techniques are disclosed for enabling structured data to be associated with visual content in a manner that preserves the ability to edit the visual content using a content application such as a notebook application. Techniques and systems enable semantic notation to be introduced into selected regions of the visual content that indicate the visual content's structured data, allowing the content to be searched and accessed more easily by common search technologies and search engines. The semantic notation is assigned to the visual content so that the introduction of the semantic notation does not hinder the user's viewing or editing of the visual content with a content application. The inclusion of the semantic notation does not cause existing visual editing tools that do not understand the semantic notation to cease to function properly.

Abstract: Systems and techniques are disclosed for enabling structured data to be associated with visual content in a manner that preserves the ability to edit the visual content using a content application such as a notebook application. Techniques and systems enable semantic notation to be introduced into selected regions of the visual content that indicate the visual content's structured data, allowing the content to be searched and accessed more easily by common search technologies and search engines. The semantic notation is assigned to the visual content so that the introduction of the semantic notation does not hinder the user's viewing or editing of the visual content with a content application. The inclusion of the semantic notation does not cause existing visual editing tools that do not understand the semantic notation to cease to function properly.

Abstract: Techniques for an inherited entity storage model are described that can be employed to implement inherited entity management for a CRM system. In at least some embodiments, input can be obtained to create a custom entity that is based at least in part upon a parent entity. The custom entity is created to inherit the parent entity according to an inheritance relationship established between the entities. To do so, the custom entity is created from the parent entity in a common table with the parent entity using some common fields and defining custom fields as appropriate. Data for the entities is then stored via the common table. This approach can reduce storage requirements, enable unified searching, and speed up data operations. Further, back-end business logic associated with parent entity in the CRM system can be automatically applied to the custom entity based upon the inheritance relationship established between the entities.

Abstract: Techniques for an inherited entity storage model are described that can be employed to implement inherited entity management for a CRM system. In at least some embodiments, input can be obtained to create a custom entity that is based at least in part upon a parent entity. The custom entity is created to inherit the parent entity according to an inheritance relationship established between the entities. To do so, the custom entity is created from the parent entity in a common table with the parent entity using some common fields and defining custom fields as appropriate. Data for the entities is then stored via the common table. This approach can reduce storage requirements, enable unified searching, and speed up data operations. Further, back-end business logic associated with parent entity in the CRM system can be automatically applied to the custom entity based upon the inheritance relationship established between the entities.