Native XML printer

[0001] This application claims the benefit of priority from co-pending provisional patent application Serial No. 60/345,389, filed on Jan. 4, 2002, entitled XML Printer Technology, and also claims the benefit of priority from co-pending provisional patent application Serial No. 60/341,427, filed on Dec. 17, 2001, entitled Bar Code Labeling Systems Having Machine Readable Standards. Provisional patent application Serial No. 60/345,389 and Serial No. 60/341,427 are incorporated herein by reference in their entirety.

[0002] A portion of this disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office Patent files or records, but otherwise reserves all copyright rights whatsoever.

[0003] The present invention relates generally to a method and apparatus for printing bar code labels and more specifically to a native printer that prints bar code labels based on an XML data stream.

[0004] Printer systems for printing barcodes and for transmitting data to a barcode printer are known. However, many such systems use proprietary methods of data encoding, and therefore such methods cannot be used interchangeably with other barcode printers. Also, known data encoding methods typically render the underlying data unreadable by humans. While this presents no impediment to the computer systems, it may be burdensome to humans attempting to review, debug or understand certain data appearing in the underlying barcode element names.

[0005] Barcode labeling is used extensively in many facets of commerce. In particular, packages or merchandise shipped from one destination to another are identified by the shipper by a specific barcode label. Conversely, merchandise received may also be identified and entered into the receiver's inventory system by use of the barcode label. Often, the receiver of merchandise may dictate the form and content of the barcode applied by the shipper. This is referred to as compliance labeling. Of course, merchandise need not be shipped to avail itself of the benefits of barcode labeling. For example, inventory control systems make extensive use of barcode labeling to track and monitor various goods within a facility or between facilities.

[0006] Compliance labeling is typically used by buyers of merchandise having relatively large market power or purchasing power. Because of their economic power, they may be able to dictate the form and content of the barcode labels applied to products provided to them by their suppliers or vendors. Although this may be burdensome to the supplier, if the supplier desires to do business with the buyer, they must comply with their demands with respect to labeling. For example, large retailers, such as Wal-Mart, Inc., not only have the ability and purchasing power to require that suppliers meet their compliance labeling demands, but may also fine suppliers who fail to comply with the labeling requirements.

[0007] Further, such barcode labeling requirements may change at the whim of the entity demanding compliance. Accordingly, the supplier must implement the new labeling requirements and test the modified barcode to insure that it meets all specifications. This is relatively inefficient and time consuming. It is also prone to errors, which may translate into monetary fines.

[0008] A need exists to provide an open standard for defining barcode labeling information that is self-validating and which does not require significant software programming changes to implement a change in form or content of a barcode label. A need also exists for use of a format in which to provide data to a barcode printer where the data is understandable by a human reading the data.

[0009] The features of the present invention which are believed to be novel are set forth with particularity in the appended claims. The invention, together with further objects and advantages thereof, may best be understood by reference to the following description in conjunction with the accompanying drawings.

[0010] FIG. 1 is a high-level hardware block diagram of a specific embodiment of a printer system according to the present invention;

[0011] FIG. 2 is a high-level software block diagram of a specific embodiment of a printer system;

[0012] FIG. 3 is a combined high-level software block diagram and data flow diagram of a specific embodiment of a printer system;

[0013] FIG. 4 is a high-level software block diagram of a specific embodiment of a bitmap/barcode rendering engine;

[0014] FIG. 5 is a specific representation of a barcode label produced in accordance with the printer system of FIGS. 1-4; and

[0015] FIG. 6 is a specific example of an alternate embodiment of a printer system configured as a barcode rendering server.

[0016] In this written description, the use of the disjunctive is intended to include the conjunctive. The use of definite or indefinite articles is not intended to indicate cardinality. In particular, a reference to the object or thing or an object or a thing is intended to also describe a plurality of such objects or things.

[0017] Referring now to FIG. 1, a specific embodiment of a high-level hardware block diagram of an XML printer system 10 is shown generally. The XML printer system 10 includes a computer or processing system 12, which includes various hardware components, such as RAM 14, ROM 16, hard disk storage 18, cache memory 20, database storage 22, and the like (also referred to as memory subsystem 26), as is known in the art. The computer system 12 may include any suitable processing device 28, such as a computer, microprocessor, RISC processor (reduced instruction set computer), CISC processor (complex instruction set computer), mainframe computer, work station, single-chip computer, distributed processor, server, controller, micro-controller, discrete logic computer and the like, as is known in the art. For example, the processing device 28 may be an Intel Pentium microprocessor, x86 compatible microprocessor, or equivalent device.

[0018] A user interface 30 may be coupled to the computer system 12 and may include various input devices 36, such as switches selectable by the user and/or a keyboard. The user interface also may include suitable output devices 40, such as an LCD display, a CRT, various LED indicators and/or a speech output device, as is known in the art.

[0019] To communicate between the computer system 12 and external sources, a communication interface 42 may be operatively coupled to the computer system. The communication interface 42 may be, for example, a local area network, as an Ethernet network, intranet, or other suitable network 43. The communication interface 42 may also be connected to a public switched telephone network (PSTN) 46 or POTS (plain old telephone system), which may facilitate communication via the Internet 44. Dedicated and remote networks may also be employed. Any suitable commercially available communication device or network may be used, as is known in the art.

[0020] The computer system 12 is further coupled to a printer system 50. The printer system 50 may include a media/paper control system 52, a printer driver 54 and a print head mechanism 56. Any suitable printer capable of printing barcode labels may be used, which may include various dot matrix, ink jet, laser and/or thermal printers. Of course, dot matrix printers are usually of lower quality and require closer monitoring of the label output. Preferably, the printer system 50 is a thermal transfer printer. Such suitable printers, for example, are available from Zebra Technologies Corporation of Vernon Hills, Ill., and may include the Model Xi series barcode printers (XiIII, 90XiIII, 96XiIII, 140XiIII, 170XiIII, 220XiIII, etc.), the 2800 Series barcode printers, Model Z4M, Z6M, 105SL barcode printers, and others. Any suitable barcode label printer may be used.

[0021] Typically, such printers may include various motors, label cutters, ribbon handlers, sensors, and the like (not shown). Additionally, such printers may include various control inputs or sensors, such as a media sensor, print head temperature sensor, head open sensor, ribbon sensor, and the like (not shown), as is known in the art. The printer system 50 may include one or more additional processors 60, other than the processor 28 residing in the computer system 12. Alternatively, the processor 28 in the computer system 12, if sufficiently powerful, may control and handle the printer system 50 functions without the need for a separate processing device.

[0022] Preferably, the computer system 12 and the printer system 50 are located in a common enclosure, but need not necessarily be constructed in this manner. For example, the computer system 12 may be housed in an enclosure separate and apart from the printer system 50.

[0023] Referring now to FIGS. 1-3, FIG. 2 illustrates a specific embodiment of a high-level software block diagram, while FIG. 3 illustrates a specific embodiment of a combined high-level software block diagram and data flow diagram. The software described below may be executed by the processor 28 of the computer system 12 of FIG. 1. Again, the processor 28 may perform functions common to both the computer system 12 and the printer system 50. There may be one or more processors, which may function in concert or which may function separately. It is not material to the scope of this invention whether the processing or processing functions are performed by or in the computer system or by or in the printer system.

[0024] The software blocks illustrated in FIGS. 2-3 include an XML (extensible mark-up language) processor 70 (also referred to as the XML parser), an XSLT (extensible stylesheet language transformation) processor 74, an XSLFO (extensible stylesheet language formatting object) processor 78, a barcode rendering engine 80 (also referred to as the bitmap/barcode rendering engine), and the printer driver 54 (FIG. 1). Note that the printer driver 54 is an example of a component described above whose function may be performed by either the processing device in the computer system 12 or the processing device 60 (FIG. 1) in the printer system 50, depending upon the physical location of the associated processing device. Again, a single processing device, if sufficiently powerful, may handle all functions for the XML printer system 10.

[0025] An XML schema repository 82 (schema repository) may provide input to the XML processor 70 while an XSLT stylesheet repository 84 (stylesheet repository) may provide input to the XSLT processor 74. Also shown is an enterprise resource planning (ERP) system 88, which may be, for example, a warehouse management system that transmits an XML input data stream 90 to the XML processor 70. The ERP system 88 essentially initiates the request to print the barcode label, and provides the XML data that forms the bar code and other variable label or element fields to be printed. Such variable label fields may include, for example, any or all of the human-readable text and/or characters printed on the label. Of course, any enterprise computer system may be used, and this invention is not limited to use with any specific type of enterprise computer system.

[0026] When referring to the XML data, two basic types shall be referred to herein, namely, the XML value data and the XML element name. The XML value data is the changeable data or the data that is desired to be printed on the barcode label, such as the data 1122 Green Street, which may be part of the XML value data corresponding to, for example, a shipping address. The XML element names are part of the XML language semantics where an arbitrary label or element name may be selected to represent the XML value data, the use of which is defined by the XML language. Typically, the element names appear between angled bracket (<element name>).

[0027] As described above, known barcode label systems often use proprietary software encoding schemes. Additionally, such schemes are often prone to errors, and the underlying value data is usually unreadable by a non-technical individual. In known systems, if an error exists in the underlying value data sent from the enterprise system, or if the data is missing or otherwise incorrect, the barcode printer will print what it is instructed to do, which of course, produces an error in the barcode label, rendering it inaccurate or useless.

[0028] Moreover, when dealing with compliance labeling, known systems require non-trivial changes in the data encoding when the form or content of the label changes in accordance with the compliance label demands. Such changes in the form or content of the barcode, again, are susceptible to errors, which in turn can lead to monetary fines by the entity demanding compliance. Business relationships may also be damaged by continued problems in the barcode labeling system, especially if such errors disrupt the business of the compliance demander.

[0029] The present XML printer system 10 utilizes an open format. In particular, the formatting requirements and the form of the barcode label are all defined in the XML language. Moreover, not only is XML well defined and available for all to use, but non-programmers can understand the data and commands in an XML data stream or file (or hard copy) with minimal training.

[0030] Various XML software blocks shown in FIGS. 2-3 are commercially available. Several different commercially available XML processors 70 may be used interchangeably or with little modification. For example, the following commercially available XML processors 70 may be used: XML for C available from IBM Corporation, MSXML3 available from Microsoft Corporation, Oracle XML Developers Kit for C available from Oracle Corporation, Expat available from Thai Open Source Software Center, Ltd., or Xerces-C available from the Apache Software Foundation. However, any suitable XML processor may be used.

[0031] Similarly, several different commercially available XSLT processors 74 may be used interchangeably or with little modification. For example, the following XSLT processors 74 may be used: iXSLT available from Infoteria Corporation, MSXML3 available from Microsoft Corporation, and Libxslt available from Gnome. However, any suitable XSLT processor may be used.

[0032] Again, several different commercially available XSLFO processors 78 may be used interchangeably or with little modification. For example, the following XSLFO processors 78 may be used: XEP available from RenderX Corporation, XSL Formatter available from Antenna House Corporation, and FOP available from the Apache Software Foundation. However, any suitable XSLFO processor may be used.

[0033] Still referring to FIGS. 1-3, the XML processor 70 receives the XML input data stream 90 from an external source 88. For example, the external source may be the ERP system 88, such as the warehouse management system. The XML processor 70 is essentially parses and processes the XML input data stream 90 and generates a set of nodes, which may be in a tree structure, as is known in the art. Each of the software processing blocks shown in FIGS. 2-3 act on the nodes of the tree to perform their required function. The underlying value data contained in the XML input data stream 90 from the ERP system 88 is processed and entered into a label values node tree, 100 which holds the data.

[0034] The following is a brief overview of the operation of the various software components. First, note that the XML input data stream 90 includes text that identifies the name and location of other required XML documents or files. One such document is referred to as XML schema or schema. The schema is used to validate the XML input data stream, including the underlying value data. If validation is successful, a stylesheet is applied, as will be described below. The name and location of the stylesheet is also specified in the XML input data stream 90. Application of the stylesheet is handled by the XSLT processor 74, which under the direction of the stylesheet, may transform the underlying XML element names and/or underlying value data. Next, the data is processed by the XSLFO processor 78, which handles formatting and layout of the underlying value data, which may include, for example, formatting the underlying value data in accordance with, for example, font type, font size, color, and the like. Next, the underlying value data is processed by the bitmap rendering engine 80, which creates a bitmap 92 of the barcode label corresponding to the transformed and formatted data. The bitmap rendering engine 80 may utilize an instream foreign object residing in the stylesheet to direct creation of the bitmap. The bitmap 92 is then sent to the printer driver 54 (FIG. 1) for subsequent printing of the barcode label by the barcode printer.

[0035] As described above, the schema functions to validate the entire input data stream 90, in particular, the underlying value data, where errors may be typically found. In practice, errors are often inadvertently introduced when changes are made to the form or content of the bar code label.

[0036] The name and location of the schema document is contained in the XML input data stream 90, which XML input data stream corresponds to the request to print a barcode label. The XML processor 70 in conjunction with a schema validation module 110 validates the underlying value data. The use of schema is cost effective because it prevents errors and omissions with respect to the final output, namely, the bar code label or shipping label.

[0037] If the XML input data stream 90 is rejected or flagged as having an error, an error message may be transmitted back to the source 88. This may flag or trigger human intervention to correct the error. For example, in this specific example, the source is the ERP system 88. In this way, the data is initially checked prior to processing to insure that it complies with all required label and barcode rules.

[0038] This may be particularly beneficial when dealing with compliance labeling. In known systems, the compliance demander would merely notify the supplier as to the changes in the compliance labeling requirements. If the supplier then makes an error in interpreting or implementing these changes or instructions, the labels produced and applied to products shipped to the compliance demander may have errors, which could jeopardize future business or cause monetary fines to be applied.

[0039] In the present invention, the compliance demander preferably makes the changes directly to the schema and/or the XSLT stylesheet. For example, if the physical layout of the label has been changed or if element names have been changed, the compliance demander will modify the XSLT style sheet. Similarly, if the underlying value data has been added or deleted or otherwise qualified (i.e., a new acceptable numerical range for a zip code), the compliance demander may modify the schema. In this way, the supplier need only modify the output of its ERP system 88 to ensure that it matches the modified XML input data stream 90. If only the physical layout of the label has changed, the supplier does not need to make any modifications at all.

[0040] For example, the compliance demander may now require that a nine digit zip code be used rather than the original five digit zip code. Accordingly, the compliance demander will modify the schema to require both a first and second zip code field, and the second field will also be limited to numerical digits within a certain range, perhaps 0000-9999. The compliance demander may also modify the stylesheet to accommodate that change. In response thereto, the supplier must insert the added zip code field in its ERP system so that it appears in the XML input data stream 90 sent to the XML printer system 10. If such modification of the XML input data stream 90 is not performed correctly, the schema will cause an error to be reported back to the ERP system 88, and the label will not be printed.

[0041] Thus, the supplier need only access the modified schema and/or stylesheet from the repository 82, 84, which is automatically applied to the underlying value data when received. Essentially, minor changes, and significantly, major changes, to the form and content of the barcode label are transparent to the supplier, and such changes to the content of the barcode label are validated in accordance with the schema. Accordingly, the supplier need not incur costs to change the form or content of the barcode label dictated by the compliance demander, and cannot make any errors in implementing such changes. If there are any errors, such errors would have been inadvertently made by the compliance demander, who could not then blame the supplier.

[0042] The schema documents are preferably obtained from the XML schema repository 82. In one specific embodiment, the schema repository 82 may be external to the XML printer system 10 and the computer system 12, and may be accessed via the network, the Internet, or via any suitable network 43, 44 to which the computer system is coupled. The schema repository 82 may contain a plurality of schema documents. Thus, the XML input data streams 90 representing the various requests to create a barcode label may each specify the name and location of the corresponding schema in the repository 82. When the request is received by the XML processor 70, the corresponding schema may be retrieved from the schema repository 82.

[0043] In another embodiment, the schema obtained from the schema repository 82 via the network 42, 43 may be kept locally, and thus may temporarily reside in the memory subsystem 26 (FIG. 1), such as the hard disk 18 or database 22. In this way, if the same schema is used for multiple XML input data streams 90 or for subsequent barcode label requests, the XML processor 70 need not retrieve the same schema externally via the network 42, 44, but rather, may retrieve that schema from the memory subsystem 26, which may be more efficient. According to this embodiment, the compliance demander may change or modify the schema in the external repository 82 at only certain times. For example, the compliance demander may change the stylesheet only at 1:00 AM each day. Thus, the supplier need only update the schema from the repository 82 into the memory subsystem 26 only once per day, for example, after the compliance demander has performed the schema update. The supplier would then know that the schema saved temporarily in the memory subsystem 26 is the most recent schema document, at least up until the time that the updating is scheduled to occur.

[0044] Regardless of the location from where the schema is obtained, the schema validation module 110 performs the checking and validation of the underlying data. Although the schema validation module 110 is shown as a separate block from the XML processor 70 in FIG. 2, it is shown in this location for purposes of illustration only so that it may be shown on the drawing adjacent to the label values node tree 100, which is the data upon which it acts. However, the schema validation module 110 may be part of and integrated into the XML processor 70, or it may be a separate and apart therefrom.

[0045] Of course, the schema is also an XML document, and thus it is also processed by the XML processor 70. Accordingly, the result of the processing of the schema is the XML schema node tree 114 shown in FIG. 3, which is the memory representation or working model of the schema that was processed. The XML schema node tree 114 may be in the form of a document object model (DOM), as is known in the art. Further, the XML schema node tree 114 may reside in cache memory for efficiency, as shown in an XML schema cache 116. The schema validation module 110 and/or the XML processor 70 operate on the data in the XML schema node tree 114 to perform its function of validating the underlying value data in accordance with the schema document.

[0046] As described above, if an error exists in the XML input data stream 90, as determined by application of the schema, an error message may be generated. If the XML input data stream 90 is validated, the data remains essentially untouched. The data in the label value node tree 100 is then processed by the XSLT processor 74 using the XSLT stylesheets.

[0047] The stylesheet documents are preferably obtained from the XSLT stylesheet repository 84. In one specific embodiment, the stylesheet repository 84 may be external to the XML printer system 10 and the computer system 12, and may be accessed via the network, the Internet, or via any suitable network 43, 44 to which the computer system is coupled. The stylesheet repository 84 may contain a plurality of stylesheets. Thus, XML input data streams 90 representing the various requests to create a barcode label may each specify the name and location of the corresponding stylesheet in the repository 84. When the request is received by the XML processor 70, the corresponding stylesheet may be retrieved from the stylesheet repository 84.

[0048] In another embodiment, the stylesheet obtained from the stylesheet repository 84 via the network 43, 44 may be kept locally, and thus may temporarily reside in the memory subsystem 26 (FIG. 1), such as the hard disk 18 or database 22. In this way, if the same stylesheet is used for multiple XML input data streams 90 or for subsequent barcode label requests, the XML processor 70 need not retrieve the same stylesheet externally via the network 43, 44, but rather, may retrieve that stylesheet from the memory subsystem 26, which may be more efficient.

[0049] According to this embodiment, the compliance demander may change or modify the stylesheet in the external stylesheet repository 84 at only certain times. For example, the compliance demander may change the stylesheet only at 1:00 AM each day. Thus, the supplier need only update the stylesheet from the stylesheet repository 84 into the memory subsystem 26 only once per day, for example, after the compliance demander has performed the stylesheet update. The supplier would then know that the stylesheet saved temporarily in the memory subsystem 26 is the most recent stylesheet, at least up until the time that the updating is scheduled to occur.

[0050] Of course, the stylesheet is also an XML document, and thus it is also processed by the XML processor 70. Accordingly, the result of the processing of the stylesheet is the XSLT stylesheet node tree 120 shown in FIG. 3, which is the memory representation or working model of the stylesheet that was processed. The XSLT stylesheet node tree 120 may be in the form of a document object model (DOM), as is known in the art. Further, the XSLT stylesheet node tree 120 may reside in cache memory for efficiency, as shown in an XSLT stylesheet cache 126. The XSLT processor 74 operates on the data in the XSLT stylesheet node tree 120 to perform its function of transforming the underlying value data or underlying element names in accordance with the stylesheet.

[0051] Note that although the XSLT style sheet is shown as an input to the XML processor 70 in FIG. 3, the XSLT processor 74 processes the stylesheet. It is initially provided to the XML processor 70 because all XML documents are first processed and placed into the appropriate data structure for subsequent processing.

[0052] The XSLT processor 74 may modify, reposition, and rearrange the underlying value data or may add to the underlying value data or delete some of the underlying value data. For example, under direction of the stylesheet, the underlying value data may be rearranged into table format or into columns. In particular, the stylesheet may add XSLFO formatting elements and attributes.

[0053] After the underlying value data in the label value node tree 100 has been processed in accordance with the corresponding stylesheet, an XSLFO instance node tree 130 is produced. Again, the XSLFO instance node tree 130 may be in the form of a document object module, as is known in the art. The XSLFO instance node tree 130 contains XSLFO commands (layout instructions) that directs the XSLFO processor 78 with respect to formatting and layout. The XSLFO processor 78 then interprets the XSLFO commands and applies such commands to the underlying value data so as to properly format and layout the underlying value data. The XSLFO processor 78 produces the XSLFO area node tree 130, which represents the final output of formatting before rendering.

[0054] Turning now to FIG. 3 and a code segment shown immediately below entitled code segment 1 for an XML input data stream, the code segment 1 illustrates an XML input data stream 90 in hard copy, which may, for example, be sent to the XML printer system 10 by the ERP or warehouse management system 88. Line numbering has been inserted for purposes of illustration only and is not part of the code.

Code Segment 1 For An XML Input Data Steam
	<xml version1.0 encodingUTF-8>
	<xml-stylesheet typetext/xsl
	hrefD:ProjectsXMLNativeDocsShipLabels.xsl>
<labels
	xmlns:xsihttp://www.w3.org/2001/XMLSchema-instance
	xsi:noNamespaceSchemaLocatian
	D:ProjectsXMLNativeDocsShipLabels.xsd>
	<label>
	<name>Albert Einstein</name>
	<address>1234 Relative Way</address>
	<city>Princeton</city>
	<state>NJ</state>
	<zip>08540</zip>
	</label>
	<label>
	<name>Steven Hawking</name>
	<address>5678 Black Hole Drive</address>
	<city>Los Angeles</city>
	<state>CA</state>
	<zip>90007</zip>
	</label>
	<label>
	<name>Richard Feynman</name>
	<address>90 Quantum Circle</address>
	<city>New York</city>
	<state>NY</state>
	<zip>10044</zip>
	</label>
</labels>

[0055] The XML input data stream identifies the schema document as ShipLabels.xsd, and that schema document may be found, in this specific example, in a directory called D:/Projects/XML/Native/Docs, as shown at line 7 in code segment 1. Further, the XML input data stream identifies the stylesheet document as ShipLabels.xsl, and that stylesheet document may also be found in a directory called D./Projects/XML/Native/Docs, as shown at line 3 of the code segment 1. Of course, the schema document and the stylesheet document may be located anywhere, for example, as identified by an Internet address.

[0056] This specific example shows the underlying value data and element names for three shipping labels to be printed. Each shipping label contains an XML element name defined between angular brackets as follows: <name>, <address>, <city>, <state> and <zip>. The value of the first element name, <name>, is Albert Einstein, the value of the second element name, <address>, is 1234 Relative Way, the value of the third element name, <city>, is Princeton, the value of the forth element name, <state>, is NJ and the value of the fifth element name, <zip>, is 08540. This is the underlying value data.

[0057] Now turning to FIG. 3, code segment 1, and a code segment shown immediately below entitled code segment 2 for XML schema, the code segment 2 illustrates a specific example of an XML document in the form of the XML schema document specified in the XML input data stream of code segment 1. Line numbering has been inserted for purposes of illustration only and is not part of the code.

Code Segment 2 For XML Schema
<xml version1.0 encodingUTF-8>
<xs:schema
	xmlns:xshttp://www.w3.org/2001/XMLSchema
	elementFormDefaultqualified>
	<xs:element nameaddress typexs:string/>
	<xs:element namecity typexs:string/>
	<xs:element namelabel>
	<xs:complexType>
	<xs:sequence>
	<xs:element refname/>
	<xs:element refaddress/>
	<xs:element refcity/>
	<xs:element refstate/>
	<xs:element refzip/>
	</xs:sequence>
	</xs:complexType>
	</xs:element>
	<xs:element namelabels>
	<xs:complexType>
	<xs:sequence>
	<xs:element reflabel maxOccursunbounded/>
	</xs:sequence>
	</xs:complexType>
	</xs:element>
	<xs:element namename typexs:string/>
	<xs:element namestate>
	<xs:simpleType>
	<xs:restriction basexs:string>
	<xs:enumeration valueCA/>
	<xs:enumeration valueNJ/>
	<xs:enumeration valueNY/>
	</xs:restriction>
	</xs:simpleType>
	</xs:element>
	<xs:element namezip>
	<xs:simpleType>
	<xs:restriction basexs:int>
	<xs:minInclusive value00000/>
	<xs:maxInclusive value99999/>
	</xs:restriction>
	</xs:simpleType>
	</xs:element>
</xs:schema>

[0058] As mentioned above, the schema is used to validate the underlying value data. This entails checking to determine that all required data is present, that no extraneous data is present, that the data present is within the specified ranges, and the like. Any suitable validation scheme may be specified in the schema, depending upon the application. The XML language is robust and code may be written to handle a vast multitude of requirements.

[0059] For example, the schema document shown in code segment 2 above specifies that the underlying value data corresponding to the element name, <address>, must be a string, as defined in the XML Schema specification, as shown by line 5 in the code segment 2. The schema document also specifies that the underlying value data corresponding to the element names of <name>, <address>, <city>, <state>, and <zip> must also be present in the sequence indicated, as shown by lines 9-15 in the code segment 2. Further, this specific schema document shown in the code segment 2 specifies that the underlying value data corresponding to the element name, <state>, must be one of three states, namely, CA, NJ, or NY. Of course, this is only an abbreviated example, and not all states have been included for purposes of illustration only. The schema document shown in code segment 2 also specifies that the underlying value data corresponding to the element name, <zip>, must be in the range from 00000 to 99999. If any of the above-mentioned schema criteria are not met by the data in the XML input data strear, the schema validation module 110 will reject it, and will preferably return an error message back to the source 88.

[0060] Now turning to FIG. 3, code segments 1-2, and a code segment shown immediately below entitled code segment 3 for an XSLT stylesheet, the code segment 3 shows a specific example of an XML document in the form of the XSLT stylesheet document specified in the XML input data stream of the code segment 1. Line numbering has been inserted for purposes of illustration only and is not part of the code.

Code Segment 3 For An XSLT Stylesheet
<xml version1.0 encodingUTF-8 >
<xsl:transform version1.0
	xmlns:xslhttp://www.w3.org/1999/XSL/Transform
	xmlns:fohttp://www.w3.org/1999/XSL/Format
	xmlns:bohttp://www.zebra.com/2002/XSL/Barcode>
<xsl:output methodxml version1.0 indentyes />
	<xsl:template matchlabels>
	<fo:root>
	<fo:layout-master-set>
	<fo:simple-page-master master-nameall-labels>
	<fo:region-body marginlin />
	</fo:simple-page-master>
	</fo:layout-master-set>
	<fo:page-sequence master-nameall-labels>
	<fo:flow flow-namexsl-region-body font12pt Times>
	<xsl:apply-templates />
	</fo:flow>
	</fo:page-sequence>
	</fo:root>
	</xsl:template>
	<xsl:template matchlabel>
	<fo:block break-afterpage>
	<xsl:apply-templates selectname />
	<xsl:apply-templates select-address />
	<fo:block fontbold 14pt Times text-alignleft>
	<xsl:apply-templates selectcity />
	<xsl:apply-templates selectstate />
	</fo:block>
	<xsl:apply-templates selectzip />
	<fo:block>
	<fo:instream-foreign-object>
	<bo:barcode>
	<bo:postnet interpretation-linenone>
	<xsl:value-of selectzip />
	</bo:postnet>
	</bo:barcode>
	</fo:instream-foreign-object>
	</fo:block>
	</fo:block>
</xsl:template>
<xsl:template matchname>
	<fo:block fontbold 14pt Times text-alignleft>
	<xsl:value-of select. />
	</fo:block>
</xsl:template>
<xsl:template.matchaddress>
	<fo:block fontbold 14pt Times text-alignleft>
	<xsl:value-of select. />
	</fo:block>
</xsl:template>
<xsl template matchcity>
	<xsl:value-of select. />
</xsl:template>
<xsl:template matchstate>
	<xsl:text>,</xsl:text>
	<xsl:value-of select. />
</xsl:template>
<xsl:template matchzip>
	<fo:block fontbold 14pt Times text-alignleft>
	<xsl:value-of select. />
	</fo:block>
</xsl template>
</xsl:transform>

[0061] As mentioned above, the stylesheet is used to transform the data. In this specific example, the stylesheet of the code segment 3 defines two types of namespace, namely, a bo type object, which is selected to be a barcode-type object, and an fo type object, which is selected to be a formatting object, which was described above with respect to the XSLFO processor 78. This permits differentiation between the different objects, as is known in the art. The stylesheet may cause some data to be transformed or even added. For example, the underlying value data from the XML input data stream of the code segment 1, namely Einstein, 1234 Relative Way, and the like, is inserted, as indicated by lines 40-62.

[0062] This stylesheet also causes a variety of fo type elements to be generated, which are designated as formatting elements or XSLFO objects. The XSLFO objects contain layout type commands that the XSLFO processor 78 understands and processes. Note that all lines of code having a prefix of fo are not interpreted by the XSLT processor 74, but rather, are passed on to the XSLFO processor 78.

[0063] For example, line 21 of the code segment 3 shows <xsl: template matchlaber> followed by <fo:block break-afterpage> on line 22. This is interpreted by the XSLFO processor 78 to put a page break between the three shipping labels specified in the code segment 1. Essentially a new shipping label is created due to the page break, with each new shipping label containing the underlying value data specified in the code segment 1.

[0064] Further, this specific stylesheet specifies that an instream foreign object is inserted, as shown at line 31. Line 31 is shown as <fo:instream-foreign-object> in conjunction with lines 31-37, which define the instream foreign object. Note that the instream-foreign object is not processed by either the XSLT processor 74 or the XSLFO processor 78. Rather, the instream foreign object is passed to and is processed by the bitmap/barcode rendering engine 80. For example, lines 32-36 of the code segment 3 cause a <bo:barcode> element to be inserted that contains the definition of a postnet barcode element, which element will later be processed by the bitmap/barcode rendering engine 80. At line 34, the XSLT processor 74 causes the zip code from the XML input data stream to be inserted as the text of the <bo:postnet> element.

[0065] Now turning to FIG. 3, code segments 1-3, and a code segment shown immediately below entitled code segment 4 for an XSLT instance node tree representation, the code segment 4 shows a specific example of a representation of an XSLFO instance node tree 130 output produced by the XSLT processor 74 in conjunction with the stylesheet of code segment 3, which output is a representation of the XSLFO instance node tree provided to the XSLFO processor 78. Line numbering has been inserted for purposes of illustration only and is not part of the code.

Code Segment 4 For An XSLFO Instance Node Tree Representation
<xml version1.0 encodingUTF-16 >
<fo:root xmlns:fohttp://www.w3.org/1999/XSL/Format
	xmlns:bohttp://www.zebra.com/2002/XSL/Barcode>
	<fo:layout-master-set>
	<fo:simple-page-master master-nameall-labels>
	<fo:region-body marginlin />
	</fo:simple-page-master>
	</fo:layout-master-set>
	<fo:page-sequence master-nameall-labels>
	<fo:flow flow-namexsl-region-body font12pt Times>
	<fo:block break-afterpage>
	<fo:block fontbold 14pt Times text-
	alignleft>Albert Einstein</fo:block>
	<fo:block fontbold 14pt Times text-alignleft>1234
	Relative Way</fo:block>
	<fo:block fontbold 14pt Times text-
	alignleft>Princeton, NJ</fo:block>
	<fo:block fontbold 14pt Times text-
	alignleft>08540</fo:block>
	<fo:block>
	<fo:instream-foreign-object>
	<bo:barcode>
	<bo:postnet interpretation-
	linenone>08540</bo:postnet>
	</bo:barcode>
	</fo:instream-foreign-object>
	</fo:block>
	</fo:block>
	<fo:block break-afterpage>
	<fo:block fontbold 14pt Times text-alignleft>Steven
	Hawking</fo:block>
	<fo:block fontbold 14pt Times text-aliqnleft>5678
	Black Hole Drive</fo:block>
	<fo:block fontbold 14pt Times text-alignleft>Los
	Angeles, CA</fo:block>
	<fo:block fontbold 14pt Times text-
	alignleft>90007</fo:block>
	fo:block>
	<fo:instream-foreign-object>
	<bo:barcode>
	<bo:postnet interpretation-
	linenone>90007</bo:postnet>
	</bo:barcode>
	</fo:instream-foreign-object>
	</fo:block>
	</fo:block>
	<fo:block break-afterpage>
	<fo:block fontbold 14pt Times text-
	align left>Richard Feynman</fo:block>
	<fo:block fontbold 14pt Times text-alignleft>90
	Quantum Circle</fo:block>
	<fo:block fontbold 14pt Times text-alignleft>New
	York, NY</fo:block>
	<fo:block fontbold 14pt Times text-
	alignleft>10044</fo:block>
	<fo:block>
	<fo:instream-foreign-object>
	<bo:barcode>
	<bo:postnet interpretation-
	linenone>10044</bo:postnet>
	</bo:barcode>
	</fo:instream-foreign-object>
	</fo:block>
	</fo:block>
	</fo:flow>
	</fo:page-sequence>
</fo:root>

[0066] Two main portions of code segment 4 above are briefly described, namely, one portion beginning at line 4 with the code <fo:layout-master-set> and a second portion beginning at line 9 with the code <fo:page-sequence master-nameall-labels>. This portion of the code essentially defines what a barcode label will look like or how it will be laid-out and how the underlying value data will appear in that lay-out.

[0067] With respect to formatting the underlying value data shown in code segment 1, for example, the font attribute of bold 14 pt Times and text-alignleft shown in lines 12-13 will be applied to the underlying value data of Albert Einstein so that when the barcode label is printed, the name of Albert Einstein will be printed in 14 point Times font, and it will aligned with the left margin of the barcode label. As is known in the art, may different kinds of formatting instructions may be specified, which will be interpreted by the XSLFO processor 78.

[0068] Further, this specific example of the representation of the XSLFO instance node tree 130 contains an instream foreign object, as shown at lines 21-26 of the code segment 4, which instream foreign object may not processed by the XSLFO processor 78. Rather, the insteam foreign object may be passed to the bitmap/barcode rendering engine 80 for processing. Note that at this point in the processing, the XSLFO processor 78 does not know how to print a barcode label because barcode element types are not included in the XSLFO specification. Rather, only the text information, such as the underlying value data, namely, Einstein, 1234 Relative Way, and the like, as shown in code segments 1-2, could be printed on the barcode label as text. No actual barcode symbol would appear because the XSLFO processor 78 does not know how to produce a barcode symbol.

[0069] The result of processing by the XSLFO processor 78 is an XSLFO area node tree 140. Note that the instream foreign object shown in the code segment 4 is not processed by the XSLFO processor 78, but rather, is passed to the barcode/bitmap rendering engine 80 in one or more nodes of the XSLFO area node tree 140. The instream foreign object element is referred to as <bo:barcode> and is shown at lines 21-26 of the code segment 4. The barcode/bitmap rendering engine 80 receives the <bo:barcode> element and processes the code contained in that block. For example, the rendering engine 80 interprets lines 23-24, namely, <bo:postnet interpretation-linenone>08540<bo:postnet> as defining this particular node as being a postnet barcode type of element. Many different types of barcode symbols may be defined, as is defined by corresponding industry standards, discussed below.

[0070] The underlying value data to be printed as a barcode symbol is the numerical data 08540, as shown in line 24 of code segment 4, which underlying value data is the zip code associated with Albert Einstein's address shown in the code segment 1. In this specific example, only the zip code is transformed into the barcode symbol. Of course, any and all information may be transformed into a barcode symbol, depending upon the application. Also, in this specific example, the instream foreign objects shown in the code segment 4 only relate to the three zip codes shown in the code segment 1. No other underlying value data is transformed into the barcode symbol in this example.

[0071] Turning now to FIGS. 2-4 in conjunction with the code segment 4, additional detail concerning the barcode/bitmap rendering engine 80 and the processing of the instream foreign objects will now be set forth. As described above, the rendering engine 80 processes each node of the XSLFO area node tree 140 generated by the XSLFO processor 78. As is known in the art, the XSLFO area node tree 140 is represented in memory as a document object model. Accordingly, multiple nodes may exist. For example, one node may contain the instream foreign object, another node may contain associated element names, another node may contain associated text data, another node may contain associated attributes, and the like.

[0072] As shown in block 150 in FIG. 4, the nodes of the XSLFO area node tree 140 are processed. In particular, the rendering engine 80 knows how to render or produce the actual barcode symbol defined by the instream foreign object. Commercially available XSLFO processors do not know how to process such instream foreign objects representing barcode symbols, and thus are not able to produce or render barcode symbols. Commercially available XSLFO processors may, however, render text in an acceptable manner and may even render certain types of instream foreign objects.

[0073] If a particular node does not contain an instream foreign object, meaning that it may contain, for example, text data, than this node may be processed in a standard way by utilizing the processing power of the XSLFO processor 78 rather than the rendering engine 80, as illustrated in a block 154. In one embodiment, the non-instream foreign object is provided back to the XSLFO processor 78, or the XSLFO processor is notified that a particular node in the XSLFO area node tree 140 is suitable for processing by it.

[0074] Processing of a node in the XSLFO area node tree 140 containing a non-instream foreign object may be processed by the XSLFO processor 78, as described above. Of course, different commercially available XSLFO processors render text, for example, into different formats. For example, the XSLFO processor referred to as XSL Formatter available from Antenna House Corporation, as described above, renders a node into a WINDOWS device-independent bitmap format. The XSLFO processor referred to as XEP available from RenderX Corporation, as described above, renders a node into PDF format, and the XSLFO processor referred to as FOP available from the Apache Software Foundation, as described above, may also render a node into PDF format.

[0075] Preferably, the XML printer system 10 utilizes the FOP XSLFO processor 78 available from the Apache Software Foundation because this XSLFO processor may be configured to call a subroutine or other processing function when it encounters an instream foreign object that it is not capable of processing. In particular, this XSLFO processor 78 may be set to call the rendering engine software block 80 described herein, to handle the instream foreign object that it is not capable of processing.

[0076] Next, as shown in a block 160, if the node contains an instream foreign object representing a barcode, which is not capable of being processed by the XSLFO processor 78, the rendering engine 80 checks to determine if the instream foreign object has a namespace specific to this XML printer system 10. For example, the rendering engine 80 may check to determine if the namespace associated with the instream foreign object corresponds to the Zebra corporation namespace. The namespace notation is known in the art. This is shown in line 3 of the code segment 4 as xmlns:bohttp://www.zebra.com/2002/XSL/Barcode> Thus, as shown in the code segment 4, the namespace defined above is applied to any elements having a bo prefix. Such elements having a bo prefix are then only available for processing by the rendering engine 80, which bo prefix type elements correspond to a barcode-type instream foreign object. The XSLFO processor 78 will not know how to process such elements.

[0077] If the instream foreign object is not associated with the proper namespace, it is passed back to the XSLFO processor 78, assuming that it is not a barcode type instream foreign object because the XSLFO processor may be able to process some limited number of instream foreign objects. This is shown by arrow 162 from the block 160 to the block 154. Generally, however, instream foreign objects exist or are created for the specific reason that the data associated with an instream foreign object is very unique in nature (such as a barcode), and thus, many commercially available or general purpose XSLFO processors can not process them.

[0078] Note that the commercially available XSLFO processors mentioned herein are not necessarily incapable of processing all instream foreign objects. They are, however, incapable of processing instream foreign objects corresponding to barcode symbols.

[0079] Assuming that instream foreign object has the appropriate namespace, a block 170 interprets the elements in the instream foreign object to determine barcode type. For example, the instream foreign object is shown at lines 21-26 the code segment 4. More specifically, the barcode element having a prefix of bo, indicating the correct namespace corresponding to a barcode, is shown to have a barcode type of postnet, as shown in line 23-24 of the code segment 4, which appears as <bo:postnet interpretation-linenone>08540</bo:postnet>. Note that lines 41-42 of the code segment 4 show a similar barcode element for another instream foreign object, namely, the next barcode label to be printed, which corresponds to the address of Steven Hawking shown in code segment 1.

[0080] Any barcode type may be specified in the instream foreign object depending upon the application. The barcode type is based upon known barcode standards. For example, the barcode type is not limited to a postnet type of barcode symbol, and may be, for example, Industrial 2 of 5, PDF 417, UPC, and the like. The barcode type specifies the basic structure of the barcode symbol to be printed, such as the thickness of the bars, the ratio of the thickness of the bars to the width of the space between bars, and the like. Each specific known barcode standard is concretely defined.

[0081] Next, after the barcode type has been ascertained from the instream foreign object, the attributes of the instream foreign object are interpreted to determine the barcode characteristics, as shown in a block 176. The characteristics may modify the way in which the barcode symbol is created. For example, one attribute of the postnet type barcode may be seen at lines 23-24 of the code segment 4 as interpretation-linenone As is known in the art, interpretation-linenone means that no corresponding human readable text is generated along with the specific barcode symbol. Another example of an attribute associated with the barcode element may be the height of the barcode symbol, which may also be specified in the instream foreign object as an attribute.

[0082] Using the barcode type and the attributes obtained from the instream foreign object, the rendering engine 80 then obtains the actual node text data to be converted into the barcode symbol as shown in a block 180. In this example, the actual barcode data is the zip code 08540, as is shown between reverse angled brackets (>80540<) in line 24 of the code segment 4. The physical conversion from the numerical data 80540 into the bitmap representing the lines or bars of the barcode symbol (for a linear barcode, for example) may be performed by software routines contained in, for example, the barcode label printers commercially available from Zebra Corporation. Such suitable barcode printers may be Models Xi series barcode printers (XiIII, 90XiIII, 96XiIII, 140XiIII, 170XiIII, 220XiIII, etc.), the 2800 Series barcode printers, Model Z4M, Z6M, 105SL barcode printers, and the like. Such software routines or native algorithms contained in barcode printers commercially available from Zebra Corporation are very efficient, and thus the barcodes are rendered quickly.

[0083] Once the bitmap representing the barcode symbol has been generated by the block 180, that bitmap is then placed into or merged with the master or label bitmap 184, which label bitmap represents the image of the entire shipping label, as shown in a block 182. The shipping label contains the human readable text, other text or characters, and the barcode symbol. Note that the aforementioned bitmaps may be separate, i.e., bitmaps for text and a bitmap for the barcode symbol, or one master bitmap may be used or populated as processing progresses. In that regard, note that the tree or data structure upon which the rendering engine 80 operates is referred to as the XSLFO area node tree, meaning that it contains different areas. Such areas may correspond to different or individual bitmaps or bitmap portions. However, any number of suitable bitmap structures may be used. The exact structure or configuration of the bitmap, or the number of bitmaps is not relevant to the scope of the present invention.

[0084] For example, the XSLFO processor 78 when generating text, may place its text in one particular bitmap. Such text may correspond to the name Albert Einstein discussed above. Because this text will also be printed on the shipping label along with the barcode symbol, the master or label bitmap 184 will contain all of the component bitmaps. The final master bitmap 184 is then sent to the printer driver 54 (FIG. 1) so that the shipping label may be printed.

[0085] Turning now to FIGS. 4-5, FIG. 5 is a representation 190 of the final output of the above-described processing for the first barcode shipping label specified in code segment 1. The text data is rendered and formatted in accordance with the corresponding stylesheet, while the zip code 192 is also rendered in the form of a barcode symbol by the rendering engine 80, as described above. Note that for purposes of illustration only, the font size or font type shown in FIG. 5 may not be the same as that specified in the corresponding stylesheet shown in the code segment 3.

[0086] Referring now to FIG. 6, an alternate embodiment is shown. Like reference numbers are used to denote like structures. In this specific embodiment, the XML printer system 10 need not include or specifically utilize the XML printer apparatus in all instances. In this embodiment, for example, an external requestor 194 may desire to have an XML input data stream rendered into a bitmap so that it can print the barcode label, which may be done remotely. Accordingly, the external requestor 194 may send a request to the XML server 200 over the Internet or other network 43, 44. The request may be in the same form as the XML input data stream described above with respect to FIGS. 1-3 and code segments 1-4. The request may also be in the form of a protocol that contains XML data, such as SOAP (Simple Object Access Protocol) as is known in the art.

[0087] In response, the computer system 12 of the XML server 200 may process the XML input data stream. All of the same processing functions described above are carried out in this embodiment, except that the bitmap is not sent to the printer driver. Rather, the bitmap is converted to any suitable format, such as JPEG or PNG format, as is known in the art. The JPEG or PNG file is then sent back to the external requestor 194, who then formats the JPEG or PNG file for the appropriate printer driver, and prints and/or displays the barcode label. Accordingly, the present invention may function as a barcode rendering server and need not necessarily perform the printing function.

[0088] Specific embodiments of an XML printer system according to the present invention have been described for the purpose of illustrating the manner in which the invention may be made and used. It should be understood that implementation of other variations and modifications of the invention and its various aspects will be apparent to those skilled in the art, and that the invention is not limited by the specific embodiments described. It is therefore contemplated to cover by the present invention any and all modifications, variations, or equivalents that fall within the true spirit and scope of the basic underlying principles disclosed and claimed herein.