Exception markup documents

• US 20040181750A1
• Filed: 03/12/2003
• Published: 09/16/2004
• Est. Priority Date: 03/12/2003
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Lection, David B., Noguchi, Masato, Masselle, Eric L., Reich, David E.
• Granted Patent: US 7,461,337 B2
• Time in Patent Office: Days
• US Class Current: 715/513
• CPC Class Codes: G06F 16/84 Mapping; Conversion

Abstract

A method for excluding structures from a markup document can include identifying a section within a first markup document into which at least a portion of a second markup document is to be inserted. An exception markup document can be identified that specifies structures restricted within the section. The first markup document, the second markup document, and the exception markup document can be based upon the same markup language. The portion of the second markup document can be searched for at least one excluded structure specified within the exception markup document. If no excluded structure is found the portion can be inserted into the section. If at least one of the excluded structures is found, at least one exception handling operation can be performed.

Claims

1. A method for excluding structures from a markup document comprising the steps of:

identifying a section within a first markup document into which at least a portion of a second markup document is to be inserted;

identifying an exception markup document specifying structures restricted within said section;

searching said portion for at least one excluded structure specified within said exception markup document;

if no excluded structure is found by said searching step, inserting said portion into said section; and

,

if at least one of said excluded structures is found by said searching step, performing at least one exception handling operation.

2. The method of claim 1, wherein said first markup document is provided by a portal, wherein said section specifies a container, and wherein said second markup document includes content provided by a content source, wherein said content source is different from said portal.

3. The method of claim 1, wherein said exception handling operation comprises:

displaying a message indicating that restricted structures exist within said portion.

4. The method of claim 1, wherein said exception handling operation comprises the steps of:

deleting said excluded structure from said portion; and

,

inserting said portion within said section.

5. The method of claim 6, further comprising:

identifying an initializing location specifying the beginning of said excluded structure;

identifying a terminal location specifying the ending of said excluded structure;

identifying structure content contained between said initializing location and said terminal location; and

,

deleting at least a portion of said structure content.

6. The method of claim 1, further comprising:

identifying within said exception markup document a replacement structure associated with said excluded structure; and

,

within said portion of said second document, replacing said excluded structure with said replacement structure.

7. The method of claim 1, wherein said section comprises a plurality of segments, said method further comprising:

limiting at least a portion of said restricted structures identified within said exception markup document to particular ones of said segments as specified within said exception markup document.

8. The method of claim 7, wherein at least one of said segments is a structure.

9. The method of claim 1, wherein said exception markup document is disposed within said first markup document.

10. A system for providing exceptions for markup language documents comprising:

an exception markup document configured to specify at least one structure;

a container disposed within a portal, wherein said container is configured to receive content from a content source external to said portal;

a means for comparing structures contained within said content with structures specified within said exception markup document; and

,

an exception handler configured to perform an exception handling operation responsive to matches discovered by said comparing engine, wherein said exception handler prevents content specified within said exception markup document from being inserted within said container.

11. The system of claim 10, wherein said exception markup document further comprises:

a handling instruction associated with at least one structure specified within said exception markup document, wherein said exception handler performs at least one exception handling operation based upon said handling instruction.

12. The system of claim 10, wherein at least one structure specified within said exception markup is dependant upon a browser used to display said portal.

13. The system of claim 10, wherein said exception handler is configured to display a message responsive to matches discovered by said comparing engine.

14. A machine-readable storage having stored thereon, a computer program having a plurality of code sections, said code sections executable by a machine for causing the machine to perform the steps of:

identifying a section within a first markup document into which at least a portion of a second markup document is to be inserted;

identifying an exception markup document specifying structures restricted within said section;

searching said portion for at least one excluded structure specified within said exception markup document;

if no excluded structure is found by said searching step, inserting said portion into said section; and

,

if at least one of said excluded structures is found by said searching step, performing at least one exception handling operation.

15. The machine-readable storage of claim 14, wherein said first markup document is provided by a portal, wherein said section specifies a container, and wherein said second markup document includes content provided by a content source, wherein said content source is different from said portal.

16. The machine-readable storage of claim 14, wherein said exception handling operation comprises:

displaying a message indicating that restricted structures exist within said portion.

17. The machine-readable storage of claim 14, wherein said exception handling operation comprises the steps of:

deleting said excluded structure from said portion; and

,

inserting said portion within said section.

18. The machine-readable storage of claim 17, further comprising:

identifying an initializing location specifying the beginning of said excluded structure;

identifying a terminal location specifying the ending of said excluded structure;

identifying structure content contained between said initializing location and said terminal location; and

,

deleting at least a portion of said structure content.

19. The machine-readable storage of claim 14, further comprising:

identifying within said exception markup document a replacement structure associated with said excluded structure; and

,

within said portion of said second document, replacing said excluded structure with said replacement structure.

20. The machine-readable storage of claim 14, wherein said section comprises a plurality of segments, said method further comprising:

limiting at least a portion of said restricted structures identified within said exception markup document to particular ones of said segments as specified within said exception markup document.

21. The machine-readable storage of claim 20, wherein at least one of said segments is a structure.

22. The machine-readable storage of claim 14, wherein said exception markup document is disposed within said first markup document.