Newsletter Purpose: This is the periodic newsletter of Zetein Inc. offering insights into current standards and technology topics. This letter also serves as a means of staying in touch with you. Here are the major topics covered this edition:
For the last few years there has been a lot of hype about how XML would revolutionize your business. While the technical types have been a twitter, business people have not seen much advantage from XML. In October 2003 Microsoft introduced its first XML enabled Office Suite (Office 2003). Now business people can start getting some advantages from XML.
Consistency in memos, letters, sales scripts, customer service scripts, and forms can be achieved using the schema features inherent in word. Many business rules can be imbedded in the schemas to better accuracy. A common format is assured. Documents processed can then be further processed using many of the tools available for XML.
If we use a customer service script as an example, let's look at how XML can help.
If your script were to (1) ask a question, (2) get a response.
Then, (3) if answer is proceed with process one (or more computer operations), give information the resulting to the client and (4) repeat.
Or, (5) If answer is to stop, (6) give sales pitch for expanded products and (7) repeat until a second stop is received.
Using the schemas feature of Word 2003, the script preparers would produce documents for processes like miscellaneous changes, loans, quotes, etc. Each document (script) prepared with a common schema would be in the same format with common tags. Then an automatic script driver software program could process directly from the XML documents. No conversion errors, time delays, or human intervention is required. The process controlled using schemas will provide consistency, and speed changes to implementation.
Another benefit is that since all the scripts are in a common XML format, searching across multiple scripts is a breeze. This search capability should make for better and easier maintenance.
Since the documents are in XML format, they can be stored in a version control system. Use of a version control system to store the XML documents enhances Microsoft words ability to use common paragraphs, etc. in fully integrated solutions.
If you would like me to discuss this topic in more depth or other topics in future newsletters, please let me know.
We are going to explore some basics of XSL in this letter. If you copy the two files below into a text editor and save them into the same directory with the names specified, you can see the results of this article by displaying the xml document in a browser. The first is named NameSample.xml the second is named NameSample2Flat.xsl.
The sample XML Stream (NameSample.xml):
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet
type="text/xsl" href="NameSample2Flat.xsl"?><!--
this ties the files together -->
<Party>
<Name>John Meagher</Name>
<Phone>469.374.0984</Phone>
<Address>BX 741083</Address>
<City>Dallas</City>
<State>TX</State>
<ZipCode>75374</ZipCode>
</Party>
the statement "xml-stylesheet" is a processing instruction to tie the “NameSample.xml” XML document to the “NameSample2Flat.xsl” stylesheet. The rest of the document contains only data.
The sample XSL Stream (NameSample2Flat.xsl) used to product simple output:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:template match="/">
<html>
<title>Name Display</title>
<body>
<h1>Name: <xsl:value-of
select="Party/Name" /></h1>
<h1>Address: <xsl:value-of
select="Party/Address" /></h1>
<h1>City State Zip : <xsl:value-of
select="Party/City" /><xsl:text>
</xsl:text> <xsl:value-of
select="Party/State" /> <xsl:text>
</xsl:text> <xsl:value-of
select="Party/ZipCode" /></h1>
<h1>Phone : <xsl:value-of
select="Party/Phone" /></h1>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
1. <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" identifies that the XSL namespace items are prefixed with the letters "xsl".
2. <xsl:template match="/"> tells the processor to apply this template to the root element of the XML document.
3. <html>
<title>Name Display</title>
<body>
all h1 items
</body>
</html>
are included just so the output will display using a browser. If a flat file is desired, these are removed.
4. Name: <xsl:value-of select="Party/Name" /> provides the caption "Name:" then gives the xsl processor the path to the information to it is to display after the caption. All paths are from the current location. The current location is still the root identified in #2 (above)
5. <xsl:text> </xsl:text> is used to add a space between items on the same line.
6. Notice that the input is in a different sequence than the output. You can reformat output as needed.
Now, add more information into the XML document and add display items it in the xsl document. Resave your document, then try displaying it in a browser. Were you successful?
We will look at the "how to" of other models in future newsletters.
If you would like me to discuss this topic in more depth or other topics in future newsletters, please feel free to contact me.
We have some consulting time available and are ready to assist you in your implementation. If you need training on TXLifE, XTbML, XMLifE, XSL, XML, Schema, etc, we can provide it.
We have extensive experience in insurance, XML, and ACORD standards.
Visit our website (http://www.zeteininc.com/)for more details, then please call (469.374.0984) or email me (jmeagher@zeteininc.com) to explore how we can help with your ACORD project.
Thanks, John Meagher
▲ Zetein Inc BX 741083 Dallas TX 75374
If you do not wish any future emails, please reply to this email with "Remove" in the subject line.