DR 09-0322 - OPC: Types

[MURATA Makoto (FAMILY Given)]

Dear collleagues,

The proposed response contains

> However, we suspect that more important here is that the use of the word “type” be clarified in place 
> in specific instances of use the document, that simple extensions to definitions may not be the best 
> way to clarify the confusion.  If there is agreement that is necessary and valuable, we would like to 
> consider such an enhancement to the usability of the document. 

I extracted all occurrences of the word "type" from Part 2 using a KWIC
software tool that supports OOXML, and eliminated unambiguous 
occurrences using grep.

grep -v "ontent  Type" result.dat | grep -v "ontent  type" | grep -v "edia  type" 
| grep -v "xsi: type" | grep -v "elationship  type" | grep -v "\ Type" | grep -v "imple  type" 
| grep -v "omplex  type" | grep -v "data  type" | grep -v "media- type" | grep -v "<xsd:element" 
| grep -v "<xsd:attribute" | grep -v ":element" | grep -v ":attribute" | grep -v maxOccurs | grep -v "type ="

Here is the result.

nMatch=191
kwicOffset=40
match=295	29605	29771	4	l of the pieces of a document (or other  type  of content) into a single object.                                                	0	1	6	0	
match=308	31217	31221	4	                                    The  type  of content stored in the part  Re                                                	0	1	4	0	
match=386	38014	38088	4	"content type" \b  which identifies the  type  of content that is stored in the                                                 	0	1	4	0	
match=390	38644	38648	4	                                    The  type , subtype, and parameter attribute                                                	0	1	4	0	
match=392	38887	38953	4	e linear white space either between the  type  and subtype or between an attribu                                                	0	1	4	0	
match=426	45449	45645	4	ips XE "relationship" \b  represent the  type  of connection between a source pa                                                	0	1	4	0	
match=437	48343	48441	4	o Relationship elements are of the same  type . This comparison is conducted in                                                 	0	1	5	0	
match=483	50884	50961	4	 a valid XML identifier. [M1.26] The Id  type  is xsd:ID and it shall conform to                                                	0	1	3	0	
match=929	89535	89951	4	art and using a relationship with a new  type  to point from the Core Properties                                                	0	1	4	0	
match=2822	184157	184223	4	e linear white space either between the  type  and subtype or between an attribu                                                	0	1	4	0	



Cheers,
Makoto