<div dir="ltr">I believe both examples are package relationships. Caroline<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 12, 2016 at 9:27 PM, MURATA Makoto <span dir="ltr"><<a href="mailto:eb2m-mrt@asahi-net.or.jp" target="_blank">eb2m-mrt@asahi-net.or.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Caroline,<div><br></div><div>Thank you very much!</div><div><br></div><div>I guess that the relationship in the second example (ONIX) is a package </div><div>relationship. Is this correct?</div><div><br></div><div>Regards,</div><div>Makoto</div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">2015-12-31 21:40 GMT+09:00 Arms, Caroline <span dir="ltr"><<a href="mailto:caar@loc.gov" target="_blank">caar@loc.gov</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Rex and Darrin,<br>
Attached is my revision for the section on embedding foreign parts in the MCE Guidelines. It uses the suggestion from Francis to put the new parts into folders -- which we agreed on the call was a good idea. You said that you should be able to create the appropriate diagram.<br>
<br>
Happy New Year!<br>
<br>
Caroline<br>
<br>
-----Original Message-----<br>
From: Francis Cave [mailto:<a href="mailto:francis@franciscave.com" target="_blank">francis@franciscave.com</a>]<br>
Sent: Thursday, December 10, 2015 11:52 AM<br>
To: <a href="mailto:e-SC34-WG4@ecma-international.org" target="_blank">e-SC34-WG4@ecma-international.org</a><br>
Subject: RE: Second try -- RE: Action item on additional example for Foreign Part in MCE Best Practices document.<br>
<br>
Looks good to me. But I wonder if it's a good idea to put a foreign part on the root of the package. Maybe it slightly complicates the picture, but I'd have thought that it would be better to put it inside a folder, e.g.<br>
'movies' in your first example and 'meta' in your second example.<br>
<br>
Francis<br>
<br>
<br>
-----Original Message-----<br>
From: Arms, Caroline [mailto:<a href="mailto:caar@loc.gov" target="_blank">caar@loc.gov</a>]<br>
Sent: 10 December 2015 14:32<br>
To: Francis Cave <<a href="mailto:francis@franciscave.com" target="_blank">francis@franciscave.com</a>>; <a href="mailto:e-SC34-WG4@ecma-international.org" target="_blank">e-SC34-WG4@ecma-international.org</a><br>
Subject: RE: Second try -- RE: Action item on additional example for Foreign Part in MCE Best Practices document.<br>
<br>
Here is proposed substance for this section of the guidelines. I did not define the term "foreign part" in a formal way because I did not know whether a formal definition belonged in a Terms and Definitions section.<br>
<br>
I chose to drop Tracked Changes because the section is mostly new and is easier to read that way. I make no claim for correct formatting!<br>
<br>
Thanks for the feedback. Caroline<br>
<br>
Caroline Arms<br>
Library of Congress Contractor<br>
Co-compiler of Sustainability of Digital Formats resource <a href="http://www.digitalpreservation.gov/formats/" rel="noreferrer" target="_blank">http://www.digitalpreservation.gov/formats/</a><br>
<br>
** Views expressed are personal and not necessarily those of the institution<br>
**<br>
<br>
<br>
-----Original Message-----<br>
From: Francis Cave [mailto:<a href="mailto:francis@franciscave.com" target="_blank">francis@franciscave.com</a>]<br>
Sent: Wednesday, December 09, 2015 5:32 PM<br>
To: Arms, Caroline; <a href="mailto:e-SC34-WG4@ecma-international.org" target="_blank">e-SC34-WG4@ecma-international.org</a><br>
Subject: RE: Second try -- RE: Action item on additional example for Foreign Part in MCE Best Practices document.<br>
<br>
Hi Caroline<br>
<br>
I suggest that you use '.xml' as the extension for an ONIX filename.<br>
<br>
I agree that Part 1 is clear as to the meaning of "unknown part", so I think we should avoid using this term with a different meaning in the MCE Best Practices document, as it would be confusing for implementers.<br>
<br>
However, should we define "foreign part" to be specific to OOXML? A more general definition of "foreign part" might be "a part whose specified relationship type is not defined by the MCE implementation". That would make the guidance applicable to implementations of MCE other than implementations of OOXML (Parts 1, 2 and 4).<br>
<br>
Kind regards,<br>
<br>
Francis<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Arms, Caroline [mailto:<a href="mailto:caar@loc.gov" target="_blank">caar@loc.gov</a>]<br>
Sent: 09 December 2015 21:53<br>
To: Arms, Caroline <<a href="mailto:caar@loc.gov" target="_blank">caar@loc.gov</a>>; 'Francis Cave' <<a href="mailto:francis@franciscave.com" target="_blank">francis@franciscave.com</a>>; <a href="mailto:e-SC34-WG4@ecma-international.org" target="_blank">e-SC34-WG4@ecma-international.org</a><br>
Subject: Second try -- RE: Action item on additional example for Foreign Part in MCE Best Practices document.<br>
<br>
My apologies for not getting another draft of this out yet. I've been swamped with special requests from the Library before the end of my current contract.<br>
<br>
Today I got started and realized that I still had questions that might be easier to pose directly rather than in comments on a new draft.<br>
<br>
First -- in relation to the foreign/unknown terminology<br>
<br>
>From Part 1<br>
<br>
"9.1.4 Unknown Parts<br>
With the exception of relationship parts, all other parts in an Office Open XML document that are not the target of an implicit or explicit relationship are considered unknown parts. Unknown parts shall be ignored on document consumption and can, but need not, be discarded on production."<br>
<br>
***This seems to imply that a part that is given a relationship as Chris suggests is NOT an unknown part.<br>
<br>
Again from Part 1<br>
"9.1.7 Unknown Relationships<br>
All relationships not defined within ECMA-376 are considered unknown relationships. Unknown relationships are permitted within an Office Open XML document provided that they conform to relationship markup guidelines as defined by the OPC specification. Specifically:<br>
* Conforming consumers shall not fail to load a document containing unknown relationships.<br>
* Conforming producers that are also consumers can, but are not required to, roundtrip and preserve unknown relationships and their target parts."<br>
<br>
*** So Chris's recommendation is actually to use an "unknown" relationship type not to use an "unknown part." So I propose to use the term "foreign part" to mean a part with a relationship type not defined in OOXML.<br>
<br>
Does that make sense?<br>
<br>
Back to Part 1 on the content type question I raised which no-one responded to.<br>
<br>
"9.1.6 Invalid Parts<br>
ZIP archive items that do not conform to OPC part naming guidelines or are not associated with a content type shall not be allowed in an Office Open XML document, with the exception of items specifically defined by ECMA-<br>
376-2 and trash items."<br>
<br>
*** This seems to require a declaration in /[Content_Types].xml that covers the type of the added "foreign" part. Chris's draft does not mention that requirement. Do others agree that it is a requirement? If so, I will extend the discussion of the first example to include that.<br>
<br>
I see the following in a minimal .docx file that I created in Word <Default Extension="xml" ContentType="application/xml"/><br>
<br>
I'm going to assume that for the .mov file in the example from Chris, the following would be adequate:<br>
<Default Extension="mov" ContentType="video/quicktime"/><br>
See <a href="https://www.iana.org/assignments/media-types/video/quicktime" rel="noreferrer" target="_blank">https://www.iana.org/assignments/media-types/video/quicktime</a><br>
<br>
Looking at the ONIX documentation for guidance on file extension use:<br>
From<br>
<a href="http://www.editeur.org/files/ONIX%203/ONIX_for_Books_Release3-0_html_Best_Practice+codes_Issue_31_v1-2-7.zip" rel="noreferrer" target="_blank">http://www.editeur.org/files/ONIX%203/ONIX_for_Books_Release3-0_html_Best_Pr<br>
actice+codes_Issue_31_v1-2-7.zip</a><br>
ONIX file names commonly include the '.xml', '.onix' or '.onx' suffix (the first two are preferred).<br>
The mime type should typically be 'application/xml', ...<br>
<br>
Francis, Do you have any suggestions as to which of .xml or .onix I<br>
should use for the ONIX example? Or would you recommend covering both possibilities in my example?<br>
<br>
I hope to have more time before tomorrow's call to work on revised text.<br>
<br>
Caroline<br>
<br>
PS: Apologies for sending a dud message. My touchpad took control!!<br>
<br>
Caroline Arms<br>
Library of Congress Contractor<br>
Co-compiler of Sustainability of Digital Formats resource <a href="http://www.digitalpreservation.gov/formats/" rel="noreferrer" target="_blank">http://www.digitalpreservation.gov/formats/</a><br>
<br>
** Views expressed are personal and not necessarily those of the institution<br>
**<br>
<br>
<br>
-----Original Message-----<br>
From: Arms, Caroline [mailto:<a href="mailto:caar@loc.gov" target="_blank">caar@loc.gov</a>]<br>
Sent: Friday, November 27, 2015 2:25 PM<br>
To: 'Francis Cave'; <a href="mailto:e-SC34-WG4@ecma-international.org" target="_blank">e-SC34-WG4@ecma-international.org</a><br>
Subject: RE: Action item on additional example for Foreign Part in MCE Best Practices document.<br>
<br>
Francis, Thanks again. Taking a quick look at the schemas, I'm inclined to use the 'reference' version as an example, because if anyone actually followed things up, they would find tag names that are less cryptic.<br>
<br>
I'll plan on doing a next draft, taking into account the feedback so far, sometime next week.<br>
<br>
Caroline<br>
<br>
<br>
Caroline Arms<br>
Library of Congress Contractor<br>
Co-compiler of Sustainability of Digital Formats resource <a href="http://www.digitalpreservation.gov/formats/" rel="noreferrer" target="_blank">http://www.digitalpreservation.gov/formats/</a><br>
<br>
** Views expressed are personal and not necessarily those of the institution<br>
**<br>
<br>
-----Original Message-----<br>
From: Francis Cave [mailto:<a href="mailto:francis@franciscave.com" target="_blank">francis@franciscave.com</a>]<br>
Sent: Friday, November 27, 2015 6:48 AM<br>
To: <a href="mailto:e-SC34-WG4@ecma-international.org" target="_blank">e-SC34-WG4@ecma-international.org</a><br>
Subject: RE: Action item on additional example for Foreign Part in MCE Best Practices document.<br>
<br>
After a further exchange with Graham I think that, if we wish to include an ONIX example, we should use 'application/xml' for the media type. We can use the same URI for both namespace and relationship type, so either '<a href="http://ns.editeur.org/onix/3.0/reference" rel="noreferrer" target="_blank">http://ns.editeur.org/onix/3.0/reference</a>' or '<a href="http://ns.editeur.org/onix/3.0/short" rel="noreferrer" target="_blank">http://ns.editeur.org/onix/3.0/short</a>', depending upon which tag set we choose to use.<br>
<br>
Francis<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: MURATA Makoto (FAMILY Given) [mailto:<a href="mailto:eb2m-mrt@asahi-net.or.jp" target="_blank">eb2m-mrt@asahi-net.or.jp</a>]<br>
Sent: 27 November 2015 03:30<br>
To: <a href="mailto:e-SC34-WG4@ecma-international.org" target="_blank">e-SC34-WG4@ecma-international.org</a><br>
Subject: Re: Action item on additional example for Foreign Part in MCE Best Practices document.<br>
<br>
Francis,<br>
<br>
Thank you very much!<br>
<br>
A specialized media type for ONIX would make sense if there is some special processing (such as ONIX fragment identifiers).<br>
<br>
So far, in OOXML, URIs for namespace names and those for relationship types are different. But I do not see strong reasons for separating them.<br>
Namespace names should be changed only for intentionally destroy existing application programs for new data. When should we change relationship names? Probably,when we would like to prohibit existing OOXML applications from accessing new parts. Then, it might be a good idea to use the same URI.<br>
<br>
I don't think that namespace names or relationship types have to be resolved. They are just names. Thus, I don't think that performance is an issue.<br>
<br>
Regards,<br>
Makoto<br>
<br>
<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div><br>Praying for the victims of the Japan Tohoku earthquake<br><br>Makoto</div>
</font></span></div>
</blockquote></div><br></div>