Given "Every document within a wavelet has an identifier unique within the wavelet", I take that to mean that a BlipID need only be unique within that *particular* wavelet, hence one, or more, 'duplicate' BlipIDs could exist in other wavelets. (The same being the case with WaveletIDs within WaveIDs).
In our server implementation of the specs, we have stored blips with IDs unique within the *database*. That is, as a primary key. This, for our implementation, makes the question a non-issue (for *our own* wave processing). However, if you are thinking about googlewave.com or FedOne my guess would be that you cannot assume uniqueness at the database level; and therefore should use (waveID, waveletID, BlipID) to uniquely identify a blip document. HTH Chris -- iotawave.org -- You received this message because you are subscribed to the Google Groups "Google Wave API" 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/google-wave-api?hl=en.
