<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>I’ve tried to update the BB Fig 4 chart based on conversations from today. See attached. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Main thing was to get the interface numbering consistent with our other charts. I’ve included those other charts (unchanged) after the BB Fig 4 chart in this file. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I also fixed the treatment of the Serialization and Protocol interfaces as we discussed in the meeting today. However, I also went a step farther by putting them inside the Interface 2 box instead of the Generic Adapter box. That’s following Steve’s lead (I think) when he emphasized that we’re building specs for the interfaces, not for the adapters (executables). Steve, correct me if this doesn’t reflect that correctly. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I also tried to follow Steve’s lead on making blue book stuff blue and green book stuff green. Adapters are discussed in the (informative) green book, interfaces are defined in the (normative) blue book. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I also added some text below the figure that are the main points about interfaces versus implementation, and JSON/HTTP/Rest as default specifications. These don’t go in the BB figure, but I felt like they were needed in the PPT as this figure may be used in other presentations. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Relating the WG discussion to chart 2, I think the way we should characterize it is that in the PICS-Proforma (for the OAIS-IF BB), interface 2 will be mandatory, interfaces 1 and 3 will be optional. It’s probably best to also put a statement to that effect in the text of the blue book. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Comments/Corrections welcome. Discussion in the telecon next week. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#002060'> -=- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal>Mike Kearney<span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>Huntsville, Alabama, USA <o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>