added:
<h2>Questions and comments from the workshop on 3/28</h2>
<h3>implications of who was chosen to speak to?</h3>
<p>    list received from chris and wilson - chosen mainly because of mellon funding<br />    picking people who are building things?<br />        Chris - requested study for quidelines for up coming projects, which approach to take, can OSIDs do it<br />    hard to judge success, there is not a clear picture of what that means in the context of OKI<br />        wasn't a survey of everyone working on OSIDs, but a representative of that universe<br /></p>
<h3>interoperability, did you look at as desired for a particular project, or other people that could benefit such as projects that need to interoperate with your project</h3>
<p>    short answer - yes<br />    the group that will benefit is not necessarily the group providing the funding<br /></p>
<h3>definitions - what is interoperability exactly</h3>
<p>    getting to that<br />    what Don W is hearing is using tools, data, operations, etc. They all have different implications. is there a focus on those<br />        depends on project context otherwise there is no answer to what it means<br />    finding ROI picture - there is another dimension for groups<br /></p>
<h3>Surprised over shape of graph, in that models are less useful during development phase</h3>
<p>    there is another dimension, in that style matters<br />    same problem could be addressed by different styles<br /></p>
<h3>    Ira - When thinking about osids, thinks of 2 activities - developing implementations - takes a fair amount of effort, and an individual user may see no benefit - second use is using it. deploying a particualr implementation - this would save a user effort. The question is did you discuss both aspects with folks. Not clear from the report.</h3>
<p>        the question will be answered more later. need to discuss particular osids, and not as a whole<br />        there are few implementations for some osids, making re-use difficult<br />        to get value of the osids, requires a network effect, i.e., other users who can make use of an implementation<br />            if we can build communities in other areas then the network effect can be realized<br />            if other people are making the pitch, not just MIT, then greater chance for success<br />            look for a crowd<br />        on risk - cost of changing standards, maturity, etc, in theory they help minimize risks, but there is a risk involved as well.<br />            adapting to a standard also costs<br />    <br /><br /></p>