The Cover PagesThe Cover Pages: The Online Resource for Markup Language Technologies
Advanced Search
Site Map
CP RSS Channel
Contact Us
Sponsoring CP
About Our Sponsors

Cover Stories
Articles & Papers
Press Releases

XML Query

XML Applications
General Apps
Government Apps
Academic Apps

Technology and Society
Tech Topics
Related Standards
OASIS provides the Cover Pages as a public resource to document and encourage the use of open standards that enhance the intelligibility, quality, and longevity of digital information.

Cover Stories

Web Services Calendar (WS-Calendar) TC to Create Common Scheduling Standard.   OASIS announced a new Web Services Calendar (WS-Calendar) TC, chartered to adapt existing calendaring and scheduling specifications to develop a Common Scheduling standard that defines how schedule, event, and interval information is passed between/within services. Beginning with the 'iCalendar XML Representation' standard from CalConnect/IETF, the TC will create a specification for creating, retrieving, updating, and deleting calendar events on a schedule.

OASIS Public Review: Content Management Interoperability Services (CMIS) v1.0.   The OASIS Content Management Interoperability Services (CMIS) TC approved a Committee Draft of the CMIS Version 1.0 specification for public review through December 22, 2009. CMIS defines a domain model along with Web Services and Restful AtomPub bindings that can be used by applications to work with different content management repositories/systems. CMIS defines generic/universal CMS capabilities, and the interface is layered on top of existing CM systems.

Apache Software Foundation Launches Chemistry Incubation Effort for CMIS.   The Apache Software Foundation (ASF) announced a new Incubator project to support the OASIS Content Management Interoperability Services (CMIS) specification. The Apache Chemistry Incubation development effort will implement the latest draft of the CMIS specification and provide input to the TC on the implementation details. It is also anticipated that the group will produce a CMIS Reference Implementation (RI) and a CMIS Technology Compatibility Kit (TCK).

W3C XML Security Working Group Invites Public Review of New Working Drafts.   The W3C XML Security Working Group has published eight (First Public) Working Drafts for review, including "XML Signature 1.1" and "XML Encryption 1.1". Members of the WG would appreciate feedback on these documents, with special attention to the algorithms and other proposed changes. In parallel with this v1.1 technical work, the XML Security Working Group is developing requirements and designs for a more radically different version 2 of XML Signature.

Open Virtualization Format (OVF) Version 1.0 Published as a DMTF Standard.   Distributed Management Task Force has published "Open Virtualization Format Specification v1.0 as a DMTF Standard. OVF describes an open, secure, portable, and extensible format for packaging and distribution of software to be run in virtual machines. OVF uses XML for capturing metadata about virtual appliances. Packaging virtual appliances in OVF independent software allows vendors to create pre-packaged appliances that run on any virtualization platform.

Charter Proposed for OASIS Emergency Management Adoption Technical Committee.   OASIS members have published a Proposed Charter for creation of a new TC to support adoption of emergency management specifications. The OASIS Emergency Management (EM) Adoption Technical Committee draft charter identifies the goal as collaboration to provide expertise and resources to educate the marketplace on the value of the Emergency Management OASIS Standards, including the Common Alerting Protocol (CAP) and Emergency Data Exchange Language (EDXL).

OASIS Members Form Key Management Interoperability Protocol (KMIP) Committee.   Brocade, EMC/RSA, HP, IBM, LSI, NetApp, Seagate, and Thales submitted a charter proposal for an OASIS Key Management Interoperability Protocol (KMIP) TC, based upon draft specifications. The TC will standardize KMIP for interoperability of key management services with key management clients. KMIP addresses requirements for key lifecycle management, key sharing, and long-term availability of cryptographic objects (public/private keys, certs, symmetric keys).

Oracle Beehive Object Model Proposed for Standardization in OASIS ICOM TC.   OASIS published a charter for a proposed TC to define an integrated collaboration object model supporting a complete range of enterprise collaboration activities. The ICOM data model is based upon the Oracle Beehive Object Model. The new standard model, interface, and protocol supports contextual collaboration within business processes for an integrated collaboration environment which includes communication, teamwork, content, and coordination artifacts.

Microsoft Publishes Implementation Notes for File Formats in Office 2007 SP2.   Microsoft announced the publication of an initial set of document-format implementation notes for the company's ODF 1.1 implementation in Office 2007 SP2. The Document Interoperability Initiative (DII) Web site provides hypertext access to the detailed notes, linked from the online ODF specification, covering implementation decisions, additional file data, and implementation variances. Similar implementation notes will be published for Open XML (ECMA 376).

Web Services Test Forum (WSTF) Addresses End User Interoperability Scenarios.   Industry partners have announced the Web Services Test Forum (WSTF), designed as an open community to improve the quality of the Web services standards through interoperability testing. The Forum provides a customer-centric focus driven by end user testing scenarios. WSTF has a lightweight structure: no Board, no centralized authority, no dues, few barriers to participation, and no allowance for IPR encumbrances. Individuals and corporate entities may join.

Office Open XML File Formats Published as ISO/IEC 29500:2008 Final Standard.   ISO announced the publication of the Office Open XML File Formats specification as an ISO/IEC joint standard. ISO/IEC 29500 specifies a family of XML schemas, collectively called Office Open XML, which define the XML vocabularies for word-processing, spreadsheet, and presentation documents, as well as the packaging of documents that conform to these schemas. A new Document Interoperability WG will help align ISO/IEC 29500 with ISO/IEC 26300 (OpenDocument).

W3C Forms New Web Services Resource Access (WS-RA) Working Group.   W3C has launched the Web Services Resource Access (WS-RA) Working Group, chartered to standardize a general mechanism for accessing and updating the XML representation of a resource-oriented Web Service and metadata of a Web Service, as well as a mechanism to subscribe to events from a Web Service. W3C Recommendations will be produced based upon five Member Submissions: WS-Transfer, WS-ResourceTransfer, WS-Enumeration, WS-MetadataExchange, and WS-Eventing.

Microsoft 'Geneva' Framework Supports SAML 2.0, WS-Federation, and WS-Trust.   Microsoft has announced a new identify management strategy under code-name 'Geneva'. This single, simplified, claims-based identity model includes support for several standards in the federated identity space, including SAML 2.0, WS-Federation, and WS-Trust. Components include Geneva Framework for building claims-aware .NET applications, Geneva' Server, and Windows CardSpace 'Geneva'. A Beta release was unveiled at the Microsoft PDC, available for download.

Public Review for OpenID Provider Authentication Policy Extension (PAPE) 1.0.   Members of the OpenID Provider Authentication Policy Extension (PAPE) Working Group have released PAPE Draft 7 for 60-day public review. The PAPE extension to the OpenID Authentication protocol provides a mechanism by which a Relying Party can request that particular authentication policies be applied by the OpenID Provider when authenticating an End User. For example, phishing-resistant, time-related, or multi-factor authentication methods may be requested.

EAS-CAP Industry Group Publishes Profile for the Common Alerting Protocol.   The EAS-CAP Industry Group has released a draft "EAS-CAP Industry Group EAS-CAP Profile Recommendation EAS-CAP-0.1" for public comment. ECIG is providing the profile as a recommendation to U.S. governmental agencies and industry associations on the use of CAP (Common Alerting Protocol) for Emergency Alert System (EAS) purposes, including the FCC, FEMA, National Weather Service, and other organizations. CAP is an OASIS Standard and an ITU-T Recommendation.

OASIS Identity Metasystem Interoperability TC Advances Information Card Use.   OASIS announced the formation of a new Identity Metasystem Interoperability (IMI) Technical Committee, chartered to increase the quality and number of interoperable implementations of Information Cards and associated identity system components to enable the Identity Metasystem. The goal of the IMI TC specification development work to provide the interoperability support that will enable Information Card use to become ubiquitous.

Open Web Foundation Formed to Support Community Specification Development.   Open source community leaders announced a new Open Web Foundation which seeks to apply a hybrid open source model to community-based specification development. OWF will focus on: (1) Incubation: lightweight process for creating open web specifications; (2) Licensing: or really no licensing, through non-assertion covenants; (3)Copyright: Creative Commons model; Community: collaboration of individuals and companies held accountable to support the Open Web.

Vendors Publish Content Management Interoperability Services (CMIS) Standard.   EMC, IBM, and Microsoft have published "Content Management Interoperability Services (CMIS)", distributed as four prose documents with supporting XML schemas. The CMIS standard defines a domain model and set of bindings, such as Web Service and REST/Atom, that can be used by applications to work with one or more Content Management repositories/systems. Alfresco, Open Text, Oracle, and SAP collaborated on CMIS, now proposed for submisssion to an OASIS TC.

W3C Member Submission for Creative Commons Rights Expression Language (ccREL).   W3C has published the text of a Member Submission from Creative Commons: "ccREL: The Creative Commons Rights Expression Language." ccREL builds upon the astronomical success of Creative Commons licenses, which are embeddable machine-readable legal instruments allowing authors to express permissions for others to share, remix, and reuse content. ccREL is a new XML/RDF machine-readable language to express copyright licensing terms and related information.

OASIS/ITU-T Common Alerting Protocol (CAP) Receives Support from FEMA and WMO.   Federal Emergency Management Agency (FEMA) and World Meteorological Organization (WMO) announcements highlight adoption of the XML-based Common Alerting Protocol. CAP defines a format for exchanging all-hazard emergency alerts and public warnings over multiple networks. FEMA announced a CAP Profile for the Integrated Public Alert and Warnings System. WMO issued a CFP for a December 2008 CAP Implementers Workshop in Geneva, co-sponsored by OASIS and ITU-T.

Balisage 2008 Conference in Montreal Continues Extreme Markup Tradition.   "Balisage 2008: The Markup Conference" continues the popular Montreal series (formerly "Extreme Markup Languages") under a new title "Balisage." Organizers have published the complete program for the main conference (August 12-15, 2008) and for the "International Symposium on Versioning XML Vocabularies and Systems" (August 11). Topics: Semantic Web, ontology design, schema mashups, constraint management, topic maps, annotating overlap, digital libraries...

W3C Publishes Approved TAG Finding on Associating Resources with Namespaces.   W3C has published "Associating Resources with Namespaces" as an Approved TAG Finding from the W3C Technical Architecture Group (TAG). The document addresses the question of how ancillary information (schemas, stylesheets, documentation) can be associated with an XML namespace. It offers guidance on how a namespace document can be optimally designed for humans and machines such that information at the namespace URI conforms to web architecture good practice.

Information Card Foundation Formed to Support User-Centric Digital Identity.   Equifax, Google, Microsoft, Novell, Oracle, and Paypal have announced the formation of the Information Card Foundation (ICF) as an independent, not-for-profit organization designed to advance the adoption and use of Information Cards across the Internet. ICF's mission is to advance the use of the Information Card metaphor as a key component of an open, interoperable, royalty-free, user-centric identity layer spanning both the enterprise and the Internet.

New OASIS Standard: XML Localization Interchange File Format (XLIFF) v1.2.   OASIS has announced the approval of the XML Localization Interchange File Format (XLIFF) specification v1.2 as an OASIS Standard. It was produced by the OASIS XML Localisation Interchange File Format (XLIFF) TC. The purpose of the XLIFF vocabulary is to store localizable data and carry it from one step of the localization process to the other, while allowing interoperability between tools. XLIFF is tool-neutral and supports the entire localization process.

OGC Approves Sensor Web Observations and Measurements Encoding Standard.   The Open Geospatial Consortium announced the approval of the Observations and Measurements Encoding V1.0 specification as a final OpenGIS Implementation Standard. The standard defines an abstract model and an XML schema encoding for observations and measurements as part of a framework required for use by other OGC Sensor Web Enablement (SWE) standards and for support of OGC compliant systems dealing in technical measurements in science and engineering.

Public Draft for HTML 5: A Vocabulary and Associated APIs for HTML and XHTML.   W3C announced a First Public Working Draft of "HTML 5: A Vocabulary and Associated APIs for HTML and XHTML" as a major revision of the World Wide Web's core language. HTML 5 is intended to replace HTML4, XHTML 1.x, and DOM2 HTML. New features are introduced for Web application authors; new elements are introduced based on prevailing authoring practices; processing models and clear conformance criteria are defined for user agents to improve interoperability.

W3C Publishes SPARQL Protocol and RDF Query Language Semantic Web Standard.   SPARQL (recursive acronym for "SPARQL Protocol and RDF Query Language") has been released as a standard by W3C. The three-part specification was produced by the RDF Data Access Working Group as part of the W3C Semantic Web Activity. SPARQL defines a standardized query language for RDF enabling 'joining' of decentralized collections of RDF data. SPARQL queries hide the details of data management to lower costs and increase robustness of Web data integration.

OASIS Members Propose Charter for WS-BPEL Extension for People (BPEL4People) TC.   OASIS member companies have submitted a charter proposal for a WS-BPEL Extension for People (BPEL4People) Technical Committee. Companies sponsoring the proposal include Active Endpoints, Adobe, BEA, IBM, Oracle, SAP, Software AG, and Sun Microsystems. Building upon the June 2007 two-part industry BPEL4People specification, this TC would define extensions to WS-BPEL 2.0 to enable human interactions, along with a model enabling the definition of human tasks.

More Cover Stories

Hosted By
OASIS - Organization for the Advancement of Structured Information Standards

Sponsored By

IBM Corporation
ISIS Papyrus
Microsoft Corporation
Oracle Corporation


XML Daily Newslink
Receive daily news updates from Managing Editor, Robin Cover.

 Newsletter Subscription
 Newsletter Archives
Globe Image        Articles
  • "A Uniform Resource Name (URN) for Early Warning Emergency Services and Location-to-Service Translation (LoST) Protocol Usage." IETF Standards Track Internet Draft. October 26, 2008, expires April 29, 2009. Edited by Brian Rosen (NeuStar, Inc) Henning Schulzrinne (Columbia University, Department of Computer Science), and Hannes Tschofenig (Nokia Siemens Networks). Produced by members of the IETF Session Initiation Proposal Investigation (SIPPING) Working Group. The Common Alerting Protocol (CAP) is an XML document format for exchanging emergency alerts and public warnings. Different organizations issue alerts for specific geographical regions. The Location-to-Service Translation (LoST) protocol provides a way to discover servers that distribute these alerts for a geographical region. This document defines the Service Uniform Resource Names (URN)s for warnings in the same way as they have been defined with RFC 5031 for citizen-to-authority emergency services. Additionally, this document suggests to use LoST for the discovery of servers distributing alerts. This document makes use of RFC 5222 ("LoST: A Location-to-Service Translation Protocol"). However, instead of performing a translation from location information and a Service URN to a PSAP URI (plus supplementary information), as used with "Best Current Practice for Communications Services in support of Emergency Calling", for the citizen-to-authority emergency services use case, the LoST client asks the LoST server for a URI to receive further information on how to obtain warning alerts. In a response the URIs in the 'uri' element MUST be from the following format: sip, xmpp or http. The SIP URI MUST subsequently be used with "Session Initiation Protocol (SIP) Event Package for the Common Alerting Protocol (CAP)". An XMPP URI MUST be used as described in "Common Alerting Protocol (CAP) Over XMPP". An HTTP URI MUST be used with GeoRSS. In a LoST response the optional 'serviceNumber' element is not used by this specification. In mapping citizen-to-authority services, receiving multiple mappings is an exception. However, since many organizations may provide warnings for the same area, this is likely to be more common for alerts. As such, the extensions defined in "Location-to-Service Translation Protocol (LoST) Extensions" (e.g., the ability to limit the number of returned mappings) are useful in this context...

  • "Sense/Net Adopts the CMIS Standard — the First in .NET World." By Tamás Bíró. Sense/Net 6.0 DevBlog. "We have developed a CMIS draft implementation in Sense/Net 6.0 Beta 2, soon to be released. It is possibly the first .NET implementation, as all supporting companies except from Microsoft are JAVA based. It is surely the first open source implementation on the .Net platform... Since Sense/Net 6.0 is both an Enterprise Portal and an Enterprise Content Management System, with its own Content Repository, we wanted to showcase how easy it is to use the .NET platform, WCF and Sense/Net 6.0 to implement the standard [see screenshot]. Our demo is a two way implementation, because our content repository has a CMIS service interface and our portal has a CMIS client Webpart (portlet). So other CMIS clients can access our contents, but our portal can aggregate content from other CMIS compliant systems, such as next generation SharePoint, Alfresco and others. We are also building an online CMIS demo, which is accessible from our website, but is under construction, so it might not work all the time. [Simple CMIS Client, Simple CMIS Aggregate Client] The demo features two CMIS webparts. One is able to navigate the content repository; the other is able to aggregate content from two sources that you can enter. The screenshot above is the CMIS test webpart, showing the PFS root contents. The services can also be accessed, just copy the URI-s from the input boxes. It even works with a simple browser, showing XML. There is no authentication, so no login is required. The source code will be available within a few days..." Related information from the Sense/Net Wiki: "How Does the Implementation of CMIS Work with Sense/Net 6.0?" [See also Sense/Net Enterprise Portal and ECMS from CodePlex.]

  • "Hierarchy Extensions to Atom Feeds." Edited by Nikunj Mehta [WWW] and Colm Divilly [WWW] (Oracle). Posted October 31, 2008 to the atom-syntax list; with followups. Also available in HTML format. This specification defines a mechanism to create and remove AtomPub collections using the AtomPub protocol as well as to express hierarchies of feeds within the Atom Syndication Format. Many applications provide their data in the form of syndicated Web feeds using formats such as Atom (RFC 4287 = Nottingham, M., Ed. and R. Sayre, Ed., The Atom Syndication Format, December 2005) in order to enable application integration. Applications may also manipulate the contents of these data feeds using protocols such as AtomPub (RFC 5023 = Gregorio, J. and B. de hÓra, The Atom Publishing Protocol, October 2007). A key requirement for application data feeds is the ability to dynamically create new Collections and identify relationships among such feeds and Collections. This specification defines a mechanism for identifying hierarchical master-detail relations among data feeds so that consumer applications can perfrom standard AtomPub operations on them. A hierarchical master-detail relation of an Entry to a Feed implies the detail Feed is created when the master Entry is created and the Feed is removed when the Entry is removed. The Entry is called the "master entry" and the Feed is called "detail feed". This relationship allows a client to use AtomPub to create a new Collection by posting an Entry to an existing Collection... Protocol Model: Hierarchy extensions to Atom specify operations for creating, updating, and removing AtomPub Collections using existing AtomPub methods and extensions to Atom syntax. Feed Classification: AtomPub defines Feed, Entry, and Collection resources in the Atom syntax; the hierarchy extensions to Atom are designed for use with unmodifiable Atom Feeds as well as with AtomPub Collections. The extensions in this specification define two specialized kinds of Feeds — master Feed and detail Feed. Both are represented as Atom Feed Documents..."

  • "Microsoft Joins AMQP Working Group for Open Standards Messaging Software." Staff, Microsoft Announcement. Microsoft Corp. announced that it is joining the Advanced Message Queuing Protocol (AMQP) Working Group, an organization focused on the development of the AMQP specification. Microsoft is joining the AMQP Working Group at the request of its members, including several of Microsoft's customers in the financial services industry, in order to support the development of an open industry standard for ubiquitous messaging. AMQP is a specification for platform-neutral, open standards-based business messaging. The primary goal of AMQP is to enable the communications necessary for business processes. AMQP Working Group members are collaborating on specifications for messaging infrastructure that provide businesses with a simple and more powerful way of connecting messaging-dependent applications both within and between firms. By joining the AMQP Working Group, Microsoft is seeking to contribute toward the development of such solutions and to enable greater customer choice in the marketplace. Message-based transports with security and transactional integrity are a vital infrastructure component throughout institutions. As Microsoft continues to provide vertical industry solutions, AMQP will provide an alternative to current messaging options. The AMQP specification and related implementations may provide greater interoperability for a number of vertical scenarios in addition to financial services, insurance and healthcare, among others. Members of the AMQP Working Group inculde Cisco, Credit Suisse, Deutsche Boerse Systems, Envoy Technologies Inc., The Goldman Sachs Group Inc., iMatix Corporation, IONA Technologies, J.P. Morgan, Novell, Rabbit Technologies Ltd., Red Hat Inc., TWIST Process Innovations Ltd., WSO2 and 29West Inc.

Press Releases

TC to Advance Interoperability and Conformance of OpenDocument Format (ODF) Applications.

Proposal to Create Trust Exchange (TX) Working Group.

OpenID Provider Authentication Policy Extension (PAPE) Public Review.

JanRain Launches RPX and OPX Hosted OpenID Solutions. 3.0 Released.

New OASIS TC to Enable Exchange of Healthcare Security and Privacy Information.

ECIG Publishes CAP Profile for Broadcast Emergency Alert System.

New Products Pass SAML 2.0 Interoperability Testing.

OASIS Members Form TC to Advance Information Cards Interoperability Standard.

DMTF Announces Virtualization Management Initiative (VMAN).

Open Text Completes CMIS Prototype .

Delhi Transit Routing Interoperability Pilot (D-TRIP).

EMC, IBM, and Microsoft Author CMIS for Enterprise Content Management Systems.

Alfresco Labs Provides First Draft CMIS Implementation.

Open SAML 2.0 Toolkits and Reference Implementations for eGov Federations.

OASIS WS-DD TC to Standardize WS-Discovery, SOAP-over-UDP, and DPWS.

OASIS CFP: Cross-Enterprise Security and Privacy Authorization TC.

New Open Grid Forum Documents Issued for Public Comment.

Public Comment Invited on OpenGIS Web Coverage Service Extensions.

Creative Commons Global Case Studies Project.

Red Hat MRG V1 Supports Advanced Messaging Queuing Protocol (AMQP).

Document URI:  —  Legal stuff
Robin Cover, Editor: