|
|
 |
|
|
|
XML and SOAP Programming for BizTalk™ Servers
|
|
|
Author |
|
Brian E. Travis
|
|
|
Pages |
464
|
|
Disk |
1 Companion CD(s)
|
|
Level |
Intermediate
|
|
Published |
08/30/2000
|
|
ISBN |
9780735611269
|
|
ISBN-10 |
0-7356-1126-2
|
|
Price(USD) |
$49.99
To see this book's discounted price, select a reseller below.
|
|
|
|
|
|
|
|
|
Index
Note: Page numbers in italics refer to code listings, figures, or tables.
Symbols and Numbers
" (double quote marks), 59
#! (hash-bang) notation, 310-11, 323
' (single quote mark), 59
/ (slash), 58
80112.xml file, 111, 111, 112-13
A
ACORD specification, 32, 53
ActiveXObject function, 82
actor global attribute, SOAP, 381-82
addAttribute function, 97
Adobe PostScript, 51
ADO Recordset objects, 10-11
Agency Company Organization for Research and Development (ACORD), 32, 53
aggregation. See information aggregation
Air Transport Association (ATA), 52
American National Standards Institute (ANSI), 43
ampersand (&), 58-59
ANPA 1312 specification, 22
Apache for Win32, 310
Apache Web servers, configuring to run OmniMark CGI programs, 311, 313
appendChild method, 97, 98
application protocols, OmniMark support, 303
applications, BizTalk, defined, 333
arithmetic operators, OmniMark, 283
arrays
partially transmitted, 401
in SOAP, 393, 396-401
sparse, 401
arrays of bytes as SOAP datatype, 393
asynchronous communication, 192-93
async property, 82
attachments
in BizTalk Framework specification, 350-52
BizTalk message example, 355-57
defined, 334
attributes, SOAP
actor global, 381-82
encodingStyle global, 379-80
Header, 381-82
mustUnderstand global, 147-48, 382
root, 403
attributes, XML element
adding to documents, 95-97, 96
collection in XMLDOMElement object, 84-85
overview, 59-60
auctions, reverse, 137
automating procurement, 185. See also purchase orders
B
B2B e-commerce
vs. B2C e-commerce, 5, 30
and BizTalk Framework, 171-74
and content aggregation, 30
B2C e-commerce, 3-5, 27-30
binary files, copying, 318
BizTags
in BizTalk document structure, 336-37
defined, 333
<delivery> BizTag, 178, 338-40, 347, 349
<manifest> BizTag, 178, 338, 342-44, 350, 352
<process> BizTag, 178, 338, 344-45
<properties> BizTag, 178, 338, 340-42, 346
specific header entries for BizTalk documents, 338-45
BizTalk documents
with attachments, 335, 350-52
vs. BizTalk messages, 334
defined, 333
example, 335-37
and HTTP protocol, 353-57
reliable delivery, 345-50
in SOAP <Body> element, 337-38
SOAP header entries in, 336, 338-45
structure of, 335-37
transformation (see XSL Transformations (XSLT))
BizTalk Document Tracking, 255
BizTalk Editor
loading, 244
saving documents, 246
using to create purchase order schema, 244-47
vs. XML Authority, 244
BizTalk Framework
in B2B transactions, 174-85
comparing versions, 330
facets of initiative, 172-73
logical layering, 334-35
non-normative specifications, 332
normative specifications, 331-32
overview, 171-72
role in creating XML documents, 173-74
role of SOAP, 330, 331
sample BizTalk document (SOAP 1.1 message), 178-82
sample scenario, 174-85
scope of specification, 329
specification introduction, 328-29
terminology, 332-35
versioning model, 331
XML schema data types, 332
BizTalk Framework 2.0 Draft Document and Message Specification, 327-63
BizTalk Framework Compliant (BFC) Servers, 332
BizTalk Framework Independent Document Specification, 172
BizTalk Framework receipts, 182-83, 346-49
BizTalk home page, Microsoft, 366
BizTalk Management Desk, 255
BizTalk Mapper
creating maps, 249-53
other features, 255
overview, 247-48
saving specification, 253
selecting schemas for mapping, 248
starting, 248
using to map two purchase order schemas, 248-55
BizTalk messages
attachments in multipart MIME structure, 351-52
vs. BizTalk documents, 334
defined, 333-34
example that includes attachments, 355-57
scope of specification, 330
simple example, 354-55
BizTalk.org Web site, 172, 365-66
BizTalk Server Administration Console, 255
BizTalk servers. See also Microsoft BizTalk Server 2000
building, 199-241
defined, 172, 189
need for batch support, 193
need for document tracking, 193-94
need for document transformation capability, 195
need for EDI interoperability, 196
need for extensibility, 195-96
need for message queuing, 193
need for scalability, 194
need for synchronous communication, 192-93
overview, 189-90
routing and workflow issues, 191-92
system requirements, 190-97
system setup for purchase requisition example, 207-8
and trading partner relationships, 194, 255-60
BizTalk Workflow Designer, 255
<Body> element, SOAP
in message structure, 147, 148
relationship to <Header> element, 383
specifying in BizTalk Framework specification, 337-38
specifying in SOAP W3C proposal, 378, 379, 382-83
body elements, XML, creating, 98, 99
BTServer.xom file, 204
business documents, BizTalk, defined, 333
business-to-business e-commerce
and BizTalk Framework, 171-74
vs. business-to-consumer e-commerce, 5, 30
and content aggregation, 30
business-to-consumer e-commerce, 3-5, 27-30
C
CarPoint Web site, 27-29
cascading style sheets (CSS) as W3C standard, 45
case sensitivity in XML, 57
catch and throw, OmniMark, 290-98
CD-ROMs, 26
CGI programs
catching errors, 319
compiling, 323-24
configuring Web servers for, 311-14
environment variables, 316-17
hash-bang (#!) notation, 310-11, 323
HTTP headers, 317-18
samples, 155-56, 156-61, 319-22
writing in OmniMark, 315-22
child nodes, XML, 85-86
childNodes property, 85, 86
client tier, three-tier architecture, 8
COM architecture, 137-38
comments in XML documents, 61
comparison operators, OmniMark, 283
conditional constructs, OmniMark, 280-81
Confirm.xml file, 183-84, 184
constants, OmniMark, 299-301
content aggregation. See information aggregation
content providers. See also external data sites
data format issues, 18-22
in news business, 18-22
New York Times, 18-19
role of XML, 26
Weather Channel, 14-17
for weather data, 14-18
cookies, 8-10
createAttribute function, 96
createElement method, 97, 98-99
D
databases
in data tier, 7-8
Toi Carz, Inc., 206-7, 206
Toy Car Parts Corporation, 206-7, 206
data-content rules, OmniMark, 264
data structures, OmniMark, 276-78
data tier, three-tier architecture
databases vs. data sources, 7-8
data sources in, 7-8
role of subscriber profile database, 8-10, 9
data types, OmniMark, 273-74
DCOM (Distributed COM), 138
declarations, XML, 56
de facto standards, 51
<delivery> BizTag, 178, 338-40, 347, 349
<description> BizTag, 343, 344
Distributed COM (DCOM), 138
document element, XML
accessing properties, 84-85
nodeName property, 84
text property, 84
documentElement property, 84
Document Object Model (DOM)
creating objects, 82-84
vs. event-driven models, 101-2
Microsoft implementation, 78-82
and Visual Basic, 88-94
as W3C standard, 50, 77-78
and XML documents, 77-88
document type declarations (DOCTYPEs), 64
document type definitions (DTDs), 48, 63-66
DOM. See Document Object Model (DOM)
do sgml-parse, OmniMark, 266
double quote marks ("), 59
do xml-parse, OmniMark, 266, 267
DSSSL (Document Style Semantics and Specification Language), 103-4
Duckone.xml file, 114, 114
Duck.xml file, and OmniMark, 269
E
ebXML Initiative, 31-32
e-commerce
B2B vs. B2C, 5, 30
and BizTalk Framework, 171-74
overview, 3-5
role of XML, 26, 32, 33-34
XML as lingua franca, 33-34
EDI. See electronic data interchange (EDI)
Editor. See BizTalk Editor; XRay XML Editor
electronic commerce. See e-commerce
electronic data interchange (EDI)
need for BizTalk server support, 196
overview, 30-31
role of XML, 31-34
element rules, OmniMark, 264, 269
elements, XML. See also document element, XML
empty, 60-61
nesting, 57-58
overview, 57
root, 57
empty elements, XML, 60-61
encodingStyle global attribute, SOAP, 379-80
end tags, 57
Enterprise Java Beans (EJB), 138
entity references, 58-59
enumerations as SOAP datatype, 392-93
<Envelope> element, SOAP, 178, 378, 379, 380, 409-12
environment variables
CGI, 316-17
OmniMark, 314-15
event-driven models, when to use, 101-2
exception handling, OmniMark, 290-98
<expiresAt> BizTag, 341-42, 349-50
external data sites. See also content providers
in news business, 18-22
role in three-tier architecture, 13-17, 14
role of syndication, 18-22
and SOAP, 18
ways of providing data, 17-18
Weather Channel example, 14-17
for weather data, 14-18
F
Fault element, SOAP, 383-85
financial calculations in OmniMark, 301-2
Financial Information Exchange (FIX), 32
find rules, OmniMark, 264, 265-66, 283-86
firewalls and IP ports, 47-48, 140
formatting object namespace, 104
FORM element, 144, 145
<from> BizTag, 339, 340
FTP server default port, 146
functions, OmniMark, 288-89
G
generic.xsl style sheet, 110, 110, 111, 112-13
getNamedItem method, 85
GET requests, 142-44, 315, 316
GetXMLNews.xom, 162, 162-69
H
<handle> BizTag, 344, 345
hash-bang (#!) notation, 310-11, 323
Header attributes, SOAP, 381-82
<Header> element, SOAP
in message structure, 147-48
relationship to <Body> element, 383
specifying header entries in BizTalk Framework specification, 336, 338-45
specifying in SOAP W3C proposal, 378, 379, 380-82
header entries, SOAP, 336, 338-45
headerNode elements, XML, creating, 97-98
HL7 specification, 32
HTML documents. See also Hypertext Markup Language (HTML)
demonstrating how XSL works, 104
example containing FORM element, 144
PlaceOrder.htm file, 204, 226-27, 226, 227
in SOAP client applications, 150
HTTP (Hypertext Transfer Protocol). See also Web servers
and BizTalk documents, 353-57
GET method, 142-44
how it works, 142-46
overview, 142-46
security issues, 190-91
as transport protocol for delivering BizTalk documents, 190-91
HTTP binding, 353-57
HTTP Extension Framework, 405
HTTP headers, CGI programs, 317-18
HTTP packets, 145, 145
HTTP request packets, 142-43
HTTP response packets, 143-44
HTTP server default port, 146
HTTP servers, 8-10
HTTPS vs. HTTP, 146
Hypertext Markup Language (HTML). See also HTML documents
background and evolution, 134
benefits of, 35-36
limitations of, 36-37, 134-36
overview, 35-36
relationship of SGML to, 42
as W3C standard, 45
vs. XML, 11-12, 42
I
<identity> BizTag, 341
IETF (Internet Engineering Task Force), 50-51
Independent Insurance Agents of America, 53
information aggregation
car-buying example, 27-30
importance of, 136-37
limits of HTML, 134, 136
role of XML, 27-30
travel agent example, 134-36
input scopes, OmniMark, creating, 267-68
<instance> BizTag, 344-45
integer data type, OmniMark, 273
IntelliSense processor, Visual Basic, 92, 92, 93, 93
International Organization for Standardization (ISO), 43-44
Internet Engineering Task Force (IETF), 50-51
Internet Information Server (IIS), configuring to run OmniMark CGI programs, 311-12
ISO (International Organization for Standardization), 43-44
item method, XMLDOMNodeList object, 86
J
J2008 specification, 32, 53
Java, 34, 138
JavaScript, 82
joke.xsl style sheet, 114, 114-17
JScript in SOAP client applications, 148, 151, 152-54
L
length property, XMLDOMNodeList object, 86, 86
load method, 83
loadXML method, 83, 96
looping constructs, OmniMark, 282
M
macros, OmniMark, 299-301
<manifest> BizTag, 178, 338, 342-44, 350, 352
Mapper. See BizTalk Mapper
markup
processing in OmniMark, 266-67
in XML documents, 56-57
markup-error rules, OmniMark, 264
markup rules, OmniMark, 264, 267
Mehtap Enterprises, trading partner example, 256-60
messages. See BizTalk messages; SOAP messages
methods, defined, 137-38
Microsoft BizTalk home page, 366
Microsoft BizTalk Server 2000
BizTalk Editor, 244-47
BizTalk Mapper, 247-55
defined, 172-73
overview, 243-44
and trading partner relationships, 255-60
Microsoft Data Access Components (MDAC), 10-11
Microsoft Visual Basic
adding MSXML parser to project, 91, 91
and Document Object Model, 88-94
IntelliSense processor, 92, 92
making BaseballStats the startup form, 90, 90
opening BaseballStats DOM form, 90, 90
starting, 89, 89
Microsoft Windows DNA, 7
Microsoft XML DOM object, 78
middle tier, three-tier architecture, 8-18
MIME-encoded documents, 350, 351-52
MSN CarPoint Web site, 27-29
MSXML parser, 91, 91, 106
MSXML versions, 78
mustUnderstand global attribute, SOAP, 147-48, 382
N
namespaces, XML, 48-49, 66-70, 67, 69, 70-71. See also schemas
network programming in OmniMark, 303-10
newChild object, 98
NewPO.xml file, 179, 179-81, 182
news business as content provider, 18-22
News Industry Text Format (NITF) specification, 22
Newspaper Association of America (NAA), 18, 22
New York Times as content provider, 18-19
nextNode method, XMLDOMNodeList object, 86
NITF specification, 22-25, 23
NODE_ATTRIBUTE node type, 80
NODE_CDATA_SECTION node type, 80
NODE_COMMENT node type, 81
nodeDataType property, 81-82
NODE_DOCUMENT_FRAGMENT node type, 81
NODE_DOCUMENT node type, 81
NODE_DOCUMENT_TYPE node type, 81
NODE_ELEMENT node type, 80
NODE_ENTITY node type, 80
NODE_ENTITY_REFERENCE node type, 80
NodeList object, 86
nodeName property, 84
NODE_NOTATION node type, 81
NODE_PROCESSING_INSTRUCTION node type, 80
NODE_TEXT node type, 80
nodeType property, 82
n-tier architecture, 7. See also three-tier architecture
O
OASIS (Organization for the Advancement of Structured Information Standards), 31-32, 44, 367
objDocument object, 84
objects, how they work, 137-38
OmniMark
application protocol support, 303
argument file, 322, 323
catch and throw, 290-98
catching program errors, 290-92
conditional constructs, 280-81
constants, 299-301
creating input scopes, 267-68
creating output scopes, 268-70
and current input, 264, 267-68
and current output, 264, 268-70
data structures, 276-78
data types, 273-74
defined, 263
exception handling, 290-98
functions, 288-89
implementing SOAP server, 154-55
information resources, 324
input-output model, 264
I/O and variables, 275-76
locating system libraries, 314-15
looping constructs, 282
macros, 299-301
network programming, 303-10
OMX components, 270-73
operators, 283
output keyword, 275
overview, 155
pattern matching, 283-86
pattern variables, 287-88
performing financial calculations, 301-2
vs. Perl, 263
project file, 323
put keyword, 275
rule groups, 298-99
sample programs, 155, 162, 162-69, 169-70, 264-66
server errors and recovery, 308-9
set keyword, 275
simple client example, 309-10
simple server example, 304-7
as streaming programming language, 263-66
TCPConnectionGetOutput function, 272
TCPConnectionGetSource function, 272
TCPConnectionOpen function, 272
transport protocol support, 303
types of rules, 264
variables, 273-74
and XML, 266-67
OMX components, 270-73
operators, OmniMark, 283
Oracle, 10
Organization for the Advancement of Structured Information Standards (OASIS), 31-32, 44, 367
output keyword, OmniMark, 275
output scopes, OmniMark, creating, 268-70
P
parseError object, 84, 84
parsing XML documents, 78, 79, 79, 266-67
partially transmitted arrays, 401
pattern matching, OmniMark, 283-86
pattern variables, OmniMark, 287-88
Perl, 263
Personal Web Server, configuring to run OmniMark CGI programs, 312-13
PlaceOrder.htm file, 204, 226-27, 226, 227
PlaceOrder.xom file, 204, 227
.pl files, 145
PO1-2.xsl style sheet, 253, 253-54
poConfirm.asp file
code listing, 238-40
described, 238, 240-41
overview, 204
poGen.exe file
createPO_Click subroutine, 221, 222-24, 224
described, 220, 220
Form.Load subroutine, 220, 221
overview, 203
sendMsg function, 224, 225-26, 225-26
polymorphic accessors, 393
ports, IP, 146
POST requests, 144-46, 315, 316
PostScript, 51
prEnter.asp file
code listing, 209-12
described, 208, 209, 212-13
overview, 203
<process> BizTag, 178, 338, 344-45
process rules, OmniMark, 264, 265
procurement, automating, 185. See also purchase orders
properties, defined, 137
<properties> BizTag, 178, 338, 340-42, 346
prProcess.asp file
code listing, 213-16
described, 213, 213
overview, 203
PurchaseOrder1.xml file
code listing, 247
creating in BizTalk Editor, 245-46
purchase orders
BizTalk server system setup for requisition example, 207-8
confirming, 183-84, 238-41
creating schema using BizTalk Editor, 244-47
preparing in BizTalk Framework, 174-76
processing at Toy Car Parts, 226-37
processing in BizTalk Framework, 176-77
processing Toi Carz confirmations, 238-41
using BizTalk Mapper to map schemas, 248-55
put keyword, OmniMark, 275
Q
quote marks (' and "), 59
R
readyState property, 82, 83
RealServer default ports, 146
<receipt> BizTag, 346
<receiptRequiredBy> BizTag, 340, 347, 349-50
receipts, BizTalk Framework, 182-83, 346-49
Receipt.xml file, 182, 183
<receivedAt> BizTag, 347
recursive processing in XSL style sheets, 110-13
<reference> BizTag, 343, 352
referents, OmniMark, 278-80
<reliability> BizTag, 339, 340, 347, 349
Remote Procedure Calls (RPCs), using SOAP for, 406-8
reset method, XMLDOMNodeList object, 86
result trees, defined, 104
reverse auctions, 137
root attribute, SOAP, 403
root element, SOAP, 178. See also <Envelope> element, SOAP
root elements, XML, 57
ROPE (Remote Object Proxy Engine), 216-26
RTF files, 104, 105
rules, OmniMark
bundling into groups, 298-99
data-content, 264
element rules, 264, 269
find rules, 264, 265-66, 283-86
markup-error rules, 264
markup rules, 264, 267
process rules, 264
S
SAX (Simple API for XML), 102
schemas
developing, 51-53
overview, 48, 333
W3C recommendations, 71-75
XML Data Reduced (XDR), 357-62
XSD, 75, 362-63
SDL (Service Description Language), 216-26
security and HTTP protocol, 190-91
selectNodes method, 78, 87-88, 87
selectSingleNode method, 78, 87, 87
<sendReceiptTo> BizTag, 340, 347, 349
<sentAt> BizTag, 341
Services.xml file, 217, 218, 218-19
set keyword, OmniMark, 275
SGML (Structured Generalized Markup Language)
benefits of, 38-39
and DSSSL, 103-4
limitations of, 39-40
overview, 38-39
relationship of XML to, 41-42
shelves, OmniMark, 276-78
Simple Object Access Protocol. See SOAP (Simple Object Access Protocol)
Simple Object Access Protocol (SOAP) 1.1 W3C Note, 371-412
single quote marks ('), 59
slash (/), 58
SOAP (Simple Object Access Protocol)
actor global attribute, 381-82
arrays in, 393, 396-401
Body element, 147, 148, 378, 379, 382-83
building client application that requests Web service, 148-54, 149, 151
compound types, 393-403
defined, 18, 372
design goals, 375
documents as envelopes, 147-48, 178
elements of messages, 378-79
encoding style, 385-403
encodingStyle global attribute, 379-80
<Envelope> element, 178, 378, 379, 380, 409-12
examples of messages, 375-76
Fault element, 383-85
generic compound types, 402-3
Header attributes, 381-82
Header element, 147-48, 378, 379, 380-82
how it works, 139, 139, 140
HTTP example, 405-6
implementing server in OmniMark, 154-55
message exchange model, 376-77
message structure, 147-48
mustUnderstand global attribute, 147-48, 382
overview, 139, 141, 374-76
parts of, 374
proposal to W3C, 371-412
relationship between Header and Body, 383
relationship to XML, 377-78
role in BizTalk Framework, 330
role of XML in, 139
root attribute, 403
rules for encoding types in XML, 386-90
simple types, 390-93
using for RPC, 406-8
using within HTTP, 403-6
SOAPAction HTTP request header field, 404
SOAP messages
<Body> element in, 147, 148, 337-38, 378, 379, 382-83
defined, 378
description of structure, 147-48
examples from BizTalk Framework specification, 336, 337-38, 354-57
examples in SOAP W3C proposal, 375-76
<Header> element in, 147-48, 378, 379, 380-82
header entries in, 336, 338-45
overview, 147-48
SOAPServer.xom program, 155-56, 156-61
sparse arrays, 401
SPDL (Standard Page Description Language), 51
SQL Server, 10
Standard Page Description Language (SPDL), 51
standards, XML
IETF (Internet Engineering Task Force), 50-51
ISO (International Organization for Standardization), 43-44
OASIS (Organization for the Advancement of Structured Information Standards), 31-32, 44, 367
W3C (World Wide Web Consortium), 31, 37, 44-50
start tags, 57
stream data type, OmniMark, 273
streaming languages
benefits of using, 263-64
defined, 263
OmniMark as, 263-66
strings as SOAP datatype, 391-92
Structured Query Language (SQL) and XML, 10-11
style guides, 63. See also document type declarations
subscriber profiles, 8-10, 9, 11, 12, 12, 13
switch data type, OmniMark, 273
synchronous communication, 192-93
syndication partners, 18-22
T
<TAG> Newsletter, 368
TCPConnectionGetOutput function, OmniMark, 272
TCPConnectionGetSource function, OmniMark, 272
TCPConnectionOpen function, OmniMark, 272
TCP/IP (Transmission Control Protocol/Internet Protocol), 134
text property, 84
thin clients, 8
three-tier architecture
client tier, 8
data tier, 7-8
middle tier, 8-18
role of external data sites, 13-17, 14
and XML, 6-25
tightly-coupled systems, 138-39
<to> BizTag, 339
Toi Carz, Inc.
BizTalk servers example overview, 199-200
databases, 206-7, 206
description of computer programs, 203-4
process flow with Toy Car Parts Corporation, 200, 201, 202-3
processing purchase order confirmations, 238-41
requisition process with Toy Car Parts Corporation, 205
trading partner example, 256-60
<topic> BizTag, 341
Toy Car Parts Corporation
BizTalk servers example overview, 199-200
databases, 206-7, 206
description of computer programs, 204
process flow with Toi Carz, Inc., 200, 201, 202-3
processing purchase orders, 226-37
requisition process with Toy Car Parts Corporation, 205
trading partner example, 256-60
trading partners, 194, 255-60
<Transaction> element, SOAP, 147
transformation. See XSL Transformations (XSLT)
Transmission Control Protocol/Internet Protocol (TCP/IP), 134
transport protocols, OmniMark support, 303
transports, BizTalk, defined, 335
<type> BizTag, 344
U
UNIX, 138
V
variables, OmniMark
overview, 273-74
referents as, 278-80
as shelves, 276-78
Visual Basic. See Microsoft Visual Basic
W
W3C (World Wide Web Consortium), 31, 37, 44-50. See also Simple Object Access Protocol (SOAP) 1.1 W3C Note
Weather Channel as external data site example, 14-17
weather data, 14-18
weathersheet.xsl style sheet, 108, 108, 109, 110
Web browsers as thin clients, 8
Web server default port, 146
Web servers, 8-10, 9
Web services, defined, 136
Web sites
aggregation of information, 27-30, 134-37
BizTalk.org, 365-66
return traffic, 6-7
XML.com, 366-67
XML.org, 367-68
XMLSOFTWARE, 369
Windows DNA. See Microsoft Windows DNA
World Wide Web, evolution of services, 133-34, 133
World Wide Web Consortium (W3C), 31, 37, 44-50. See also Simple Object Access Protocol (SOAP) 1.1 W3C Note
X
XDR schemas
delivery header entry, 357-58
manifest header entry, 358-59
process header entry, 359
properties header entry, 358
receipt header entry, 360
SOAP 1.1 envelope for BizTalk Document, 360-61
SOAP 1.1 envelope for BizTalk Receipt, 362
XLink standard, 46-48
XML (eXtensible Markup Language)
adding document attributes, 95-97, 96
adding document elements, 97-99, 98, 99
alternative schema syntax, 72, 73, 73-75
benefits of, 40-41
case sensitivity in documents, 57
comments in documents, 61
and content aggregation, 27-30
creating documents, 94-95, 95
declarations in documents, 56
design goals for, 40
document code example, 99-100
and Document Object Model, 77-88
documents as SOAP messages, 378
and EDI, 31-34
element attributes in documents, 59-60
element names in documents, 57
element nesting in documents, 57-58
elements in documents, 57
empty elements in documents, 60-61
entity references in documents, 58-59
vs. HTML, 11-12, 42
and international trade specifications, 31-32
and Java, 34
as lingua franca, 33-34
loading documents into XRay XML Editor, 88-89, 89
myths about, 41-42
namespaces in, 48-49, 66-70, 67, 69, 70-71
newsfeed example, 148-70
and OmniMark, 266-67
open status of, 34
parsing documents, 78, 79, 79, 266-67
and processing languages, 34
relationship to HTML, 42
relationship to SGML, 41-42
relationship to SOAP, 377-78
role in e-commerce, 26, 32, 33-34
role in SOAP, 139
role of BizTalk Framework, 173-74
root elements in documents, 57
rules for SOAP encoding types, 386-90
rules for well-formed documents, 55-61
schemas, 48
schemas in, 71-75
simple SOAP types, 390-93
special characters in documents, 58-59
and SQL, 10-11
standards, 43-53
start and end tags in documents, 56-57
streaming data using OmniMark, 266-67
and three-tier architecture, 6-25
uses for, 5-6
valid document example, 62-66
W3C standards, 46-50
XML Authority, 72, 73, 244
XML.com Web site, 366-67
XML Data Reduced (XDR) syntax, 81
XMLDOMElement object, 84-85
XMLDOMNodeList object, 86
XML DOM versions, 78
XML nodes, 79-80
XML.org Web site, 367-68
XML parser, 78, 79, 79, 266-67
XML Path Language (XPath), 106
XMLSOFTWARE Web site, 369
XPointer standard, 46-48
XQL (XML Query Language), 50
XRay XML Editor, 88-89, 89, 123, 127-28
XSD schemas, 75, 362-63
XSL (Extensible Stylesheet Language)
evolution, 103-4
how it works, 104-6
overview, 103
purposes, 104
recursive processing, 110-13
role of Microsoft, 106
style sheets as well-formed document, 110
transformation functionality (See XSL Transformations (XSLT))
as W3C standard, 49-50
XSL Transformations (XSLT)
duckone.xml example, 114, 114-22, 123
how it works, 106, 107, 108
overview, 11, 106, 123, 129, 195
for transforming purchase orders from one schema to another, 123-29
using generic.xsl style sheet to process 80122.xml file, 111, 112-13, 113
using XRay, 123, 127-28
as W3C standard, 49-50
weathersheet.xsl example, 108, 108, 109, 110
Last Updated: Friday, July 6, 2001 |
