This issue of XML Daily Newslink is sponsored by:
Sun Microsystems, Inc. http://sun.com
- W3C Call for Implementations: XML Schema Definition Language (XSD) 1.1
- Enhanced Oracle Beehive Collaboration Suite Version 1.5
- Cartella: Unified Social Content Management
- Visible Signature Profile of the OASIS Digital Signature Services Version 1.0
- W3C Workshop on Using Ink in Multimodal Applications
- NETCONF Over Transport Layer Security (TLS)
W3C Call for Implementations: XML Schema Definition Language (XSD) 1.1
Staff, W3C Announcement
Members of the W3C XML Schema Working Group invite implementation feedback on the Candidate Recommendation specifications for XML Schema Definition Language (XSD) 1.1. The XSD 1.1 specification consists of Part 1: Structures and "Part 2: Datatypes. XSD provides tools for describing the structure of XML content and constraining the contents of XML documents. Part 2 provides tools for defining datatypes (dates, times, numbers, strings, etc.) to be used in XML Schemas as well as other XML specifications. Both parts present a detailed list of changes since XSD Version 1.0. XSD 1.1 retains all the essential features of XSD 1.0, but adds several new features to support functionality requested by users, fixes many errors in XSD 1.0, and clarifies wording. This draft was published on 30-April-2009.
The major revisions in XSD 1.1 since the previous public working draft include the following (excerpt): (1) To reduce confusion and avert a widespread misunderstanding, the normative references to various W3C specifications now state explicitly that while the reference describes the particular edition of a specification current at the time this specification is published, conforming implementations of this specification are not required to ignore later editions of the other specification but instead may support later editions, thus allowing users of this specification to benefit from corrections to other specifications on which this one depends. (2) The discussion of 'schemaLocation' information in How schema definitions are located on the Web has been revised to try to make clearer the motivation for recommending user control over whether schema locations specified in the document instance should or should not be dereferenced. (3) The conceptual overview now included in Constraint Components some discussion of the overlap in functionality among identity constraints, conditional type assignment, and assertions, and identifies some of the factors which may be relevant in choosing among them; this change resolves issue 5023 Relationship between identity constraints and assertions. (4) The discussion of 'schema import' in Licensing References to Components Across Namespaces now states more clearly that references to components in external namespaces are an error if the namespace is not imported. (5) The discussion of checking content-type restriction included in an appendix in earlier drafts of this specification has now been removed, as have some references to published algorithms for the problem...
See also: the W3C XML Schema Working Group
Enhanced Oracle Beehive Collaboration Suite Version 1.5
Staff, Oracle Announcement
Oracle has announced enhancements to Oracle Beehive. Oracle Beehive delivers a range of collaboration tools including email, calendar, team workspaces, conferencing, and instant messaging on a single, standards- based platform. With the enhancements, organizations using Oracle Beehive can establish more efficient communication channels to enable easier collaboration and improve individual and team productivity. Today's announcement also extends Oracle Beehive's integration with existing systems, helping customers to lower infrastructure costs, simplify IT management, and reduce risk... Oracle Beehive delivers superior scalability, manageability and security. Updates to the latest release of Oracle Beehive include: (1) Web-based Team Collaboration: [Beehive 5.1 is] the first team workspace software that builds on an enterprise-specific security and compliance framework offers a user-friendly environment for teams to manage activities and information; it includes wikis, team calendaring, RSS support, contextual search, and advanced file sharing and can be centrally provisioned or set up by the team with no portal requirement. (2) Enhanced Web and Voice Conferencing: [Beehive 5.1] enables organizations to apply security and content management policies to conferencing; expanded feature set includes on-demand conference recording and retrieval. (3) Expanded Integration with Popular Desktop Productivity Tools: [Beehive 5.1] helps eliminate training costs and user adoption challenges by allowing users to take advantage of familiar software while IT benefits from Oracle Beehive's scalability, security and manageability. David Gilmour, Oracle Senior Vice President, Collaboration Technologies: "As organizations rely increasingly on collaboration software to drive both communication and business process efficiency, repackaged groupware and point solutions are proving to be costly and difficult to manage on an enterprise scale. With its unified platform, Oracle Beehive provides enterprise-ready collaboration in a single, easy-to-manage system with a low total cost of ownership."
Cartella: Unified Social Content Management
Staff, KM World Magazine
"Ingeniux has unveiled Cartella, the first unified social content management platform for managing the entire life cycle of social content across any Web site. The offering is said to integrate social networking tools, Web analytics and content management into a single solution for managing internal collaboration and external communities. The solution includes modules for managing documents, wikis, blogs, rich media and social networking. The Cartella solutions package includes: (1) Cartella Enterprise—a complete solution for managing employee collaboration and intranets, and for integrating social content with back-office applications. (2) Cartella Connect—a Web 2.0 extranet platform, featuring group, role and user permissions and access, team collaboration, online workspaces, notifications and analytics. (3) Cartella Community -- customer-facing collaboration and social technologies to drive deeper engagement, active participation and brand loyalty, including social networking and profiles, notifications and alerts, commenting, ratings and rich media transcoding for publishing videos and podcasts..."
From the announcement: "Gap Between Social Software and Web Content Management: With the demand for social business software on the rise, many established Web CMS and Portal vendors have attempted to bolt social features onto their legacy applications. However, these solutions don't address the distinct technical and business requirements for managing the social Web. While many social software point products have emerged to fill the usability gap, they lack IT best practices for managing and controlling social content and do not address compliance and workflow processes. To bridge the gap, Ingeniux has developed Cartella which uses proven content management principles to manage and control social content, while also making it extremely easy for end-users... Built on Microsoft ASP.NET MVC, Cartella makes it easy for .Net developers to customize existing Cartella business social software modules or build new modules and applications on top of the Cartella platform to meet their unique business requirements using commercial development tools and technologies they already know and trust. Microsoft .NET MVC also provides a streamlined implementation approach for Cartella similar to Microsoft SharePoint. Cartella-powered communities are rapidly developed using ASP.NET Master Pages and Web technologies like HTML and CSS. All content in Cartella is available through REST Web services, allowing social content to be "mashed" with other applications or accessed by any Website... Ingeniux's Web and social content management software provides a unified platform to manage Web content, social publishing, collaborative communities, and rich media. Its XML-based CMS and ASP.Net-based social content management technology empowers Web developers and content creators to build the next generation Internet with products acclaimed for ease of use, rapid deployment, extensibility and low total cost of ownership..."
See also: the web site description
Visible Signature Profile of the OASIS Digital Signature Services Version 1.0
Ezer Farhi (ed), OASIS DSS-X TC Public Review Draft
Members of the OASIS Digital Signature Services eXtended (DSS-X) Technical Committee have approved a Committee Draft of "Visible Signature Profile of the OASIS Digital Signature Services Version 1.0" for public review. The review ends June 30, 2009. The visible signature profile enables to embed visible signature characteristics into documents as part of a digital signature operation and also validate these characteristics as part of the verify signature operation. Overview: "For many processes that incorporate a digital signature operation or a verification of a digital signature, there is a need to view displayed information that is related to the binary digital signature. This visible display of information can include displaying the signer's identity, the time when the digital signature operation was performed, and additional information as well. The visible information comes in addition to the actual digital signature data, and is aimed at providing end users with information that closely relates to the digital signature act. By no means does this visible information replace the important element of the digital signature. Visible signatures are strongly associated with documents. The visible signatures will normally be displayed in the document in addition to other displayed information such as text and images.
There are several documents types and applications that already support digital signatures in conjunction with visible signatures: (1) Adobe Reader/Adobe Acrobat using digital signatures inside PDF documents. (2) Microsoft Office 2007 using signatures Line inside OOXML documents. (3) Other solutions that enable the use of visible signatures as well as digital signatures in other documents types such as TIFF, Office XP/2003, and other document types. Other types of standards or applications such as Open Document Format (ODF) do not support visible signatures yet, but already support non-visible digital signatures. The target of the Visible Signatures Profile is to define mechanisms that will enable clients that interact with a digital signature service, based on DSS core, to incorporate visible signatures into documents as part of a digital signature operation. The signature operation can be applicable for any type of document and can be displayed with any tool that displays the document's content. The signature verification service may incorporate some visible indications to signature field as part of the signature verification service.
See also: the announcement
W3C Workshop on Using Ink in Multimodal Applications
Staff, W3C Announcement
Ink Markup Language (InkML) is an XML language for ink traces which provides a range of features to support real-time ink streaming, multi-party interactions and richly annotated ink archival. Applications may make use of as much or as little information as required, from minimalist applications using only simple traces to more complex problems, such as signature verification or calligraphic animation, requiring full dynamic information. W3C now invites people to participate in a "Workshop on using Ink in Multimodal Applications within the W3C's Multimodal Architecture and Interfaces", on 10-11 July 2009 in Grand Bend, Ontario (Canada), hosted by the University of Western Ontario. The goal of the Workshop is to help the Multimodal Interaction Working Group integrate handwriting modality components (Ink Modality Components) into the MMI Architecture and clarify what should be added to the Multimodal specifications to enable applications to adapt to various modality combinations including Ink. Attendees will discuss requirements for changes, extensions and additions to Ink standards especially in Multimodal Applications developed based on the W3C's MMI Architecture as a means of making InkML more useful in current and emerging markets.
The W3C Multimodal Interaction Working Group seeks to extend the Web to allow users to dynamically select the most appropriate modes of interaction for their current needs, including (a) needs of the specific users (e.g., users with disabilities) (b) across interactions (e.g., use keyboard instead of speech in a noisy environment) and (c) within interactions (e.g., speak a command and point to select the object of the command). Multimodal modes of input are especially important for devices with small displays and small or nonexistent keypads. The workshop will produce a document that will: identify key use cases for ink in multimodal applications; describe ink modality-specific component required to support the use cases; identify possible new features of the MMI Architecture that would be required to support these modality-specific components.
See also: the Ink Markup Language (InkML)
NETCONF Over Transport Layer Security (TLS)
Mohamad Badra (ed), IETF Internet Draft
An announcement from IETF reports that new Request for Comments is now available in online RFC libraries for "NETCONF Over Transport Layer Security (TLS)," advanced to an IETF Proposed Standard Protocol. The document specifies an Internet standards track protocol for the Internet community, and IETF requests discussion and suggestions for improvements. The IETF NETCONF Configuration Protocol (RFC 4741) defines a mechanism through which a network device can be managed. NETCONF is connection- oriented, requiring a persistent connection between peers. This connection must provide integrity, confidentiality, peer authentication, and reliable, sequenced data delivery. This document defines "NETCONF over TLS", which includes support for certificate-based mutual authentication and key derivation, utilizing the protected ciphersuite negotiation, mutual authentication, and key management capabilities of the TLS (Transport Layer Security) protocol, described in The Transport Layer Security (TLS) Protocol Version 1.2 (RFC 5246). Throughout this document, the terms "client" and "server" are used to refer to the two ends of the TLS connection. The client actively opens the TLS connection, and the server passively listens for the incoming TLS connection. The terms "manager" and "agent" are used to refer to the two ends of the NETCONF protocol session. The manager issues NETCONF remote procedure call (RPC) commands, and the agent replies to those commands. When NETCONF is run over TLS using the mapping defined in this document, the client is always the manager, and the server is always the agent... The peer acting as the NETCONF manager must also act as the TLS client. It must connect to the server that passively listens for the incoming TLS connection on the TCP port 6513. It must therefore send the TLS ClientHello message to begin the TLS handshake. Once the TLS handshake has finished, the client and the server MAY begin to exchange NETCONF data. In particular, the client will send complete XML documents to the server containing 'rpc' elements, and the server will respond with complete XML documents containing 'rpc-reply' elements. The client MAY indicate interest in receiving event notifications from a server by creating a subscription to receive event notifications, per RFC 5277. In this case, the server replies to indicate whether the subscription request was successful and, if it was successful, the server begins sending the event notifications to the client as the events occur within the system.
XML Daily Newslink and Cover Pages sponsored by:
|Sun Microsystems, Inc.||http://sun.com|
XML Daily Newslink: http://xml.coverpages.org/newsletter.html
Newsletter Archive: http://xml.coverpages.org/newsletterArchive.html
Newsletter subscribe: email@example.com
Newsletter unsubscribe: firstname.lastname@example.org
Newsletter help: email@example.com
Cover Pages: http://xml.coverpages.org/