Search Results for "XLink"

While a little bit out dated for its testing realm, this article holds some still useful information for the modern developer. "XML in the browser has been the subject of many spirited discussions about bleeding-edge web development. Some feel that XML in place of HTML isn’t ready for prime time due to the lack of user agents that can properly parse and render it. Others feel that XML really belongs on the server or used solely as a descriptive framework for data and has no place in the visual world of the Web which is already adequately served by

Since Elliotte Rusty Harold recommended "complete rejection of this specification until such time as Sun's patent can be dealt with more reasonably," the XML-dev mailing list has been discussing the licensing terms for the patent. Daniel Veillard, who chaired XPointer meetings on the subject, noted that "We can't chase them all and if we did we would make no progress every effort would be wasted doing those Patent lookups and fighting them :-(((," though he clearly had little sympathy for the patent itself. Tim Bray described the situation as "a

Uche Ogbuji wrote a good article on XML.com here is a summary: "I’m still getting my Weblogger profile here updated, but this year I transitioned from one company I co-founded to another. Zepheira provides data architecture solutions, with a focus on semantic technology. I was early on the Semantic Web bandwagon, and I almost fell off at one point because I felt the useful, modest ideas at the core had been overrun by an academic brand of technological megalomania. This year I felt the timing was right to not only renew my interest in the technology,

An important application of XML is the interchange of electronic data (EDI) between multiple data sources on the Web. As XML data proliferates on the Web, applications will need to integrate and aggregate data from multiple source and clean and transform data to facilitate exchange. Data extraction, conversion, transformation, and integration are all well-understood database problems, and their solutions rely on a query language. We present a query language for XML, called XML-QL, which we argue is suitable for performing the above tasks. XML-QL is a

The Web Consortium's XML Linking working group is developing specifications to enable more advanced hypertext functionality on the Web: in particular fine-grained anchors, external annotation, and bi-directional links. This paper examines basic goals and approaches; describes HTML linking limitations XML Linking seeks to overcome; and surveys the Working Group's primary specifications: XPath, XPointer, and XLink. As of this writing, the last two, while well advanced, are not final recommendations, and so are subject to change. Consult the W3C Web site

Introduction This specification defines the XML Linking Language (XLink), which allows elements to be inserted into XML documents in order to create and describe Link between resources. XLink provides a framework for creating both basic unidirectional links and more complex linking structures. It allows XML documents to: * Assert linking relationships among more than two resources * Associate metadata with a link * Express links that reside in a location separate from the linked resources An important application of XLink is in

The design of XLink has been informed by knowledge of established hypermedia systems and standards. The following standards have been especially influential: * HTML [html]: Defines several element types that represent links. * HyTime [iso10744]: Defines inline and inbound and third-party link structures and some semantic features, including traversal control and presentation of objects. * Text Encoding Initiative Guidelines [tei]: Provides structures for creating links, aggregate objects, and link collections. Many other linking systems

XML Linking, formerly known as XLink and as XLL (the eXtensible Linking Language), is a work in progress of the Web Consortium. It is closely related to the XML Recommendation, but adds functionality for high-function hypertext and hypermedia. It is now an independent Working Group, but its projects were started under the main XML Working Group, and progressed to solid Working Drafts there before being handed off to the new XML Linking Working Group. The work of this WG has two parts: XLink proper provide advanced linking capabilities such as

XLink Attribute Usage Patterns While the XLink attributes are considered global by virtue of their use of the namespace mechanism, their allowed combinations on any one XLink element type depend greatly on the value of the special type attribute (see [XLink Element Type Attribute (] for more information) for the element on which they appear. The conformance constraint notes in this specification detail their allowed usage patterns. Following is a summary of the element types (columns) on which the global attributes (rows) are allowed, with an

This section describes the terms and concepts that are essential to understanding XLink, without discussing the syntax used to create XLink constructs. A few additional terms are introduced in later parts of this specification. 2.1 Links and Resources [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

[April 29, 2005] First Public Working Draft for XML Linking Language (XLink) Version 1.1. The W3C XML Core Working Group has produced a First Public Working Draft for XML Linking Language (XLink) Version 1.1 and requests feedback from W3C Members and other interested parties. XLink Version 1.0 was approved as a W3C Recommendation in June 2001. The XLink Version 1.1 Working Draft defines mechanisms to allow markup constructs "to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create

XLink Elements and Attributes XLink offers two kinds of links: Extended links Extended links offer full XLink functionality, such as inbound and third-party arcs, as well as links that have arbitrary numbers of participating resources. As a result, their structure can be fairly complex, including elements for pointing to remote resources, elements for containing local resources, elements for specifying arc traversal rules, and elements for specifying human-readable resource and arc titles. XLink defines a way to give an extended link special

XML Linking Language (XLink) is a generic framework for expressing links in XML documents, to complete its placement in hypertext systems such as the Web. It can be used to create simple links, such as those that are an essential part of HTML documents, or more complex types of links, such as multiended links and link databases. XML Linking Language (XLink) Version 1.0 [W3C Recommendation] provides a generic framework for expressing links in XML documents. Hypertext, which requires linking, is the foundation of the Web, and adding sophisticated

XLink Markup Design This section describes the design of XLink's markup 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 [xname] to accomplish recognition of the constructs in the XLink vocabulary. The XLink namespace defined by this specification has the following URI: http://www.w3.org/1999/xlink As dictated by [xname], the use of XLink elements and attributes requires declaration of the

Description XLink defines how to insert links in XML documents. It specifies a framework making it possible for XML applications to recognize XML elements as having link semantics. In addition to the simple, two-ended, unidirectional links which are well-known from HTML, XLink allows more general links, which must not be embedded in the document, can have any number of ends, and can be multidirectional. XLink is the XML Linking Language. It allows elements to be inserted into XML documents in order to create and describe links between

The question "who cares?" is usually a rhetorical question -- not a query for information, but a statement in question form that expresses something declarative. This rhetorical question usually means "I don't care and doubt if anyone does." When I say "XLink: who cares?", however, I don't mean it rhetorically. I really want to know: who out there still cares about XLink? I did care, ever since I first heard about the work on "XML Part 2: Linking," as it was called at the announcement of XML's existence at SGML '96. (XSL, before XSLT was split away

Abstract 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. Status of this Document This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used

Introduction Formerly also known as XLink and XLL (eXtensible Linking Language), XML Linking provides the mechanism needed by XML to interconnect. It's role is comparable to HTML's <a href="something.html">...</a> tag, but with many more possibilities. It should be noted, though, that there is practically no browser support for the additional functionality. Of course, XML Linking only works in XML enabled programs. Working Any XML element can be used as a link by adding an xlink:type attribute to the element, provided the

The XML Linking Working Group has completed its work and is no longer active. The XML Activity Statement discusses the W3C's work on XML as a whole; the XML Linking Working Group's final charter covers its last set of work on XML Linking and XPointer in more detail. Responsibility for maintenance of documents issued by the WG rests with the XML Core Working Group in the first instance. A public registry for XPointer schemes is available. Check the Implementation Chart. XML Linking and XML Base reached Recommendation status on June 27th

Introduction : The XML Linking Language [XLink] defines Extensible Markup Language (XML) 1.0 [XML] constructs to describe links between resources. One of the stated requirements on XLink is to support HTML [HTML40] linking constructs in a generic way. The HTML BASE element is one such construct which the XLink Working Group has considered. BASE allows authors to explicitly specify a document's base URI for the purpose of resolving relative URIs in links to external images, applets, form-processing programs, style sheets, and so on. This document

Abstract: This document proposes a facility, similar to that of HTML BASE, for defining base URIs for parts of XML documents. Status of this Document: This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the

In 1997 Sun Microsystems and Jakob Nielson, the noted web design and usability guru, were granted a patent on a "Method and system for implementing hypertext scroll attributes" by the US Patent Office. The patent describes the process of using a string to define an external anchor for an HTML document. The string is defined in the link to the HTML document, and the web browser, on loading the document defined by the link, will scroll to the first occurrence of the text string within the document -- hardly an innovation. The first sign that this, like

Description:If you've been paying attention to this column over the past few weeks, you'll already be familiar with XPath and XLink, two important pieces of the XML jigsaw. XPath provides a standard way to access specific nodes (or sets of nodes) within an XML document, while XLink offers XML document authors the ability to link XML data together in a myriad of different ways. XPointer is a language for locating data within an Extensible Markup Language (XML) document based on properties such as location within the document, character content, and

Abstract This document is a liaison statement from XML Linking Working Group to the XML Information Set working group. Because the XPointer specification under development in the XML Linking WG must refer to structural parts of XML documents, the structure it addresses must be explicit. Document structure specifications such as DOM and the XML Information Set may wish to consider the XPointer requirements in order to insure interoperability when used with XPointer and XLink. Thus we have set out in this document, some constraints we believe XPointer