How do I implement an application-specific XPointer
Short answer: Implement
The XPointer Framework is extensible. One of the very
coolest things about this is that you can develop your
own XPointer schemes that expose your application using
the data model that makes the most sense for your
For example, let's say that you have a CRM application.
The important logical addressing units probably deal
with concepts such as customers, channels, and products.
You can directly expose these data using a logical
addressing scheme independent of the actual XML data
model. Not only does this let people directly address
the relevant concepts using a purpose-built addressing
vocabulary, but this means that your addressing scheme
can remain valid even if you change or version your XML
data model. What a bonus!
The same approach is being used by the MindSwap
laboratory at the University of Maryland to prototype a
variety of XPointer schemes for addressing semantic web
How do I support very large resources?
You can only do this with server-side XPointer. Further,
you need to use (or implement) XPointer schemes that do
not depend on a parsed XML document model. Basically,
you need to use an XPointer scheme that interfaces with
an indexed persistence store (RDBMS, ODBMS, or XML DBMS)
which exposes to your ISchemeProcessor the information
that it needs to answer subresource addressing requests.
You will also have to provide shorthand pointer support
for your DBMS-based resource. The default shorthand
pointer processor assumes that it has access to a parsed
XML document, so it can't be used when you have a very
large XML resource.
How do I contribute?
The XPointer implementation is hosted as a SourceForge
project. If you want to contribute send an email to one
of the project administrators from the project home
The XPointer module uses numerous tests to validate
correct behavior of the XPointer processor. One valuable
way to contribute is by developing new tests that
demonstrate broken behavior. Patches that fix the
problems identified by those tests are also valuable,
but it is by the tests themselves that we can insure
that each release of the XPointer processor will
continue to meet the requirements of the various
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
Definition: An XLink link is an explicit relationship
between resources or portions of resources.]
[Definition: It is made explicit by an XLink linking
element, which is an XLink-conforming XML element that
asserts the existence of a link.] There are six XLink
elements; only two of them are considered linking
elements. The others provide various pieces of
information that describe the characteristics of a link.
(The term "link" as used in this specification refers
only to an XLink link, though nothing prevents non-XLink
constructs from serving as links.)
What are the valid values for xlink:actuate and
Don't blame me to put such a simple question here. I saw
a famous exam simulator gave wrong answer on this one.
Typing them out also help me to remember them.
xlink:actuate onRequest, onLoad, other, none xlink:show
replace new embed other none
What is the correct answer of the following question?
Which of the following is true about XLink and HTML
1. XLink can be attached with any element. Hyperlinks in
HTML can be attached to only an ANCHOR <A> element.
2. XLink can refer to a specific location in XML
document by name or context with the help of XPointer.
HTML ANCHOR<A> does not have capability to point to
specific location within an html document.
3. XLink / XML links can be multidirectional. HTML links
4. HTML links are activated when user clicks on them.
XLink has option of activating automatically when XML
document is processed.
Only 2 is incorrect, since HTML ANCHOR does have
capability to point to specific location within an html
What three essential components of security does the XML
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.
XLink Processing and Conformance
Processing Dependencies: XLink processing depends on
[XML], [XML Names], [XML Base], and [IETF RFC 2396]
An XML element conforms to XLink if:
it has a type attribute from the XLink namespace whose
value is one of "simple", "extended", "locator", "arc",
"resource", "title", or "none", and
it adheres to the conformance constraints imposed by the
chosen XLink element type, as prescribed in this
This specification imposes no particular constraints on
DTDs; conformance applies only to elements and
An XLink application is any software module that
interprets well-formed XML documents containing XLink
elements and attributes, or XML information sets [XIS]
containing information items and properties
corresponding to XLink elements and attributes. (This
document refers to elements and attributes, but all
specifications herein apply to their information set
equivalents as well.) Such an application is conforming
it observes the mandatory conditions for applications
("must") set forth in this specification, and
for any optional conditions ("should" and "may") it
chooses to observe, it observes them in the way
it performs markup conformance testing according to all
the conformance constraints appearing in this
XLink Markup Design
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