The Miser Project  
privacy 
 
 
 

Collaborative articulation of how abstraction and language is employed in the computational manifestation of numbers -- including analysis of the role of syntax, semantics, and meaning in the specification and use of software interfaces.



Click for Blog Feed
Blog Feed

Recent Items
 
A Fine Kettle of Fish, indeed.
 
What Is a Model?
 
A Fine Kettle of Fish
 
Numbering Peano: Annotated
 
Annotating Peano Numbers

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


visits to Miser Project 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

2004-06-14

 

Interfaces, Protocol Extensibility, and Versioning

Interfaces, Protocol Extensibility, and Versioning

Dave Orchard's Blog: Protocol Extensibility and Versioning.  Spotted by Danny Ayers, this blog article argues for the essential qualities of a version-1 protocol that alllows for version-n+1 and evolvability.  There are useful links and well-developed arguments. It will be clear that interface contracts are about protocols and we will need to bother with extensibility and versioning as part of exposing how that matters for Peano Numerals, as with any interfaces that will evolve over time. I am already fussing with versioning problems in preparing for the next round of examples and moving to demonstration of at least one reference implementation that honors the com.orcmid.LLC.pa.pn.Num interface.  Dave's discussion will be useful as we explore the implementation angle and also look at the impact of interface versioning.
 
The article suggests an interesting approach to managing evolution for protocols as well as formats. And I agree that it might have something to offer for interfaces.

For me the key points of the article for our exercise here are (1) authority management (what agents manage changes, is it symmetric?), and (2) the actual behaviors of interface instantiations.

I think the example used regarding protocol authority is flawed. First agent B is given authority over the protocol, but then agent A makes changes that agent B needs to handle. It's suggested that authorized versions might be managed by a directory service. I'm confused about who's in charge and how.

And I also question the assumption that protocol extensions are always mandatory. It's my experience that many "required" extensions are made to software irrespective of the larger system context of use, usability, etc.
 

 
Construction Structure (Hard Hat Area) You are navigating The Miser Project.

template created 2004-05-31-22:34 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-04-30 21:00 $
$$Revision: 22 $