Comments: Should the question not be: Is the draft specification accepted as a committed specification?
If 'no' then debate/refine until it is. If 'yes' then go ahead and make the changes to the WIAB code because WIAB does not conform to the spec.; in as smooth a way as possible, of course :) There is a general issue here: Whilst applying a spec to the code may have 'lagged' in the old Google Wave, great care must be taken so that the same does not happen with WIAB. We need to ensure that any proposed change/enhancement during WIAB coding is referenced back to the appropriate spec (and if a difference, or omission, is found then the spec must be debated/changed/created before the code is implemented). IMO it is imperative that spec precedes code, and not "we'll do the spec later; we need to get the code out of the door first". Objections: None. -- Chris iotawave.org Singapore -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
