Explore topic-wise InterviewSolutions in .

The same rule applies as for server-side inclusions, so you NEED to ensure that any embedded code which gets passed to a third-party engine (eg calls to SQL, VB, Java, etc) does not contain any characters which might be misinterpreted as XML markup (ie no angle brackets or ampersands). EITHER USE a CDATA marked section to avoid your XML application PARSING the embedded code, or use the standard <, and & character entity references instead.

The same rule applies as for server-side inclusions, so you need to ensure that any embedded code which gets passed to a third-party engine (eg calls to SQL, VB, Java, etc) does not contain any characters which might be misinterpreted as XML markup (ie no angle brackets or ampersands). Either use a CDATA marked section to avoid your XML application parsing the embedded code, or use the standard <, and & character entity references instead.

Yes, so long as what they generate ends up as part of an XML-conformant file (ie either valid or just well-formed). Server-side tag-replacers LIKE SHTML, PHP, JSP, ASP, Zope, etc store almost-valid files USING comments, Processing Instructions, or non-XML markup, which gets replaced at the point of service by text or XML markup (it is unclear why some of these systems use non-HTML/XML markup). There are also some XML-based preprocessors for formats like XVRL (eXtensible Value Resolution Language) which resolve SPECIALISED references to EXTERNAL data and output a normalised XML file.

Yes, so long as what they generate ends up as part of an XML-conformant file (ie either valid or just well-formed). Server-side tag-replacers like shtml, PHP, JSP, ASP, Zope, etc store almost-valid files using comments, Processing Instructions, or non-XML markup, which gets replaced at the point of service by text or XML markup (it is unclear why some of these systems use non-HTML/XML markup). There are also some XML-based preprocessors for formats like XVRL (eXtensible Value Resolution Language) which resolve specialised references to external data and output a normalised XML file.

An XML namespace is a COLLECTION of element type and attribute names. The collection itself is unimportant — in fact, a reasonable argument can be MADE that XML namespaces don’t actually exist as physical or CONCEPTUAL entities . What is important is the name of the XML namespace, which is a URI. This allows XML namespaces to provide a two-part naming SYSTEM for element types and attributes. The first part of the name is the URI used to identify the XML namespace – the namespace name. The second part is the element type or attribute name itself — the local part, also known as the local name. Together, they form the universal name. This two-part naming system is the only thing defined by the XML namespaces recommendation.

An XML namespace is a collection of element type and attribute names. The collection itself is unimportant — in fact, a reasonable argument can be made that XML namespaces don’t actually exist as physical or conceptual entities . What is important is the name of the XML namespace, which is a URI. This allows XML namespaces to provide a two-part naming system for element types and attributes. The first part of the name is the URI used to identify the XML namespace – the namespace name. The second part is the element type or attribute name itself — the local part, also known as the local name. Together, they form the universal name. This two-part naming system is the only thing defined by the XML namespaces recommendation.

No.
If an element TYPE or attribute name is not specifically declared to be in an XML NAMESPACE — that is, it is unprefixed and (in the CASE of element type names) there is no default XML namespace — then that name is not in any XML namespace. If you want, you can think of it as having a null URI as its name, although no “null” XML namespace actually exists. For example, in the following, the element type name B and the attribute names C and E are not in any XML namespace:
&LT;google:A xmlns:google=”http://www.google.org/”>
<B C=”bar”/>
<google:D E=”bar”/>
</google:A>

No.
If an element type or attribute name is not specifically declared to be in an XML namespace — that is, it is unprefixed and (in the case of element type names) there is no default XML namespace — then that name is not in any XML namespace. If you want, you can think of it as having a null URI as its name, although no “null” XML namespace actually exists. For example, in the following, the element type name B and the attribute names C and E are not in any XML namespace:
<google:A xmlns:google=”http://www.google.org/”>
<B C=”bar”/>
<google:D E=”bar”/>
</google:A>

Although the XML 1.0 recommendation anticipated the need for XML NAMESPACES by noting that ELEMENT type and ATTRIBUTE names should not include colons, it did not actually support XML namespaces. THUS, XML namespaces are LAYERED on top of XML 1.0. In particular, any XML document that uses XML namespaces is a legal XML 1.0 document and can be interpreted as such in the absence of XML namespaces.

Although the XML 1.0 recommendation anticipated the need for XML namespaces by noting that element type and attribute names should not include colons, it did not actually support XML namespaces. Thus, XML namespaces are layered on top of XML 1.0. In particular, any XML document that uses XML namespaces is a legal XML 1.0 document and can be interpreted as such in the absence of XML namespaces.

There are only two differences between XML namespaces 1.0 and XML namespaces 1.1:
* Version 1.1 adds a WAY to undeclare PREFIXES. For more information,
* Version 1.1 uses IRIs (Internationalized Resource IDENTIFIERS) INSTEAD of URIs. Basically, URIs are restricted to a subset of ASCII characters, while IRIs ALLOW much broader use of Unicode characters.

There are only two differences between XML namespaces 1.0 and XML namespaces 1.1:
* Version 1.1 adds a way to undeclare prefixes. For more information,
* Version 1.1 uses IRIs (Internationalized Resource Identifiers) instead of URIs. Basically, URIs are restricted to a subset of ASCII characters, while IRIs allow much broader use of Unicode characters.

You can DECLARE an XML NAMESPACE on any ELEMENT in an XML document. The namespace is in scope for that element and all its DESCENDANTS UNLESS it is overridden.

You can declare an XML namespace on any element in an XML document. The namespace is in scope for that element and all its descendants unless it is overridden.

To OVERRIDE the prefix USED in an XML namespace declaration, you simply declare ANOTHER XML namespace with the same prefix. For example, in the following, the google prefix is associated with the http://www.google.org/ namespace on the A and B elements and the http://www.bar.org/ namespace on the C and D elements. That is, the NAMES A and B are in the http://www.google.org/ namespace and the names C and D are in the http://www.bar.org/ namespace.
<google:A xmlns:google=”http://www.google.org/”>
<google:B>
<google:C xmlns:google=”http://www.bar.org/”>
<google:D>abcd</google:D>
</google:C>
</google:B>
</google:A>
In general, this leads to documents that are confusing to read and should be avoided.

To override the prefix used in an XML namespace declaration, you simply declare another XML namespace with the same prefix. For example, in the following, the google prefix is associated with the http://www.google.org/ namespace on the A and B elements and the http://www.bar.org/ namespace on the C and D elements. That is, the names A and B are in the http://www.google.org/ namespace and the names C and D are in the http://www.bar.org/ namespace.
<google:A xmlns:google=”http://www.google.org/”>
<google:B>
<google:C xmlns:google=”http://www.bar.org/”>
<google:D>abcd</google:D>
</google:C>
</google:B>
</google:A>
In general, this leads to documents that are confusing to read and should be avoided.

To override the CURRENT default XML NAMESPACE, you simply declare another XML namespace as the default. For EXAMPLE, in the following, the default XML namespace is the http://www.google.org/ namespace on the A and B elements and the http://www.bar.org/ namespace on the C and D elements. That is, the names A and B are in the http://www.google.org/ namespace and the names C and D are in the http://www.bar.org/ namespace.
<A xmlns=”http://www.google.org/”>
<B>
<C xmlns=”http://www.bar.org/”>
<D>abcd</D>
</C>
</B>
</A>
Using multiple default XML namespaces can lead to documents that are confusing to read and should be done carefully.

To override the current default XML namespace, you simply declare another XML namespace as the default. For example, in the following, the default XML namespace is the http://www.google.org/ namespace on the A and B elements and the http://www.bar.org/ namespace on the C and D elements. That is, the names A and B are in the http://www.google.org/ namespace and the names C and D are in the http://www.bar.org/ namespace.
<A xmlns=”http://www.google.org/”>
<B>
<C xmlns=”http://www.bar.org/”>
<D>abcd</D>
</C>
</B>
</A>
Using multiple default XML namespaces can lead to documents that are confusing to read and should be done carefully.

There are literally thousands of applications that can BENEFIT from XML TECHNOLOGIES. The point of this question is not to have the candidate rattle off a laundry list of projects that they have worked on, but, rather, to allow the candidate to explain the rationale for choosing XML by citing a few real world examples. For instance, one appropriate answer is that XML allows content management systems to store documents independently of their format, which thereby reduces data redundancy. Another answer relates to B2B exchanges or supply chain management systems. In these instances, XML provides a MECHANISM for multiple companies to exchange data ACCORDING to an AGREED upon set of rules. A third common response involves wireless applications that require WML to render data on hand held devices.

There are literally thousands of applications that can benefit from XML technologies. The point of this question is not to have the candidate rattle off a laundry list of projects that they have worked on, but, rather, to allow the candidate to explain the rationale for choosing XML by citing a few real world examples. For instance, one appropriate answer is that XML allows content management systems to store documents independently of their format, which thereby reduces data redundancy. Another answer relates to B2B exchanges or supply chain management systems. In these instances, XML provides a mechanism for multiple companies to exchange data according to an agreed upon set of rules. A third common response involves wireless applications that require WML to render data on hand held devices.

Even if CANDIDATES have never participated in a project involving this type of architecture, they should recognize it as one of the common uses of XML. Querying a database and then FORMATTING the result set so that it can be validated as an XML document allows developers to translate the data into an HTML table using XSLT rules. Consequently, the format of the resulting HTML table can be modified without CHANGING the database QUERY or application code since the document rendering logic is isolated to the XSLT rules.

Even if candidates have never participated in a project involving this type of architecture, they should recognize it as one of the common uses of XML. Querying a database and then formatting the result set so that it can be validated as an XML document allows developers to translate the data into an HTML table using XSLT rules. Consequently, the format of the resulting HTML table can be modified without changing the database query or application code since the document rendering logic is isolated to the XSLT rules.

ORACLE deals with Null values using NVL function. The function replaces the NULL value in the given column with the value PROVIDE to it. The function accepts two parameters, the first one is the column NAME and the second one is the value with which NULL has to be replaced.
Example
Select Amount – NVL(Disc, 0) from PRICE

Oracle deals with Null values using NVL function. The function replaces the NULL value in the given column with the value provide to it. The function accepts two parameters, the first one is the column name and the second one is the value with which NULL has to be replaced.
Example
Select Amount – NVL(Disc, 0) from Price

IS NULL operator is USUALLY USED to check if a COLUMNS value is NULL or not.

IS NULL operator is usually used to check if a columns value is NULL or not.

LIKE in oracle ENABLES the user to search for a string of the MATCHING type. “%” is used as a WILD card in the QUERY.

LIKE in oracle enables the user to search for a string of the matching type. “%” is used as a wild card in the query.

IN OPERATOR in a query ALLOWS you to have multiple VALUES in a WHERE clause.

IN operator in a query allows you to have multiple values in a WHERE clause.

There are four TYPES of segments used in ORACLE DATABASES:
- data segments
- index segments
- ROLLBACK segments
- TEMPORARY segments

There are four types of segments used in Oracle databases:
- data segments
- index segments
- rollback segments
- temporary segments

Application layer and transport layers of a network are USED by SOAP. SMTP and HTTP are the valid application layer protocol USES as transport for SOAP. Wider acceptance is gained by HTTP, as it works BETTER with the current internet infrastructure, especially with firewalls.

Application layer and transport layers of a network are used by SOAP. SMTP and HTTP are the valid application layer protocol uses as transport for SOAP. Wider acceptance is gained by HTTP, as it works better with the current internet infrastructure, especially with firewalls.

Remote methods over multiple platforms and technologies are used with HTTP. SOAP is XML based PROTOCOL and platform-agnostic. Each application USES different technology. This may cause problems with proxy server and firewalls. SOAP is the solution for this situation.

Industries transport the request for FINDING best route and best cost price. So the application transfers a request to other similar SERVICES which uses SOAP.

Remote methods over multiple platforms and technologies are used with HTTP. SOAP is XML based protocol and platform-agnostic. Each application uses different technology. This may cause problems with proxy server and firewalls. SOAP is the solution for this situation.

Industries transport the request for finding best route and best cost price. So the application transfers a request to other similar services which uses SOAP.

SOAP is the acronym for Simple Object Access Protocol. XML based messages over a NETWORK of computers are exchanged by using SOAP standard, using HTTP.
SOAP purpose:
A web service needs a combination of XML, HTTP and a protocol which is application-specific. A web service uses XML data for exchanging. The WEATHER service, stock quote service, look up service of postal DEPARTMENT are all sending XML messages and receiving an XML reply. This is the pattern that dominates the web services. To perform these web services, SOAP is the reliable protocol. 

SOAP is the acronym for Simple Object Access Protocol. XML based messages over a network of computers are exchanged by using SOAP standard, using HTTP.
SOAP purpose:
A web service needs a combination of XML, HTTP and a protocol which is application-specific. A web service uses XML data for exchanging. The weather service, stock quote service, look up service of postal department are all sending XML messages and receiving an XML reply. This is the pattern that dominates the web services. To perform these web services, SOAP is the reliable protocol. 

The easiest way to get started with Web services is to learn XML-RPC. Check out the XML-RPC SPECIFICATION or read my book, Web Services ESSENTIALS. O'Reilly has also recently RELEASED a book on Programming Web Services with XML-RPC by Simon St.Laurent, Joe Johnston, and Edd Dumbill.

Once you have learned the basics of XML-RPC, move ONTO SOAP, WSDL, and UDDI. These topics are also covered in Web Services Essentials. For a comprehensive treatment of SOAP, check out O'Reilly's Programming Web Services with SOAP, by Doug Tidwell, JAMES Snell, and Pavel Kulchenko.

The easiest way to get started with Web services is to learn XML-RPC. Check out the XML-RPC specification or read my book, Web Services Essentials. O'Reilly has also recently released a book on Programming Web Services with XML-RPC by Simon St.Laurent, Joe Johnston, and Edd Dumbill.

Once you have learned the basics of XML-RPC, move onto SOAP, WSDL, and UDDI. These topics are also covered in Web Services Essentials. For a comprehensive treatment of SOAP, check out O'Reilly's Programming Web Services with SOAP, by Doug Tidwell, James Snell, and Pavel Kulchenko.

The World Wide WEB Consortium (W3C) is actively pursuing standardization of Web service protocols. In September 2000, the W3C established an XML Protocol Activity. The GOAL of the group is to establish a formal standard for SOAP. A draft version of SOAP 1.2 is currently under review, and PROGRESSING through the official W3C recommendation process.

On January 25, 2002, the W3C also announced the formation of a Web Service Activity. This new activity will include the current SOAP work as well as two new groups. The first new group is the Web SERVICES Description Working Group, which will take up work on WSDL. The second new group is the Web Services Architecture Working Group, which will attempt to CREATE a cohesive framework for Web service protocols.

The World Wide Web Consortium (W3C) is actively pursuing standardization of Web service protocols. In September 2000, the W3C established an XML Protocol Activity. The goal of the group is to establish a formal standard for SOAP. A draft version of SOAP 1.2 is currently under review, and progressing through the official W3C recommendation process.

On January 25, 2002, the W3C also announced the formation of a Web Service Activity. This new activity will include the current SOAP work as well as two new groups. The first new group is the Web Services Description Working Group, which will take up work on WSDL. The second new group is the Web Services Architecture Working Group, which will attempt to create a cohesive framework for Web service protocols.

RPC is very friendly in implementing the client to server INTERACTION model which makes it very prominent. When the server is interacting and searching for information the client side MESSAGING is blocked and server activity goes on. RPC has huge pool of protocols which at TIMES make it difficult to WORK with. Client server interaction can be best ACHIEVED by RPC.

RPC is very friendly in implementing the client to server interaction model which makes it very prominent. When the server is interacting and searching for information the client side messaging is blocked and server activity goes on. RPC has huge pool of protocols which at times make it difficult to work with. Client server interaction can be best achieved by RPC.

To “UNDECLARE” the DEFAULT XML namespace, you declare a default XML namespace with an empty (zero-length) NAME (URI). Within the scope of this declaration, unprefixed element type names do not belong to any XML namespace. For example, in the following, the default XML namespace is the http://www.google.org/ for the A and B ELEMENTS and there is no default XML namespace for the C and D elements. That is, the names A and B are in the http://www.google.org/ namespace and the names C and D are not in any XML namespace.
<A xmlns=”http://www.google.org/”&GT;
<B>
<C xmlns=”">
<D>abcd</D>
</C>
</B>
</A>

To “undeclare” the default XML namespace, you declare a default XML namespace with an empty (zero-length) name (URI). Within the scope of this declaration, unprefixed element type names do not belong to any XML namespace. For example, in the following, the default XML namespace is the http://www.google.org/ for the A and B elements and there is no default XML namespace for the C and D elements. That is, the names A and B are in the http://www.google.org/ namespace and the names C and D are not in any XML namespace.
<A xmlns=”http://www.google.org/”>
<B>
<C xmlns=”">
<D>abcd</D>
</C>
</B>
</A>

The scope of an XML namespace declaration is that part of an XML document to which the declaration applies. An XML namespace declaration remains in scope for the element on which it is declared and all of its DESCENDANTS, unless it is OVERRIDDEN or UNDECLARED on ONE of those descendants.

The scope of an XML namespace declaration is that part of an XML document to which the declaration applies. An XML namespace declaration remains in scope for the element on which it is declared and all of its descendants, unless it is overridden or undeclared on one of those descendants.

XML namespace DECLARATIONS that are MADE on the root ELEMENT are in scope for all elements and attributes in the document. This means that an easy WAY to declare XML namespaces is to declare them only on the root element.

XML namespace declarations that are made on the root element are in scope for all elements and attributes in the document. This means that an easy way to declare XML namespaces is to declare them only on the root element.

No.
XML NAMESPACES can be declared only on elements and their scope consists only of those elements and their DESCENDANTS. Thus, the scope can never INCLUDE the DTD.

No.
XML namespaces can be declared only on elements and their scope consists only of those elements and their descendants. Thus, the scope can never include the DTD.

No.
In particular, an xmlns attribute DECLARED in the DTD with a default is not an XML NAMESPACE DECLARATION for the DTD.. (Note that an earlier version of MSXML (the parser USED by Internet Explorer) did USE such declarations as XML namespace declarations, but that this was removed in MSXML 4.

No.
In particular, an xmlns attribute declared in the DTD with a default is not an XML namespace declaration for the DTD.. (Note that an earlier version of MSXML (the parser used by Internet Explorer) did use such declarations as XML namespace declarations, but that this was removed in MSXML 4.

Yes.
For example, the following is legal:
<!ELEMENT google:A (google:B)>
<!ATTLIST google:A
google:C CDATA #IMPLIED>
<!ELEMENT google:B (#PCDATA)>

However, because XML namespace declarations do not APPLY to DTDs , qualified NAMES in the DTD cannot be converted to universal names.

As a result, qualified names in the DTD have no SPECIAL meaning.

For example, google:A is just google:A — it is not A in the XML namespace to which the prefix google is mapped.

The reason qualified names are allowed in the DTD is so that validation will continue to work.

Yes.
For example, the following is legal:
<!ELEMENT google:A (google:B)>
<!ATTLIST google:A
google:C CDATA #IMPLIED>
<!ELEMENT google:B (#PCDATA)>

However, because XML namespace declarations do not apply to DTDs , qualified names in the DTD cannot be converted to universal names.

As a result, qualified names in the DTD have no special meaning.

For example, google:A is just google:A — it is not A in the XML namespace to which the prefix google is mapped.

The reason qualified names are allowed in the DTD is so that validation will continue to work.

The same as you create documents that don’t use XML namespaces. If you’re CURRENTLY using Notepad on Windows or emacs on LINUX, you can CONTINUE using Notepad or emacs. If you’re using an XML editor that is not namespace-aware, you can also continue to use that, as qualified names are legal names in XML documents and xmlns attributes are legal attributes. And if you’re using an XML editor that is namespace-aware, it will probably provide FEATURES such as automatically declaring XML namespaces and keeping TRACK of prefixes and the default XML namespace for you.

The same as you create documents that don’t use XML namespaces. If you’re currently using Notepad on Windows or emacs on Linux, you can continue using Notepad or emacs. If you’re using an XML editor that is not namespace-aware, you can also continue to use that, as qualified names are legal names in XML documents and xmlns attributes are legal attributes. And if you’re using an XML editor that is namespace-aware, it will probably provide features such as automatically declaring XML namespaces and keeping track of prefixes and the default XML namespace for you.

From a document author’s perspective, this is GENERALLY not a RELEVANT question. Most XML documents are WRITTEN in a specific XML language and processed by an application that understands that language. If the language USES an XML namespace, then the application will already use that namespace — there is no need for any special XML namespace software.

From a document author’s perspective, this is generally not a relevant question. Most XML documents are written in a specific XML language and processed by an application that understands that language. If the language uses an XML namespace, then the application will already use that namespace — there is no need for any special XML namespace software.

Applications process documents that use XML NAMESPACES in almost exactly the same way they process documents that don’t use XML namespaces. For example, if a namespace-unaware APPLICATION adds a new sales order to a database when it encounters a Sales Order element, the equivalent namespace-aware application does the same. The only difference is that the namespace-aware application:
* Might need to check for xmlns ATTRIBUTES and parse qualified names. WHETHER it does this depends on whether such processing is ALREADY done by lower-level software, such as a namespace-aware DOM implementation.
* Uses universal (two-part) names instead of local (one-part) names.

Applications process documents that use XML namespaces in almost exactly the same way they process documents that don’t use XML namespaces. For example, if a namespace-unaware application adds a new sales order to a database when it encounters a Sales Order element, the equivalent namespace-aware application does the same. The only difference is that the namespace-aware application:
* Might need to check for xmlns attributes and parse qualified names. Whether it does this depends on whether such processing is already done by lower-level software, such as a namespace-aware DOM implementation.
* Uses universal (two-part) names instead of local (one-part) names.

SAX 2.0 primarily supports XML NAMESPACES through the following methods: * startElement and endElement in the ContentHandler interface RETURN namespace NAMES (URIs) and local names as well as qualified names. * getValue, getType, and getIndex in the Attributes interface can retrieve attribute information by namespace name (URI) and local name as well as by qualified name.

SAX 2.0 primarily supports XML namespaces through the following methods: * startElement and endElement in the ContentHandler interface return namespace names (URIs) and local names as well as qualified names. * getValue, getType, and getIndex in the Attributes interface can retrieve attribute information by namespace name (URI) and local name as well as by qualified name.

Yes.
This is a common situation for generic applications, such as EDITORS, browsers, and parsers, that are not wired to understand a particular XML language. Such applications SIMPLY treat all element type and attribute NAMES as qualified names. Those names that are not mapped to an XML namespace — that is, unprefixed element type names in the absence of a default XML namespace and unprefixed attribute names — are simply processed as one-part names, such as by using a null XML namespace NAME (URI).

Yes.
This is a common situation for generic applications, such as editors, browsers, and parsers, that are not wired to understand a particular XML language. Such applications simply treat all element type and attribute names as qualified names. Those names that are not mapped to an XML namespace — that is, unprefixed element type names in the absence of a default XML namespace and unprefixed attribute names — are simply processed as one-part names, such as by using a null XML namespace name (URI).

Yes.
However, there is generally no reason to do this. The reason is that most applications understand a particular XML LANGUAGE, such as one used to TRANSFER sales orders between companies. If the element type and attribute names in the language belong to an XML namespace, the application must be namespace-aware; if not, the application must be namespace-unaware.

For a few applications, being both namespace-aware and namespace-unaware makes sense. For example, a parser might choose to redefine VALIDITY in terms of universal names and have both namespace-aware and namespace-unaware validation modes. However, such applications are uncommon.

Yes.
However, there is generally no reason to do this. The reason is that most applications understand a particular XML language, such as one used to transfer sales orders between companies. If the element type and attribute names in the language belong to an XML namespace, the application must be namespace-aware; if not, the application must be namespace-unaware.

For a few applications, being both namespace-aware and namespace-unaware makes sense. For example, a parser might choose to redefine validity in terms of universal names and have both namespace-aware and namespace-unaware validation modes. However, such applications are uncommon.

The XML NAMESPACES RECOMMENDATION does not specify what a namespace-aware application does when it encounters a document that does not conform to the recommendation. Therefore, the behavior is application-dependent.

For example, the application could stop processing, POST an error to a log and continue processing, or IGNORE the error.

The XML namespaces recommendation does not specify what a namespace-aware application does when it encounters a document that does not conform to the recommendation. Therefore, the behavior is application-dependent.

For example, the application could stop processing, post an error to a log and continue processing, or ignore the error.

A qualified name is a name of the FOLLOWING FORM. It consists of an optional PREFIX and colon, FOLLOWED by the local part, which is SOMETIMES known as a local name.
prefix:local-part
–OR–
local-part

A qualified name is a name of the following form. It consists of an optional prefix and colon, followed by the local part, which is sometimes known as a local name.
prefix:local-part
–OR–
local-part

An XML namespace prefix is a prefix used to SPECIFY that a LOCAL element TYPE or ATTRIBUTE name is in a particular XML namespace.

An XML namespace prefix is a prefix used to specify that a local element type or attribute name is in a particular XML namespace.

Yes.

Yes.

If a default XML NAMESPACE declaration is in SCOPE, then the element type name is in the default XML namespace. OTHERWISE, the element type name is not in any XML namespace.

If a default XML namespace declaration is in scope, then the element type name is in the default XML namespace. Otherwise, the element type name is not in any XML namespace.

An XML NAMESPACE name is a URI that uniquely identifies the namespace. URIS are used because they are WIDELY UNDERSTOOD and well documented. Because people may only allocate URIs under their control, it is easy to ensure that no two XML namespaces are identified by the same URI.

An XML namespace name is a URI that uniquely identifies the namespace. URIs are used because they are widely understood and well documented. Because people may only allocate URIs under their control, it is easy to ensure that no two XML namespaces are identified by the same URI.

YES. HOWEVER, such USAGE is DEPRECATED, so you should NEVER do it.

Yes. However, such usage is deprecated, so you should never do it.

Yes.

Yes.

You can use the XPointer Framework with non-XML resources. This is especially effective when your resource is BACKED by some KIND of a DBMS, or when you want to QUERY a data model, such as RDF, and not the XML syntax of a representation of that data model. However, please note that the authoratitive interpretation of the fragment IDENTIFIER is determined by the Internet Media Type. If you want to opt-in for XPointer, then you can always create publish your own Internet Media Type with IANA and specify that it supports the XPointer Framework for some kind of non-XML resource. In this case, you are GOING to need to declare your own XPointer schemes as well.

You can use the XPointer Framework with non-XML resources. This is especially effective when your resource is backed by some kind of a DBMS, or when you want to query a data model, such as RDF, and not the XML syntax of a representation of that data model. However, please note that the authoratitive interpretation of the fragment identifier is determined by the Internet Media Type. If you want to opt-in for XPointer, then you can always create publish your own Internet Media Type with IANA and specify that it supports the XPointer Framework for some kind of non-XML resource. In this case, you are going to need to declare your own XPointer schemes as well.

The XPOINTER integration DISTRIBUTIONS support shorthand POINTERS.
In addition, they BUNDLE support for at last the following XPointer schemes:
* xmlns()
* element()
* xpath() - This is not a W3C defined XPointer scheme since W3C has not published an XPointer SHEME for XPath.

The XPointer integration distributions support shorthand pointers.
In addition, they bundle support for at last the following XPointer schemes:
* xmlns()
* element()
* xpath() - This is not a W3C defined XPointer scheme since W3C has not published an XPointer sheme for XPath.

This specification defines the XML Linking Language (XLink), which allows elements to be inserted into XML documents in ORDER to CREATE and describe links between resources. It USES XML SYNTAX to create structures that can describe links similar to the simple UNIDIRECTIONAL hyperlinks of today’s HTML, as well as more sophisticated links.

This specification defines the XML Linking Language (XLink), which allows elements to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create structures that can describe links similar to the simple unidirectional hyperlinks of today’s HTML, as well as more sophisticated links.

AUTHENTICATION, MESSAGE integrity, and non-repudiation. In addition to signature information, an XML Signature can also contain information describing the key used to SIGN the content.

authentication, message integrity, and non-repudiation. In addition to signature information, an XML Signature can also contain information describing the key used to sign the content.

Link markup needs to be RECOGNIZED reliably by XLINK applications in order to be traversed and handled properly. XLink USES the mechanism described in the Namespaces in XML Recommendation [XML Names] to ACCOMPLISH RECOGNITION of the constructs in the XLink vocabulary.

Link markup needs to be recognized reliably by XLink applications in order to be traversed and handled properly. XLink uses the mechanism described in the Namespaces in XML Recommendation [XML Names] to accomplish recognition of the constructs in the XLink vocabulary.

No, it lets you MAKE up names for your own element types. If you think TAGS and elements are the same thing you are ALREADY in CONSIDERABLE trouble: read the rest of this question CAREFULLY.

No, it lets you make up names for your own element types. If you think tags and elements are the same thing you are already in considerable trouble: read the rest of this question carefully.

Document types usually need a formal description, either a DTD or a Schema. Whilst it is POSSIBLE to process well-formed XML documents without any such description, trying to create them without one is asking for trouble. A DTD or Schema is used with an XML editor or API INTERFACE to guide and control the construction of the document, making sure the right elements go in the right places.

Creating your own document type therefore begins with an analysis of the class of documents you want to describe: REPORTS, INVOICES, letters, configuration files, credit-card verification requests, or whatever. Once you have the structure correct, you write code to express this formally, using DTD or Schema syntax.

Document types usually need a formal description, either a DTD or a Schema. Whilst it is possible to process well-formed XML documents without any such description, trying to create them without one is asking for trouble. A DTD or Schema is used with an XML editor or API interface to guide and control the construction of the document, making sure the right elements go in the right places.

Creating your own document type therefore begins with an analysis of the class of documents you want to describe: reports, invoices, letters, configuration files, credit-card verification requests, or whatever. Once you have the structure correct, you write code to express this formally, using DTD or Schema syntax.

No. This is DONE in the DOCUMENT's Document TYPE DECLARATION, not in the DTD.

No. This is done in the document's Document Type Declaration, not in the DTD.