<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=iso-8859-1">
<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;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">On yesterday’s call, I was asked to write up some notes on part references, given the discussion we wrapped up with around section 9.2 Part Addressing.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My take on the published clause 9.2 and its sole subclause 9.2.1 is that it exists simply to note how (1) relative references and (2) base URIs are handled.
That is: (1) by starting from the part containing the reference rather than, for example, the .rels file, (2a) what the default base URI is for a part and (2b) that a base URI may be explicitly specified if the content type of the part containing the reference
supports that. I think the text under 9.2 is just some trivial introductory verbiage to avoid having an empty clause; 9.2.1 is the real information.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">On to 9.3. Relationships exist as an explicit OPC concept and part/markup because the way in which a reference is stored in the core content parts of an OPC
package are specific to those parts’ content types. Relationships are an OPC-common way to represent those references. They also allow references to have associated metadata information.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">9.3.2 Relationship Markup. Murata-san pointed out the last sentence of this subclause, which disallows use of xml:base. Given that entire paragraph, I believe
the scope of that is disallowing use of xml:base inside the Relationship element markup to specify a base URI for a relative reference. That is, a value of a Target attribute of a Relationship element that is a relative reference shall always be relative
to the part containing the reference – described here as the “Relationships source part” (that language can be improved), aka the part associated with the Relationships part that contains the Relationship element in question.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">9.3.2.2 Relationship Element. This specifies the markup requirements, including that the value of the Target attribute must be a URI reference – either a URI
or a relative reference, depending on the value of the TargetMode attribute. See
<a href="http://tools.ietf.org/html/rfc3986">RFC 3986</a>: §4.1 - ABNF defining URI reference as a URI or a relative reference; §3 - ABNF defining URI; §4.2 - ABNF defining relative reference.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Given the assertion that 9.2.1 exists to discuss concepts, that Relationships are the only way references are stored at the OPC level, that 9.3.2.2 specifies
allowable values for the Target attribute in terms of RFC terminology, and that 9.3.2.2 notes that the value of Target is not restricted to the syntax requirements for part names, I don’t think we should apply part name ABNF or prose restrictions to the clause
about part addressing (9.2 / 9.2.1), as was proposed. Merging Annex A into this area seems to be a good idea, though.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">(Note that all the section numbers in Murata-san’s proposed draft document are off by one, since clause 6 Acronyms and Abbreviations seems to be missing from
the base document his changes were made to.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">John<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> eb2mmrt@gmail.com [mailto:eb2mmrt@gmail.com]
<b>On Behalf Of </b>MURATA Makoto<br>
<b>Sent:</b> Tuesday, February 4, 2014 5:43 AM<br>
<b>To:</b> SC34<br>
<b>Subject:</b> Part 2 rewrite for part names and part references<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">As the owner of the below DRs, I tried to provide a solution. See <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">the attached document. It implements changes sketched in <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">WG 4 N 0207.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">09-0280 – general DR about sections of OPC assuming non-ASCII is disallowed<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">09-0281 – terminology; all uses of “part” should specify what kind of part is meant<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">09-0283 – similar to 09-0280<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">09-0284 – terminology; need to re-associate the ABNF term names with the prose for part names<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">09-0285 – terminology; use of “part IRI” and “part URI”<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">09-0286 – need to update 9.2 (Part Addressing) to specify the format of a reference, based on the changes to be made to 9.1.1 (Part Names)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">09-0288 – same as 09-0286, but for 9.3.2 (Relationship Markup)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">09-0291 – terminology; specify what “Unicode string” means, based on the changes to be made to 9.1.1<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">09-0292 – which characters are allowed in a part name (e.g., whitespace, delimiters, special characters)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">13-0002 – fix previous changes made to Annex H for introduction of non-ASCII support<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">10-0015 – clarify “source part” for relationships<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Regards,<br>
Makoto <o:p></o:p></p>
</div>
</div>
</body>
</html>