Q000702a: Interpreting ODMA Logs

Status	Date	Description






	2006-04-11	The 2.0-3 specification draft needs to be placed in an ODMdev folder and the pieces shared to the appropriate folders.
	2006-04-11	The errata needs to be placed in an ODMdev folder.
	2006-04-11	Q000702f: Cross reference with Q000702e and Q000702d.
	2006-04-10	Deal with the version parameter case from both the application to the DMS and the ODMA/DMS to the application case.
	2006-04-10	Link to the Raymond Chen blog articles on breaking changes, and also the Larry Osterman ones too? [This applies to Q000705 even more than here.]
	2006-04-06	There needs to be a new FAQtip or support folio on the breaking changes problem and mitigation of that by restraint in the development of DMS integrations and/or the use of some sort of shim DMS.
	2006-04-06	The diagram in the NuovoDoc analysis needs to be annotated in a way where the agreement and invariants that has ODMA sit neutrally in the middle is clear. This is needed to explain why certain changes (such as filtering a DMS behavior) don't belong in the ODMA connection manager, but they can be done with a shim DMS integration that filters another DMS integration.
	2006-04-06	odma200h.htm: The header page and related information needs to be moved to a dev folder so that we can add warnings and maintain an accountable revision progression of what is done here.
	2006-04-06	Q000702c: Put the ODMA.info ClustrMap on this page after creating a construction page to obtain the ClustrMap from.
	2006-04-06	ODMA2.0-3.htm: The set of specifications for 2.0 need to be organized in a (Download or dev) folio and managed under that structure as a cleaner way to keep track of revision progression and separation of in-progress from previously-completed work.
	2006-04-06	Q000702c: The existence of breaking changes, and warnings about them for developers of DMS integrations needs to be announced somewhere. I can make something prominent on the ODMA pages here, and there may be other things I can do. Announce on SourceForge, put banner on ODMA.info, and also mention to Betsy Fanning and see if there should be a notice on the AIIM site. I can also make a notice on the download page and in the on-line version of the ODMA header pages. I can put something on the top of ODMA 2.0-3 also.
	2006-04-06	X000002: This Incident Report needs to be refreshed in a folio and and also comprehended in a project to (1) capture the existing header files and materials, (2) start managing them on SourceForge, and (3) do a repackaging that has the ODMA license asserted and then (4) do updates that are corrected and also deal with versioning issues better.
	2006-04-06	Q000702c: The ODMQueryInterface function needs its own explanation and identification of result codes. There are also result codes defined for callbacks, and something might need to be done for those too. This is a marker to look more closely at how to handle that.
	2006-04-06	Q000702: Link in the other Incident and FAQtip items as general available information
	2006-04-06	The 2.0-3 draft should be tweaked so that the APPSELECT case for ODMSelectDocEx is not overlooked.
	2006-04-05	Q000702: Need to develop standard scenarios for reading the log. [dh:2006-04-10 see the 2006-04-04 use cases and also the items added starting on 2006-04-10. This item also applies to the folio cover and how it can provide a map into our coverage here.]
	2006-04-05	Q000702d: Setup as an Operation Request List, explaining what the items are.
	2006-04-04	Maybe we need use cases, such as the standard sequences for creating new documents, accessing existing documents, updating a document, and also the Save As ... and local Saves. [dh:2006-04-10 I have the basic wrapper, the declined-ODMA local operation, the New document, and updated document, and the Open, Save, Close progress. These should go a long way for understanding normal use.]
	2006-04-04	Q000702c: consider parameter codes, maybe on different page or not.
	2006-04-04	I need to look at version sensitivities and as well as which operations different features turn up in. [dh:2006-04-06 The basic cases are handled on Q000702c, but I need to handle the "breakable" ones better. I think the treatment of the individual log entries will lead me to any refinement that is needed.]
done 2006-04-11	2006-04-10	Q000702e: Create the basic wrapper case: Have it be the context for other materials and the overall format. Start with placeholder.
done	2006-04-11	Q000702f: Make a separate page just for ODMRegisterApp, providing the placeholder for further development.
done 0.27 2006-04-10	2006-04-06	Q000702c: Update the reference to Q000705 to refer to the adjusted version ~~0.15~~ 0.20.
done	2006-04-06	Move items about Q000705 to the new job jar for a folio refresh of that FAQtip.
done 0.26	2006-04-06	Q000702: Link in the Q000702c as it is now.
done 0.26	2006-04-06	Q000702c: Add ODMSelectDocEx to the ODM_E_APPSELECT cases.
done 0.25	2006-04-06	Q000702c: Repair the unwanted centering in the explanations and other columns
done 0.25	2006-04-05	Publish enough to obtain early review and communication to interested parties.
done	2006-04-05	Correct Q000705 to include ODM_E_ACCESS as a 2.0 addition to ODMSetDocInfo.
done 0.25	2006-04-05	Q000702c: Include all three versions of ODMA Specification in the references
done 0.25 2006-04-05	2006-04-04	Q000702c: Do result code cases as well as we can
done 0.25 2006-04-05	2006-04-04	Q000702c: Setup as Result Code List
done 0.25 2006-04-06	2006-04-04	Q000702c: Include references to the different items on missing codes, etc.
done 0.25	2006-04-04	Q000702c: Include Reference to header file definition.
done	2006-04-04	Customize Q000702b and Q000702c as placeholders
done	2006-04-04	Create this page for immediate collection of action items and notes.