Curated for content, computing, and digital experience professionals

Category: Web technologies & information standards (Page 44 of 58)

Here we include topics related to information exchange standards, markup languages, supporting technologies, and industry applications.

OASIS DITA Technical Committee Seeks your Input

Passing this along from Don Day, Chair of the OASIS DITA Techical Committee:

The OASIS DITA Technical Committee seeks your input on the list of known requirements/enhancements for upcoming DITA TC activity. Your help in ranking this list (or suggesting additional new requirements) will help the TC prioritize the most urgent issues for upcoming DITA 1.1 design work, and beyond. I have posted a list osf the issues currently known to the TC at this location: http://www.oasis-open.org/committees/document.php?document_id=12814&wg_abbrev=dita

Please assess what you consider to be your top 5 requirements and submit those Issue numbers to the DITA TC via the comment form:
http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=dita .
If you have a new issue or requirement not included in this list, please enter it as a separate comment via the comment form. We still need your “top 5” from this list, so read it carefully–most of the known hot issues are in there in one way or another, possibly including yours. There is no need to include more than 5 items in your list at this time; all of the 48 items are candidates for work, but we need to know which are MOST critical for initial work going into DITA 1.1.

This review period opens on May 23 2005 and closes end of day on June 6 2005 (2 weeks).

OpenDocument an OASIS standard, but …

It is excellent news that OASIS has approved OpenDocument as a standard. Hopefully it will also become an ISO standard. However, neither of these mean that it is necessarily the right approach for you. A single schema, no matter how well-designed, will not work for everyone. James Governor is quoted in the release: “One key to success will be the royalty free status of the spec; there are no financial penalties associated with developing to it.” Very true, but Microsoft’s schema is also royalty and cost free, and I believe they have committed (contractually even I think…?) e.g., to the EU, to keep it that way. See more on this here and here.

OASIS Approves OpenDocument as Standard

OASIS announced that its members have approved the Open Document Format for Office Applications (OpenDocument) v1.0 as an OASIS Standard, a status that signifies the highest level of ratification. OpenDocument provides a royalty-free, XML-based file format that covers features required by text, spreadsheets, charts, and graphical documents. OpenDocument provides a single XML schema for text, spreadsheets, charts, and graphical documents. It makes use of existing standards, such as HTML, SVG, XSL, SMIL, XLink, XForms, MathML, and the Dublin Core, wherever possible. OpenDocument has been designed as a package concept, enabling it to be used as a default file format for office applications with no increase in file size or loss of data integrity. Future plans for the OASIS OpenDocument Technical Committee include extending the standard to encompass additional areas of applications and users, as well as adapting it to incorporate ongoing developments in office applications. All those interested in advancing this work, including governments, open source initiatives, educational institutions, and software providers, are encouraged to participate in the Committee. OASIS hosts an open mail list for public comment and the opendocument-dev mailing list for exchanging information on implementing the standard. http://www.oasis-open.org

DITA Breakfast Seminar in Amsterdam

A complimentary breakfast seminar and discussion:
“Technology Directions: Driving DITA Adoption in Europe”, has been added to next week’s conference in Amsterdam on Friday, May 27, 8 – 10:00 a.m. IBM, Idiom and Nokia will present on DITA and its practical applications, while leading an open discussion focused specifically on the adoption of DITA-based publishing initiatives in Europe through establishing regular meetings, networking opportunities and education events. Panelists from Thursday’s presentation will be on hand, with the addition of Indi Leipa, senior information architect, Nokia.

XForms Wiki

Mark Birbeck’s company, x-port.net Ltd., makers of formsPlayer, have launched an XForms Wiki, and they have some seeded it with some good material. Some of the initial content includes tutorials, industry news, reference material, and sample applications.

PCAOB Clarifies SOX Compliance Rules

Yesterday the Public Company Accounting Oversight Board (PCAOB) issued its
response to concerns that Sarbanes Oxley Section 404 requirements were onerous,
unwieldy, and just too expensive. The PCAOB published a policy
statement
that affirmed the goals and requirements in the regulations
implementing Section 404, which requires that public companies have effective
internal controls over financial reporting and requires that an independent
auditor provides an opinion regarding the effectiveness of these controls. No
surprise there. 

What was more interesting and important was that the PCAOB did acknowledge
that many first year audit efforts were inefficient and too expensive. The
important parts of the statement called for a top-down, rather than bottom-up,
approach to internal control assessment. The PCAOB also made important
clarifications about the kinds of interactions between auditors and the
companies that they audit that are permissible and useful.

Understanding this business about "top-down" and
"bottom-up" is easier if you put it in the context of how auditing
practice has developed over time. Without that big picture perspective, Section
404 and the PCAOB statements sound like a lot of accounting jargon. But, given
the perspective, it is easier to see that we are talking about some fundamental
changes–and about expense and confusion emerging from not getting the changes
right during this past year.

Continue reading

The Operational Approach to Governance, Risk Management, and Compliance

Today marks the official release of the public draft of the governance, risk management, and compliance (GRC) paper that I have worked on over the past couple months with Ted Frank, of The Compliance Consortium, and others. The writing of the paper was driven by three convictions:

  • GRC stands apart: Governance, risk management, and compliance are all of a piece–and they are related to a coherent set of objectives and practices that are fundamentally different from the other things going on in an organization.
  • GRC needs high level attention: Governance, risk management, and compliance comprise a set of concerns and objectives that must be dealt with at the board of directors and senior management level.
  • GRC is manageable: Even though governance, risk management, and compliance touch thousands of processes and objectives throughout an organization, there really is a small, manageable set of concerns that should inform board and management decision-making.

This last point relates to the “both forest and trees” view that I wrote about in my recent post on XBRL and Compliance. To make GRC manageable we need ways to zoom into the details and zoom back out to the big picture. Said more formally, we need ways to deal with the concept at different levels of abstraction, from fine-grained to chunky. XBRL looks promising in this regard.

One of the key ideas expressed in the paper is that the United States Sentencing Commission guidelines regarding compliance and ethics can serve as a good starting point for identifying the important, board and senior management level GRC objectives. This idea is practically appealing, since following the guidelines can result in a 95% reduction in penalties in the event that, despite a company’s best efforts to prevent it, fraudulent activity takes place. The intent of the paper is to also make this idea appealing at an operational and functional level — we believe that we make the case that concentrating on just seven objectives can get management and board members focused on the right concerns and questions.

If this interests you, take a look at the paper.  If you have comments, you can of course add them here — but if you want your comments to get more in the way official consideration, you should also express your views on the Compliance Consortium website.

Arbortext Announces Version 5.2 of its Enterprise Publishing Software

Arbortext announced the company will release version 5.2 of its enterprise publishing software in September 2005. Representing a year-long development effort, this release has improvements in functionality and compatibility for organizations implementing enterprise publishing applications. The Import/Export feature, which provides conversion between word processing/desktop publishing files and XML, will provide over 50% new functionality and replace Arbortext’s Interchange product. The Import feature will offer much finer control over the conversion of styles into XML tags, so that word processing and desktop publishing files can more easily be translated into XML. The Contributor Web-based XML editor will be able to track changes (additions and deletions) so that editors can review, revise and approve documents more easily. In addition, Contributor will provide an API that provides developers with a greater level of control over the product’s functionality and appearance. DMC (Digital Media Composer) DMC replaces CD-ROM Composer and represents a major upgrade in Arbortext’s capability to publish large sets of documents that are too big to distribute over the internet. DMC can produce both DVDs and CD-ROMs for very large data sets and supports multiple volumes, password security and data compression. http://www.arbortext.com

« Older posts Newer posts »

© 2024 The Gilbane Advisor

Theme by Anders NorenUp ↑