On Fri, 3 Feb 2017, at 06:11 AM, Ricardo Signes wrote: > 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!). Yes, there are no polymorphic foreign references, so the creation id should be scoped to the particular type, and thus unambiguous in that example. I'll expand this portion of the spec; how about: *Creation ids are scoped by type; a separate `creation id -> id` map MUST be kept for each type. Foreign key references are always for a particular record type, so use of the same creation key in two different types cannot cause any ambiguity. Creation ids sent by the client SHOULD be unique within the single API request for a particular data type. If a creation id is reused for the same type, the server MUST map the creation id to the most recently created item with that id.* Neil. -- 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/1486092050.1328539.868801536.39A33281%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
