System and method of supporting "extrinsic" xml and "intrinsic" xml in text processor document

BACKGROUND ART

In recent years, markup languages ​​have achieved widespread popularity. One type of markup language, Extensible Markup Language (XML), is a universal language that provides a way to identify, exchange, and process various kinds of data. For example, XML is used to create documents that can be used by various application programs. Elements of an XML file have an associated namespace and schema.

In XML namespace is typically used to uniquely identify each document XML. Each XML document can use a namespace to allow processes to easily identify the type of XML, associated with the document. The unique namespaces may also help to differentiate markup elements that come from different sources and happen to have the same name.

XML Schema provides a way to describe and validate (check admissibility) data among XML. Scheme states what elements and attributes are used to describe content in an XML document, where each element is allowed, and which elements can appear within other elements. Using circuits ensures that the file is structured the same way. Diagrams can be created by the user and generally supported by an appropriate markup language such as XML. Using XML editor, which supports the circuit, the user can influence the XML file and generate XML documents, which adhere to the schema of the user.

XML documents can be created, adhering to one or more circuits. However, conventional mechanisms validation elements within an XML document against more than one schema become unacceptable in some situations.

If elements associated with the first circuit elements embedded in the second scheme, any "child" elements nested elements can not be checked for correctness with respect to the first circuit when both circuits are structured so as to accommodate each other. In other words, the existing mechanisms of validation can verify the correctness with respect to the scheme, only an element and its "daughter" elements, but not his "granddaughter" elements directly. Often, the "parent" element is the only one who can set the rules for their "child" elements. If the "daughter" element is in another scheme, the scheme "daughter" element shall refer to the "parent" scheme, if there is a need to insert a "grand" element in the "parent" scheme. In fact, there was no way to "subsidiary" scheme was "transparent" and let the "parent" element is to determine what would be "grand" element. Until now this restriction has created a problem for developers of tools markup language.

SUMMARY OF THE INVENTION

The present invention is directed at enabling validation of the document Extensible Markup Language (XML), having elements associated with two or more circuits, where elements of each schema may be arbitrarily nested within elements of the other circuits, and each set of elements remains correct (authentic) within his own schemes. The word processor is mainly due to him, or "native" (own), a scheme that corresponds to the "native" (own) XML. The document is generated according to the "native" XML, may include arbitrary elements, or "non-native" elements of XML, elements embedded in the "native" XML, and elements of the "native" XML, elements embedded in "non-native" XML. Elements of "non-native" XML word processor ignored when validating elements of the "native" XML file mixed XML. Elements of "non-native" XML checked for correctness separately using parallel tree XML, generated elements of "non-native" XML file within the mixed XML, and processing elements of the "native" XML as if they are "transparent".

The present invention allows the introduction of elements of the "non-native" XML, which have their own respective namespace elements of the "native" XML, which have other related namespace. Previously users to convert XML files into other formats for display or other functions. Previous editors of XML validation does not recognize (that is considered wrong) elements of the first namespace, elements embedded in the second namespace (if both related scheme is clearly not allowed namespace each other within itself). The present invention provides that the "native" XML enables you to implement other elements of the "non-native" XML elements in "native" XML in the same XML file, regardless of the fact as to whether the any of the XML schema is clearly the presence of interstitial elements. Remove items "native" XML from an XML file would have led to the fact that the document is correct in relation to the scheme of "non-native" XML, I had only a "non-native" XML. Accordingly, removing items "non-native" XML from XML files would lead to the fact that the document right in relation to the scheme of the "native" XML, has only a "native" XML. Accordingly, a single XML schema namespace "transparent" in relation to another XML schema namespace, so that the elements associated with each circuit can be checked for correctness, individually and separately.

To ensure the "transparency" elements "non-native" XML stored in a separate place called "parallel XML tree", when a document is created from the mixed XML file. Each node of the tree corresponds to an element XML namespace in a mixed file XML. Nodes are displayed at locations corresponding elements within the mixed XML file. Accordingly, when the XML file is saved, it retains elements and "native" XML, and "non-native" XML. The advantage of XML tree is that it can handle "non-native" XML separately from the "native" XML for validation in relation to the scheme of "non-native" XML while maintaining the position "non-native" XML within the "native" XML. The fact that "native" XML is considered "transparent" to the "non-native" XML, allows you to use and save the XML file is still as a single file.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 - shows an exemplary computing device that may be used in one exemplary embodiment of the present invention.

FIG. 2 - block diagram showing an exemplary environment for practicing the present invention.

FIG. 3 - shows an exemplary mixed XML file in accordance with the present invention.

FIG. 4 - shows an exemplary block diagram of an exemplary relationship between the mixed XML file and an exemplary parallel XML tree in accordance with the present invention.

FIG. 5 - the logical flowchart of an exemplary process for generating a mixed XML document in accordance with the present invention.

FIG. 6 - the logical flowchart of an exemplary process handling elements within a mixed XML document in accordance with the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENT

Throughout the specification and claims, the following terms have the meanings explicitly indicated below, unless the context clearly dictates otherwise value.

The terms "markup language" or "DM" refers to language for special codes within a document that specify how parts of the document are to be interpreted by the application. In a word processor file, markup elements may be associated with particular formatting that specifies how the content item should be displayed or taken. In other documents, such as other documents XML, the markup can be directed to the description of the data, without referring to the consideration of the display.

The terms "native" (own) Extensible Markup Language "or" native "(own) XML" refer to markup language elements that are associated with a word processor application and a schema associated with the word processor application.

The terms "non-native" (improper) Extensible Markup Language "or" non-native "(improper) XML" refer to markup language elements that have created the user or other applications that adhere to the scheme, the scheme differs from "native" XML.

The term "element" refers to the basic module XML document. The element may contain attributes, other elements, content, and other building blocks for an XML document creation.

The term "tag" refers to a command inserted in a document which describes the elements within a document XML. Each element usually has no more than two tags: the start tag and the end tag. There may be an empty element (with no content) in which case one tag is allowed.

The content between the tags is considered a "child elements" element (or "child elements"). Hence, other elements embedded in the element's content are called "child elements" or "child nodes" or the element. Text embedded directly in the content of the item is considered "child text nodes" item. However, "child" elements and the text within an element constitute the "contents" of the element.

The term "attribute" refers to an additional property set to a particular value and associated with the element. Elements may have an arbitrary number of parameters of the attribute associated with them, including the lack of options. Attributes are used to associate with an element of additional information, which does not include the content of the element.

Exemplary Operating Environment

Referring to FIG. 1, one exemplary system for implementing the invention includes a computing device, such as computing device 100. In a basic configuration, computing device 100 typically includes at least one processor 102 and system memory 104. Depending on the exact configuration and type of computing device, system memory 104 may be volatile (such as random access memory (RAM)), non-volatile (such as read only memory (ROM), flash memory, etc.) or some combination thereof. System memory 104 typically includes an operating system 105, one or more applications 106, and may include program data 107. In one embodiment, application 106 may include a word processor application 120 that further includes XML editor 122. This basic configuration is illustrated in FIG. 1 components within dashed line 108.

Computing device 100 may have additional features or functionality. For example, computing device 100 may also include additional data storage devices (removable and / or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in FIG. 1 as a removable storage 109 and non-removable storage 110. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, modules programs or other data. System memory 104, removable storage 109 and non-removable storage 110 - are all examples of computer storage media. Computer storage media include OD, ROM, electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disc (CD-ROM), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computing device 100, but is not limited thereto. Any such computer storage media may be part of device 100. Computing device 100 may also have input device (s) 112 of data entry such as a keyboard, mouse, pen, voice data input device, touch input device, etc. It may also include a device (s) 114 output, such as a display, speakers, printer, etc. These devices are well known in the prior art and development need not be discussed in detail.

Computing device 100 may also contain communication connections 116 that allow the device to communicate with other computing devices 118, such as over a network. Communication connection 116 is one example of communication means. Communication typically embodiment may be embodied as computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier, or may use other transport mechanism and includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. For example, and not as a limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared and other wireless media. It is believed that the term "computer readable medium" includes a storage medium and communication means.

File Structure Word Processors

FIG. 2 is a block diagram showing an exemplary environment for practicing the present invention. Exemplary environment shown in FIG. 2, is a word processor environment 200 that includes word-processor 120, mixed XML file 210, circuit 215 "non-native" XML, parallel XML tree 220, and means 225 XML validation. The mixed XML file 210 includes the "native" XML 211, and "non-native" XML 212.

In one embodiment, word-processor 120 has its own namespace and a set of schemas, that is defined for use with documents associated with word-processor 120. The set of tags and attributes that are defined by circuit for word processor 120 may determine the format of the document to such an extent he referred to his own markup language, "native" XML. "Native" XML is supported by word-processor 120 and may adhere to the rules of other markup languages ​​to create more of its own rules. "Native" XML provides a markup language, which includes a lot of information that is displayed and the user can use without having to spend time creating circuit according to the displayed information.

"Native" XML 211 and "non-native" XML 212 mixed 210 mixed file XML. In accordance with the present invention, elements of "non-native" XML 212 may be nested within elements of "native" XML 211 elements, and the "native" XML 211 can be nested within elements "non-native" XML 212. Accordingly, when word-processor 120 internally validates "native" XML File 210 211 mixed XML, process of internal validation at odds with elements of "non-native" XML 212. An exemplary mixed XML file 210 is described below in the discussion of FIG. 2.

Driving 215 "non-native" XML elements associated with "non-native" XML 212. When validation elements of "non-native" XML 212 examines as to whether they correspond to circuit 215 "non-native" XML. As previously described above, the circuit states what tags and attributes are used to describe the contents of the XML document, where each tag is allowed, and which tags can appear within other tags, ensuring that the document is structured in the same manner. Accordingly, the "non-native" XML 212 is correct, when it is structured as set forth in Scheme 215 "non-native" XML. Checking the "non-native" XML 212 is described further below in the discussion of FIG. 5.

Before checking the correctness of the elements of "non-native" XML 212 is stored in the parallel tree 220 XML. Parallel XML tree 220 is described below in the discussion of FIG. 4. Parallel XML tree 220 is transmitted by means of 225 XML validation to validate the "non-native" XML 212. Means 225 XML validation works like any other available means of validation for documents XML. Means 225 evaluates XML validation XML, which is a circuit structure 215 "non-native" XML. In one embodiment, a large number of validation means may be associated with word-processor 120 to verify a large number of markup language structures.

FIG. 3 illustrates an exemplary mixed XML file in accordance with the present invention. The mixed XML file 210 includes elements of "native" XML, and elements of the "non-native" XML. An element in a markup language usually includes an opening tag (indicated by "<" and ">"), some content, and a closing tag (indicated by "</" and ">"). It is believed that the tags associated with the "native" XML, namespace associated with a word processor. In contrast, the tags that are associated with the "non-native" XML, referred to as associated with a different namespace, in this example the namespace "resume" (summary). The elements of mixed XML document 210 may further include content. For example, a "Work" (work) is contained in a "objective" (target), and the element of "123 Main" (page 123) is contained in a "street" (street). Element "address" (e) includes an element of "street". These elements are determined according to the scheme "non-native" XML, the appropriate namespace "resume" (for example, the scheme "resume"), which was previously provided by the user or by another application.

In the study of the mixed XML file 210 This file includes elements of "non-native" XML, elements embedded in the "native" XML, and elements of the "native" XML, elements embedded in "non-native" XML. Accordingly, when the mixed XML file 210 internally checked for correct word processor or tree is passed as the validation, the application checks the correctness of the mixed XML file 210, is in conflict with nested elements, which correspond to two different schemes. Depending on the rules relating to the application that checks the validity of mixed file 210 XML can be unacceptable if the scheme is "non-native" XML is not allowed for the "native" XML. For example, if the mixed image 210 XML has been completely sent to another facility validate XML, the file would probably be defined as invalid. XML schema does not typically allow the elements of one namespace elements were embedded in the second namespace. In one embodiment, the present invention overcomes this limitation through a scheme of "native" XML, coupled with a word processor that allows you to put any elements related to another scheme "non-native" XML. An exemplary process of obtaining the correct (allowable) mixed XML file is described further in the discussion accompanying FIG. 5 and 6.

FIG. 4 shows a block diagram of an exemplary relationship between exemplary mixed XML file and an exemplary parallel XML tree in accordance with the present invention.

Parallel XML tree 220 is generated as word-processor 120 (shown in FIGS. 1 and 2) creates a document internally checking the correctness of the mixed XML file 210. Internal validation allows word-processor 120 to evaluate each element according to its own set of rules. When the item "non-native" XML conflicts, being embedded in the element of "native" XML, within the parallel XML tree 220 is generated by the node (eg, 402), which corresponds to this element. Assembly position in a parallel XML tree 220 is determined by the position of the corresponding element in the mixed XML document 210 relative to other elements. Accordingly, each element of "non-native" XML mixed XML file 210 is represented by a node (e.g., 402) of parallel XML tree 220. Direct "parent-child" relationship is established between the elements of XML, presented in the parallel tree 220 XML, some of which may have originally existed in a mixed XML file 210 because the intermediate marking the "native" XML. An exemplary process associated with generation of an exemplary tree of nodes 220 "non-native" XML, described below with reference to FIG. 6. Parallel tree 220 XML allows word-processor 120 is essentially ignore the elements of "non-native" XML, when it internally checks the validity of the mixed file 210 XML. Parallel XML tree 220 can then be checked for correctness separately from mixed XML file 210, as described below with reference to FIG. 5.

TREATMENT OF MIXED ELEMENTS XML file

FIG. 5 - the logical flowchart of an exemplary process for generating a mixed XML document in accordance with the present invention. Process 500 begins at step 501, where a mixed XML file has been previously generated by the user application word processing, such word-processor 120 shown in FIG. 1. Processing continues at block 502.

In step 502 processing element of the mixed XML file. When processing each element of a determination whether the item is part of "native" XML element or "non-native" XML. How each element is handled depends on the type of element. When the element is a "non-native" XML, node corresponding to that element is inserted into the parallel XML tree, as further described with reference to FIG. 6. An exemplary process for handling each element is described below with reference to FIG. 6. Once the element is processed, the process proceeds to step 503 decision.

In step 503, a determination decision whether each of the elements treated, which includes the mixed XML file. Each element has been processed, when the word processor has reached the last closing tag of the mixed XML file when you create a document from a mixed file XML. If further elements have not yet been processed, then processing returns to step 502 and begins processing further elements. If all elements have been processed, processing continues at step 504.

In step 504 is validated parallel XML tree. The parallel XML tree is transmitted using a word-processor XML validation means, means 225 which is similar to XML validation, FIG. 2. Means XML validation engine operates in such a way that it explores the parallel XML tree in accordance with a related circuit, which is similar to circuit 215 "non-native" XML, as shown in FIG. 2. Associated circuit determines which tags and attributes are used to describe the contents of the document in the resulting XML, where each tag is allowed and what elements can appear in other elements. The parallel XML tree is correct when it adheres to the associated schema. Once the parallel XML tree is verified to be correct, processing continues at step 505.

In step 505 a word processor document is generated corresponding to the mixed XML file. In one embodiment, the document is formatted according to the scheme of "native" XML, provided by the word processor, and it displays the tags associated with items "non-native" XML mixed XML file. Processing continues at step 506 where the process ends.

In one embodiment, process 500 may vary as a result of internal validation "native" XML validation or "non-native" XML. For example, the process may determine that either "native" XML, or "non-native" XML unacceptable. As a result, the process 500 may be interrupted, may return an error message, the program can be launched to assist in the correction of XML and can be activated additional operations.

FIG. 6 is a logic flowchart of an exemplary process handling elements within a mixed XML document in accordance with the present invention. Process 600 begins at block 601 when process 500 shown in FIG. 5, proceeds to step 502. Processing continues at step 602.

In step 602, a determination is made whether the handling unit element "native" XML element or "non-native" XML. Item type can be determined by examining the opening tag of each element. The opening tag of each element includes a reference to the schema that corresponds to that element (see. FIG. 3). Each circuit is connected or "native" XML, or "non-native" XML. Once the type of element is determined, the process proceeds to step 603 decision.

In step 603, a decision determining whether an item is an element of "non-native" XML. As indicated above, each element is handled differently depending on the type of element. If the element is an element of "non-native" XML, processing continues at step 604.

In step 604, the element is processed in accordance with the "native" (own) format word processor (such as "native" XML). In one embodiment, the word processor provides its own internal validation elements within its own format. In other words, the processor does not need to seek a means to validate an XML validation elements appropriate to the "native" format (such as "native" XML). Recognizing the elements of his "native" format, as valid or not, word processor can create a document corresponding to these elements, while the process continues. Once the element of "native" XML is processed according to the "native" XML, processing continues at step 607 where the process returns to step 503 in FIG. 5. However, if the element is "non-native" XML, processing continues to step 605.

In step 605, in a parallel XML tree node is created that matches the opening-tag or attribute element "non-native" XML. The parallel XML tree is examined for correctness using the validation XML. XML validation tool determines whether the sticks parallel XML tree related schemes "non-native" XML. By generating and separately checking the correctness of the parallel XML tree, the present invention includes functionality for checking the correctness of the mixed XML document, which has the elements associated with two or more circuits, wherein the elements of each schema may be arbitrarily nested within each other. Once the node is created in the parallel tree, processing continues at step 606.

In step 606, the element "non-native" XML is displayed on the node created in the parallel tree. In one embodiment, a placeholder is associated with each element within the mixed XML file. Placeholder for each node determines the position of each element of "non-native" XML file within the mixed XML. Displayed items "non-native" XML to their respective nodes allows to create and / or used by the user to set a precise elements within the resulting document XML. Once the element "non-native" XML is displayed on the node, processing continues at step 506 where the process returns to step 503 in FIG. 5.

In one embodiment, the relevant sections of the same mixed XML file may include multiple circuit "non-native" XML. Generated parallel tree XML, where each element corresponding to each of the schemes "non-native" XML, corresponds to a node. In this case, when the parallel XML tree is validated, the elements of "non-native" XML, corresponding to each circuit are checked for correctness, as if each relevant section of the same mixed XML file is actually a separate file XML. However, if multiple circuit "non-native" XML link to each other, it may result in that the elements are mixed.

The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention may be made without departing from the spirit and form of the invention, the invention is defined by the appended claims.