US2008082634A1PendingUtilityA1

Selecting a dtd for transforming malformed layout expressions into wellformed ones

Assignee: NETSCAPE COMM CORPPriority: Sep 29, 1998Filed: Oct 5, 2007Published: Apr 3, 2008
Est. expirySep 29, 2018(expired)· nominal 20-yr term from priority
Inventors:Rick Gessner
G06F 40/10G06F 40/143
46
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A network client such as a world wide web browser and corresponding method that includes and involves a scanner component that accesses an input content stream via a network connection (e.g., such as via a URL, etc.) to extract renderable content therefrom, a parsing component coupled to the scanner component for parsing the renderable content, and a replaceable document type definition component configured to control the parsing component based on a particular document type definition corresponding to a particular grammar. The replaceable document type definition component being replaceable during execution of the network client. The network client and its corresponding method may be used within a data processing system to receive and manifest content based on a document type definition that is not otherwise known prior to execution and run time of the network client.

Claims

exact text as granted — not AI-modified
1 . A method of rendering content received over a network comprising: 
 receiving, over a network, first content provided by a first content source, the first content being defined using a first syntax;    identifying first syntax data indicating the first syntax used to define the first content;    identifying, based on the identified first syntax data, first data configured for use in rendering content defined using the first syntax;    accessing the first data configured for use in rendering content defined using the first syntax;    rendering a display of the first content using the accessed first data configured for use in rendering content defined using the first syntax;    receiving, over the network and subsequent to rendering the display of the first content, second content provided by a second content source, the second content being defined using a second syntax that is different than the first syntax such that the second content is not properly rendered using the accessed first data;    identifying second syntax data indicating the second syntax used to define the second content;    identifying, based on the identified second syntax data, second data configured for use in rendering content defined using the second syntax;    accessing the second data configured for use in rendering content defined using the second syntax; and    rendering a display of the second content using the accessed second data configured for use in rendering content defined using the second syntax.    
     
     
         2 . The method of  claim 1  wherein: 
 accessing the first data configured for use in rendering content defined using the first syntax comprises accessing, from electronic storage, the first data configured for use in rendering content defined using the first syntax; and    accessing the second data configured for use in rendering content defined using the second syntax comprises receiving, over the network, the second data configured for use in rendering content defined using the second syntax.    
     
     
         3 . The method of  claim 1  wherein accessing the second data configured for use in rendering content defined using the second syntax comprises receiving, over the network and during runtime of a web browsing application performing the operations of rendering the display of the first content and rendering the display of the second content, the second data configured for use in rendering content defined using the second syntax.  
     
     
         4 . The method of  claim 3  wherein the second data configured for use in rendering content defined using the second syntax is unknown to the web browsing application prior to runtime of the web browsing application.  
     
     
         5 . The method of  claim 4  wherein the first data configured for use in rendering content defined using the first syntax is known to the web browsing application prior to runtime of the web browsing application.  
     
     
         6 . The method of  claim 1  wherein: 
 identifying the first data configured for use in rendering content defined using the first syntax comprises selecting, based on the first content defined using the first syntax, a first data file from among multiple data files configured for use in rendering content defined using particular syntaxes; and    identifying the second data configured for use in rendering content defined using the second syntax comprises selecting, based on the second content defined using the second syntax, a second data file from among the multiple data files configured for use in rendering content defined using particular syntaxes.    
     
     
         7 . The method of  claim 1  wherein: 
 accessing the first data configured for use in rendering content defined using the first syntax comprises accessing a first document type definition, and    accessing the second data configured for use in rendering content defined using the second syntax comprises accessing a second document type definition that is different than the first document type definition.    
     
     
         8 . The method of  claim 1  wherein the first syntax used to define the first content is the hyper-text markup language.  
     
     
         9 . The method of  claim 1  wherein the first syntax used to define the first content is the extensible markup language.  
     
     
         10 . The method of  claim 1  further comprising: 
 determining whether the second context is not properly rendered using the accessed first data, wherein    accessing second data configured for use in rendering content defined using the second syntax is conditioned on determining that the second context is not properly rendered using the accessed first data.

Join the waitlist — get patent alerts

Track US2008082634A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.