Search Results for "w3c"

The world is developing too fast and there are many reasons for its rapid development the main reason is the new things appearing in the computer, restless search is taking place in inventing new languages so once it is approved by the people then within no time the other one is appearing. HTML5 is a technology developed by the WHATWG, it is a open community started by four major browser vendors these vendors are Mozilla, opera and apple, this HTML5 is not the replacement of HTML 4.01 or XHTML, it is an evolution, the aims of it are big it tries

Though the XSLT and XQuery share the same data model, type system and function library they are created by different working groups within W3C in order to work in large collections the query language was initially created and this language deals with the large collections of XML documents and not only with large collection of the documents it can also work with the documents that are individual documents, there are many differences between these languages. In the web development circles the XHTML is continually expanding, since there are

For the integration of data there are many techniques of using SQLXML and .net the sql client data provider supports execute xml reader it can consume directly the result of it to do the xml query the user can use xml directly, the role of XML query in reinventing the wheel is very large the overlap between the xquery and xslt is too great for W3C to recommend both as separate languages if the XSLT is not considered enough as an XML query language then its development should be built from the same and semantic syntactic base as XSLTThe most

EXI is designed in view to carry out extensive works with the help of W3C’s XML binary characterization. This is one of the efficient XML interchange working groups. The XBC is authorized to find out an alternative form of XML and they succeeded in that venture by developing a substitute format for XML. With respect to the recommendations from XBC, the EXI was first used for measuring, evaluating and comparing the progress of various XML technologies. This evaluation and comparing process are with respect to the measurements proposed by XBC.

The new public review draft of the document "ebXML Registry Profile for Web Ontology Language (OWL) Version 1.5" has been released. Being produced by the OASIS ebXML Registry Semantic Content Management Subcommittee, it defines a new version of the ebXML profile used for publishing, management, discovery and reuse of the ontologies developed by the OWL Lite standards. This document tries to define the normative ebXML Registry Profile for the OWL (Web Ontology Language) Lite. It has the purpose to normatively specify how the OWL Lite constructs are

Abstract: This document lists the design principles, scope, and requirements for the XML Digital Signature specification. It includes requirements as they relate to the signature syntax, data model, format, cryptographic processing, and external requirements and coordination. Status of this document: This Working Draft of XML Signature Requirements is a very stable result of this Working Draft having been advanced through W3C Last Call. Relatively small changes have been made to clarify the stated requirements during that period. This document will

The XML Key Management Specification (XKMS) initiative was jointly developed by VeriSign, Microsoft and WebMethods as an open standard to simplify the securing of XML-based Internet transactions using PKI and digital certificates. The ability to secure all Web Services communications and transactions is critical for the success of Web Services in the enterprise. With XKMS, developers can integrate authentication, digital signature, and encryption services, such as certificate processing and revocation status checking, into applications in a matter of

On Jan. 23, 2007 the W3C granted Recommendation status to XQuery, the XML query language designed to do for Web services what SQL did for relational databases. XQuery allows you to work in one common model no matter what type of data you're working with -- relational, XML or object data. It's used for queries that must represent results as XML, to query XML stored inside or outside the database, or to span relational and XML sources. SQL/XML is another standard that uses declarative, portable queries to return XML by querying relational data. It's an

Steve Holzner, another big name in the computing world has written a very informative article that covers many different ways to use XML. This is only one of them: "XML at Work: Synchronized Multimedia Integration Language Synchronized Multimedia Integration Language (SMIL, pronounced "smile") has been around for quite some time. It's a W3C standard that you can find more about at http://www.w3.org/AudioVideo/#SMIL. SMIL attempts to fix a problem with modern "multimedia" browsers. Usually, such browsers can handle only one aspect of multimedia

EXI is the result of extensive work carried out by the W3C's XML Binary Characterization (XBC) and Efficient XML Interchange (EXI) Working Groups. XBC was chartered to investigate the costs and benefits of an alternative form of XML, and formulate a way to objectively evaluate the potential of a substitute format for XML. Based on XBC's recommendations, EXI was chartered, first to measure, evaluate, and compare the performance of various XML technologies (using metrics developed by XBC [XBC Measurement Methodologies]), and then, if it appeared suitable,

This document specifies protocols for distributing and registering public keys, suitable for use in conjunction with the proposed standard for XML Signature [XML-SIG] developed by the World Wide Web Consortium (W3C) and the Internet Engineering Task Force (IETF) and an anticipated companion standard for XML encryption. The XML Key Management Specification (XKMS) comprises two parts -- the XML Key Information Service Specification (X-KISS) and the XML Key Registration Service Specification (X-KRSS).The X-KISS specification defines a protocol for a Trust

Think about how many times a day you use forms, electronic or otherwise. On the Web, forms have become commonplace for search engines, polls, surveys, electronic commerce, and even on-line applications. Nearly all user interaction on the Web is through forms of some sort. This ubiquitous technology, however, is showing its age. It predates XML by half a decade, which is a contributing factor to some of its limitations: Poor integration with XML Limited features make even common tasks dependent on scripting Device dependent, running well only on

Although XQuery was initially conceived as a query language for large collections of XML documents, it is also capable of transforming individual documents. As such, its capabilities overlap with XSLT, which was designed expressly to allow input XML documents to be transformed into XML or other formats.The XSLT 2.0 and XQuery standards were developed by separate working groups within W3C, working together to ensure a common approach where appropriate. They share the same data model, type system, and function library, and both include XPath 2.0 as a

OASIS announced the publication of a public review draft for the "ebXML Registry Profile for Web Ontology Language (OWL) Version 1.5" specification, ending 11-February-2007. Produced by members of the OASIS ebXML Registry Semantic Content Management Subcommittee, this document defines the ebXML Registry profile for publishing, management, discovery, and reuse of OWL Lite Ontologies. The SC was chartered to define use cases and requirements for managing semantic content within the ebXML Registry 4.0, seeking to establish a formal liaison with relevant

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,

In a sense, nobody is in charge of the web. The web is an open standard, with no restrictions on who can post content, or what that content should be about. The web belongs to everybody, and so it belongs to nobody. The openness and decentralization of the web is one of its greatest strengths. But it wouldn't work at all without some sort of standard way of encoding the information. That's where the World Wide Web consortium (W3C) comes in. The W3C is an international, vendor-neutral group that determines the protocols and standards for the web. They

The Efficient XML Software Development Kit (SDK) provides the tools you need to integrate Efficient XML into your application, system, or enterprise. Efficient XML SDK Contents The Efficient XML Runtime, used to encode and decode data in the Efficient XML format. The Efficient XML format was chosen by the W3C as the basis for the forthcoming Efficient XML Interchange (EXI) standard. Support for Popular XML APIs including SAX, DOM, JAXP, and a pull-model streaming API patterned on StAX, are built into the Efficient XML runtime. Efficient XML

Public Page Publications • Testing Framework • Status• Further Information• Charter and Participation• Timeline This is the public web page for the Efficient XML Interchange (EXI) Working Group of the World Wide Web Consortium (W3C). The EXI group is part of W3C's XML Activity. Here we present literature and data that may be of interest to the public. There is also a private page for members of the EXI group, for internal information. The objective of the Efficient XML Interchange Working Group is to develop a specification for an

"The EXI format uses a hybrid approach drawn from the information and formal language theories, plus practical techniques verified by measurements, for entropy encoding XML information. Using a relatively simple algorithm, which is amenable to fast and compact implementation, and a small set of data types, it reliably produces efficient encodings of XML event streams" The W3C has recently announced the first public draft for the Efficient XML Interchange Format which is a suggestion for compressing XML to increase the efficiency on the

More and more companies are considering or making the move to XML as the format they rely on for transmitting data to and from applications and web services. XML is a flexible, cross-platform, robust, commonly accepted standard that has spawned a rich ecosystem of tools, utilities, and applications that leverage its power and extensibility. Yet, even with all these strengths, XML adoption has been hampered because its sheer size and verbosity clogs networks, overwhelms smaller devices, and can slow data transmission to a crawl. Because the cost of

Efficient XML Interchange (EXI) is a proposed data format from the Efficient XML Interchange Working Group of the World Wide Web Consortium (W3C). It is one of the various efforts to encode XML documents in a binary data format, rather than plain text. Using a binary XML format generally can reduce the verbosity of XML documents and cost of parsing. The EXI format is derived from the Agile Delta efficient XML format[1]. Semantic Web at Work? Uche Ogbuji wrote a good article on XML.com here is a summary: “I’m still getting my

listen Wednesday April 12, 2006 1:49AM by Rick Jelliffe in Opinion Last week on XML-DEV I suggested that there should be a competition with prize money to stimulate development of faster XML parsers suitable for high transaction work. Elliotte Harold even quoted my (not original) Open Source is not a free lunch, it is stone soup. There are examples of industry consortia sponsoring such development: the OpenMP implementation contest for example. And groups such as OSDL offer fellowships to make sure strategic software is maintained. At the

Abstract The Semantic Web Services Initiative Architecture Committee (SWSA) proposes the following architectural and protocol abstractions as a foundation for supporting Semantic Web Service technologies on the World Wide Web. This document is based on a review of requirements gathered from a number of different environments to identify the scope and potential requirements for this Semantic Web Services architecture. Introduction The Semantic Web Services Initiative (SWSI) is an 'ad hoc' initiative of academic and industrial researchers, many

I confess: when it comes to XML and web services, I am a Big Picture person. There are hundreds of angle-bracket jockeys in the XML development community, to whom we can all look for the ins and outs of particular XML technologies. But the job of the XML-Deviant column, as I understand and practice it, is to focus the collective intelligence of the XML development community on the Big Picture. Toward that end I have often written about the W3C's Technical Architecture Group, describing it as the Web's court of last appeal, and in particular about the

Web Services have three basic platform elements. These are called SOAP, WSDL and UDDI. What is SOAP? The basic Web services platform is XML plus HTTP. * SOAP stands for Simple Object Access Protocol * SOAP is a communication protocol * SOAP is for communication between applications * SOAP is a format for sending messages * SOAP is designed to communicate via Internet * SOAP is platform independent * SOAP is language independent * SOAP is based on XML * SOAP is simple and extensible * SOAP allows you to get around firewalls * SOAP

XForms is a relatively recent standard from the W3C, designed to allow us to create sophisticated user interfaces using mark-up. This means that defining a user interface is much the same as using HTML, except that XForms has been designed from the ground up to cope with many of the things that we usually have to dive into script to do. And XForms doesn't just make it easy to replace script in our applications, it also provides us with the means to manipulate and validate XML; unlike most languages that you might have used, XForms brings XML right

HTML is probably the world's most important data format, and so changes come very slowly. But the World Wide Web Consortium's HTML Working Group has big plans for HTML. The current HTML standard is actually now XHTML 1.0 Second Edition, which is a set of minor changes to HTML to turn it into valid XML while still allowing current Web browsers to handle it. The big news is XHTML 2.0, a from-the-ground-up rethinking of HTML that keeps its strengths while ditching some long-standing stupidities or legacy items. It will not be fully backward-compatible

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

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

Tree controls provide a hierarchical view of data and XML provides a way to structure data hierarchically, so viewing XML data as a tree structure is a natural fit. But browsers don't provide a tree control. Instead, use this mix of XML, XSLT, JavaScript, and CSS to produce an extensible HTML tree control. After writing the Build an Object-Oriented Tree Control Using JavaScript article, it occurred to me that using XML as the data source for the tree would be a natural fit. I wanted to create a solution that was both maintainable and extensible. That

A consortium of computer industry heavyweights, including Microsoft, IBM, Cisco Systems, Dell, EMC, Hewlett-Packard, Intel, and Sun have gathered together to back a specification called the Service Modeling Language, or SML. SML is designed to help IT managers keep better track of the computers and services on their networks. IT managers can use SML to build up complex descriptions of their network and services using building blocks of XML data. Because the XML data is standardized, these blocks can be reused, and third-party developers can create

XML Encryption provides end-to-end security for applications that require secure exchange of structured data. XML itself is the most popular technology for structuring data, and therefore XML-based encryption is the natural way to handle complex requirements for security in data interchange applications. Here in part 1 of this two-part series, Bilal explains how XML and security are proposed to be integrated into the W3C's Working Draft for XML Encryption. Currently, Transport Layer Security (TLS) is the de facto standard for secure communication over

The World Wide Web Consortium has announced the launch of its XML Key Management Activity, tasked with the development of "an XML application/protocol that allows a simple client to obtain key information (values, certificates, management or trust data) from a web service. Based upon the XML Key Management Specification (XKMS), the Activity is chartered to produce a companion Recommendation for the IETF/W3C XML Encryption and XML Digital Signature Activities. An initial working draft XML Key Management Specification (XKMS) defines "protocols for

Introduction: The increasing number and complexity of XML-related specifications (e.g., Namespaces, XSLT, Schema, XInclude, XBase) as well as inherent functions of XML (entity resolution and validation) have created the need for an XML processing model, in order to disambiguate the order and depth of processing when applying these mechanisms. There are already a number of efforts to define a distributed processing model for the Web, encompassing proprietary efforts, embryonic efforts at standards (e.g., ESI and OPES), and as parts of other W3C

Introduction: XML and Data XML stands for eXtensible Markup Language. XML is a meta-markup language developed by the World Wide Web Consortium(W3C) to deal with a number of the shortcomings of HTML. As more and more functionality was added to HTML to account for the diverse needs of users of the Web, the language began to grow increasingly complex and unwieldy. The need for a way to create domain-specific markup languages that did not contain all the cruft of HTML became increasingly necessary and XML was born. The main difference between HTML and

More and more devices including PCs, PDAs, mobile phones, and various kinds of appliances are being connected to the network and many people are trying to use them for network applications such as e-commerce. One of the most important requirements for a network application is the security of data exchanged through the network. XML has been widely accepted as a standard format for data exchange in Internet and security mechanisms for XML documents and messages must be provided in the first place. The security mechanisms have to be implemented in Java

Activity Statement Work on Digital Signatures is being managed as part of W3C's Technology and Society domain. Introduction Digital signatures provide integrity, signature assurance and non-repudiatability over Web data. Such features are especially important for documents that represent commitments such as contracts, price lists, and manifests. In view of recent Web technology developments, future work will address the digital signing of XML -- and any of its applications such as RDF (Resource Description Framework) or P3P (Platform for

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

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

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

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