>3) Added an optional RequestId parameter, that is returned along with the >corresponding response. This may facilitate thin clients and gateways - >especially if we use asyncronous transports. This was discussion at the meeting and agreed that it wasn't necessary. Any asynchronous transport we may use would have a transport level feature for doing this sort of thing so it shouldn't be needed in ZNG. >4) Added the ResponseSchemaId and RecordSchemaId to the SearchResponse. This >may also facilitate future developments and make life easier for thin >clients. I thought that these were going to be in an optional extension to the base response schema rather than optional elements within the base schema. Matthew