Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
2) XML & SOAP
XML & SOAP
| Question | Answer |
|---|---|
| XML | Extensible Markup Language XML is a software- and hardware-independent tool for storing and transporting data. |
| XML element | An element is a sequence of characters that begins with a start tag and ends with an end tag and includes everything in between |
| XML content | The characters in between the tags (rendered in green in this presentation) constitute the content |
| root element | The topmost element of the XML document is a single element which we see in the first line. |
| nested elements | Elements contained in other elements |
| attribute specification | a name–value pair that is associated with an element. |
| XML Namespaces | When using prefixes in XML, a namespace for the prefix must be defined. The namespace can be defined by an xmlns attribute in the start tag of an element. The namespace declaration has the following syntax. xmlns:prefix="URI". |
| XML schema | defines the legal building blocks of an XML document: the elements and attributes that can appear the number of (and order of) child elements data types for elements^attribs default and fixed values for elements&attribs |
| XML schema supports meta data characteristics | structural relationships, cardinality, valid values, and data types. |
| XSD | XML Schema Definition, the file extension of the schema definition files |
| attributeGroup | group of schema attributes that can be included in an attribute group |
| sequence schema element | The sequence element specifies that the child elements must appear in a sequence. Each child element can occur from 0 to any number of times. |
| XML naming rules | names are are 1) case-sensitive, 2) must start with a letter or underscore, 3) cannot start with the letters xml (or XML, or Xml, etc) 4) can contain letters, digits, hyphens, underscores, and periods 5) cannot contain spaces |
| avoid XML attributes? | attributes cannot contain multiple values (elements can) attributes cannot contain tree structures (elements can) attributes are not easily expandable (for future changes) |
| prefix | Name conflicts in XML can easily be avoided using a name prefix. <h:table> <f:table> |
| Document Object Model (DOM) | The W3C Document Object Model (DOM) is a platform and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure, and style of a document. |
| Simple Element | A simple element is an XML element that can contain only text. It cannot contain any other elements or attributes. <xs:element name="childname" type="xs:string" maxOccurs="unbounded"/> |
| Complex Type | Simple elements cannot have attributes. If an element has attributes, it is considered to be of a complex type. But the attribute itself is always declared as a simple type. |
| How to extend a complex type | 1) declare the type <xs:element name="employee" type="fullpersoninfo"/> 2) declare a complex type <xs:complexType name="personinfo"> 3) <xs:complexType name="fullpersoninfo"> <xs:complexContent> <xs:extension base="personinfo"> |
| Declare a reusable complex type | <xs:element name="employee" type="fullpersoninfo"/> |
| Extend a complex type | <xs:complexType name="fullpersoninfo"> <xs:complexContent> <xs:extension base="personinfo"> |
| Declare a complex type | <xs:element name="children"> <xs:complexType (if the name="children", reusable type")> <xs:sequence> <xs:element name="childname" type="xs:string" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> |
| SOAP | SOAP (Simple Object Access Protocol) provides a way to communicate between applications running on different operating systems, with different technologies and programming languages. |
| XSLT | eXtensible Stylesheet Language Transform The XSLT process transforms an XML structure into presentation technology such as HTML or into any other required forms and structures |
| SOAP Building Blocks | XML document containing the following elements: An Envelope element that identifies the XML document as a SOAP message A Header element that contains header information A Body element A Fault element containing errors and status information |
| XPath | XPath is an abstract language that defines a tree model that codifies the logical structure of an XML document against which all expressions are evaluated |
| CORBA | Common Object Request Broker Architecture is a standard, enables communication between software written in different languages and running on different computers |
| DCOM | Distributed Component Object Model (DCOM) is a proprietary Microsoft technology for communication among software components distributed across networked computers. |
| SOAP's primary application | SOAP is the standard messaging protocol used by Web services. SOAP’s primary application is inter application communication. SOAP codifies the use of XML as an encoding scheme for request and response parameters using HTTP as a means for transport |
| SOAP as lightweight protocol | SOAP is a lightweight protocol that allows applications to pass messages and data back and forth between disparate systems in a distributed environment, enabling remote method invocation |
| SOAP messages | A SOAP message consists of an <Envelope> element containing an optional <Header> and a mandatory <Body> element. The contents of these elements are application defined and not a part of the SOAP specifications. Either application-specific data or a fault |
| SOAP Envelope Element | The required SOAP Envelope element is the root element of a SOAP message. Defines the XML document as a SOAP message. <soap:Envelope xmlns:soap=" |
| The encodingStyle Attribute | The encodingStyle attribute is used to define the data types used in the document. This attribute may appear on any SOAP element, and applies to the element's contents and all child elements. |
| The SOAP Body | The SOAP body is the area of the SOAP message, where the application specific XML data (payload) being exchanged in the message is placed The <Body> element must be present and is an immediate child of the envelope. |
| Application-specific data | Application-specific data is the information that is exchanged with a Web service. |
| SOAP Communication Model | Encoding style are about how applications on different platforms share and exchange data, although they may have different data types SOAP supports two possible communication styles: – remote procedure call (RPC) and – document (or message). |
| SOAP Fault element | It distinguishes between the conditions that result in a fault, and the ability to signal that fault to the originator of the faulty message or another node. The SOAP <Body> is the place where fault information is placed |
| SOAP Advantages | – Simplicity: highly-structured format of XML – Portability: No dependencies on underlying platform – Firewall friendliness: By posting data over HTTP – Useofopenstandards:text-basedXMLstandard – Interoperability (XML and HTTP) – Universal acceptance |
| SOAP Disadvantages | – Too much reliance on HTTP: bad performance – Statelessness: difficult for transactional and business processing applications – Serialization by value and not by reference: impossible to refer or point to external data source |
Created by:
timeakiss
Popular Computers sets