Collaboration between designers and developers is always great topic to write about. I believe that for the first time that kind of collaboration is possible to full extent and it is possible today. Key element for enabling this is XAML – eXtensible Application Markup Language aka Holy Grail of designer – developer collaboration.
XUL is a surprisingly easy way to build cross-platform browser extensions or even stand-alone applications. Discover how to build powerful, flexible Mozilla browser extensions that go beyond the capabilities of other tools like embedded scripting languages or CGI--because they're built right into the user's browser.
The emerging XML based web increasingly relies upon ways of presenting content in a just in time manner. Presentation technologies such as SVG and XHTML can do so, yet the power to properly harness them will likely lie in the emergent binding languages such as XBL, sXBL, and XTF. In this presentation, bindings and binding languages will be explored, illustrating how such environments as the Mozilla Firefox 1.5 browser are using XBL as a means for performing component binding into XHTML, SVG and XForms interfaces, looks at sXBL and the W3C's XBL directions, and details why such binding languages likely represent the future of XML presentation and interaction.
Some browsers have difficulty upon encountering the XML Prolog. In some cases, the browser will render all the markup as text. In other cases, when a browser has some XML support, it might attempt to render the document as an XML tree. To avoid these problems, many practicing web professionals prefer to leave the prolog off. This table will help you make that decision by showing you which browsers have known problems with the XML prolog.
The concepts behind Web Services are remarkably simple, and in this article we'll be taking a deeper look at what's involved. Then, with a little help from our good friend PHP, we'll set up our first Web Service.
The Mozilla platform offers a rich support of XML techniques, from low level ones (XPath, RDF, DOM, e4x) to rendering dialects like XHTML, SVG, XUL and XForms, thus making this platform a natural choice for the XML inclined. It is becoming a platform of choice when developing rich connected applications. When building dynamic applications, the developer is often facing a common set of programming patterns : gathering data from various remote and local sources, storing data with an optional transformation phase, and updating parts of the GUI to reflect the modifications in the data store. With today's ubiquitous use of XML as a data exchange syntax, a major part of these tasks can be achieved with XML based solutions. In this article we will present an XML centric solution that aims at minimizing the impedance mismatch between different data models that plagues classical architectures involving for instance XML/object/relationnal translation. It combines some of Mozilla's existing capabilities with REX (Remote Events for XML) and a native XML database with XQuery support. REX provides means to update the XUL based GUI and the database, while the XML database is used as a versatile storage engine.
In the information age it is widely understood that there is now too much information. Some of this newly created information will most certainly be valuable, but despite marked improvement in search tools, finding the valuable information is a slow panhandle. Perhaps in light of this situation, the W3C under the direction of Berners-Lee has begun to build the foundation for the next phase of the web. This phase, called the Semantic Web, will make information stored with this technology much more processible by machines.
As companies and consumers rely more on Web services, it becomes increasingly important for Web services developers to know how to properly design, develop, deploy, and ultimately manage a Web services system. However, because of the inherent complexities that can arise with a Web service implementation, it can be difficult to grasp practical fundamentals and devise a step-by-step plan for Web services development.
Converting an Atom document to JSON might, at first, appear to be a fairly straightforward task. Atom is, after all, just a bit of XML and XML-to-JSON conversion tools are widely available. However, the Atom format is more than just a set of XML elements and attributes. A number of subtle details can make proper handling of Atom difficult. This article describes those issues and demonstrates a mechanism implemented by the Apache Abdera project to convert Atom documents into JSON and produces a result that is readable, usable, and complete.
At the recent XML conference, Norm Walsh hosted a nocturne on Practical RDF, the highlight of which was his tour through thenorman.walsh.name setup. From the outside you may think this is a mere blog, but it’s actually a side-effect of a frighteningly gnarly confluence of metadata streams which are shaken and stirred to produce a sprawling network of resources a small part of which you might want to peruse for Norm’s news & views. I have a picture that made the audience at the session gasp in disbelief.
It's been 7 years and three "levels" since the first W3C DOM activity. XML and the way it is used has changed vastly over that time. DOM itself has moved from an API to access and manipulate an in-memory tree with no concept of namespaces, to an end to end XML technology, where parsing, modification of the tree (with the ability to check for validity with a schema as you go) and serialization are all specified.
In this article we will introduce the concept of WS-Management and Common Information Model (CIM). By exploring the SOAP message with multiple examples, we will learn how to transfer CIM operations through WS-Management SOAP messages.
Enterprises are adopting Web Services to ease application integration across heterogeneous environments within and across security domain boundaries. Security is an important element for the adoption of Web Services. The Organization for the Advancement of Structured Information Standards (OASIS) has recently ratified the Web Services Security standards (Web Services Security: SOAP Message Security 1.0 (WS-Security 2004 ), Web Services Security: UsernameToken Profile 1.0 , and Web Services Security: X.509 Certificate Token Profile ) to provide an extensible framework for providing message integrity, confidentiality, identity propagation, and authentication. The Web Services Interoperability Organization (WS-I) is profiling standards to provide guidelines for implementation and use of relevant standards to enhance interoperability. This paper describes the activities of the WS-I Basic Security Profile (BSP) Working Group (WG). This Working Group is chartered to improve interoperability of security technologies for Web Services by profiling the OASIS Web Service Security and HTTP Over TLS standards. This interoperability profile (known as the Basic Security Profile 1.0) is an extension of the WS-I Basic Profile . The WS-I Basic Profile addresses interoperability for implementations of core Web Services standards.
Firefox 2.0 brought several important changes in its XML support. It's currently reaching its peak in user deployment. Learn about updated XML features in Firefox 2.0, including a controversial change to the handling of RSS Web feeds.
This paper motivates the need for a lightweight, standards-based web services implementation that runs on mass market mobile devices. It describes the advantages of using web services and the challenges which must be overcome to use web services on mass market devices with limited computing power and network bandwidth. The paper concludes by describing a new approach to web services which drastically reduces the code required to exchange data with remote services, enabling the creation of more compelling applications with sophisticated user interfaces and application logic.
Since 2005 the German National Library of Science and Technology (TIB) is established as a DOI registration agency for scientific content. Data providers transmit XML-files containing the DC-based metadata descriptions of the scientific data to a webservice infrastructure at the TIB, which was created by the Research center L3S during a project founded by the registration agency for scientific content. Data providers transmit XML-files containing the DC-based metadata descriptions of the scientific data to a webservice infrastructure at the TIB, which was created by the Research center L3S during a project founded by the German research association (DFG). This webservice infrastructure is based on the web application framework COCOON. We have however extended COCOON with full webservice functionalities. Using XSLT the webservice is furthermore able to transform XML-metadata files into well-formed PICA-files to insert the metadata information into the library catalogue of the TIB.
XML feeds, though useful, are boring to look at in a browser because they are simple XML files. It's possible though to make them easier on the eye, and in this article we'll look at two ways of doing that. First, we'll use simple CSS properties to format each XML node, and then we'll use a little more complex but much more powerful XSL transformation.
RDFa (“Resource Description Framework in attributes”) is having its five minutes of fame: Google is beginning to process RDFa and Microformats as it indexes websites, using the parsed data to enhance the display of search results with “rich snippets.”
RELAX NG is not a capitalized misspelling of something you probably get to do all too rarely as a busy programmer and web designer. If you use XML to any great degree, you'll want to take a close look at it. It can help make your life as a web developer easier, allowing you to relax a little more.
Really Simple Syndication (RSS) is an XML format for news headlines. With RSS-enabled feeds, other web sites can easily include your content in their sites. And other applications (besides web browsers) can be used to view your content.
The ability to interoperate across disparate vendors, platforms and infrastructure stacks is inherently important to the adoption of Web Services technology. For most organizations, cross platform interoperability and the move to a loosely coupled, Service Oriented Architecture (SOA) is usually the main rationale for adoption of the underlying Web Service technologies. In this paper we will discuss some of the issues and stumbling blocks towards interoperability. We will also demonstrate with an example, how an application developed in Java and deployed in a J2EE 1.4 compatible container can interoperate and be consumed from a different client, developed in C# on the .NET platform.
So you have heard about microformats, read the introductory articles, and even bought the book. But now you are probably thinking "great - I have done my part to make the web a better place by adding microformats; what's next? What can people do with my data besides add it to their address book or calendar?" The intent of this article is to get you to think about microformats in different ways, and to demonstrate some interesting visualizations and mash-ups of microformatted content.