Hi Mario, On Mon, May 27, 2019 at 01:02:15PM +0200, Mario Loffredo wrote: > in this new version the "IANA Considerations" section has been updated to > include the request for the registration of the "subsetting" value in the > RDAP Extensions Registry.
Thanks for putting this together. Some comments/feedback: - Section 5 of RFC 7483 suggests that objects should always include a 'self' link, regardless of whether they are top-level objects, embedded objects, or search result objects. I think that including 'self' links for all objects, even those returned in response to an 'id' fieldset search, would be useful, because it saves the client from having to re-search when they want further details for only a small number of objects in a set of search results. - The draft defines the basic field sets (in section 5) at a high level, and is not prescriptive about the fields that must (or must not) be included. I can see from the change log that this was a deliberate decision, but I'm curious as to why you went with this approach. Defining a minimum set of fields that will be included (if they exist) for the non-'full' field sets seems like something that would save clients some trouble (with the current text, clients would need logic like "query for 'brief', and then query for 'full' if response does not include field F"). - Do you think it's worth extending this to standard object lookup, in addition to searches? -Tom _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
