ODMA: Open Document Management API

Q000705 ODMA FAQtip
Changes Between ODMA Versions

Diary & Job Jar

ODMA>faq>
2000>07>

Q000705a>
0.00 2010-08-29 20:13 -0700

Status

Date

Description

     
     
     
     
     
  2006-04-10 The odma.h 2.0.0-1 file needs to be found in a folio.  That is so it can be updated and have the IP notice included.  This clearly goes under ODMdev.
  2006-04-10 Q000705d: 2.1.1 Check the odmacom.h file for confirmation that E_INVALIDARG is not defined and that it doesn't get a value in normal COM usage.
  2006-04-10 Q000705d: 2.1.1 Reference to E_INVALIDARG needs to be softened because it is not defined and is not generally expected. 
  2006-04-10 Turn Q000901 into a folio and refer to that from here.
  2006-04-10 Q000705d: 2.1.1 Make a better reference to the article on using COM, it also belongs in the 2.1.2 section.
  2006-04-10 When there is a generic folder with stable incoming labels, refer to those anchors from links on this page.  That way, as the document is revised, these will find the latest sections without making any changes.  Refer to specific versions only when that is crucial to the sense in which the link is being made.
  2006-04-10 Have the ODMA 2.0-3 materials be in a version-progressed folder.
  2006-04-10 Q000705d: Add a revision date under the dateline under the authorship of the summary.
  2006-04-10 Q000705d: Correct or remove the material above the summary and reconcile how this will be related to other download material separately, maybe on the folio cover.
  2006-04-10 Q000705d: Use permalinks for all of the section numbers and entries.  Expand the table of contents to include the next-lower (m.n) section levels.
  2006-04-06 Q000705d: In readying an 0.25 or later version, it is useful to consider whether any spun-out sections should be separate pages or FAQ.  
done 2006-04-11 Reflect current content in the FAQtip catalog.
done 2006-04-11 Q000705: Add links to the current content
done 2006-04-10 Q000705d: Clone to begin modifying to make a later, refined version
done 0.20 2006-04-10 Q000705c: Correct the anchor link file name from Q000702c to Q000705c.
done 0.20 2006-04-10 Have Q000702c refer directly to the Q000705c page.  That way, the cross-references are nailed but links to later material are preserved.  A See-also can refer to the latest here at Q000705b.
done 0.20
2006-04-10
2006-04-06 Q000705: This FAQtip needs to be changed to a folio in the FAQtip hierarchy and the old page preserved as an Include Page that preserves existing links and allows for potential later versions.
done 0.20 2006-04-10 Q000705 (in Downloads): Map to the latest version by including Q000705b.
done 0.20 2006-04-10 Q000705b: Include Q000705c 0.20 as the latest version as an Include Page.
done 0.20
2006-04-10
2006-04-06 Q000705c: The old top-section material about ODMA section of AIIM DMware needs to be corrected.  In a newer version, I need to do some things about the ODMA 2.0 Documentation files that are being referred to.
done 0.20
2006-04-10
2006-04-06 Q000705c: The table layout doesn't work without borders.  The framing needs to be improved.
done 0.20
2006-04-10
2006-04-06 Q000705c: Make the current version in downloads be here as 0.15 0.20 here.
done 2006-04-06 Post placeholder folio pages to the hosted-site so that the placeholder is propagated before further changes.  It is not yet linked from any material other than itself.
done 2006-04-06 Customize Q000705b and Q000705c as placeholders
done 2006-04-06

Create this page for immediate collection of action items and notes.

done 0.11 2006-04-05 Correct Q000705 to include ODM_E_ACCESS as a 2.0 addition to ODMSetDocInfo.
Revision History:
0.00 2006-04-06-13:12 Create Initial Placeholder
Introduce an initial placeholder that serve as a target of links and provides a diary & job jar that can be employed immediately.

Construction Zone (Hard Hat Area) You are navigating the
ODMA Interoperability Exchange.

created 2006-04-06-13:12 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-08-29 20:13 $
$$Revision: 21 $