Search Results for "xpath"

This short description is about the work of XForms. Before talking about XForms it's important to understand the concept of forms. Forms are to collect the data so we should not get surprised if we say XForms is basically depending on instance data. Instance data are these data which are based on XML. The data are defined in the terms of XPath's internal tree illustration and dispensation of XML. It may look odd at first to relate XPath with XForms. However, XPath is the well-known as the ordinary layer between XSLT and XPointer. Since XForms

Debates on the XML-DEV and XSL mailing lists over the last two weeks concern the futures of XSLT, XPath, and, the latest addition to the W3C XML toolkit, XML Query. There are no signs of these debates ending this week. Discussion on XML-DEV about the design of XML Query rages on. Reinventing the Wheel The focus of last week's XML-Deviant was the concern expressed by several XML-DEV contributors that the interdependence of several W3C specifications may have exceeded the dictates of software reuse and become instead a tangled mess. Suggestions were

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

Forms are for collecting data, so it's not surprising that the most important concept in XForms is "instance data", an internal representation of the data mapped to the familiar "form controls". Instance data is based on XML and defined in terms of XPath's internal tree representation and processing of XML. It might seem strange at first to associate XPath and XForms. XPath is best known as the common layer between XSLT and XPointer, not as a foundation for web forms. As XForms evolved, however, it became apparent that forms needed greater structure

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

Sometimes it seems you spend more time manipulating XML files than you do writing Java code, so it makes sense to have one or two XML wranglers in your toolbox. In this article, Laurent Bovet gets you started with XmlMerge, an open source tool that lets you use XPath declarations to merge and manipulate XML data from different sources. As a Java developer you use XML every day in your build scripts, deployment descriptors, configuration files, object-relational mapping files and more. Creating all these XML files can be tedious, but it's not

Welcome to Processing XML with Java, a complete tutorial about writing Java programs that read and write XML documents. This is the most comprehensive and up-to-date book about integrating XML with Java (and vice versa) you can buy. It contains over 1000 pages of detailed information on SAX, DOM, JDOM, JAXP, TrAX, XPath, XSLT, SOAP, and lots of other juicy acronyms. This book is written for Java programmers who want to learn how to read and write XML documents from their code. The paper version is published by Addison-Wesley, and can be found at fine

Summary: LINQ to XML was developed with Language-Integrated Query over XML in mind and takes advantage of standard query operators and adds query extensions specific to XML. The samples in most of this document are shown in C# for brevity. Introduction: XML has achieved tremendous adoption as a basis for formatting data whether in Word files, on the wire, in configuration files, or in databases; XML seems to be everywhere. Yet, from a development perspective, XML is still hard to work with. If you ask the average software developer to work in

[July 12, 2004] W3C Releases Public Working Draft for Full-Text Searching of XML Text and Documents. W3C has published an initial Public Working Draft for XQuery 1.0 and XPath 2.0 Full-Text. Created as a joint specification by the W3C XML Query Working Group and the XSL Working Group as part of the XML Activity, this new draft specification defines a language that extends XQuery 1.0 and XPath 2.0 with full-text search capabilities. As defined by the draft, "full-text queries are performed on text which has been tokenized, i.e., broken into a

Description This work defines the XML Pointer Language (XPointer), the language to be used as a fragment identifier for any URI-reference that locates a resource of Internet media type text/xml or application/xml. XPointer has been split into a framework for specifying location schemes, and three schemes: element(), xmlns() and xpointer(). The framework and the first two schemes form the XPointer Recommendation, and provide a minimal inventory of mechanisms. The xpointer() scheme, which is based on the XML Path Language (XPath), is still under

How do I install the XPointer processor? Download the latest "cweb-xpointer" release from SourceForge. This project uses Apache Maven and Java 1.4+, so you will need to install those as well. Normally you will also want to download one of the XPointer Framework integrations, such as the xpointer+dom4j or the xpointer+jdom package. These "integration packages" provide support for a specific XML Document model. The project dependencies are explicitly declared in the Maven POM. This means that Maven can automagically download the required releases of

XPointer is a system for addressing components of XML based internet media. At the present time (late 2002), XPointer is divided among four specifications: a "framework" which forms the basis for identifying XML fragments, a positional element addressing scheme, a scheme for namespaces, and a scheme for XPath-based addressing. The XPointer language is designed to address structural aspects of XML, including text content and other information objects created as a result of parsing the document. Thus, it could be used to point to a section of a

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

XPointer provides a more fine-grained addressing than XPath. * Instead of just nodes, XPointers address locations, which can be nodes, points, or ranges. * A point can represent the location preceding or following any individual character in e.g. chardata nodes. The special node test point() selects the set of points of a node. * A range consists of two points in the same document, and is specified using a special range-to location step construct. * XPointer provides some extra functions: here() get location of element

XPointer is based largely upon a widely-used technology, the Text Encoding Initiative "extended pointer" [Sperberg-McQueen 1994], [Ide 1995]. Extended pointers provide axes for navigating within trees and a rudimentary predicate language for selecting nodes along axes, and have been implemented in several SGML-based browsing systems. TEI extended pointers introduced "location terms" including root, here, id, child, descendant, ancestor, previous (sibling), next (sibling), preceding, following, and pattern (content matching by regular expressions) --