ࡱ> 5@ Rwbjbj22 2XXG=/dOdOdO8O PtGU"PP(PPPPPPTTTTTTT$iXRZTT9PPPPPTPPUSSSPPPTSPTSSTTPP qtMdO|RTTU0GUT[|R6[Tjr[T PPSPPPPPTTD% *D%S *Co-editors preliminary draft resolutions on FCD 19763-3 ballot comment (for discussion) # NB Clause No Type 1 US Title page ed Comment by the NB An acronym could be included for this family of Standards, just as "MDR" is an acronym for ISO/IEC 11179. Proposed change by the NB Add "FMI" to title name as an acronym for this family of standards. See comment 2. Change title to: Information Technology--Framework for Metamodel Interoperability (FMI)--Part 1: Reference Model Preliminary draft resolution by the co-editors Change title to Information Technology--Metamodel framework for interoperability (MMFI)--Part 3: Metamodel for ontology registration. Define MMFI Ontology registration as its abbreviation. Rationale: What this family of standards specify are a set of metamodels (i.e. metamodel framework) to facilitate the interoperability of several kinds of artifacts, not limited to metamodels, but including also models, ontologies etc. from the point of their administrations. So, the current title Framework for metamodel interoperability is not appropriate and it is better to be Metamodel framework for interoperability. And its acronym should be MMFI. # NB Clause No Type 2 US Throughout document ed Comment by the NB Reference to the name of the standard and family of standards is inconsistent. The title page calls it "Framework for Metamodel Interoperability". In several places it is called similar, but different names such as "metamodel framework for interoperability" or "metamodel framework". The term metamodel framework is also used where it does not refer to the family of standards. Proposed change by the NB For clarity use the same name consistently, throughout document. All references to the name of the family of standards should be changed to "Framework for Metamodel Interoperability" or to "FMI". A statement needs to be included to show that the term "metamodel framework" is sometimes used synonymously for FMI. There are many instances of the acronym "MMF" in the text and graphics that should be changed to "FMI" or to "metamodel framework". Preliminary draft resolution by the co-editors This comment is not applicable to FCD19763-3, but to FCD19763-1. FCD19763-3 does not use any of the term "metamodel framework for interoperability" or "metamodel framework". # NB Clause No Type 3 US 3.3 Abbreviated terms ed Comment by the NB List contains both abbreviations and acronyms. Proposed change by the NB Change title of section to: "3.3 Acronyms and Abbreviations". Preliminary draft resolution by the co-editors This title is conformed to ISO Directives Part2. Since an acronym is a special kind of abbreviation, Abbreviated term is enough even if the list contains acronyms. See comment #24. # NB Clause No Type 4 US 3.3 Abbreviated terms ed Comment by the NB Clause 3.3. Contains the acronym "MMF" and NOT "FMI". Two acronyms for the same standard is confusing. Proposed change by the NB Make consistent with resolution of comment #2. Delete the acronym "MMF" and include the acronym "FMI". Use the term "metamodel framework" where appropriate (rather than the acronym "MMF). Preliminary draft resolution by the co-editors See comment #1. # NB Clause No Type 5 US 3.3 Abbreviated terms ed Comment by the NB No reference is provided for ODM. Proposed change by the NB Add ODM draft to Bibliography. Preliminary draft resolution by the co-editors The proposed change is accepted. # NB Clause No Type 6 US 3.2.x ed Comment by the NB Some abbreviations that are used in the document are not listed here. Proposed change by the NB Add: MDR, DL. Preliminary draft resolution by the co-editors MDR is added at 3.3 Abbreviated term. DL need not be added because this is defined as a name in table 1 at Annex C (informative). # NB Clause No Type 7 US Throughout ed Comment by the NB There are several proof reading errors that need to be fixed. Proposed change by the NB Suggested fixes for proof reading errors have been made in the document with "tracking changes" turned on. See the attached document. Note that none of the changes that would arise from the other ballot comments are made in the edited document. Edited document file name is: 32N1363T-FCD19763-3-with edits-v2.doc Preliminary draft resolution by the co-editors 32N1363T-FCD19763-3-with edits-v2.doc will be accepted. # NB Clause No Type 8 US Clause 3 ed Comment by the NB The terms appear in the table of contents. This is from misuse of the template. Editor used the wrong styles for headings, terms and text. Proposed change by the NB Change to termnum, term, and termdef styles. Preliminary draft resolution by the co-editors The proposed change is accepted. # NB Clause No Type 9 US Throughout ed Comment by the NB This document does not appear to use the ISO template. Proposed change by the NB Put into ISO template. Preliminary draft resolution by the co-editors The proposed change is accepted. # NB Clause No Type 10 US Clause 3.2.1 ed Comment by the NB Not clear what is meant by the collective qualification. Proposed change by the NB Strike it or find a better wording. Preliminary draft resolution by the co-editors Change the definition to description of a universe of discourse. # NB Clause No Type 11 US Clause 3.2.1,3.2.2, 3.2.3 te Comment by the NB Definitions are vague and unclear. Proposed change by the NB Define universe of discourse, formalized and localized. Also, clarify the implications with respect to sharing and sharability, and contrast ontology to model as defined in Part 1. Preliminary draft resolution by the co-editors Add the definition of universe of discourse in TR9007. Change the definition of Reference ontology to An ontology that is valid and used and saharble by a community of interest (i.e. formalized) because the word formalized is not necessary. Change the definition of local ontology to An ontology that is localized for one specific application based on at least one reference ontology since localized is a general term and need not be defined. # NB Clause No Type 12 US Clause 3.2.4 te Comment by the NB Definition is imprecise, and differs substantially from that provided in 24707. Proposed change by the NB Change definition of Sentence to A logical statement which has a truth value, and define Axiom as A sentence which is asserted to be true in some context, such as an ontology. Preliminary draft resolution by the co-editors Change the definition of sentence to A text that has a truth value since the meaning logical is vague and redundant because a text that has a truth value is a logical text. Axiom is not used in FCD19763-3. # NB Clause No Type 13 US Clause 3.2.5 te Comment by the NB Definition does not agree with use of the term symbol in ISO 704 and ISO 1087-1. Also, most primitive construct is not clear. Proposed change by the NB Define symbol, paying attention to its use by TC37 and by the logic community. Also clarify what non-logical means. Preliminary draft resolution by the co-editors This symbol is different from the one defined in ISO 704. In logic, symbol or name is the most popular wording for the lexicon (word) that composes a sentence. But, name is used in the different meaning in MDR and should not be used. So, symbol is the best wording. Symbol can be defined as a most primitive lexical construct that composes a sentence and logical symbol is a symbol whose meaning is defined by its language, irrelevant to interpretations. In usual elementary logic, not and or and variables (actual symbols vary, depending on languages) are examples of logical symbols, Non-logical symbol is a symbol that is not a logical symbol. See, for example, Computability and logic, third edition by Gorege S. Boolos and Richard C. Jeffrey. We think that to define this kind of terms is a matter of an elementary textbook of logic and beyond the scope of this standard because it is almost equivalent to creating a standard of an upper ontology of logic or a terminological standard of logic and it is very difficult and may need hundreds of pages. # NB Clause No Type 14 US Figures 2, 3 and 10 ed Comment by the NB Font difference for abstract classes vs. concrete classes is difficult to see. Proposed change by the NB Use a more distinctive font for abstract classes, preferably italics. Preliminary draft resolution by the co-editors The fonts for abstract classes and concrete classes are the same. There is no rule nor necessity to distinct fonts for abstract classes and for concrete classes. # NB Clause No Type 15 US Clause 4.3.1 te Comment by the NB The description of the URI attribute suggests that a URL is required. Proposed change by the NB Either rename the attribute to URL or change the description. Preliminary draft resolution by the co-editors Change the description to URI that identifies the corresponding ontology. # NB Clause No Type 16 US Clause 4.3.1 ed Comment by the NB The wording where...exists is imprecise. Proposed change by the NB Change the description to URL which specifies the location of the ontology. Preliminary draft resolution by the co-editors See comment #15. # NB Clause No Type 17 US Clause 4.3.1 ed Comment by the NB We're concerned about the subclass relationship between Ontology and ModelDomainProfile. This implies that every Ontology is a ModelDomainProfile. It is not clear whether this is a consequence of the specific purposes of FMI or is expected to be true of all ontologies. Proposed change by the NB Either clarify the definition of Ontology in the context of FMI to make clear that it is a restriction of the general notion of an ontology, or provide some justification for the asserted subclass relationship. Preliminary draft resolution by the co-editors Change Ontology to Ontology_whole since this is not an actual ontology but an administered item that corresponds to an actual ontology and that is a specialization of ModelDomianProfile. # NB Clause No Type 18 US Clause 4.3.3 te Comment by the NB Do not understand the reason for the first constraint specified. Proposed change by the NB Explain (in the clause text) why a Local_Ontology cannot consist entirely of Reference_Ontology_Components. Preliminary draft resolution by the co-editors Change the clause text to Local_Ontology is a metaclass designating an ontology that is localized for one specific application based one at least one ontology that is designated by Reference_Ontology. Local_Ontology consists of at least one Local_Ontology_Component since this is localized for one specific application and also consists of at least one Reference_Ontology_Component or a Local_Ontology_Component which is the same as a Reference_Ontology_Component since this is based on at least one Reference_Ontology. # NB Clause No Type 19 US Clause A.1 te Comment by the NB The textual explanation of the meaning of RC1 does not match the OWL shown in the figure. Proposed change by the NB Change either the explanation or the figure. Preliminary draft resolution by the co-editors Need more specific comment. # NB Clause No Type 20 US Clause A.1 te Comment by the NB The names measure and Dimension are confusing. Proposed change by the NB Change measure to dimensionality and change Dimension to Dimensionality. Preliminary draft resolution by the co-editors The use of dimentionality and Dimentionality in different meanings is more comfusing. Moreover, if they are translated in Japanese (maybe, also in Chinese and Korean), they are exactly the same. (Japanese does not have an upper letter and a lower letter.) # NB Clause No Type 21 US Clause A.2 te Comment by the NB The textual explanation of the meaning of RC4 is not as precise as the OWL shown in the figure. Proposed change by the NB Change the explanation to A prefixed unit is a unit, has exactly one prefix, and has exactly one kernel. Preliminary draft resolution by the co-editors We do not understand the difference. The current explanation A prefixed unit is a unit that has exactly one prefix and exactly one kernel seems more natural. # NB Clause No Type 22 ISO? General ed Comment by the NB Document does not follow basic ISO presentation. Proposed change by the NB The document should be prepared using the ISO template, available from the ITTF website. As a minimum, change margins, headers, footers, line spacing and font size to align with the ISO template. Preliminary draft resolution by the co-editors The proposed change is accepted. # NB Clause No Type 23 ISO? 2 ed Comment by the NB Only documents which are publicly available and which are cited elsewhere in the document in a way which indicates that they are indispensable for the0application of ISO/IEC 19763-3 may be listed in Clause 2. Incorrect title given for ISO/IEC 11179-3. Proposed change by the NB Remove ISO/IEC 19501 and ISO/IEC 19502, which are not cited elsewhere in the document. Change last element of Part 3 title to "Registry metamodel and basic attributes" Preliminary draft resolution by the co-editors The proposed change is accepted. # NB Clause No Type 24 ISO? 3, 3.1 ed Comment by the NB Incorrect clause/subclause title. Proposed change by the NB Replace "Definitions and abbreviated terms" with "Terms, definitions and abbreviated terms"; replace "3.1 Definitions" with "3.1 Terms and definitions" Preliminary draft resolution by the co-editors The proposed change is accepted. # NB Clause No Type 25 ISO? 3.1 ed Comment by the NB Incorrectly drafted introductory paragraph. Proposed change by the NB Replace with "For the purposes of this document, the terms and definitions given in ISO/IEC 11179-3, ISO/IEC 19763-1, ISO/IEC 19763-2 and the following apply." IMPORTANT ISO/IEC 19763-2 must be a publicly available document by the time ISO/IEC19763-3 is submitted for FDIS since the user is required to consult it in order to apply ISO/IEC 19763-3. Otherwise, it cannot be cited in 3.1 or given as a normative reference. Preliminary draft resolution by the co-editors What does a publicly available document mean? How about ISO/IIEC 19763-1? # NB Clause No Type 26 ISO? 3.2 ed Comment by the NB Superfluous subclause title. Terms and definitions are incorrectly presented. Proposed change by the NB Remove "3.2 Broad terms" and draft terms and definitions as follows: 3.1.1 [TermNum style] ontology [Term style] collective description ... Use of these styles in the ISO template will ensure correct presentation in Clause 3 and non appearance of terms in table of contents. Preliminary draft resolution by the co-editors The proposed change is accepted. # NB Clause No Type 27 ISO? 3.3 ed Comment by the NB Abbreviations are not numbered in International Standards. Proposed change by the NB Remove 3.3.1, 3.3.2, etc. Preliminary draft resolution by the co-editors The proposed change is accepted. # NB Clause No Type 27 ISO? 5 ed Comment by the NB Clause 2 is the conformance clause in International Standards. Proposed change by the NB Insert this clause after the Scope and renumber subsequent clauses. Preliminary draft resolution by the co-editors The proposed change is accepted. # NB Clause No Type 27 ISO? figures ed Comment by the NB Figure 1 contains text that is partially hidden; Figure 3 contains text that is too small to be legible. Proposed change by the NB Improve/resize as necessary. Preliminar  [\stx  N O   # F T i j t u ǵ}n}n}n}n}n}n}n}nn}n}n}n}n}n}nh|!CJKHOJQJaJo(h|!CJKHOJQJaJ h|!CJo(#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ$h|!5CJKHOJQJ\^JaJ'h|!5CJKHOJQJ\^JaJo(+.Z[]s  d8!|8!|8!|8!|8!|8!|8!|8!8!|8!v 8!|8!8!|8!|8! 8!8!|8!|8!|8!|8!|8!pVD $7$8$H$^a$ VD^` $ N 7$8$H$a$ $7$8$H$a$ $7$8$H$a$Gv     ) * U V u v ~    G H i j /0cd~μ#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo( h|!CJo(h?K CJKHOJQJaJh|!CJKHOJQJaJo(h|!CJKHOJQJaJ?n!"<lm*@AVW|}ǸǸǸոǸǸǸոǸǸǸǸǸǸǸոǸǸǸ#h|!5CJKHOJQJ\aJo(h|!CJKHOJQJaJo(h|!CJKHOJQJaJ h|!CJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo(A1`?n"<*c#8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!v 8!|8!|8!v 8!v 8!| $7$8$H$`a$ VD^` $7$8$H$a$ $7$8$H$^a$VD<=KLPQ    " % & 8 j k -!.!Y!!!!!!!!!!!!!!!!"":";"=">"C" h|!CJo(#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo(h|!CJKHOJQJaJo(h|!CJKHOJQJaJB & 8 Z!!="`"a"x"""&#@###!$$&((8!|8!|8!|8!|8!|8!8!8!|8!v 8!|8!|8!|8!|8!|8!8!|8!8!|8!|8!v 8!j8! 8!|^ $7$8$H$^a$VD $7$8$H$`a$ VD^` $7$8$H$a$C"D"a"v"w"x"{"""""""""""""%#@#m#n###########+$,$2$3$7$8$<$=$$$$$$$$$$$%%N%O%T%U%c%d%%%%%%%%% h|!CJo(#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo(h|!CJKHOJQJaJo(h|!CJKHOJQJaJB%%%%%%%C&D&V&W&&&&&#'1'''''(4(5(6(9(=(I(J(P(S(U(V(h((((()))F))))))))*******-*_*`*r******+пп h|!CJo(#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo(h|!CJKHOJQJaJh|!CJKHOJQJaJo(A(6(V(h((()F))))**-*s****H+I+_+x+++8!|8!|8!|8!|8!|8!|8!|8!|8!8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!| $7$8$H$^a$VD $7$8$H$`a$ VD^` $7$8$H$a$++E+F+I+^+a+e+r+u+w+x+++++++,M,_,t,w,{,,,,,,,,,,--O-P--------../._.`........h|!CJKHOJQJaJo(h|!CJKHOJQJaJ h|!CJo(#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo(h|!CJKHOJQJaJo(h|!CJKHOJQJaJ6++,M,^,_,u,,,--../////0)000228!|8!|8!|8!|8!|8!|8!|8!|8! 8!|8!v 8!|8!v 8!|8!|8!|8!|8!|8!|8!8!|8!8!| $7$8$H$^a$ VD^` $7$8$H$a$ $7$8$H$`a$VD....../(/u/v//////////////0)0Z0[0u0v00000112222222222 3:3;3f33333444 4"4#4$4&4'494`4a4l44 h|!CJo(#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo(h|!CJKHOJQJaJo(h|!CJKHOJQJaJB222 3g3333334'494l4445 6 6!686J6668!|8!|8!|8!8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!8!|8! 8!|8!|8!|8!|8!8!| $7$8$H$`a$VD $7$8$H$^a$ VD^` $7$8$H$a$44444555 5!5&5'55565:5C5 6 6#6'6163646567686J6z6{666666%7&7.7/7^7777777777888%8(8*8+8=8m8n88888899A9C9ʹʹ#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo( h|!CJo(h|!CJKHOJQJaJo(h|!CJKHOJQJaJB6/7^77778+8=8n88L9{999999N;;;C<<<8!8!|8!|8!8!|8!|8!|8!|8!|8!|8!v 8!|8!|8!|8!|8!|8!|8!v 8!|8!|8!8!8!| VD^` $7$8$H$a$ $7$8$H$`a$VD $7$8$H$^a$C9K9{9999999999::|:~:::::;;;<<s<t<<<<<<= = ===#=D=_========&>H>]>`>f>i>m>p>q>>>>>>>W?X?t?u??ʹʹʹ#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo(h|!CJKHOJQJaJo( h|!CJo(h|!CJKHOJQJaJB<<<<=#=E=_==&>G>H>^>q>>>>j?p@@@@@@8!|8!|8!|8!|8!|8!|8!|8!8!|8!|8!|8!|8!|8!|8!|8!|8!v 8! 8!|8!|8!|8!|8!| $7$8$H$^a$VD` VD^` $7$8$H$a$ $7$8$H$`a$????@@O@P@o@p@@@@@@@AA AAAAA(AvAwAAAAAAAAAAAABBPBQByBzBBBBBɸuh|!CJKHOJQJaJo( h|!6CJKHOJQJ]aJ h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo( h|!CJo(h|!CJKHOJQJaJh|!CJKHOJQJaJo(.@AA(AEAwAAAABBBBBB CC0CkCCC8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!8!|8!|8!|8!|8!|8!|8!|8!|8!| $7$8$H$^a$ $H7$8$H$^Ha$ $H7$8$H$`Ha$VD $7$8$H$`a$ VD^` $7$8$H$a$BB C CCCCCC0C_C`CjCkCCCCCCCDDDDDDD)D\D]DgDhDDDDDDDEEE,E/E5E=E@EBECEVEEEEEEEEF%28GWͻͻͻ𴦴ͻͻͻͻͻͦ𴤴 h|!o(Uh|!CJKHOJQJaJ h|!CJo(#h|!5CJKHOJQJ\aJo( h|!5CJKHOJQJ\aJ#h|!5CJKHOJQJ\aJo(h|!CJKHOJQJaJo(>CCCCDD)DhDDDDEE-EDEVEEEE%FGMW8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!|8!8!|8!|8!|8!|8!|8!2r8!2r $7$8$H$^a$ VD^` $7$8$H$a$ $7$8$H$`a$VDy draft resolution by the co-editors The proposed change is accepted. 32N 32WG2N  PAGE 10/ NUMPAGES 11 WXtuvw8!2r8!| $7$8$H$a$$a$WXY_`bcdeoprstvwh|!CJKHOJQJaJo( h|!o( h|!0Jo(h?K 0JmHnHu h|!0Jjh|!0JUh|!01h2P. A!"#$%S ^@^ Normal $1$a$,CJKHOJPJQJ_HaJmH nHsH tHj@j Heading 1#$$7$8$@&H$VDd^a$5CJKHOJQJ\aJDA@D Default Paragraph FontVi@V  Table Normal :V 44 la (k@(No List 6@6 Header 8!G$6 @6 Footer 8!G$.)@. Page Numbere@" HTML Preformatted@$ 2( Px 4 #\'*.25@91$a$CJKHOJ PJ QJ ^J aJ.O1. nonterminal$OA$ syntaxRY@RR ?K Document Map-D M OJ QJ ^J w=  "& "& "& "& "& "& "& "& "& "& "& $*/H5k:w=x;$@  .Z[]s d~;j  0 Q c  J   Y   < k )7f,j%&=Se 7f1`?n"<*c# &8Z=`ax&@!  6 V h !F!!!!""-"s""""H#I#_#x####$M$^$_$u$$$%%&&'''''()(((**** +g++++++,',9,l,,,- . .!.8.J...//^////0+0=0n00L1{111111222C3333334#4E4_44&5G5H5^5q5555j6p77777788(8E8w8888999999 ::0:k::::::;;);h;;;;<<-<D<V<<<<%=F=G=M=W=X=t=x=000000000000000000000000d00;0;0;0;0;00Q 00 00 0 0 0 0 0 00 00 00Y 0Y 0Y 0Y 00 0000< 0< 0< 0< 00 00007070707070000j0000000S000070707070000001010101000000?0?0?0?0000"000000000&00000Z0Z0Z0Z0Z0000&0000000000V 00 00!0!0!0!0!00"00s"00"0"0"0"00x#00#00$0$0$0$00$00%00&0&0&0&00'00(00(0(0(0(00*00g+00+0+0+0+00',00l,00,0,0,0,008.00.00//0//0//0//0//00+000n000L10L10L10L1001010020200303030300400E400404040400q50050500p70p70p70p70p70p70080800w80w80w80w80w800909090900:00k:00:0:0:0:00;00h;00;0;0;0;00D<00<00<0<00M90<Z/0M90<Z.Z[]s d~;j  0 Q c  J   Y   < k )7f,j%&=Se 7f1`?n"<*c# &8Z=`ax&@!  6 V h !F!!!!""-"s""""H#I#_#x####$M$^$_$u$$$%%&&'''''()(((**** +g++++++,',9,l,,,- . .!.8.J...//^////0+0=0n00L1{111111222C3333334#4E4_44&5G5H5^5q5555j6p77777788(8E8w8888999999 ::0:k::::::;;);h;;;;<<-<D<V<<<<%=F=G=M=W=X=t=x=000000000000000000000000d00;0;0;0;0;00Q 00 00 0 0 0 0 0 00 00 00Y 0Y 0Y 0Y 00 0000< 0< 0< 0< 00 00007070707070000j0000000S000070707070000001010101000000?0?0?0?0000"000000000&00000Z0Z0Z0Z0Z0000&0000000000V 00 00!0!0!0!0!00"00s"00"0"0"0"00x#00#00$0$0$0$00$00%00&0&0&0&00'00(00(0(0(0(00*00g+00+0+0+0+00',00l,00,0,0,0,008.00.00//0//0//0//0//00+000n000L10L10L10L1001010020200303030300400E400404040400q50050500p70p70p70p70p70p70080800w80w80w80w80w800909090900:00k:00:0:0:0:00;00h;00;0;0;0;00D<00<00<0<00M90Z80M90Z...1 C"%+.4C9?BWw#&()+-/12468:<>BdY1(+26<@CWw$'*,.03579;=?Av%(+1!'."$""$$%1%&&v''''L(Z(v((((((z))))))&*B*H*`*x******$,&,- -'-5-U-^-5.7.88G=x=uv{{  & x_#x#M$_$u$$''0+01134^5q588 ::;;F=G=I=M=O=V=c=d=x=qgNR*h_O>yqgNR*h_O>yqgNR*h_O>yqgNR*h_O>yqgNR*h_O>yqgNR*h_O>yqgNR*h_O>yqgNR*h_O>yqgNR*h_O>y Ray Gates?K |!@88X 88< 423=w=`@`:`x@`@Unknown Gz Times New Roman5Symbol3& z ArialQ Helvetica-BoldArial7 ArialMTM  Arial-BoldMTArialQ Arial-ItalicMTArialG5  hMS Mincho-3 fg7CenturyK1   MS Gothic-3 0000?5 z Courier New5& z!Tahoma pHhƳfC% "4 o% "4 o3!%),.:;?]}  0 2 3 !000 0 0 00000000000 =]acde$([\{  0 0 0000;[b2(=(=3AH??K # NBqgNR*h_O>y Ray GatesOh+'0 $ @ L Xdlt|# NB? NB東京電力株式会社t Normal.dot Ray Gates5y Microsoft Word 10.0@R\ @i9 J@:tM % "4՜.+,0 hp|   # o(=A # NB Title  !"#$%&'()*+,-./0123456789:;<=>?@ABCEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqstuvwxy{|}~Root Entry F1tM1TableD[WordDocument2SummaryInformation(rDocumentSummaryInformation8zCompObjj  FMicrosoft Word Document MSWordDocWord.Document.89q