proposal: consistent message format

Drummond Reed drummond.reed at
Wed Sep 20 16:48:01 UTC 2006

+1. I'm not that close to the code bases, so I can't measure the cost. But I
am close to the namespace issues and consistent namespace prefixing is a
really good practice, especially at this foundational level.


-----Original Message-----
From: specs-bounces at [mailto:specs-bounces at] On Behalf
Of Dick Hardt
Sent: Monday, September 18, 2006 7:51 PM
To: specs at
Subject: proposal: consistent message format

Direct and indirect messages have different formats. This adds  
complexity for the developer. Specifically:
	- some messages have parameters start with "openid.", others are  
bare keywords.
	- some messages have the namespace parameter, and others don't

	= All openid protocol parameters start with "openid."
	= All messages have the parameter

	+ consistent for developers
	+ all messages are versioned

	- code changes

specs mailing list
specs at

More information about the specs mailing list