Embedded reuse meta information

• US 7,681,112 B1
• Filed: 05/30/2003
• Issued: 03/16/2010
• Est. Priority Date: 05/30/2003
• Status: Active Grant

• Current Assignee: Adobe Inc.
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Francis, Andrew
• Primary Examiner(s): Rutledge; Amelia
• Application Number:
  US10/449,878
• Time in Patent Office: 2,482 Days
• Field of Search: 715/501, 715/501.1, 715/201, 715/234, 715/243
• US Class Current: 715/201
• CPC Class Codes: G06F 40/131 Fragmentation of text files, e.g. creating reusable text-blocks; Linking to fragments, e.g. using XInclude; Namespaces

Abstract

Systems and techniques to facilitate reuse of page components. In general, the techniques includes: generating multiple components of a markup language document to be rendered, the multiple components being derived from one or more information sources, designating the multiple components in the markup language document using a recognized identifier of document sections, and adding reuse information to the designated components of the markup language document so that the reuse information is readable with the components but not revealed when the markup language document is rendered, the reuse information specifying how the components may be repurposed via access to the one or more information sources. The techniques further include: rendering multiple components of a presentation, and in response to a selection of one or more components in the presentation, using reuse information contained in the one or more components to facilitate repurposing of the one or more components.

Claims

1. A computer implemented method comprising:

generating multiple components of a web page to be rendered, the multiple components being derived from one or more information sources;

designating the multiple components in the web page using a recognized identifier of document sections; and

adding reuse information to the designated components in the web page so that the reuse information is readable with the components but not revealed when the web page is rendered, the reuse information specifying how the components may be repurposed.

2. The method of claim 1, further comprising sending the web page, including the reuse information, to a client in response to a request from the client, wherein said generating the multiple components comprises generating the multiple components in response to the request from the client, and the reuse information includes terms of use information.

3. The method of claim 1, wherein the reuse information identifies a source of further reuse information, the further reuse information describing how the components are reusable.

4. The method of claim 1, wherein the reuse information comprises syndication information, the syndication information comprising one or more of a link, push/pull information, or times of availability.

5. The method of claim 1, wherein the web page comprises a hypertext markup language page.

6. The method of claim 1, wherein the multiple components comprise one or more visual components and an audio component of the web page.

7. The method of claim 1, wherein the reuse information specifying how the components may be repurposed comprises terms of use.

8. The method of claim 1, wherein the reuse information specifying how the components may be repurposed comprises payment information.

9. The method of claim 1, wherein the reuse information specifying how the components may be repurposed comprises legal or business metadata, comprising one or more of author notices, copyright notices, or prices.

10. The method of claim 1, wherein the reuse information specifying how the components may be repurposed comprises technical metadata, comprising one or more of application-specific component information, creation date and time, or resource requirements.

11. The method of claim 1, wherein the reuse information specifying how the components may be repurposed comprises a link to a catalog of further reuse information, the further reuse information specifying how the components may be repurposed.

12. A computer implemented method comprising:

obtaining a web page that defines a presentation and includes multiple components to be rendered, the multiple components being derived from one or more information sources;

reading reuse information from the web page when the multiple components are read for the rendering, the reuse information specifying how the components may be repurposed;

rendering the multiple components of the presentation, the rendering not revealing the reuse information; and

in response to a selection of one or more of the multiple components in the presentation, using the reuse information contained in the one or more components to facilitate repurposing of the one or more components.

13. The method of claim 12, wherein the web page comprises a markup language document, and the multiple components are designated in the markup language document using a recognized identifier of document sections.

14. The method of claim 13, wherein the markup language document comprises a hypertext markup language page.

15. The method of claim 12, wherein the reuse information comprises syndication information, the syndication information comprising one or more of a link, push/pull information, or times of availability.

16. The method of claim 12, wherein the multiple components comprise one or more visual components and an audio component, and the presentation comprises an audio/video presentation.

17. The method of claim 12, wherein using the reuse information comprises incorporating the selected one or more components into a second document based on the reuse information.

18. The method of claim 17, wherein after the selected one or more components are modified.

19. The method of claim 18, wherein the modifying the components is done in accordance with terms of use information included in the reuse information.

20. The method of claim 12, wherein the reuse information specifying how the components may be repurposed comprises terms of use.

21. The method of claim 12, wherein the reuse information specifying how the components may be repurposed comprises payment information.

22. The method of claim 12, wherein the reuse information specifying how the components may be repurposed comprises legal or business metadata, comprising one or more of author notices, copyright notices, or prices.

23. The method of claim 12, wherein the reuse information specifying how the components may be repurposed comprises technical metadata, comprising one or more of application-specific component information, creation date and time, or resource requirements.

24. The method of claim 12, wherein the reuse information specifying how the components may be repurposed comprises a link to a catalog of further reuse information, the further reuse information specifying how the components may be repurposed.

25. A software product tangibly stored on a machine-readable medium, the software product comprising instructions operable to cause a programmable processor to perform operations comprising:

generating multiple components of a web page to be rendered, the multiple components being derived from one or more information sources;

designating the multiple components in the web page using a recognized identifier of document sections; and

adding reuse information to the designated components in the web page so that the reuse information is readable with the components but not revealed when the web page is rendered, the reuse information specifying how the components may be repurposed.

26. The software product of claim 25, wherein the operations further comprise sending the web page, including the reuse information, to a client in response to a request from the client, wherein said generating the multiple components comprises generating the multiple components in response to the request from the client, and the reuse information includes terms of use information.

27. The software product of claim 25, wherein the reuse information identifies a source of further reuse information, the further reuse information describing how the components are reusable.

28. The software product of claim 25, wherein the reuse information comprises syndication information, the syndication information comprising one or more of a link, push/pull information, or times of availability.

29. The method of claim 25, wherein the reuse information specifying how the components may be repurposed comprises one or more of:

terms of use;

payment information;

legal or business metadata, comprising one or more of author notices, copyright notices, or prices;

technical metadata, comprising one or more of application-specific component information, creation date and time, or resource requirements;

or

a link to a catalog of further reuse information, the further reuse information specifying how the components may be repurposed.

30. A software product tangibly stored on a machine-readable medium, the software product comprising instructions operable to cause a programmable processor to perform operations comprising:

obtaining a web page that defines a presentation and includes multiple components to be rendered, wherein the multiple components are derived from one or more information sources;

reading reuse information from the web page when the multiple components are read for the rendering, wherein the reuse information specifies how the components may be repurposed;

rendering the multiple components of the presentation, the rendering not revealing the reuse information; and

in response to a selection of one or more components in the presentation, using reuse information contained in the one or more components to facilitate repurposing of the one or more components.

31. The software product of claim 30, wherein the web page comprises a markup language document, and the multiple components are designated in the markup language document using a recognized identifier of document sections.

32. The software product of claim 31, wherein the markup language document comprises a hypertext markup language page.

33. The software product of claim 30, wherein the reuse information identifies a source of further reuse information, the further reuse information describing how the one or more components are reusable.

34. The software product of claim 30, wherein the reuse information comprises syndication information, the syndication information comprising one or more of a link, push/pull information, or times of availability.

35. The software product of claim 30, wherein the multiple components comprise multiple visual components, and the presentation comprises an audio/video presentation.

36. The software product of claim 30, wherein using the reuse information comprises incorporating the selected one or more components into a second document based on the reuse information.

37. The software product of claim 36, wherein after the selected one or more components are incorporated into the second document, the selected one or more components are modified.

38. The software product of claim 37, wherein said allowing modification of the components comprises allowing modification in accordance with terms of use information included in the reuse information.

39. The method of claim 30, wherein the reuse information specifying how the components may be repurposed comprises one or more of:

terms of use;

payment information;

legal or business metadata, comprising one or more of author notices, copyright notices, or prices;

technical metadata, comprising one or more of application-specific component information, creation date and time, or resource requirements;

or

a link to a catalog of further reuse information, the further reuse information specifying how the components may be repurposed.

40. A software product tangibly stored on a machine-readable medium, the software product comprising:

an electronic document in a markup language format including multiple components to be rendered;

the multiple components being designated in the web page using a recognized identifier of document sections; and

the multiple components including reuse information specifying how the components may be repurposed,

wherein the reuse information is read with the multiple components but not revealed when the web page is rendered.

41. The software product of claim 40, wherein the multiple components comprise empty limitations with attributes containing at least a portion of the reuse information.

42. The method of claim 40, wherein the reuse information specifying how the components may be repurposed comprises one or more of:

terms of use;

payment information;

legal or business metadata, comprising one or more of author notices, copyright notices, or prices;

technical metadata, comprising one or more of application-specific component information, creation date and time, or resource requirements;

or

a link to a catalog of further reuse information, the further reuse information specifying how the components may be repurposed.

43. A system comprising:

a processor;

a machine-readable medium coupled with the processor; and

a Web publishing software product tangibly stored on the machine-readable medium, the Web publishing software product comprising instructions operable to cause the processor to perform operations comprising;

receiving a Web page;

identifying a reusable component of the Web page, the reusable component being designated within the Web page, the reusable component containing reuse information, where the reuse information is not rendered when the Web page is rendered; and

in response to a selection of the reusable component, using the reuse information contained in the reusable component to facilitate repurposing of the reusable component.

44. The system of claim 43, wherein the operations further comprise enforcing restrictions on modification to the reusable component indicated by the reuse information.

45. The system of claim 43, wherein the operations further comprise supporting syndicated content purchase negotiations using the reuse information.

46. The system of claim 43, wherein the operations further comprise searching for component resources based on the reuse information.