priority-claim 

Priority-claim, IFD tags :
	080 = country;
	090 = doc-number;
	180 = kind-code (generated from kind in combination with linkage-type);
	100= date; 
Priority-claim,ST.30 tags :
	330 = country;
	310 = doc-number;
	A31 = kind-code;
	320 = date; 
Notes on Contents :
	When data-format = "original", ONLY the priority-number	
	DOCDB keeps record of very early publications; where possible these are grouped into families; in these instances :
		doc-number = suffixed by letter 'T';
		date = all zeroes;
		priority-linkage-type = 'T';
	DOCDB has reformatted PCT applications for reasons of standardisation, in these instances :
		country = country of filing;
		doc-number = numerical string, preceded by year indication;
		kind = 'W';
	Linkage type and active indicator serve EPO internal business needs :
		priority-linkage-type = 1 byte indication of priority relation, eg. '1' = "for continuation";
		priority-active-indicate = Y or N included in the priority picture that defines EPO simple patent family;
Attributes used :
	sequence = sequence as printed on the published document;
	data-format = "docdb" - standardised following the DOCDB standardisation rules -  then exchange of a full set of reference; 
	data-format=  "epodoc" - format as represented in espacenet, concatenated in "doc-number";
	data-format = "original" - as supplied by the provider - then exchange of "doc-number" only;
	NOTE THAT "sequence" restarts with every change of "data-format"
	priority claims in different formats but with identical sequence numbers cannot be guaranteed to be representations of one and the same entity

Element Information

Model

document-id+ , office-of-filing{0,1} , (priority-doc-requested | priority-doc-attached | priority-doc-from-library) , restore-rights{0,1} , priority-linkage-type{0,1} , priority-active-indicator{0,1}
Children: document-id, office-of-filing, priority-active-indicator, priority-doc-attached, priority-doc-from-library, priority-doc-requested, priority-linkage-type, restore-rights

Attributes

QName Type Fixed Default Use Inheritable Annotation
data-format xs:string optional
id xs:ID optional
kind restriction of xs:token required
sequence xs:string optional
status xs:string optional

Used By

Complex Types ops:any-reference-listType, ops:any-referenceType, ops:any-referenceType-with-biblio, ops:patent-familyType, priority-claimsType
Elements ops:biblio-retrieval, ops:family-member

Source 

<xs:element name="priority-claim" type="priority-claimType">
  <xs:annotation>
    <xs:documentation>Priority-claim, IFD tags : 080 = country; 090 = doc-number; 180 = kind-code (generated from kind in combination with linkage-type); 100= date; Priority-claim,ST.30 tags : 330 = country; 310 = doc-number; A31 = kind-code; 320 = date; Notes on Contents : When data-format = "original", ONLY the priority-number DOCDB keeps record of very early publications; where possible these are grouped into families; in these instances : doc-number = suffixed by letter 'T'; date = all zeroes; priority-linkage-type = 'T'; DOCDB has reformatted PCT applications for reasons of standardisation, in these instances : country = country of filing; doc-number = numerical string, preceded by year indication; kind = 'W'; Linkage type and active indicator serve EPO internal business needs : priority-linkage-type = 1 byte indication of priority relation, eg. '1' = "for continuation"; priority-active-indicate = Y or N included in the priority picture that defines EPO simple patent family; Attributes used : sequence = sequence as printed on the published document; data-format = "docdb" - standardised following the DOCDB standardisation rules - then exchange of a full set of reference; data-format= "epodoc" - format as represented in espacenet, concatenated in "doc-number"; data-format = "original" - as supplied by the provider - then exchange of "doc-number" only; NOTE THAT "sequence" restarts with every change of "data-format" priority claims in different formats but with identical sequence numbers cannot be guaranteed to be representations of one and the same entity</xs:documentation>
  </xs:annotation>
</xs:element>

Sample