<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: [OAI-implementers] Question about sets</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi Dean,<BR>
<BR>
I believe if sets are supported, the expectation is that the response contains all relevent setSpec elements for each record. So if an item is a member of two sets, and a request specifies a specific set, the returned record would still need to list both. That's how I've always interpreted it.<BR>
<BR>
Cheers,<BR>
Chris<BR>
<BR>
-----Original Message-----<BR>
From: oai-implementers-bounces@openarchives.org on behalf of Cummins, Dean<BR>
Sent: Sun 2/12/2006 10:15 PM<BR>
To: oai-implementers@openarchives.org<BR>
Subject: [OAI-implementers] Question about sets<BR>
<BR>
Hi all,<BR>
<BR>
<BR>
<BR>
I wish to use sets (setspec etc), however is it mandatory to include<BR>
this with all metadata elements, even if that page was called with the<BR>
setSpec tag? (thus it would be just informing the user about what it<BR>
already knows - that the resource is part of a specific setSpec).<BR>
<BR>
<BR>
<BR>
Just after some clarification,<BR>
<BR>
<BR>
<BR>
Dean<BR>
<BR>
<BR>
**********************************************************************<BR>
This message is intended for the addressee named and may contain<BR>
privileged information or confidential information or both. If you<BR>
are not the intended recipient please delete it and notify the sender.<BR>
**********************************************************************<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>