<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 14 Sep 2012, at 18:56, Andy Dale <<a href="mailto:dalea@oclc.org">dalea@oclc.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<title>Hi from a new guy</title>
<div><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">I have noticed that the spec seems to be quite old and that there are what appear to be unresolved discussion threads on this list that may indicate an edit might be in order.</span></font></div></blockquote><div><br></div><div>For basic uses of the kind you're talking about (querying for the whole aggregate or for individual entity metadata) the spec is not so much old as stable. The outstanding issues are over the question of whether additional features should be added in order to service more advanced use cases. I'm personally of the opinion that we should expect to see some real take-up of and experience with the basic stuff before we push towards the complex cases.</div><br><blockquote type="cite"><div><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">I’m afraid to say I also have some ideas of how I would like to optimize Metadata retrieval that I would be interested to get vetted by some folks smarter than me (that’s you).<br></span></font></div></blockquote><div><br></div><div>I think this list would be a good place to do that.</div><br><blockquote type="cite"><div><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">So first... Is there anyone still on this list that wants to make progress? Are there other lists we should notify and include if we do want to proceed? I’m willing to do a little wrangling and maybe even a little documentation of consensus if there are interested participants.</span></font></div></blockquote><div><br></div><div>I guess you'd have to say what you think progress would look like: if you mean that the existing draft doesn't meet your use cases, talking about why that's the case would be very useful. If the existing draft *does* meet your use cases, we're talking about implementations and several people here have things cooking at various levels of maturity.</div><div><br></div></div><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><span class="Apple-tab-span" style="white-space: pre; "> </span>-- Ian<br></div><div><span class="Apple-style-span" style="font-size: medium; "><br></span></div></span></span><br class="Apple-interchange-newline">
</div>
<br></body></html>