Bottom line for me is that there needs to be an expectation that, like introspection documents, "the content of [the collection's feed] can vary based on aspects of the client request, including, but not limited to, authentication credentials". Whatever language is needed to get that point across is fine with me.
Joe Gregorio wrote: >[snip] > """If a POST to a collection results in a member resource being > successfully created then an entry SHOULD appear > in the collection feed that has a link/@rel='edit' with an > @href that matches the URI returned in the Location: header. > Some reasons that an entry might not appear in a > collection feed include: the member may have been deleted between > creation and the time the client retreives the collection > document, or the collection may represent a blind dropbox > where collection members may be created by one groupd of > people but can only be read by a third party, for example a > collection for students to POST homework results to that can only > be read by the teacher. > """ > > -joe > > -- > Joe Gregorio http://bitworking.org >
