Blunder Dome Sighting  
privacy 
 
 
 

Hangout for experimental confirmation and demonstration of software, computing, and networking. The exercises don't always work out. The professor is a bumbler and the laboratory assistant is a skanky dufus.



Click for Blog Feed
Blog Feed

Recent Items
 
Republishing before Silence
 
Command Line Utilities: What Would Purr Do?
 
Retiring InfoNuovo.com
 
Confirmable Experience: What a Wideness Gains
 
Confirmable Experience: Consider the Real World
 
Cybersmith: IE 8.0 Mitigation #1: Site-wide Compat...
 
DMware: OK, What's CMIS Exactly?
 
Document Interoperability: The Web Lesson
 
Cybersmith: The IE 8.0 Disruption
 
Cybersmith: The Confirmability of Confirmable Expe...

This page is powered by Blogger. Isn't yours?
  

Locations of visitors to this site
visits to Orcmid's Lair pages

The nfoCentrale Blog Conclave
 
Millennia Antica: The Kiln Sitter's Diary
 
nfoWorks: Pursuing Harmony
 
Numbering Peano
 
Orcmid's Lair
 
Orcmid's Live Hideout
 
Prof. von Clueless in the Blunder Dome
 
Spanner Wingnut's Muddleware Lab (experimental)

nfoCentrale Associated Sites
 
DMA: The Document Management Alliance
 
DMware: Document Management Interoperability Exchange
 
Millennia Antica Pottery
 
The Miser Project
 
nfoCentrale: the Anchor Site
 
nfoWare: Information Processing Technology
 
nfoWorks: Tools for Document Interoperability
 
NuovoDoc: Design for Document System Interoperability
 
ODMA Interoperability Exchange
 
Orcmid's Lair
 
TROST: Open-System Trustworthiness

2008-02-20

 

DMware: Documents as Evidence

Over the years, the AIIM International sponsorship of standards has included fostering of committee C22 on Evidentiary Support for Electronic Information.  I just learned that C22, which is tied to ISO TC171/SC3, is being rebooted.  I confess that I lost track of this work and I'm heartened to see announcement of its rejuvenation:

Why Comply with Standards
WHEN YOU CAN WRITE THEM?

When you join the AIIM C22 Evidentiary Support Standards Committee, you'll play a pivotal role in the creation of new standards for the legal admissibility of electronic documents in courts across the country.

Led by Co-Chairs Bob Williams and Paul Doyle, the committee deals with law and IT in relation to enterprise information management, with particular focus on information as evidence... for or against the enterprise.

About a quarter of our stakeholders are attorneys who are conversant with IT. The rest of us are mostly IT people who are conversant with legal issues, legal thinking, and the nature and practice of law. We are focused on enterprise business activities that are conducted electronically. Our committee is trying to stay even with - and, if possible, ahead of - the technology curve, in order to advise IT designers on strategies for making e-records  trustworthy in the eyes of the law. We also work on strategies for enterprises trying to identify and dispose of unwanted electronic information.

We concentrate on evidentiary considerations for the design of e-business systems, on the retrieval of information in discovery, on the erasure of information that the enterprise does not want to hold, and on intellectual property considerations in the management of electronic information.

The work of AIIM C22 is substantive, intellectually challenging and its influence is wide-ranging.  We invite you to join us.

Send your contact information to standards@aiim.org and copy C22 committee member Paul Doyle, at paul@proofspace.com so that we can add you to the C22 e-mail list.  There you'll learn about upcoming meetings and ongoing projects in which you can get involved.

For further information and general interest in the focus of AIIM-supported standards activity, visit the AIIM Standards page.  There is also an AIIM Standards Watch blog. 

Although the evidentiary nature and use of electronic information, including documents and source code, is not the most exciting thing for Information Technology organizations to be concerned about, understanding the importance and the risks of how electronic information is managed is becoming increasingly important.


It occurs to me that the folks who object to the ISO Standardization of DIS 29500 (Office Open XML) would place a different spin on the invitation's headline.  I think the spirit of this announcement is clear even if the headline is a little over the top.

I also think work to make the legal implications of IT policies and practices around electronic information more understandable is very important.  It is one of those odd situations where it is desirable to make discovery (and auditing) more efficient because of the burdensome cost that it can involve, while also making sure that electronic information is destroyed at appropriate times to avoid the secondary burden of witch-hunting by discovery.  C22 is a forum where knowledgeable people worry about that tension and how to delimit it.

[Cross posted on Professor von Clueless in the Blunder Dome and Orcmid's Lair because of overlapping communities of interest.]

2008-02-19

 

VC++ Novice: DreamSpark for Students


Bill Gates talks about Free Software, Students, and Technology
 
   

Yesterday, Bill Gates spoke about the DreamSpark program to put Microsoft's professional developer tools into the hands of students at no charge.  There is an exciting list of available tools, including Visual Studio 2008 Professional and the complete Expression Studio.

The initiative is now available in eleven countries around the world.  Within those countries, you must be a student at one of the recognized institutions or other recognized student organization.  Your student status will be verified with the appropriate organization, and it must be reviewed every 12 months.

The program will rapidly expand to more educational institutions and countries.  For now, students must be enrolled in a recognized post-secondary (after high-school) program.  The program will be extended to high-school students at a later time.

DreamSpark software is downloaded directly by the students, rather having to be obtained through academic departments and campus book stores.  This should make the packages more-consistently available.

There are some restrictions.  I also have some concerns.

Restrictions

First, the software is only available for academic use.  From the FAQ for Students:

"We’re giving you the software for non-commercial use to support and advance your learning and skills through technical design, technology, math, science and engineering activities."

Secondly, the software is only available to use so long as student status is maintained.  From the FAQ for Administrators:

"This benefit is available to all tertiary (post-secondary) students around the world who are attending accredited schools or universities. However, this program requires all students to have their status verified by an authorized verification source."

Not being a verifiable student, I am unable to look at the complete license and explore the download process.  You will need to find broadband access and be able to download and record CD-ROM and DVD-ROM images.  You should also explore any restrictions on redistribution and on distribution of software that you produce. 

Concerns

If the DreamSpark idea appeals to you and you are a qualified student, remember that these products are designed for professionals.  There is no provision of tutorials or introductory materials for learning how to use the various programming languages and other resources.  You will need to invest in separate books and resources beginning with these tools.

It may also be difficult to find a community of other students and beginners who are also learning to work with these tools. 

I suspect that there will be more material and more community as time goes on. 

If you are a beginner and are not taking courses or using books you already have for the fundamentals, I recommend that you look at one of the Express Editions and use that to calibrate whether you are prepared to take on the additional features and capabilities of the professional tools without considerable assistance.  This is also a good place to start until you are prepared to declare yourself to be an advanced student.

I don't want to discourage you; this is a great offer.  But you should qualify your expectations.  Mastery of these tools is not something that happens overnight or even in a single university term.  If you want to use these tools for self-directed learning separate from your course work, it is even more important for you to understand the investment of personal time that will be needed.

My recommendation: Go for Expression Studio and Windows Live.  Use the Express Editions for everything else until you are prepared to step up to Visual Studio 2008 Professional.

What Others Are Saying


As a side matter, it is interesting that Shibboleth and Information Card (they say Cardspace) Identity Providers are supported in the verifying institutions.

[update 2008-02-20: Alfred Thompson's post adds information beyond the basic "hooray" posts and I linked to it.  I stick by my recommendation, especially for those who want to learn non-.NET fundamentals.]

2008-02-18

 

DMware: ODMA Futures Roadmap

After taking some time to envision what might be possible for an ODMA64 implementation of an Open Document Management API [2], I began to look at further details for a roadmap that could end there.  At this point, it looks like there are four overlapping and mutually-supporting stages:

    1. Enhancing ODMA Effectiveness
      preserving the sweet spot and improving its support
         
    2. Preserving the ODMA Core
      conserving the historical materials and adding versions that are more appropriate with contemporary tools and libraries
        
    3. ODMA32 2.5 Integration
      surrounding the ODMA32 Connection Manager with higher-level integration layers that happen to permit confirmation of new connection manager releases as well as experimental use of integration points that anticipate ODMA 3.0 simplifications
        
    4. ODMA64 3.0 Interoperability
      breaking with the past to achieve simplified interoperability on 64-bit systems with exclusive reliance on Unicode

Although a few items are slated to commence in March 2008, most of the activity is without fixed calendar commitments and with no detailed deliverables.   Here's the current level of thinking.

1. Enhancing ODMA Effectiveness

There are four critical features that have ODMA be effective in bridging desktop software products to document-management systems:

  1. Simple Integration in Desktop-Software User Interfaces
    With the cooperation of desktop programs, the ODMA-integrated document management systems present their dialogs as dialog boxes of the desktop programs.  This provides direct connection into the flow of information-worker activities.   User attention is not taken away from the desktop software.  The additional dialogs that accompany creation and use of managed documents are provided automatically.  There is nothing for the user to forget to do.  This is what users see and what makes ODMA so appealing for using already-available productivity software with managed documents.
      
  2. Easy Deployment to the Desktop
    The ODMA Connection Manager, the enabling middleware, is deployed to office desktop systems along with the ODMA-compliant document-management system client software.  ODMA-aware productivity software automatically discover the presence of the Connection Manager; the Connection Manager completes the connection to the document-management system that is to be used in the application setting.  The configuration of desktop and document-management connections is managed by ODMA-specific settings in the Windows registry.  No software modification is involved.
      
  3. Trouble-Shooting Support
    ODMA 2.0 Connection Manager software provides logging functions that are usable in confirming and trouble-shooting connections between desktop software and document-management integrations.  There are also utilities that can be operated to verify correct operation and to experiment with configuration changes.
      
  4. Low Barrier to Entry for Document-Management Vendors
    This characteristic of the ODMA deployment and integration model is appealing for new, small, and specialized document-management vendors.   Instead of making difficult per-desktop software (version) custom integrations, the supplier of an ODMA-compliant DMS can be assured that most ODMA-aware desktop programs will "just work" with that DMS. 
      
    There is a similar advantage for specialized ODMA-aware desktop software, although ODMA integration is more difficult and takes more preparation when designing desktop software.  It is not necessary to build-in any knowledge of individual ODMA-compliant document-management systems, however.

All future development is focused entirely on preserving and enhancing these four qualities.  In many cases, it is a matter of providing improved guidance and documentation.  Tutorials, supplemental utilities, reference implementations, improved samples, and implementation kits will also be provided over time.

2. Preserving the ODMA Core

The ODMA SDK packages and other materials have become stale on the ODMA Interoperability Exchange site.  As part of a general site repaving operation, the core materials of ODMA 1.0, ODMA 1.5, and ODMA 2.0 will be re-organized and preserved on the site and on an anniversary CD-ROM.   The CD-ROM will be preserved at AIIM International as well, so that the historical materials are not lost.

Along with preservation of the historical materials, the ODMA32 Core will also be supplemented [3]:

  • Existing materials will be identified better in the files themselves, and also repackaged for more-convenient separate use.  These will also be available on the ODMA Interoperability Exchange site.
      
  • The identified and repackaged materials will be made available as downloads of the ActiveODMA SourceForge project.  The source code and documentation will be placed on the ActiveODMA subversion source-control system as a foundation for further work.
      
  • Some of the developer materials, such as header files, will be supplemented with versions that are more appropriate for development of production ODMA-based programs.   These changes will be made in parallel with other activities where the changes can be tested in actual usage.  This work has already begun on behalf of ODMJNI 1.0 and it will parallel other ODMA32 2.5 developments.
      
  • Existing samples circulated as part of the ODMA Core will be replaced by ones that correct known defects and provide more effective demonstration of the use of ODMA features. 
       
  • At some point, there may be a maintenance release of an upgraded ODMA32 2.0 Connection Manager.  This connection manager will contain some minor corrections and be thoroughly confirmed via automated tests produced before any Connection Manager changes are considered.  ODMA-aware applications and ODMA-compliant DMS integrations should see no difference whatsoever.  Some areas of ODMA effectiveness will be strengthened.

ODMA Core preservation activities will be initiated in March 2008, following the Public Beta release (0.60) of ODMJNI 1.0.  The activity will be carried out in parallel with further ODMJNI releases as well as other ODMA32 2.5 integration activities.

3. ODMA32 2.5 Integration

ODMA32 2.5 is the achievement of supplemental integration layers surrounding ODMA32 2.0.  The idea is to enhance the opportunities for ODMA integration with provisions of this kind:

  • Native COM-based Libraries 
    There's development of Win32 Native Unicode-based libraries that deliver COM binary interfaces instead of the ODMA API.  The use of ODMA32 and the C Language ODMA API is completely hidden.  This allows creation of ODMA-aware applications using object-oriented technology.
      
  • Managed Code Libraries
    The Native COM-based libraries are used to build Java and .NET libraries that can be used to make Java-based and .NET-based ODMA-aware desktop software.  If there is any remaining point, an ActiveX library could also be produced.
       
  • Native DMS-integration Fixtures
    Components needed to build ODMA-compliant DMS integrations are developed as integration kits and also as a basis for test fixtures that allow end-to-end exercise of the ODMA Connection Manager from the Native COM-based Libraries (and above) through to test DMS-integration fixtures below.  This creates the possibility of automated regression testing of the ODMA32 Connection Manager.  With that possibility, maintenance upgrades to the ODMA 2.0 Connection Manager can be considered.
      
  • Managed-Code DMS Integration Interop
    Although more difficult, experimental interop layers between Native DMS-integration layers and managed-code implementations (Java or .NET) of ODMA-compliant DMS integrations can be attempted.
       
  • ODMA32 Exploration for ODMA 3.0 Integration
    As preparation for ODMA64, the native DMS-integration and Interop fixtures might be arranged to allow preparation of DMS integrations that only use features that will be supported under ODMA 3.0 for ODMA64.  This will simplify development of ODMA-aware ODMA32 DMS integrations, especially when the Document Management System is already designed around Unicode.

ODMA32 2.5 developments are already underway.  Beyond the delivery of the ODJNI 1.0 Public Beta release in March 2008, there is no fixed schedule.  The further development and release of ODMA32 2.5 components will be leisurely, paced by ODMA Core continuation work.

The ODMA32 2.5 supplements, along with maintenance updates to the ODMA Core and the ODMA Connection Manager, should continue to be available and usable so long as the Win32 platform remains in use on x86 architectures.  No further development is expected for ODMA32 beyond 2.5.

4. ODMA64 3.0 Interoperability

Initial thoughts toward a potential ODMA64 appeared in November 2007 [2].  I am now thinking that creation of ODMA64 for 64-bit platforms will mark the introduction of ODMA 3.0 [4].  ODMA 3.0 will only be supported on 64-bit processors.  It will not be backward compatible with the ODMA 2.0, although there will be useful overlap with ODMA 2.5 provisions.

Development of ODMA64 is not expected before 2010.  Whenever development does occur, there are three key provisions:

  • The ODMA Effectiveness qualities are completely preserved (section 1).
      
  • Anticipation of ODMA64 will be worked out via ODMA32 2.5 supplements that provide proof-of-concept and also a way to stage ODMA32-based software for migration to ODMA64 by abandoning those features that will not survive into ODMA64.
      
  • The ODMA64 Connection managers and supplemental software should be portable to non-Win64 64-bit platforms.  There will need to be GUI dependency coordination between ODMA-aware desktop software and ODMA-compliant DMS integrations, but this will be done in a way that does not involve ODMA64 Connection Managers.

I am still bemused that, 10 years after the AIIM ODMA Consortium shipped the last version of the ODMA Core components, based on the ODMA 2.0 specification, I am still supporting this long niche software and its integration model [1].  Not only that, I am now proposing further development in this interesting little middleware laboratory.

[1] Dennis E. Hamilton: ODMA: The Little Middleware that CouldOrcmid's Lair (web log), 2005-12-20.
This article celebrates the 10th anniversary of the ODMA 1.0 specification and availability of the initial middleware for 16-bit Windows and Win32.  The AIIM ODMA Coalition ceased formal activity following the completion of the ODMA 2.0 specification and the 1998 availability of the final ODMA Core, still for 16-bit Windows and Win32.
  
[2] Dennis E. Hamilton: DMware: How About That ODMA64?  Professor von Clueless in the Blunder Dome (web log), 2007-11-10.  Updated 2008-02-15.
Initial thoughts on taking ODMA into the 64-bit world.  I have updated this note to extend the timeline into 2010, allowing more room for polishing the ODMA32 Core and building up the ODMA32 2.5 supplemental integration layers first.
     
[3] Dennis E. Hamilton: ODMA32 Core.  ODMdev Development Note d071004 0.01, AIIM ODMA Interoperability Exchange, February 15, 2008.
This Development Note will be used to track polishing of ODMA32 Core up through any ODMA 2.5 maintenance release of the ODMA32 Connection Manager, followed by any migration to an ODMA64 3.0 core.  ODMA 3.0 will not be backward compatible to ODMA 2.0 (or 2.5), using the change of platform to switch over to exclusive use of Unicode and also drop out unsuccessful ODMA 2.0 features.
      
[4] Dennis E. Hamilton: ODMA64 3.0 Interoperability.  ODMdev Development Note d071002 0.02, AIIM ODMA Interoperability Exchange, February 15, 2008.
  
 

Cybersmith: Software Craftsmanship Wiki

From Sara Payton (via Tim O'Reilly) I learned of the forthcoming book, Software Craftsmanship: From Apprentice to Journeyman.  This book is being developed on a Wiki and is a community effort in collaboration with the authors, Dave Hoover and Adewale Oshineye.

I thought this would be really cool.  I thought, maybe I won't have to invest so much in what I want to put here on "Professor von Clueless" and on nfoWare for encouraging novices and supporting advances in craftsmanship.

Then I said, "Uh Oh."  The terms and conditions for playing in the forum, whatever that is (I haven't gotten through to it yet) are 7 pages on my screen.  This is discouraging.  Since I always read the terms and conditions, and life is too short to dive into these, I have not registered. 

Also, I looked at the table of contents and a few chapters (one HTML page apiece, it seems) and I am not sure I care about this book.  It is written as a form of pattern language.  It also says some things that I am not sure I agree with.  So, rather than sign up and chime in over there, I think I will stick to my guns and continue with VC++ Novice and Cybersmith postings right here (with backup material on the web site real soon now).

You may find this more valuable than I did.  I certainly like the idea.  Please go visit and develop your own sense of the material that is posted so far.  It is a work in progress and you might check back later to see how it becomes beefier.


Since I started taking action on the nfoWorks idea, I find that I have trouble typing the correct one of the two terms nfoWorks and nfoWare.  They are really different, even though connected.  I will have to work at this.  Since Harmony domains are unavailable, I will have to live with my too-similar choices.

[update 2008-02-19-12:44 I am going crazy tagging. I used quotes instead of the comma-separated form required here in Windows Live Writer because I get confused about how de.licio.us uses space separate lists where I must use underscores versus my photo tagging tool which uses space-separated lists but quotes on multi-word-space-separated phrases.  Sheesh.  I also couldn't find any of my posts in Technorati, so I was looking for the culprit and ready to file bug reports when I noticed that there is this authority business and my personal settings for viewing tagged posts were set so high that my own posts weren't being reported to me.  Urghh.]

 
Construction Structure (Hard Hat Area) You are navigating Orcmid's Lair.

template created 2004-06-17-20:01 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-04-30 22:33 $
$$Revision: 21 $