Suppose we first enumerate the problem(s) we're solving:
- Allow the client to request a mets (or other container-schema) record
along with a list of contained schemas (Ray)
- what else?
----- Original Message -----
From: "Robert Sanderson" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, August 11, 2005 12:13 PM
Subject: Multiple Schemas per Request summary
> Modify recordSchema semantics to allow multiple schema identifiers/names.
> If multiple schemas are given:
> a) The first MUST be a wrapper schema, the rest are schemas to include.
> If the first isn't then it's an error. (Ray)
> b) If the first is not a wrapper schema, then it's a choice of schema
> (as per one of the current extensions) (Rob)
> Just define new identifiers for each combination of wrapper and wrapped
> Allow multiple record schemas in recordSchema but only allow a single
> wrapper schema, to be specified by the protocol. [As I understand it]
> Allow compound schemas to be identified in a new nested XML structure in
> SRW, and map that structure into a set of parameters in SRU.
> Hope I've done all the proposals justice!