A while ago we discussed how backrefs behave in the face of duplicate creation ids. The spec was amended to cover this in 72f845e5.
> Creation ids sent by the client SHOULD be unique within the single API > request for a particular data type. The "for a particular data type" indicates to me that a given creation id can be used multiple times, so that you can setFoos create "xyz" and setBars create "xyz" and then "#xyz" is unambiguous because its placement tells us the type of object we're referencing (unless we introduce polymorphic backrefs!). I want to be sure that we agree on this. Today I was looking at a JMAP implementation and saw an undivided backref namespace, which would break the above guarantee. Thanks! -- rjbs -- You received this message because you are subscribed to the Google Groups "JMAP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jmap-discuss/CF819EEB-A12A-427B-A809-99693C58C314%40icgroup.com. For more options, visit https://groups.google.com/d/optout.
