Patents
Literature
Hiro is an intelligent assistant for R&D personnel, combined with Patent DNA, to facilitate innovative research.
Hiro

109 results about "XSLT" patented technology

XSLT (eXtensible Stylesheet Language Transformations) is a language for transforming XML documents into other XML documents, or other formats such as HTML for web pages, plain text or XSL Formatting Objects, which may subsequently be converted to other formats, such as PDF, PostScript and PNG. XSLT 1.0 is widely supported in modern web browsers.

Extending the capabilities of an XSL style sheet to include components for content transformation

Systems and methods consistent with the present invention use a Namespace paradigm to define an external component reference to a style sheet. When the style sheet processor processes the tags in the style sheet, it recognizes the external component declaration. The style sheet will contain a name of the external component instance and a definition of the method to execute associated with the external component instance, and may contain arguments for the method associated with the external component instance which is executing. The XSLT processor then relinquishes control to the external component to execute the method defined in the style sheet. The results of the method's execution may be placed in the transform document generated by processing the style sheet. However, this is not required and other results may be generated, including those not related to the transform document.
Owner:ORACLE INT CORP

Method, computer program and system for style sheet generation

Device-type-specific XSLT style sheets (or equivalent) are generated from page layout files or "presentation skeleton' files which define a Web page layout including abstract component references that can be mapped to complex, device-specific or repeated style sheet components and are more easily constructed than XSLT style sheets. The presentation skeleton files use and extend existing mark-up languages. One presentation skeleton file can be used to generate XSLT style sheets for many devices that use the same mark-up language. In addition, presentation skeleton files can be produced directly from storyboard files to demonstrate Web sites statically before constructing them for real. This provides a route from initial Web site design to final implementation for multiple output devices.
Owner:IBM CORP

Creating mapping rules from meta data for data transformation utilizing visual editing

A visual editor creates the meta rules for transforming or mapping data between the source meta data and target meta data representation via a wide variety of Graphical User Interfaces (GUIs). A set of transformation rules or scripts is generated by the editor using a transformation rule engine, e.g., XSL, and sent to a standard transformation engine, e.g., XSLT, which accepts an input data file and using the transformation rules generates a transformed output data file. The meta rules are represented in a template and stored in a configuration file. The configuration file can be updated with other rules by the visual editor specifying in the rule file the transformation/mapping language as an element of the rule file. The editor specifies any attributes or parameters on the rule transformation/mapping element. The transformation rule engine reads in a new meta rule generated by the editor. Parameter values are added to complete the rule based on the description from a meta rule configuration file. A locking mechanism in the template is selected to lock the context to the template or portion of the rule definition selected at the time the lock is clicked. The new transformation/rule is saved into the transformation rule file. An editor-mapping engine generates a notification of the creation of a new transformation-mapping rule; updates the meta data rules file; and provides the updated rule file to the transformation engine. Input data to the transformation engine is processed using the updated rule file and the transformed data is provided as an output.
Owner:IBM CORP

Computer directory system having an application integration driver infrastructure

An application integration driver infrastructure for facilitating the use of a distributed directory running in a computer network is provided. The infrastructure can transform specific directory events into a vendor-neutral data identification system and then use vendor-neutral transformation technologies to transform the neutral data identification into a specific application's data format, and vice-versa. The infrastructure receives an event from the distributed directory into a markup language generation system, such as an extensible markup language (“XML”) generator. The XML generator converts the event into XML data and provides the XML data to a transformation processing system, such as an extensible transformation language (“XSLT”) processor. The XSLT processor transforms the XML data to a predetermined format. The format can be dictated by a stylesheet provided to the XSLT processor, the stylesheet being responsive to requirements of a computer application. The transformed data is then provided to the application for the application to use in a conventional manner. The application may use an application shim to convert the transformed data into a native application program interface (“API”) for the application.
Owner:EMC IP HLDG CO LLC

Internet document services

A subscriber service for on-line document editing includes an Internet client in which a browser window is opened to begin XHTML editing, e.g., in Microsoft INTERNET EXPLORER. The text is transmitted to a host in a message over the Internet. In the host, a next process verifies this user has an account, or is otherwise authorized to use this site or access a particular document. A process receives the mal-formed XHTML typical of Microsoft INTERNET EXPLORER editing. A process cleans up this input, and converts it to fully formed XML, e.g., with TIDY freeware. A next process uses XSLT style sheets to transform the XML to LaTex source. Alternatively, the input is converted to Tex-type source lines. Another process includes a LaTex engine to typeset the input text according to the style sheets. Such produces a DVI-type output file. A next process converts the DVI to PDF. Commercial programs are available for this purpose. A process transmits the completed PDF file back to the client in a message. A next process at the client receives the PDF-formatted document. A further process allows such document to be printed at convenience. A final process notes the subscriber account at the host to track subscription charges and uses.
Owner:WARNOCK KEVIN L
Who we serve
  • R&D Engineer
  • R&D Manager
  • IP Professional
Why Eureka
  • Industry Leading Data Capabilities
  • Powerful AI technology
  • Patent DNA Extraction
Social media
Try Eureka
PatSnap group products