|
|
 |
|
|
|
 |
 |
 |
 |
 |
 |
 |
 |
|
|
|
|
[June 29, 2001] A posting from Renato Iannella (Chief Scientist, IPR Systems Pty Ltd) announces the publication of an updated 'work-in-progress' specification for the Open Digital Rights Language (ODRL). ODRL defines a set of semantics "for rights management expressions pertaining to digital assets. The ODRL complements existing analogue rights management standards by providing digital equivalents, and supports an expandable range of new services that can be afforded by the digital nature of the assets in the Web environment. The ODRL is a standard vocabulary for the expression of terms and conditions over assets. The ODRL covers a core set of semantics for these purposes including the rights holders and the expression of permissible usages for asset manifestations. ODRL specifies an XML binding and is expected to be utilised within open and trusted environments. The XML syntax is supported by the XML Schema language. The ODRL will be standardized via an appropriate, open, and non-competitive organisation with an public process for the future maintenance of the standard." The new version 0.9 specification supersedes the previous draft of 2000-11-21. Version 0.9 of ODRL now includes the following new features: (1) Agreement expressions [between parties]; (2) Requirements, e.g., payments for permissions; (3) Separation of the Expression Language from the Data Dictionary elements, as specified by the MPEG-21 Requirements; (4) Additional Permissions and Constraints; (5) Container mechanisms; (6) Additional Examples; (7) Full W3C XML Schema definitions and documentation. [Full context] [June 28, 2001] A communiqué from Rick Jelliffe announces the availability of the Topologi Schematron Validator tool. The Schematron Validator user interface "supports validation of multiple files, and store/recall of locations to allow validation of chains of transformations. As well as Schematron validation, the tool also supports DTDs and W3C XML Schemas validation. Schematron schemas can be embedded in W3C XML Schemas schemas to augment them. The tool is highly reconfigurable. It also provides XSLT transformations, and the automatic generation of Topic Maps and RDF (beta). It allows simple editing and a variety of different viewers, including text, single-pane web-browser and double-pane web-browser. The Topologi Schematron Validator comes with schemas for CALS tables, NITF, QAML, RDDL, RDF, RSS, Schematron, SOAP, SMIL, XHTML WAI, WSDL, XLink, and XTM. These are all open source and readily accessible. The tool will be useful for anyone with document which have constraints that cannot be expressed in schema languages such as DTDs, XML Schemas, RELAX, etc. and for creating friendly validators for files. Educators may find it convenient for teaching XML classes. Experimenters will appreciate the tool's configurability." The tool is available for no cost from the Topologi web site. The developers have provided an online version of the Schematron Validator manual, together with screen shots. [Full context] [June 28, 2001] A communiqué from Russell F. Moody of Science Applications International Corporation (SAIC) reports on the recent release of the EIA Standard 836 for public review and comment. Developed by member organizations of the Government Electronics and Information Technology Association (GEIA), the EIA-836 standard for 'Configuration Management Data Exchange and Interoperability' is a fundamental reference for business-to-business access, sharing and exchange of CM data, and for the development, mapping and use of CM related tools, systems and databases. The EIA-836 XML vocabulary and grammar can be used within XML frameworks to facilitate interoperability between trading partner systems, databases, and people performing configuration management and product support functions throughout a product's life cycle. EIA-836 supports CM data exchange regardless of trading partner information system implementation or method of data transfer. EIA-836 utilizes the Extensible Markup Language (XML), the emerging lingua franca of e-commerce data exchange, in defining CM data elements, and data element relationships, as well as a set of XML schemas and XML document templates for the exchange of CM business objects such as Engineering Change Proposals, Request for Deviations, and a host of others. The EIA-836 Business Objects can be tailored by users to suit specific trading partner situations and different industry domains. The EIA-836 development team is actively collaborating with other e-business initiatives including STEP (ISO 10303), the Product Life Cycle Support (PLCS) Program, and the Aerospace Industries Association Electronic Commerce Working Group (ECWG) to harmonize related efforts." The comment and review period for EIA-836 version 0.3 will extend through July 20, 2001. [Full context] [June 27, 2001] A communiqué from Chad Williams (Epicentric, Inc.) announces the release of 'WSUI' as an open standard "for the presentation of Web services as user interface components that can be delivered as Web applications to end users." The WSUI developers "are part of a working group formed to review and comment on the specification; once the specification has been reviewed and commented on by all interested parties, the resulting work will be submitted for standardization." Participation in the working group is welcome. A working draft document "describes the syntax and semantics of Web Service User Interface (WSUI). WSUI is a component model for adding presentation and multistage interaction to XML and SOAP-based network services. It is designed to be lightweight and easily implementable by using standard XML technologies such as XSLT, XPath, and XHTML." Rationale for the design is provided in the specification Introduction: "XML-based network services have become a very popular application integration mechanism. The aggregation and integration of these services at the presentation layer (such as HTML) is increasingly performed by non-technical or semi-technical business users. However, most standards for integrating or consuming XML-based network services are designed for a developer audience and are intended principally for RPC communication between server applications. A number of vendor-specific approaches have emerged to facilitate non-developer integration of network services, particularly to aid in the construction of e-commerce and portal web sites. WSUI is an attempt to standardize this 'last mile' of integration by defining a web component model that couples network services with interaction and presentation information. These components can be dynamically embedded into container applications at run-time by non-developers." WSUI's goal is "to enable a simple mechanism for integrating applications which are remotely exposed as XML and SOAP Web services into a Web site. Simplicity and elegance are the key technical goals, and the specification has been made simple enough that it can pass the 'weekend test' -- a single programmer working for one weekend can create an implementation." Other industry partners participating in the WSUI initiative include Documentum, Intraspect, Jamcracker, NewsEdge, Securant, and Yellowbrix. [Full context] [June 27, 2001] The W3C XML Encryption Working Group has released a first public working draft for XML Encryption Syntax and Processing. The formal model for syntax is provided in W3C XML Schema notation. The working draft "specifies a process for encrypting data and representing the result in XML. The data may be arbitrary data (including an XML document), an XML element, or XML element content. The result of encrypting data is an XML Encryption element which contains or references the cipher data. When encrypting an XML element or element content the EncryptedData element replaces the element or content (respectively) in the encrypted version of the XML document. When encrypting an entire XML document, the EncryptedData element may become the root of the new document. And when encrypting arbitrary data, the EncryptedData element may become the root of a new XML document or become a child element in an application-chosen XML document." An experimental namespace URI is provided: xmlns:enc='http://www.w3.org/2001/04/xmlenc#'; the WD specification also makes use of the XML Signature namespace and its schema definitions, xmlns:ds='http://www.w3.org/2000/09/xmldsig#'. [Full context] [June 27, 2001] The World Wide Web Consortium has announced the publication of the XML Base and XML Linking Language (XLink) specifications as W3C Recommendations, indicating that specifications are "stable and contribute to Web interoperability; W3C Recommendations have been reviewed by the W3C membership, who are in favor of supporting adoption by academic, industry, and research communities." A posting from Daniel Veillard (W3C) expressed the hope that "the XPointer specification will reach a similar status in a reasonable timeframe; this is in a large part dependant on getting enough interoperable implementation." From the announcement: "XLink is a way to allow elements to be inserted into XML documents in order to create and describe links between resources, whether internal or external to the original document. XML Base provides a way to indicate the URI base for linking in XML documents. Together, XLink and XML Base bring the functionality necessary for robust, rich XML applications spread across multiple documents... XLink provides flexible linking for XML: XML application developers are eager to have both the basic hyperlinking capabilities of HTML, and a range of further capabilities appropriate to XML documents, including links that can point to multiple resources, collections of links separate from the resources they connect, and an attribute-based link declaration syntax which doesn't interfere with users' decisions about XML document vocabulary. XLink supports not only traditional, or simple, links familiar from HTML, but also extended links. Extended links may be used to connect two or more resources via a single link, which need not be contained within any of them. This makes it possible to associate metadata or other supplemental information with resources without editing them. XLink also supports richer information about link types and the roles of each resource that an XLink connects. XML Base provides a proven approach for Base URI Services in XML: One of the requirements of XLink was to support the way HTML 4 provides linking capabilities in a more portable way. The HTML 'base' element allows authors to identify the base URI of a document, thus making it possible for an author to make use of relative URIs for external images, applets, style sheets, and other resources, without compromising portability. XML Base provides that same functionality for XML applications, including XLink. Since it has been written as a module, it may be reused or referenced by other applications." [Full context] [June 26, 2001] Reuters has announced an updated release of the NewsML Toolkit Version 1.0. "The NewsML Toolkit is an open-source Java library for reading and processing NewsML documents. NewsML 1.0 is a news-industry packaging and metadata standard for exchanging multi-part news and information in multiple media. This latest version of the Java based toolkit follows the alpha testing version released in December 2000. Developed in conjunction with XML specialists, Megginson Technologies Ltd., it is designed to simplify the processing of NewsML documents for subscribers to NewsML Services. NewsML Toolkit v1.0 now offers increased functionality including: (1) Access to all elements and attributes in a NewsML document via a Java Application Programming Interface; (2) Complete metadata extraction; (3) The ability to locate vocabularies which source content values for elements in a NewsML document; (4) Complete JavaDoc documentation. The NewsML Toolkit is available for use under the GNU Lesser General Public License. Reuters is also developing two complementary toolkits that build on NewsML Toolkit v1.0's document content extraction. These tools include: (1) A conformance checking tool, which will verify a NewsML document beyond visual basic DTD validation; (2) An application level toolkit, which will provide an intuitive level of parsing of a NewsML document. This allows the user to pose queries from a news perspective and 'prune' NewsItems in order to keep only selected content." [Full context] [June 25, 2001] The Uniform Code Council, Inc. (UCC) has announced the development of an initial set of EAN-UCC XML schemas which constitutes "first steps in a global solution that will reduce costs and bring greater clarity and functionality to Internet-based e-business processes. The UCC and EAN International will make XML the cornerstone of an open, global electronic commerce standard that bridges legacy EDI systems with Internet-based users and enables all companies to maximize their e-business opportunities." The XML schemas have been developed together with EAN International based upon input from some of the world's largest companies. This first suite of XML standards is "based on a core set of schemas that are shared across all industries. The standards include Item, Party, Purchase Order, Despatch Advice, Invoice, Charges, and Payments. Their development was based on Simple e-Business (Simpl-eb), a growing global business practice that involves a common definition of e-Business data and processes across the value chain. Each XML schema has an extensible, modular design to enable multi- industry adoption and implementation, as well as industry-specific customization. When fully implemented, these standards will expand the global user base for electronic commerce and enable companies of any industry, size, or geography to streamline their e-business processes via improved interoperability and efficient data transmission. The EAN-UCC System is recognized as one of the most important innovations in the history of commerce, enabling nearly one million member companies in 23 major industries to conduct efficient business in more than 141 countries around the world. Both organizations share a history that is user-driven and consensus based, ensuring that standards and solutions seamlessly cross over industries and national borders." [Full context] [June 23, 2001] Tomas Sander (InterTrust STAR Lab) recently posted a 'Call for Papers' in connection with an ACM Workshop on Security and Privacy in Digital Rights Management, to be held November 5, 2001 in Philadelphia, PA. The workshop is part of the Eighth ACM Conference on Computer and Communications Security (CCS-8). The workshop "will consider technical problems faced by rights holders (who seek to protect their intellectual property rights) and end consumers (who seek to protect their privacy and to preserve access they now enjoy in traditional media under existing copyright law). The organizers seek submissions from academia and industry presenting novel research on all theoretical and practical aspects of DRM, as well as experimental studies of fielded systems; they encourage submissions from other communities such as law and business that present these communities' perspectives on technological issues... Digital Rights Management (DRM) systems are supposed to serve mass markets, in which the participants have conflicting goals and cannot be fully trusted. This adversarial situation introduces interesting new twists on classical problems studied in cryptology and security research, such as key management and access control." Interest in Digital Rights Management is rapidly gaining ground, as evidenced by the growing number of industry and consortial initiatives proposing new architectures and models. XML-based standardization efforts are also underway within ISO, IETF, W3C, OASIS, and related arenas. [Full context] [June 22, 2001] Several draft documents covering the Security Assertion Markup Language (SAML) are now available for public review. SAML is being developed within the OASIS XML-Based Security Services Technical Committee (SSTC) as an "XML security standard for exchanging authentication and authorization information." The documents are under active revision, but provide a snapshot of the committee's design work. A draft 'SAML Specification' prepared for use at FTF3 contains material on the SAML domain model (description of the SAML problem space), a glossary, SAML core assertions, alternate assertion model, protocol models, and conformance. A version 0.9 draft of Security Assertions Markup Language: Core Assertion Architecture provides the text proposed by the Core Assertions and Protocol group for the Core Assertions section of the SAML. SAML "specifies several different types of assertion for different purposes; these are: (1) Authentication Assertion: An authentication assertion asserts that the issuer has authenticated the specified subject. (2) Attribute Assertion: An attribute assertion asserts that the specified subject has the specified attribute(s). Attributes may be specified by means of a URI or through an extension schema that defines structured attributes. (3) Decision Assertion: A decision assertion reports the result of the specified authorization request. (4) Authorization Assertion: An authorization assertion asserts that a subject has been granted specific permissions to access one or more resources." [Full context] [June 21, 2001] XBRL.org recently announced the release of 'XBRL for General Ledger' for public comment, along with a new version of the 'XBRL for Financial Statements' specification. The XBRL (Extensible Business Reporting Language) initiative "is a worldwide effort to develop a common framework for using XML for business reports such as financial statements, bank loans, credit reports and tax filings." The enhanced XBRL Financial Statements "harmonizes with the new World Wide Web Consortium (W3C) XML Schema to better align itself with initiatives of the W3C and other XML organizations and share technology and tools. The new XBRL for General Ledger specification "is an agreement on how to represent accounting and after-the-fact operational information and transfer it to and from a data hub or communicate it in a data stream. It incorporates the UN Standard Messages ENTREC (Journal) and LEDGER. Users of XBRL for General Ledger will be able to more easily bridge the gap between operational, off-site or outsourced systems and their back office accounting and reporting systems. XBRL for General Ledger is currently designed to meet international accounting requirements and allow an extensible, flexible, multi-national solution to exchange data required by internal finance, accountants, creditors, banks or other audiences across all software formats that can be brought into and out of accounting systems and reported using XBRL. It will also allow the future linkage of XML development on the transactional level to the general ledger level as such frameworks are developed. Working in alliance with the UN/EDIFACT Working Group (EWG) this Joint EWG Accounting, Auditing, Registration and Financial Information Services (EWG sub working group D14) and XBRL.org effort is focused on the urgent need to fill the gap between e-business and e-accounting and overcome the inefficiencies of disparate, non-integrated and outsourced accounting and financial systems by using the power of XML." XBRL for General Ledger has been released for a ninety-day feedback period, from June 18, 2001 to September 17, 2001. UML models for the specification are to be released soon. [Full context] [June 21, 2001] UN/CEFACT and OASIS, sponsors of the ebXML electronic business specifications, "today announced the formation of new technical committees (TC) within OASIS to carry forward the the infrastructure portions of the ebXML work. ebXML specifications, which provide a standard method for companies to exchange business messages, conduct trading relationships, communicate data and define and register business processes, were recently approved, marking a successful 18-month initial development phase. To continue ebXML maintenance and enhancements, OASIS has formed the ebXML Messaging TC, the ebXML Collaboration Protocol Profile and Agreement TC and the ebXML Implementation, Interoperability and Conformance TC. Members of the existing OASIS Registry/Repository TC have expanded their charter to embrace the ebXML Registry/Repository Specification. UN/CEFACT plans to form a working group for ebXML business process and core components in the near future. Together, OASIS and UN/CEFACT will continue to manage ebXML Technical Architecture and Marketing Awareness functions." [Full context] [June 20, 2001] An announcement from RealNetworks describes a new industry initiative designed to create an open XML-based standard for Internet media commerce and digital rights management. The Extensible Media Commerce Language (XMCL) initiative is "an open XML-based language designed to establish industry-wide standards for Internet media commerce. By standardizing the language for business rules, XMCL will enable content to be played in a way that is independent of codecs, digital rights management systems, and e-commerce systems. XMCL will greatly simplify deployment and accelerate the market for digital media commerce over the Internet. RealNetworks intends to submit the XMCL proposal to the appropriate standards organization, and will work with other industry leaders to ensure the initiative evolves into a widely accepted standard. The XMCL Initiative endorsed by many industry leaders proposes a standard business rule definition language providing rights holders the ability to take existing media business models -- such as purchase, rental, video-on-demand, and subscription services -- and deploy them on the Internet to generate new commerce opportunities. XMCL will give rights holders the freedom to use multiple back-end systems that interoperate with rights management solutions under a common interchange language." [Full context] [June 19, 2001] An announcement from Antarcti.ca Systems Inc. (ASI) describes the development of 'Visual Net' visualization technology which uses mapping software to "act as a front end to the Universal Description, Discovery and Integration (UDDI) Registry. The UDDI Business Registry is a global, public, online directory that gives businesses a uniform way to describe their services, discover other companies' services, and understand the methods necessary to conduct e-business with a particular company. Visual Net places the UDDI Business Registry data on large-scale maps utilizing a superior navigation system and information-rich visuals to enable users to find information on businesses." The UDDI Registry Map under development will feature (1) "A visual map displaying categories of information enabling users to browse through all the data and drill down into those areas of interest; (2) The ability to search the database using classification taxonomies such as the North American Industry Classification System (NAICS) and the Standard Industrial Classification (SIC) code from the same interface; (3) An intuitive display that instantly and visually shows the user valuable information about data in the Registry such as how wide-ranging the services of a business are and provides a relevancy scale of the data for the user." [Full context] [June 19, 2001] The Business Internet Consortium recently announced that RosettaNet has joined the Consortium in order "to help drive XML standard convergence activities in the industry." The Business Internet Consortium is an open-industry group formed to develop cross-industry eBusiness implementation guidelines, facilitated especially within its XML-based eBusiness Standard Convergence Workgroup. The XML working group was formed "to bring clarity by defining the generic layers and the corresponding recommended XML standards of a complete B2B, XML-based solution stack that is standardized, comprehensive, and interoperable, and to develop an implementation path." Details from the announcement: "RosettaNet's membership [in the Business Internet Consortium] pairs the efforts of these two leading eBusiness consortia to effectively promote supply chain interoperability. RosettaNet brings a substantial body of eBusiness XML standards expertise, research and results to the Business Internet Consortium's effort. RosettaNet represents more than 400 companies committed to the implementation of eBusiness process standards for the information technology, electronic components and semiconductor manufacturing industries. By joining the Business Internet Consortium, RosettaNet will share its learning with other industries looking to standardize their respective business processes. The Business Internet Consortium XML-based eBusiness Standard Convergence Workgroup is incorporating customer requirements to develop a generic XML-based standards reference stack and best practice guidelines for B2B processes, as well as a roadmap for businesses to migrate to the stack. The Workgroup expects to make recommendations to various standards bodies, such as the World Wide Web Consortium (W3C) and OASIS." [Full context] [June 18, 2001] An announcement from the Universal Description, Discovery, and Integration (UDDI) Project describes the publication of the UDDI Specification Version 2. The project is creating a "platform-independent, open framework for describing services, discovering businesses, and integrating business services using the Internet, as well as an operational registry that is available today." The Version 2 specification "delivers upon the roadmap and requirements outlined at the launch of UDDI in September 2000. New Features and improvements in the UDDI V2 specification will enable: (1) Description of Complex Organizations: Businesses can now describe and publish their organizational structure, including their business units, departments, divisions, and subsidiaries. (2) Improved support for internationalization: Businesses now have more flexibility in describing their business and services in multiple languages. (3) Additional categorization and identifier schemes: Businesses can use additional industry specific categories and identifiers to describe their businesses. For example, a chemical company may now use existing industry specific categories to describe themselves and their services. These categories can be validated during registration through third parties such as a chemical industry association. (4) Richer searching options: Businesses can now search the registry using more expressive query parameters, using more fields and complex combinations of fields. The UDDI Community is comprised of more than 280 business and technology leaders working together to enable companies to quickly, easily, and dynamically find, and transact with one another." UDDI version 2 specification documents include the UDDI Data Structure Reference, UDDI XML Schema, UDDI Programmer's API, UDDI Replication Specification (with XML schema), UDDI XML Custody schema, and the UDDI Operators Specification. [Full context] [June 18, 2001] A posting from Stephen Katz (FAO) announces the availability of draft documents specifying a Dublin-Core based standard for describing document-like agricultural resources. A 'Metadata Framework' document identifies a "metadata set of core elements and qualifiers that are generic to the description of agricultural resources. This document presents a further development of a specific application profile for description of document and document-like agricultural resources. This gives an example of how a unique application profile can be developed from the generic metadata set. The metadata set describe a minimum level format to allow interoperability between different islands of information." A second document 'Presentation of a metadata set' provides the elements and qualifiers of the proposed standard, presented in a hierarchical structure. The authors have tried to make a clear distinction between where they are applying Dublin Core elements and qualifiers as specified by the DCMI, and where they have suggested additional requirements to meet the needs of the Agricultural Community." An 'Element Description' document supplies definitions "based on formal standards for the description of metadata element sets; there are 10 attributes for defining the DC elements of which all were discussed for their suitability in meeting [the design] needs. The set of attributes conforms to the ISO/IEC 11179 standards for description of data elements." [Full context] [June 18, 2001] A posting from Tinny Ng (IBM Toronto Laboratory) announces the release of Xerces-C 1.5.0 with partial support for the W3C XML Schema Recommendation. The developers intend to update this package until it implements all the functionality of the current XML Schema Recommendation. Apache Xerces-C is a "validating XML parser written in a portable subset of C++. Xerces-C makes it easy to give your application the ability to read and write XML data. A shared library is provided for parsing, generating, manipulating, and validating XML documents. Xerces-C is faithful to the XML 1.0 recommendation and associated standards (DOM 1.0, DOM 2.0. SAX 1.0, SAX 2.0, Namespaces). The parser provides high performance, modularity, and scalability. Source code, samples and API documentation are provided with the parser. For portability, care has been taken to make minimal use of templates, no RTTI, no C++ namespaces and minimal use of #ifdefs. In addition to the implementation of XML Schema subset, Xerces-C 1.5.0 offers: (1) Mac OS X command line configuration and build support; (2) Enabled libWWW NetAccessor support under UNIX; (3) Enabled COMPAQ Tru64 UNIX machines to build xerces-c with gcc; (4) Updated support for SCO UnixWare 7 [gcc]; (5) Experimental IDOM; (6) Support for ICU 1.8; (6) Documentation in PDF format; (7) Bug fixes and performance improvement." Xerces-C 1.5.0 source code and binaries are available for AIX, HP11, Linux, Solaris, Windows. [Full context] [June 14, 2001] Altova has announced a limited beta testing phase for the XML Spy 4.0 product line, including the XML Spy 4.0 Integrated Development Environment (IDE) and the XML Spy 4.0 Document Framework, released to customers and invited industry experts. The XML Spy 4.0 Integrated Development Environment (IDE) "builds on the success of the award-winning XML Spy 3.5 product in the developer market and adds expanded ODBC database access functionality, enhanced user interface customization, as well as support for the final XML Schema Recommendation for both graphical XML Schema editing and validation of XML instance documents based upon XML Schema. The XML Spy 4.0 Document Framework is based on a combination of XML Schema and XSLT Stylesheets. This provides the customer with a highly user-friendly interface -- very much like a typical word processor -- that allows for true XML content editing and creation. The framework consists of two applications: (1) The XML Spy 4.0 Document Editor supports free-flow WYSIWYG text editing, form-based data input, graphical elements, presentation and editing of arbitrary repeating XML elements as tables, real-time validation, and consistency checking using XML Schema and is deployed on the end-users desk. (2) The XML Spy 4.0 Document Administrator application includes a graphical XSLT Generator that enables the customization of the document editor by defining an XSLT Stylesheet and additional editing-specific options based upon the underlying DTD or XML Schema for use during the content creation or editing process." [Full context] [June 14, 2001] A posting from Mark Reinhold (Sun Microsystems, Inc.) announces the version 1.0 early access implementation release of the Java Architecture for XML Binding (JAXB), previously referenced as the "Adelard" project. JAXB "provides an API and tools that automate the mapping between XML documents and Java objects. It is being developed through the Java Community Process program under [Java Specification Request] JSR-31. JAXB makes XML easy to use by compiling an XML schema into one or more classes. The generated classes handle all the details of XML parsing and formatting, they ensure that the constraints expressed in the schema are enforced, and in many cases they are much more efficient than using a SAX (Simple API for XML) parser or an implementation of the DOM (Document Object Model) API. An application that uses the generated classes can build a Java object tree representing an XML document, manipulate the content of the tree, and re-generate XML documents from the tree, all without requiring the developer to write complex parsing and processing code. JAXB 1.0 will be available as an optional package for the Java 2 Platform, Standard Edition (J2SE). JAXB may be included in future releases of J2SE or the Java 2 Platform, Enterprise Edition (J2EE). According to the working draft issued in conjunction with the implementation: "The primary components of the XML data-binding facility described in this specification are the schema compiler, the binding framework, and the binding language. (1) The schema compiler transforms, or binds, a source schema to a set of derived classes. As used in this specification, the term 'schema' includes the document-type definition language of the XML 1.0 specification. (2) The binding framework is a set of public interfaces and classes upon which derived classes rely to implement the operations of unmarshalling, marshalling, and validation. (3) The binding language is an XML-based language that describes the binding of a source schema to a set of derived classes. A binding schema written in this language specifies the details of the classes derived from a particular source schema." [Full context] [June 13, 2001] James Clark, Chair of the OASIS RELAX NG Technical Committee, has announced the release of the RELAX NG Tutorial as an official 'Committee Work Product' and the availability of validation software for RELAX NG schemas. The draft RELAX NG Tutorial edited by James Clark and Makoto MURATA is structured as a graded series of examples illustrating and explaining principal features of the RELAX NG structure-validation language. A RELAX NG schema "specifies a pattern for the structure and content of an XML document" in support of validation software which can test XML instances against these declarations. Of the tutorial's three appendices, Appendix A "Comparision with XML DTDs" most succinctly summarizes the goals and methodological approach taken in RELAX NG vis-à-vis SGML/XML DTDs. "RELAX NG provides functionality that goes beyond XML DTDs. In particular, RELAX NG (1) uses XML syntax to represent schemas; (2) supports datatyping; (3) integrates attributes into content models; (4) supports XML namespaces; (5) supports unordered content; (6) supports context-sensitive content models; (7) has improved support for cross-references. RELAX NG does not support features of XML DTDs that involve changing the infoset of an XML document. In particular, RELAX NG; (8) does not allow defaults for attributes to be specified; (9) does allow entities to be specified; (10) does allow notations to be specified; (11) does not specify whether white-space is significant. Also RELAX NG does not define a way for an XML document to associate itself with a RELAX NG pattern." A collection of other resources (schemas, transformation stylesheets, software) supporting RELAX NG has also been announced. James Clark's 'Jing' is a validator for RELAX NG implemented in Java. As a command-line tool, it validates an XML instance against a RELAX NG schema and reports (any) errors in a file; one may specify multiple XML files for validation in a single command. Jing is written on top of SAX2, and represents an adaptation of James Clark's validator for TREX. Jing supports validation of datatypes from W3C XML Schema Part 2. The version 2001-06-11 implementation is available for download as a JAR file and as a Win32 executable for use with the Microsoft Java VM; the sources are also available. [Full context] [June 12, 2001] ISO JTC1/SC34/WG1 recently approved a proposal for a new work item on a 'Document Schema Definition Language (DSDL)'. The NP was submitted by the British Standards Institution (BSI), who have been asked to appoint an editor "to complete a first draft based on extensions to RELAX-NG and forward it to SC34 for review." The specification would govern "the definition of document structures, data types and data relationship constraints that can be applied to data represented using the ISO/IEC 8879 Standard Generalized Markup Language and its derivatives, such as ISO/IEC 10744, Hypermedia/Time-based Structuring Language (HyTime), and the W3C Extensible Markup Language (XML)." Background for the NP: "SGML Document Type Definitions (DTDs) allow document structures to be formally modelled but do not allow details of data types or data relationships to be recorded in an XML-compatible way. While the W3C XML Schema Definition language (XSD) does allow data types to be used to validate the contents of SGML elements and values of attributes, it does not allow the relationships between the values of different attributes and contents of elements to be validated. A new, compact, efficient and XML document type definition for the integrated description of document structures, data types and data relationships will make it possible to automate the processing of structured information resources to the level required by business users, which has a higher level of requirements than those identified from the publishing community for which SGML was originally developed. The standard will also define the scope and notation for converting and interworking a core subset of document structure, data type, and data relationship constraint models among the three notations: DSDL, DTD declarations, and XSDL." According to the draft proposal, a "preparatory draft will be contributed by the UK National Body for the SC34 meeting in December 2001. Liaison with the W3C XML Coordinating Committee will be undertaken to keep the standard aligned with the work being done to manage information sets developed for XML. The committee expects to be able to integrate the best practices of [recent] proposals to form the basis of a first draft of the new standard... [for example,] the RELAX TR developed by the Japanese National Body as ISO 22250 and the TREX language developed by James Clark (the editor of the ISO/IEC 10179 Document Style Semantics and Specification Language) both propose efficient XML representations of document models, including data types. The widely acknowledged XML Schema Data Types specification will be referenced. The Schematron language allows the relationships between data elements and attributes to be described." [Full context] [June 12, 2001] The W3C XML Query Working Group has released a first public working draft specifying an XML syntax for the W3C XML Query language (XQuery). The draft supplies a W3C XML Schema for the XQuery XML Syntax as well as an XML DTD. The working group intends that the XQueryX DTD and XML Schema "will track the XQuery 1.0 syntax and will be changed as often as the XQuery 1.0 syntax is changed in future Working Drafts." The syntax specification in 'XQueryX' "is a close representation of the abstract syntax found in Appendix B of the XQuery Working Draft; for each production in the abstract syntax, the authors created an equivalent XML representation. XQueryX is thus an XML representation of an XQuery. [Because] it was created by mapping the productions of the XQuery abstract syntax directly into XML productions, the result is not particularly convenient for humans to read and write; however, it is easy for programs to parse, and because XQueryX is represented in XML, standard XML tools can be used to create, interpret, or modify queries." Concurrent with the release of the new XQueryX draft, the XML Query Working Group has published four updated related working drafts: "XQuery 1.0," the "XML Query Use Cases," "XQuery 1.0 and XPath 2.0 Data Model" [replaces the former "XML Query Data Model"], and "XQuery 1.0 Formal Semantics" [replaces the former "XML Query Algebra"]. W3C XQuery "is designed to be a small, easily implementable language in which queries are concise and easily understood. It is also flexible enough to query a broad spectrum of XML information sources, including both databases and documents." [Full context] [June 11, 2001] An announcement from ElCel Technology describes the availability of its 'XML Validator' and 'Canonical XML Processor' applications, now featuring support for entity resolution specified by the draft XML Catalogs specification. Rob Lugt (Founder and Technical Director, ElCel Technology) writes: "The XML Validator is built using our C++ XML Toolkit, which is designed to be fast, flexible and 100% conforming to the XML 1.0 recommendation. Use of ISO-standard C++ makes our toolkit highly portable, enabling us to provide binary versions of the XML Validator for both Windows and Linux. The XML Validator is uniquely packaged to validate from the command line with a host of options to facilitate use in batch scripts or to validate a whole set of documents in one go. It is one of the first tools to support a draft of the OASIS XML Catalog specification for entity resolution." The ElCel Technology Canonical XML Processor "is a free command-line utility built using the SAX 2.0 interface of our C++ XML Toolkit. It implements the canonicalization algorithm as described by the W3C's Canonical XML recommendation. It also implements the original Canonical XML specification from James Clark. This is a very useful program for converting valid XML with a DTD into a standalone document." Both tools may be downloaded for free. [Full context] [June 11, 2001] The W3C XForms Working Group has published a new Working Draft of XForms 1.0 that "incorporates new material agreed upon at the Boston face to face meeting, including the adoption of XML Schema to replace XForms Simple Syntax, as well as initial efforts at modularizing XForms and additional feedback from outside sources. XForms are the W3C's response to demands from Web applications and eCommerce solutions, which require Web forms with richer interactions. XForms are the successor to XHTML forms, and benefit from the lessons learned in the years of HTML forms implementation experience. The specification represents extended analysis, followed by the creation of a new platform-independent markup language for online interaction between an XForms Processor and a remote entity. More flexible than previous HTML and XHTML form technologies, the new generation of Web forms called 'XForms' separates purpose, presentation, and data. The specification introduction includes a brief tutorial on XForms and a discussion of design principles behind XForms. Core chapters contain the XForms reference manual. The bulk of the reference manual consists of the specification of XForms. This reference defines what may go into XForms and how XForms Processors must interpret the various components in order to claim conformance. Appendixes contain a normative description of XForms described in XML Schema, information on optional function libraries, references, a change history, and other useful information." [Full context] [June 09, 2001] An announcement from TIBCO Software Inc. describes the release of a new streaming XML validator with full support for W3C XML Schema. Details: Tibco has "announced the commercial release of XML Validate, a member of the TIBCO Extensibility product family. XML Validate is an enterprise-grade solution for validating streaming XML documents or messages against an XML Schema or DTD. The Simple API for XML (SAX)-based implementation for run-time validation provides organizations with the core component in developing high bandwidth, XML-based processing. This release of XML Validate is also the first commercially available validator to fully support the World Wide Web Consortium (W3C) XML Schema Recommendation. The XML Schema Recommendation was released [2001-05-02] by the W3C... this XML Schema validation support will facilitate the creation of XML driven ecosystems based on open-standards. Additionally, XML Validate supports the validation of DTDs to allow connectivity with organizations not currently using XML Schema. XML Validate is a core building block for creating an e-commerce processing engine for XML documents and messages. As organizations conduct e-commerce with a growing and global audience, the processing capabilities of XML Validate can scale to the demand. XML Validate has the potential of handling millions of transactions per day per server. XML Validate can easily be inserted into an existing XML parsing scenario, enabling validation to occur the instant it is received by the parser. Because SAX is an event-based API, XML Validate is the ideal solution in a streaming run-time environment, creating an enterprise-grade XML processing engine." [Full context] [June 09, 2001] The W3C HTML Working Group has published an updated working draft specification for 'XHTML Events', designed to "(1) expose the DOM event model to an XML document, (2) provide for new event types without requiring modification to the DOM or the DTD, and (3) to support integration with other XML languages." The new draft supersedes the previous working draft of 2000-08-28; changes are provided in the diff-marked HTML version. The XHTML Events module specification "defines an element onevent which represents a DOM level 2 event listener. The element onevent and its associated markup encapsulate the various aspects of the the DOM level 2 event interface, thereby providing markup level access for specifying the actions to be taken during the various phases of event propagation." From the document abstract: "The XHTML Events module defined in this specification provides XHTML host languages the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 2 event interfaces. The result is to provide XHTML based languages an interoperable way of associating behaviors with document-level markup. In addition, this specification defines a subset of the XHTML Events module called basic events for use on simpler client devices. Finally, the XHTML Event Types Module defines the XHTML language event types." The DTD Implementation is provided in the normative Appendix A. [Full context] [June 09, 2001] A communiqué from James Anderson reports on a "preliminary re-release of CL-XML which (1) includes not only a validating XML parser/processor, but also XPath and XQuery compilers, (2) supports namespace-aware DTD-based validation, and (3) can claim conformance. CL-XML is a collection of Common LISP modules for data stream parsing and serialization according to the Extensible Markup Language and ancillary standards. The modules perform parsing and serialization between XML, XML Query, and XML Path expressions and DOM-compatible CLOS instances." The associated Web site provides extensive doumentation for CL-XML, including separate BNF descriptions of the XML, XPath, and XQuery syntax used to generate the parsers. According to the site description: "The processor is intended for use both as a stand-alone XML interface and as an extension to the CL-HTTP server. The XML module implements a conformant, namespace-aware, validating XML processor which instantitiates an Info-Model compatible document model. The processor always incorporates external references. A referenced document definition is instantiated and incorporated in the document instance as an internal document type definition model. The definition is used to effect instance defaulting and typing and to perform in-line document validation. The parser can be invoked with validation enabled or disabled. It can be invoked so as to produce a data instance, a parse tree, or to parse without generating a result. The XMLPath module implements access to document models based on XML Path expressions. It includes an implementation for the XML Path library, an interpreter for paths formulated as S-expressions and, a parser to translate string-encoded expressions into the equivalent S-expression form. The XMLQuery module implements access to document models based on XML Query expressions. These incorporate XML Path expressions to address document elements and extend them with construction operations. The module includes an implementation for the XML Query library, an interpreter for queries formulated as S-expressions and, a parser to translate string-encoded expressions into the equivalent S-expression form. The base CLOS model comprises a class library which implements the XML Query Data Model and presents an Infoset compatiable programming interface." [Full context] [June 06, 2001] Members of the W3C XLink/XSL Joint Task Force (XML Linking and XSL Working Groups) have released a conceptual model specification for the interaction of XLink linking elements and styling. The document XML Linking and Style has been published as a W3C NOTE, and addresses the (hitherto unclarified) "interaction of XLink linking elements and styling." Background to the NOTE is provided in the document Introduction: "Linking and styling have significant interactions: on the one hand, style may be applied to elements because they participate in links; on the other hand, selecting a link may modify, replace, or create a new document which must then be styled. This note introduces a conceptual model for describing the interactions of XLink linking elements and styling. It then shows how this model may be applied in two different ways: (1) Using current and anticipated technologies supported by existing W3C Recommendations [and Working Drafts, Candidate Recommendations, and Proposed Recommendations]. (2) In an environment where the XSLT processor provides significantly more functionality for linking and contains several new features." Appendix B contains the (Non-Normative) "Summary of Proposed Changes to XSLT." [Full context] [June 06, 2001] A communiqué from Misha Davidson (SilverStream Inc.) describes the release of 'jBroker Web' as a public beta version of a new SOAP ORB product. jBroker Web is "a complete XML RPC environment for platform-independent building, running, and invoking Web services using Java. It supports writing Web service interfaces using WSDL as well as Java. jBroker Web provides a complete set of compilers for converting WSDL to Java and vice versa, as well as for generating client and server XML RPC glue (stubs and skeletons) code. It comes with a high-performance, scalable SOAP 1.1 runtime that uses HTTP transport and is on-the-wire compatible with Apache SOAP and .NET. JBroker Web-generated skeletons are Java servlets. They can be deployed in any J2EE Web Application container using standard J2EE Web Application deployment. They can also benefit from the standard J2EE security features like authentication, access control, and confidentiality using SSL." [Full context] [June 06, 2001] At the JavaOne Developer Conference, Sun Microsystems has issued several announcements for support of XML-based web services. Sun revealed its plans for native support of 'web services' as key components in the next version of the Java 2 Platform, Enterprise Edition (J2EE). "Working through the Java Community Process, Sun will leverage several web services related technology projects now underway in the JCP." Sun also "announced plans to make available a Web Services Pack, an all-in-one download containing key technologies to simplify building of web services using the Java 2 Platform. The announcement also lays out the roadmap for incorporation of the technologies into integrated development environments (IDEs) from key software development tools suppliers. The Web Services Pack is a collection of application programming interfaces (APIs) and architectures developed by Sun and the other members of the Java Community that provide support in the Java technology for important web services features. These are to include: (1) JavaServer Faces, which establishes a standard API for creating Java Web application graphical user interfaces (GUIs), eliminating the burden on developers to create and maintain the GUI infrastructure from scratch. (2) Tomcat, a free, open-source implementation of JavaServer Pages and Java Servlet technologies developed under the Jakarta project at the Apache Software Foundation. (3) JAX Pack, a collection of XML-based Java APIs [Java API for XML Processing, Java API for XML Registries, Java API for XML Messaging, Java Architecture for XML Binding, Java API for Remote Procedure Call]." The new Java Community Process web site lists ten JSRs (Java Specification Requests) which focus on the development of Java technology APIs specifically targeted at building XML-based applications. [Full context] [June 06, 2001] Microsoft recently announced the release of three new 'Web Services' specifications which support its effort to "combine the best aspects of component-based development and the Web, and provide a cornerstone of the Microsoft .NET programming model." The specifications are provided "as-is, for review and evaluation only." (1) SOAP Routing Protocol (SOAP-RP) is a "SOAP-based, stateless protocol for exchanging one-way SOAP messages from an initial sender to the ultimate receiver, potentially via a set of intermediaries. In addition, SOAP-RP provides an optional reverse message path enabling two-way message exchange patterns like request/response, peer-to-peer conversations, and the return of message acknowledgements and faults. SOAP-RP is expressed as a SOAP header entry within a SOAP envelope making it relatively independent of the underlying protocol. This specification defines the use of SOAP-RP in combination with TCP, UDP, and HTTP but other underlying protocols are possible." (2) Direct Internet Message Encapsulation (DIME) is a "lightweight, binary encapsulation format that can be used to encapsulate multiple application defined entities or payloads of arbitrary type and size into a single message construct. It is used by SOAP-RP as the encapsulation mechanism when exchanged directly over TCP or UDP in order to support encapsulation of attachments to the SOAP-RP message as well as to provide efficient message delimiting." (3) XLANG is an "XML business process language which provides a way to orchestrate applications and XML Web services into larger-scale, federated applications by enabling developers to aggregate even the largest applications as components in a long-lived business process. XLANG has a two-fold relationship with WSDL. An XLANG service description is a WSDL service description with an extension element that describes the behavior of the service as a part of a business process. XLANG service behavior may also rely on simple WSDL services as providers of basic functionality for the implementation of the business process." [Full context] [June 05, 2001] Significant progress has been made on the specification for 'RELAX NG' since the April 2001 announcement by the TREX and RELAX design teams declaring their intent to unify the two similar structure-validation languages. The OASIS Technical Committee originally chartered under the name TREX has been named RELAX NG, and key draft documents have been published as sketches for the new validation language. These include a RELAX NG Tutorial, a RELAX NG Formal Semantics specification, and a draft RELAX NG schema for RELAX NG. The goals for RELAX NG are summarized in a recent announcement from the TC: "Members of the OASIS TREX Technical Committee announced their decision to integrate TREX (Tree Regular Expressions for XML) and RELAX (REgular LAnguage description for XML) in order to collaborate on a unified lightweight specification for validating XML-based languages. They renamed their work RELAX NG. RELAX was initially developed at the Information Technology Research and Standardization Centre (INSTAC) in Japan, which advances Japanese national standards for XML under the auspices of the Japanese Standard Association (JSA). TREX was created by James Clark, widely regarded as one of the most prolific contributors to the field of structured information standards. Clark decided to continue development of his schema language at the OASIS XML interoperability consortium in March 2001. 'RELAX and TREX both focus on simplicity,' said James Clark, chair of what is now the OASIS RELAX NG Technical Committee. 'RELAX NG will remain straightforward and easy to use, incorporating the best of TREX and RELAX.' Said Murata Makoto, one of the original developers of RELAX: 'It is important to note that RELAX NG is not intended to replace the W3C XML Schema Recommendation. Instead, it represents a lightweight alternative to Schema. We believe that users are likely to adopt multiple schema languages, and many will find RELAX NG fills a very important need.' According to the OASIS technical committee, the specification offers a middle ground that will make RELAX NG a useful tool for many developers. The team is interested in facilitating conversion among DTDs, XML Schema and RELAX NG. 'RELAX NG fits in well with the W3C XML Schema Formal Description,' added Clark. 'Our hope is that RELAX NG will be a constructive influence on the future development of XML Schema'." [Full context] [June 04, 2001] The XML Application Development team at IBM's alphaWorks lab has released an 'XRR' data management tool which supports registration, searching, and delivery for XML resources. The IBM XML Registry/Repository (XRR) is "a data management system that manages and provides services for XML artifacts including schemes (DTD, XSD), stylesheets (XSL) and instance documents (WSDL). User can use XRR to obtain an XML artifact automatically, search or browse for an XML artifact, deposit an XML artifact with or without related data, and register an XML artifact without deposit. The XRR 'Registry' service is "where organizations submit and register DTDs, schemes, stylesheets, and other types of XML documents. Once approved, these documents are referred to as registered objects. The registry provides a search of registered objects based on their metadata. Registry facilities include (1) Registration: An organization must first register itself with the registry as a submitting organization (SO) before it can make submissions. SO make submissions through one of its contacts whose role is referred to as a submitter. The 'submitter' must always be authenticated. Only an SO can make submissions. (2) Search and Retrieval Registered Object: Anyone can search the registry for registered objects based on their matadata. No authentication is required. (3) Administration: A Registry Administrator can change user status and get the registry content. The 'Repository' service "provides access to registered objects. Through the repository, a user can download a registered object using standard identifiers (URLs)." The current version of XRR runs on Windows NT, Windows 2000, Linux, AIX, and Solaris; it supports basic Servlet/JSP functionality. [Full context] [June 01, 2001] Two new specifications relating to 'Ruby' annotation have been released by the W3C. 'Ruby' are "small character annotations, sometimes added to the characters of an ideographic script like Japanese, to clarify the pronunciation (and/or the meaning) of those characters. They are usually put in a very small font, along the side of the ideogram in vertical text, or at the top in horizontal text... Ruby annotations are used frequently in Japan in many kinds of publications, including books and magazines; a sequence of ideographic characters (kanji) is supplemented with the simpler hiragana which show how the word should be pronounced. Ruby is also used in China, especially in schoolbooks. Ruby text is usually presented alongside the base text, using a smaller typeface. The name 'ruby' in fact originated from the name of the 5.5pt font size in British printing, which is about half the 10pt font size commonly used for normal text. While many international typography needs can be fulfilled through the use of style sheet languages such as CSS or XSL, additional markup is needed [in this case] to define the relationship between the base text and its annotation. Ruby Annotation delivers this functionality to the Web in the form of an XHTML module, thus allowing ruby to be correctly rendered along with the basic text without using special workarounds or graphics. XHTML 1.1 includes the Ruby Annotation module, enhancing XHTML 1.1's power and extensibility." As part of the W3C Internationalization Activity, the Internationalization Working Group has produced a markup specification for ruby which is now a W3C Recommendation, Ruby Annotation. A companion document Implementing the Ruby Module from Masayasu ISHIKAWA has been released as a W3C Note. It describes sample module implementations of the abstract definition of ruby annotation markup using several schema notations: XML DTD, RELAX, TREX, and the W3C XML Schema. This document also illustrates W3C's Amaya browser/editor implementation of ruby as part of XHTML 1.1. [Full context] [June 01, 2001] The World Wide Web Consortium has now issued XHTML 1.1 - Module-based XHTML as a W3C Recommendation, indicating that the XHTML 1.1 specification "is stable, contributes to Web interoperability, and has been reviewed by the W3C Membership, who are in favor of supporting its adoption by academic, industry, and research communities. The specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML. The purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 that was brought forward into the XHTML 1.0 document types. The XHTML 1.1 document type is essentially a reformulation of XHTML 1.0 Strict using XHTML Modules. This means that many facilities available in other XHTML Family document types (e.g., XHTML Frames) are not available in this document type. These other facilities are available through modules defined in Modularization of XHTML, and document authors are free to define document types based upon XHTML 1.1 that use these facilities. The document type is designed to be portable to a broad collection of client devices, and applicable to the majority of Internet content. Content developers who base their content upon XHTML 1.1 can trust that it will be consistently portable across user agents which support XHTML." [Full context] More Information on Robin Cover's XML pages at xml.coverpages.org |
