Index

A

Accounting XML, 187
ACORD XML
for life insurance, 191
for property and casualty insurance, 191
for reinsurance and large commercial, 191
Adapters, 198
Address Data Interchange Specification (ADIS), 181
Address XML, semantic vocabulary, 181
AdsML framework, 187
Advertising XML, 187
Agents, 198
Analytics, 198
Application programming interface (API), 10, 39, 198
Application routers, 62
Application server, 198–199
Application vulnerability description language (AVDL), 181
Architecture Description Markup Language (ADML), 188
Astronomy XML, 187
Atomic service, 199
Audio-video (AV) system
analogy, 36
simpler AV system, 38
software systems architecture, 16–17
AV system. See Audio-video (AV) system

B

Big data, 199
Brittleness, 26–27
Building XML, 187–188
Business intelligence (BI), 199
Business intelligence (BI)/analytics systems, 10, 59–60, 151–152
Business process, 115
analysis lane, 123–124
analyze
with decomposition matrix or other technique, 123
for services, 123–124
diagram, 116–119
Business process execution language (BPEL), 199–200
Business process modeling notation (BPMN), 200
Business process query language (BPQL), 200
Business process specification schema (BPSS), 200

C

Caching, 200
Candidate project analysis lane, 124–125
add project to candidate pool, 124–125
use force field analysis for each project, 124
use resistance issues and suggestions worksheet for each project, 124
Change issues affecting adoption, 85–88
consolidated analysis for adopting SOA with cloud computing, 102–105
forms of resistance, 88–92
feeling that jobs may be threatened, 90–91
inertia, 90
lack of training/understanding, 89
loss of familiarity, competence, and control, 91–92
not invented here, 91
our problems are special, 91
power of internal “expert,” 89–90
resistance to change, 85–88
some resistance scenarios
complicated, 95–98
elephant in room, 101–102
Guerilla tactics, 100–101
resistance issues in this scenario, 100–102
suggestions for addressing resistance, 101–102
suggestions for addressing resistance to change, 92–95
ask for participation and form partnerships, 95
communicate at many levels, 94
get resistance out in open, 94–95
Guerilla tactics, 98–100
really listen, 93–94
resistance issues in this scenario, 96–99
seek appropriate avenues to involve people, 94
selecting right people, 92–93
suggestions for addressing resistance, 99–100
suggestions for addressing resistance to change, 97–98
use second set of eyes, 93
technical change issues diminishing, 85
worksheet for resistance issues and suggestions, 102
Change management issues during development, 108
adopting semantic vocabulary, 108–109
buying a model, 108–109
change issues, encountered, 108–109
design as little as possible, 108–109
existing services, 108
methodology, 110–111
minimal coding, 109–110
new system, 108
reduce project scope, 110
second check, 111
using small teams, 111–112
Chem eStandards, 188
Chemical markup language (CML), 188
Chemistry XML, 188
City geography markup language (CityGML), 183
Clinical Data Interchange Standards Consortium (CDISC) Operational Data Model (ODM), 190
Cloud, 200–201
Cloud computing
affected by additional services of, organizations, 37
availability issues, 166–167
availability options for database management systems, 168
being self cloud provider, 170
blurring of internal and external services, 37–38
business issues, 165
categories of cloud providers, 42–44
cloud brokers, 170
data center, virtual machines/servers, 166
data center considerations, 166–167
defined, 4, 39–41
disaster recovery issues, 167
expand your internal SOA to include external services, 164–165
change issues, 165–166
staffing issues, 164
getting started with, 164
governance considerations, 165–166
high-definition television (HDTV) and smartphone connected to, 36
internal systems with cloud computing for big data store and CRM service, 77
legal issues, 165
organizations moving to cloud, 37
organizations using SOA with cloud computing, 38–39
relationship of web services, SOA and, 39
SOA basics with various combinations of, 40
stack, 43
technical forces driving adoption of. See Technical forces driving adoption
technical issues, 165–166
technical issues related to availability, examples, 167–170
database availability options, 168–169
failover options for messaging and databases, 167–168
replication options for messaging and databases, 169–170
types of, 41–42
community cloud, 41
hybrid cloud, 42
private cloud, 41–42
public cloud, 41–42
virtual private cloud, 42
Cloud providers, 40–41
categories of
infrastructure as service (IaaS), 42–43
Platform as service (PaaS), 42–43
Software as service (SaaS), 42–43
pricing, 41
Collaboration protocol profile/agreement (CPP/A), 201
Commoditizing services, 42–44
Common Data Format Markup Language (CDFML), 193
Common Object Request Broker Architecture (CORBA), 57, 59
Common Picture eXchange environment (CPXe), 193
Community cloud, 201
Composite service, 201
Computing environment XML, semantic vocabulary, 181–182
Connected representative (C.R.), 3–4
augmenting experiences, 41–42
business trip
managing, 12
services and data interchange related to, 11
business trip, services for, 171–174
detail for services and data interchange related to, 11
external expense report service used by, 39
future of C.R.’s organization, 8
including PaaS cloud provider, SaaS cloud provider, and middle-tier persistence, systems used by, 158
Connections, 18
web services, 18
Construction XML, 188
Content syndication XML, semantic vocabulary, 182
Controlled trade markup language (CTML), 185
CORBA, 29–30, 201
Customer data, keeping track of detailed, 10
Customer data warehouse creating, 139
CustomerInfoRequest, 7
Customer information XML, semantic vocabulary, 182–183
Customer relationship management (CRM) service, 6

D

Data cleansing, 61, 139, 201–202
Data element definition, 51
Data warehousing, 202
DCOM, 202
Deployment lane, 125–126
analyze parameters needed for interface, 125–126
analyze vocabulary needed for interface, 125
business process, 126
deploy services, 126
refactor services using decomposition matrix or other technique, 126
Deployment selection lane, 125
project selection with best chance of success, 125
Device independence, 41
Distributed Common Object Model (DCOM), 57
DocBook, 193–194
DOT service, 5
Driving forces, 48–51, 53

E

EbXML registry, 202
Education XML, 188
Election Markup Language (EML), 189
Electronic data interchange (EDI), 202–203
Electronic data interchange (EDI) XML, semantic vocabulary, 183
Enterprise data warehouse (EDW), 59, 138–140, 157
adopting, 59–62
creating, 138–139
Enterprise service bus (ESB), 62–67, 158, 203
for existing software systems, 65
ETL software, 61
EXtensible Access Control Markup Language (XACML), 203
EXtensible Business Reporting Language (XBRL), 188
EXtensible Customer Information Language (xCIL), 185
EXtensible Customer Relationships Language (xCRL), 185–186
EXtensible Data Format (XDF), 184–185
EXtensible Name Address Language (xNAL), 181
EXtensible rights Markup Language (XrML), 203
EXtensible Stylesheets Language (XSL), 203
External cloud, 41
Extract, Transform, and Load (ETL), 203–204

F

Failover, 204
Finance xml, 188–189
Financial information eXchange (FIX) protocol, 188
Financial products markup language (FpML), 188
Flexible Image Transport System Markup Language (FITSML), 187
FOOD XML, 189
Force field analysis, 48–50, 114
for adopting EDW, 48–50
for adopting ESB, 66
adopting SOA with cloud computing, 104
of technical issues related to, 86, 104
for adopting standard
communications protocol, 51
data element definitions, 50
enterprise-wide software, 56
of change issues related to adopting SOA, 87
defined, 41
driving forces, 48
for making system change, 49
overview, 48
restraining forces, 48
web services, for adopting, 53

G

Geography markup language (GML), 183
Geospatial XML, semantic vocabulary, 183–184
Global Justice XML Data Model (Global JXDM), 191
Global positioning system (GPS), 5
Government XML, 189–190
Guerilla tactics, 98–101

H

Healthcare XML, 190
Health Level 7 (HL7) Healthcare XML Format, 190
HR XML, 190
HTTP, 204
HumanML, 184
Human resources (HR) XML, 190
Human XML, semantic vocabulary, 184
Hybrid cloud, 204

I

Incremental SOA, change management with, 114
analyze business process for services, 123–124
analyze business process with decomposition matrix or other technique, 123
business process analysis lane, 123–124
candidate project analysis lane, 124–125
add project to candidate pool, 124–125
use force field analysis for each project, 124
use resistance issues and suggestions worksheet for each project, 124
data flow diagram, 119–121
decomposition matrix, 115–121
business process diagram, 116–119
decomposition matrix for services, 119
decomposition of services, 120
deployment lane, 125–126
analyze parameters needed for interface, 125–126
analyze vocabulary needed for interface, 125
business process, 126
deploy services, 126
refactor services using decomposition matrix or other technique, 126
deployment selection lane, 125
project selection with best chance of success, 125
force field analysis, 114
generated business process diagram, 118
incremental SOA analysis, 122–127
principles for, 121–122
modify business process, 123
tools, 114–121
vocabulary management lane, 126–127
add to organization’s semantic vocabulary, 127
develop organization-specific vocabulary, 127
review cross-industry vocabularies, 127
review industry-specific vocabularies, 126–127
worksheet for resistance issues and suggestions, 114–115
Incremental SOA analysis, 122–127
principles for, 121–122
Inertia, comfortable in current situation, 90
Information and content exchange (ICE), 182
Information technology used for business trip, 3–8
Infrastructure as a Service (IaaS), 42–43, 204
Instrument Markup Language (IML), 190
Instruments XML, 190–191
Insurance XML, 191
Interactive financial exchange (IFX), 188
Internet Inter-ORB Protocol (IIOP), 204
Intrusion detection message exchange format (IDMEF), 181

J

Java API for XML Parsing (JAXP), 204–205
JavaScript Object Notation (JSON), 28, 205
when to use, 28

L

Legal XML, 191–192
LegalXML eContracts, 191
LegalXML electronic court filing, 191
LegalXML eNotary, 191
LegalXML integrated justice, 191
LegalXML legal transcripts, 191
LegalXML legislative documents, 191–192
LegalXML Online Dispute Resolution (OdrXML), 192
LegalXML subscriber data handover interface (SDHI), 192
Load leveling, 205
Localization XML, semantic vocabulary, 184
Location independence, 41, 207–208
Loosely coupled, 205

M

Mail.XML, 181
Manufacturing XML, 192
Mapped, 205
Mapping, 205
Market data definition language (MDDL), 188–189
Mashups, 205
MathML, 184
Math XML, semantic vocabulary, 184–185
Meat and Poultry XML (mpXML) Schema, 189
Mergers and acquisitions, 53, 56–57, 69
Message routers, 54, 205–206
example transformations needed with, 64
interconnections when using, 53
mechanism, 204
Meta-object facility (MOF), 206
Middleware, 206
Model Driven Architecture (MDA), 206
Mortgage Industry Standards Maintenance Organization (MISMO), 194
Multitenancy, 41, 207–208

N

National Information Exchange Model (NIEM), 189–190
.NET, 206
News Industry Text Format (NITF), 192
NewsML, 192–193
News XML, 192–193
NoSQL database management system, 206–207

O

OBIX, 187
Object request broker (ORB), 29–30, 57, 207
adopting, 58
defined, 57
OGC web services (OWS), 183
Oil and gas XML, 193
OMG interface definition language (IDL), 207
Open applications group integration specification (OAGIS), 185
OpenDocument Format (ODF), 185
Open financial exchange (OFX) XML Schema, 189
Opengis location services (openls), 183
OpenMath, 184
Open mathematical documents (OMDoc), 184
Open office XML, 185
OpenTravel Alliance (OTA), 194

P

PapiNet, 192
Parlay X Web services, 194
Partner Interface Process (PIP), 207
Photo XML, 193
Physics XML, 193
PIDX standards, 193
Planning and scheduling language on XML specification (PSLX), 192
Platform as a Service (PaaS), 42–43, 150, 158, 207
“Plug-compatible” software components, 110
Production Planning and Scheduling (PPS), 192
PROSE/XML, 193–194
Public cloud, 207–208
Publishing Requirements for Industry Standard Markup (PRISM), 193
Publishing XML, 193–194

R

Real estate XML, 194
Real Estate Transaction Standard (RETS), 194
Real simple syndication (RSS), 182
Reduce project scope, 110
Registry, 208
REgular LAnguage Description for XML (RELAX), 208
RELAX NG, 208
Replication, 208
Representational State Transfer (REST), 22, 208–209
messaging, 23
using, 22–24
when to use, 28
Research information eXchange markup language (RIXML), 189
Resistance to change, 85–88
forms of resistance, 88–92
feeling that jobs may be threatened, 90–91
inertia, 90
lack of training/understanding, 89
loss of familiarity, competence, and control, 91–92
not invented here, 91
our problems are special, 91
power of internal “expert,” 89–90
resistance issues and suggestions worksheet, 103
suggestions for addressing, 92–95, 97–98
ask for participation and form partnerships, 95
communicate at many levels, 94
get resistance out in open, 94–95
Guerilla tactics, 98–100
really listen, 93–94
resistance issues in this scenario, 96–99
suggestions for addressing resistance, 99–100
use second set of eyes, 93
Resource Description Framework (RDF), 209
Restraining forces, 48–51, 53
affecting adoption of Web service, 52–53
redundancy of data, 61
related to data for ORB, 57–58
weakening, 49, 60
RosettaNet Implementation Framework (RNIF), 209

S

Scenarios, resistance
complicated, 95–98
elephant in room, 101–102
Guerilla tactics, 100–101
resistance issues in this scenario, 100–102
suggestions for addressing resistance, 101–102
Schematron, 209
Schools interoperability framework (SIF), 188
Security assertion markup language (SAML), 209
Semantic vocabulary, 29, 180–186
accounting XML, 187
address XML, 181
adopting, 108–109
computing environment XML, 181–182
content syndication XML, 182
customer information XML, 182–183
electronic data interchange (EDI) XML, 183
Geospatial XML, 183–184
human XML, 184
localization XML, 184
math XML, 184–185
open applications group integration specification (OAGIS), 185
open office XML, 185
opportunity and importance of, 29
topic maps XML, 185
trade XML, 185–186
translation XML, 186
universal business language (UBL), 186
universal data element framework (UDEF), 186
Service, 209
Service-oriented architecture (SOA)
adopting, 57
technical, 69
architecture in, 4
assembly of services into, 32
atomic service, 31
basics, 18
cloud, with advantage of, 37
collection of services in, 17
composite service, 31
conflict between indeterminate and operational access, 149
C.R.’s organization, systems supporting, 151
defined, 4, 15–16, 209–210
design challenge, 31
establishing, 146–150
basics for middle tier architecture, 153–154
caching performance gain, 155–156
design considerations, 146–148
expanded catching, 154–155
fast growth of data warehouse, 150–151
likely change issues, 149–150
middle-tier databases, 156–157
persistence in middle tier, 153–157
protected catching, 155
response time of services provided by internal system was inadequate, 151–157
staffing issues, 148–149
unplanned/unexpected issues, 150–157
example layers of, 160
explained, 29–33
external expense report service used by C. R., 39
getting started with, 145
governance, 161–162
history, 16
identification and design of, 30–31
interface services of, 160
keep high-volume, high-speed messages within service, 148
loosely service, 31
managing change with incremental. See Incremental SOA, change management with
overview, 17–19
relationship of web services, cloud computing and, 39
relationship of web services and, 39
services and, 157–161
sources of services in, 32
systems used by C. R.’s organization, 158
technical forces driving adoption of. See Technical forces driving adoption
two data services, 159
use with cloud computing, 38–39
using PaaS cloud provider for big data store and BI/analytics, 152
using persistent cache in middle tier, 156
Service provisioning markup language (SPML), 210
Services
atomic, 17
composite, 17
defined, 17
identification and design of, 30–31
provider and WSDL, 19–20
Shipment and Logistics Specification (SnL), 194
Simple Object Access Protocol (Soap), 20–22
alternative to. See Representational State Transfer (REST)
messaging, 23
messaging with directory, 21
using, without UDDI, 22
Small and medium-sized business XML (smbXML), 187
Smartphone
See also Virtual personal assistant (VPA)
C. R. using, 3–8
connected to cloud, HDTV and, 36
managing business trip, 3–8
SOA. See Service-oriented architecture (SOA)
Soap, 210
Software as service (SaaS), 42–43, 157, 210
adopting, 56
Specifications for publisher & agency communications exchange XML (SPACE/XML), 187
SportsML, 193
SWIFT standards, 189

T

Tax XML, 190
TCP/IP, 51
Technical forces driving adoption of cloud computing, 69
adopting platform as a service, 74–76
adopting software as a service, 72–74
service-oriented architecture with cloud computing, 76–79
of SOA, 47
adapters, 63
adopting enterprise service bus, 62–67
brittleness of fixed record exchanges, 61
data quality issues, 61
ETL software, 61
message routers, 62–63
possible connections for internal systems, 51
Technical forces driving adoption of, web services
adopting standard communications protocol, 51–52
adopting standard data element definitions, 50–51
adopting web services, 52–54
aspects of web services, 47
Telecommunications XML, 194
Topic Maps Published Subjects for Geography and Languages (GeoLang), 185
Topic maps XML, semantic vocabulary, 185
Trade XML, 185–186
Translation web services, 186
Translation XML, semantic vocabulary, 186
Travel XML, 194
Tree Regular Expressions for XML (TREX), 210–211

U

Unified Modeling Language (UML), 211
Uniform Resource Identifier (URI), 211
Universal business language (UBL), 186
Universal data element framework (UDEF), 186
Universal data models, 108, 211
Universal description, discovery, and integration (UDDI), 20, 211
using SOAP without UDDI, 22

V

Virtualization, 41
Virtual personal assistant (VPA), 10
advantages, 7–8
application programming interfaces (API), 5
C.R. using, 4
defined, 4
GPS of, 5
information request by C.R., 6
meetings and messages, 4–5
work mechanism, 4–5
Virtual private cloud, 13, 42, 211–212
Vocabulary management lane, 126–127
add to organization’s semantic vocabulary, 127
develop organization-specific vocabulary, 127
review cross-industry vocabularies, 127
review industry-specific vocabularies, 126–127

W

Web application security (WAS), 182
Web-based enterprise management (WBEM) initiative, 181–182
Web Distributed Data Exchange (WDDX), 212
Web Service Endpoint Definition (WSEL), 212
Web services, 4, 15–16
adapters, 67
adapt existing systems to use, 138–142
additional systems, 141–142
change issues, 142
connect components to web services, 140–142
enterprise database warehouse, 138–140
staffing issues, 142
add additional systems, 141
all connections look same, 132
basics, 153
component model, 212
connect data warehouse and internal system with, 151
display content on webpage
using external service to, 159
using internal service to, 40
drive to use, effect of, 26
to exchange data, 50
exchange data between existing systems, 135–136
explained, 10
getting started, 132
history of specification, 19
impact of, 132–133
likely change issues, 137–138
relationship of cloud computing, service-oriented architecture (SOA) and, 39
and service-oriented architectures, 3
Soap messages sent using, 7
specifications, 22–29
staffing issues, 137
standards, establishment, 4
start by experimenting with, 133–138
develop external service, 134–135
use external service, 132
technical forces driving adoption of. See Technical forces driving adoption
use of, 133
using ESB, 136–137
Web services conversation language (WSCL), 212
Web services description language (WSDL), 19, 212–213
Web services distributed management (WSDM), 182
Web services flow language (WSFL), 213
Web services for Interactive Applications (WSIA), 213
Web Services for Report Portals (WSRP), 213–214
Web Services user Interface (WSUI), 214
Workflow, 214

X

XLANG, 214
XML, 24–28
adding new element, 25
alternative. See JSON
brittleness of fixed record messages, 27
copying wrong data using fixed records, 27
effect of change, 26–27
example of resilience provided by tagged messages, 25
fixed record format, 26
record content changes without changing length record, 26
vocabularies, 29
vs. JSON, 28–29
when to use, 28
XML Book Industry Transaction Standards (XBITS), 213
XML common biometric format (XCBF), 214
XML/EDI, 183
XML encryption, 214
XML key management specification (XKMS), 194
XML linking language (XLink), 215
XML Localization Interchange File Format (XLIFF), 184
XML namespaces, 215
XML path language, 215
XML pointer language (XPointer), 215
XML protocol (XMLP), 215
XML schema, 216
XML signature, 216
XQuery, 216
XSL formatting objects (XSL-FO), 216
XSL transformations (XLST), 216