Common annotation framework

• US 7,243,301 B2
• Filed: 04/10/2002
• Issued: 07/10/2007
• Est. Priority Date: 04/10/2002
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Gupta, Anoop, Bargeron, David M.
• Primary Examiner(s): Hong; Stephen
• Assistant Examiner(s): Stork; Kyle R.
• Application Number:
  US10/119,544
• Publication Number:
  US 20040205545A1
• Time in Patent Office: 1,917 Days
• Field of Search: 715/500, 715/512, 715/511, 715/513, 715/517, 715/523, 715/530
• US Class Current: 715/205
• CPC Class Codes: G06F 40/169 Annotation, e.g. comment data or footnotes

Abstract

A Common Annotation Framework includes, in an embodiment, an annotation having a context anchor that identifies a resource and a position in the resource that the annotation pertains to, and a content anchor that identifies data that is annotating the resource. The annotation can also be extended with client application-defined data and/or functionality, and the framework can be extended with one or more of application-defined objects, methods, and annotation stores.

Claims

1. A system comprising:

a client application layer implemented in a computing device including one or more client applications;

a storage layer including an annotation store;

a common annotation layer, situated between the client application layer and the storage layer, including an annotation manager; and

wherein the annotation manager operates to allow the one ore more client applications to store annotations to and retrieve annotations from the annotation store, and wherein the annotation manager further operates to create new property types for the annotations the new property types being identified by the one or more client applications and in addition to existing property types in the client application, so that each of the annotations to be stored in the annotation store can have a property value associated with each of the created new property types.

2. A system as recited in claim 1, wherein the client application layer and the common annotation layer are implemented on two different computing devices.

3. A system as recited in claim 1, wherein the annotation manager further operates to allow the one or more client applications to create annotations for storage in the annotation store and remove annotations from the annotation store.

4. A system as recited in claim 1, wherein the new types of properties property types include new data types.

5. A system as recited in claim 1, wherein the new types of properties property types include new methods.

6. A system as recited in claim 1, wherein each new property type has an associated codebase identified in the annotation, wherein the codebase identifies a location where information can be obtained that describes how to process the new property type.

7. A system as recited in claim 6, wherein the information comprises a software code module.

8. A method implemented in a computing device, comprising:

receiving, from a client application, a request to create an annotation;

generating the annotation; and

allowing the client application to,

add context anchor data to the annotation, wherein the context anchor data identifies a resource and a position in the resource that the annotation pertains to,

add content anchor data to the annotation, wherein the content anchor data identifies data that is annotating the resource, and

extend the types of data that can be stored in the annotation by creating one or more additional new property types to the annotation so that the annotation can have a property value associated with each of the created new property types, wherein the one or more additional new property types are in addition to the existing property types in the client application.

9. A method as recited in claim 8, further comprising allowing the client application to add an additional property that describes an additional method that can be performed on the data stored in the annotation.

10. A method as recited in claim 8, wherein allowing the client application to extend the types of data comprises allowing the client application to extend the types of data that can be stored in the annotation by adding one or more additional properties to the context anchor of the annotation.

11. A method as recited in claim 8, wherein allowing the client application to extend the types of data comprises allowing the client application to extend the types of data that can be stored in the annotation by adding one or more additional properties to the content anchor of the annotation.

12. A method as recited in claim 8, further comprising allowing the client application to add a plurality of context anchors to the annotation, each including different context anchor data.

13. A method as recited in claim 8, further comprising allowing the client application to add a plurality of content anchors to the annotation, each including different content anchor data.

14. A method as recited in claim 8, wherein each of the one or more additional properties includes a codebase that identifies a location where instructions can be obtained that describe how to process the data type in the additional property.

15. A method as recited in claim 14, wherein the instructions comprise a software code module.

16. One or more computer readable media having stored thereon a plurality of instructions that, when executed by one or more processors, causes the one or more processors to:

receive, from a client application, a request to create an annotation;

generate the annotation; and

allow the client application to,

add context anchor data to the annotation, wherein the context anchor data identifies a resource and a position in the resource that the annotation pertains to,

add content anchor data to the annotation, wherein the content anchor data identifies a second resource, wherein the second resource annotates the first resource, and

extend the types of data that can be stored in the annotation by creating one or more additional new property types to the annotation so that the annotation can have a property value associated with each of the created new property types, wherein the one or more additional new property types are in addition to the existing property types in the client application.

17. One or more computer readable media having stored thereon a plurality of instructions that, when executed by one or more processors, causes the one or more processors to:

receive a request to retrieve an annotation;

identify an extended property in the annotation, wherein the extended property is a created new property type identified by one or more client applications, wherein the created new property types is in addition to existing property types in the client application;

identify a codebase corresponding to the extended property, wherein the codebase identifies a location where information can be obtained that describes how to process the contents of the extended property; and

process the contents of the extended property in accordance with the information.

18. One or more computer readable media as recited in claim 17, wherein the information comprises a software code module.

19. One or more computer readable media as recited in claim 17, wherein the contents of the extended property comprise data.

20. One or more computer readable media as recited in claim 17, wherein the contents of the extended property comprise a method.

21. One or more computer readable media as recited in claim 17, wherein the instructions to receive the request comprise instructions that cause the one or more processors to receive, by a client application, a request from a user to retrieve an annotation.

22. One or more computer readable media as recited in claim 17, wherein the instructions to receive the request comprise instructions that cause the one or more processors to receive, by an annotation manager, a request from a client application to retrieve an annotation.

23. One or more computer readable media as recited in claim 17, wherein the plurality of instructions comprise a client application.

24. One or more computer readable media as recited in claim 17, wherein the plurality of instructions comprise an annotation manager.

25. One or more computer readable media as recited in claim 17, wherein the codebase comprises a uniform resource locator (URL) of the location.

26. A system implemented in a computing device implementing a Common Annotation Framework comprising:

a plurality of annotation objects, each configured to store data regarding a resource being annotated and data annotating the resource; and

an object manager configured to allow a client application to access he plurality of annotation objects, and further configured to allow the client application to create new property types of the plurality of annotation objects with client application-defined data and in addition to existing property types in the client application, so that the annotation objects can have a property value associated with each of the created new property types.

27. A system as recited in claim 26, wherein the object manager includes a create method interface that allows the client application to request that an annotation object be created.

28. A system as recited in claim 26, wherein the object manager includes a save method interface that allows the client application to request that an annotation object be saved into an annotation store.

29. A system as recited in claim 26, wherein the object manager includes a remove method interface that allows the client application to request that an annotation object be removed form an annotation store.

30. A system as recited in claim 26, wherein the object manager includes a retrieve method interface that allows the client application to request that an annotation object be retrieved from an annotation store.

31. A system as recited in claim 26, wherein the object manager includes an invoke method interface that allows the client application to request that a client application-defined method be executed by the object manager.

32. A system as recited in claim 26, wherein the object manager includes a codebase method interface that allows another client application to obtain an identifier of a location of instructions regarding how to process the client application-defined data.

33. A system as recited in claim 26, wherein the client application-defined data comprises methods.

34. A system as recited in claim 26, wherein the client application-defined data comprises properties.

35. A system as recited in claim 26, wherein each of the plurality of annotation objects exposes an annotation interface that allows the client application to access a pointer to an anchor object that identifies a location of the resource that the annotation object pertains to.

36. A system as recited in claim 26, wherein each of the plurality of annotation objects exposes an annotation interface that allows the client application to access a pointer to an anchor object that identifies a location of another resource that contains the data annotating the resource.

37. A system as recited in claim 26, wherein the Common Annotation Framework further comprises a set object that allows selected ones of the plurality of annotation objects to be grouped together.

38. A system as recited in claim 26, wherein the Common Annotation Framework further comprises an event object that includes data to be returned to the client application in an asynchronous manner.

39. A system as recited in claim 26, wherein the Common Annotation Framework further comprises an anchor object that contains the data regarding the resource being annotated.

40. A system as recited in claim 26, wherein the Common Annotation Framework further comprises an anchor object that contains the data annotating the resource.

41. A system as recited in claim 26, wherein the Common Annotation Framework further comprises a property object that contains the client application-defined data.

42. A method implemented in a computing device comprising:

receiving a request to retrieve, from an annotation store, one or more annotation objects; and

implementing one or more of a plurality of handlers as needed to respond to the request, the plurality of handlers including an extended property handler, extended object handler, and an extended storage handler, wherein the extended property handler is configured to create new property types identified by a client application to the one or more annotation objects so that annotation objects can have a property value associated with each of the created new property types, wherein the one or more additional new property types are in addition to the existing property types in the client application.

43. A method as recited in claim 42, wherein the extended property handler operates on annotation object properties.

44. A method as recited in claim 42, wherein the extended property handler operates on anchor object properties.

45. A method as recited in claim 42, wherein the extended storage handler operates on objects from the annotation store.