Hi all, We've recently published a draft specification for wave and wavelet identifiers: h<http://wave-protocol.googlecode.com/hg/spec/waveid/waveidspec.html> ttp://wave-protocol.googlecode.com/hg/spec/<http://wave-protocol.googlecode.com/hg/spec/waveid/waveidspec.html> waveid <http://wave-protocol.googlecode.com/hg/spec/waveid/waveidspec.html>/<http://wave-protocol.googlecode.com/hg/spec/waveid/waveidspec.html> waveidspec<http://wave-protocol.googlecode.com/hg/spec/waveid/waveidspec.html> .ht <http://wave-protocol.googlecode.com/hg/spec/waveid/waveidspec.html>ml<http://wave-protocol.googlecode.com/hg/spec/waveid/waveidspec.html>
We've aimed to make the identifiers easy to use with URIs and links while being capable of embedding data, including wave addresses and international characters sets. This draft describes the protocol-level syntax of the identifiers, allowed characters, etc., but not the internal structure or semantics, i.e., how Google Wave embeds structure in identifiers using '+' as a separator. We'll publish a description of our usage and conventions in the future. This is an early draft, but we're keen for your feedback. If you've worked with the Wave Sandbox you may notice that Google Wave's identifiers don't actually conform to this specification yet. We'll be working to implement the spec and migrate as details firm up. Alex North, for the Google Wave team -- 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.
