publication-reference

Publication-reference, IFD tags
	010 = country
	030 = doc-number
	020 = kind
	060 = date
Publication-reference, ST.30 tags
	190 = country
	110 = doc-number
	221 = kind
	A40 = date
Notes on Contents :
	Defined  "repeatable" 
		to be able to cater for multiple formats in the future, e.g. data-format="docdb" and data-format="epodoc". 
	DOCDB keeps record of very early publications, in those instances 
		date = all zeroes
	DOCDB exchanges "withdrawn" publications, in those instances
		date = not supplied
	DE utility models: publication-date = "Bekanntmachunstag" 
	"Modifications of full specification/first page", eg. A8
		multiple publication stages per publication-id possible
		extending key with publication-date provides unique and unambiguous reference		
Attributes used
	data-format="docdb", standardised following DOCDB prime standardisation rules
Provisions for future use :
	defined  "repeatable" to be able to exchange more than one representation, eg.
	data-format="epodoc" etc.

Element Information

Model

Children: document-id

Attributes

QName Type Fixed Default Use Inheritable Annotation
id xs:ID optional

Used By

Source

<xs:element name="publication-reference" type="publication-referenceType">
  <xs:annotation>
    <xs:documentation>Publication-reference, IFD tags 010 = country 030 = doc-number 020 = kind 060 = date Publication-reference, ST.30 tags 190 = country 110 = doc-number 221 = kind A40 = date Notes on Contents : Defined "repeatable" to be able to cater for multiple formats in the future, e.g. data-format="docdb" and data-format="epodoc". DOCDB keeps record of very early publications, in those instances date = all zeroes DOCDB exchanges "withdrawn" publications, in those instances date = not supplied DE utility models: publication-date = "Bekanntmachunstag" "Modifications of full specification/first page", eg. A8 multiple publication stages per publication-id possible extending key with publication-date provides unique and unambiguous reference Attributes used data-format="docdb", standardised following DOCDB prime standardisation rules Provisions for future use : defined "repeatable" to be able to exchange more than one representation, eg. data-format="epodoc" etc.</xs:documentation>
  </xs:annotation>
</xs:element>

Sample

< bibliographic-data xmlns = "http://www.epo.org/exchange" >

< publication-reference>

< document-id document-id-type = "docdb" >

< country>

KR

</ country>

< doc-number>

20100130646

</ doc-number>

< kind>

A

</ kind>

< date>

20101213

</ date>

</ document-id>

< document-id document-id-type = "epodoc" >

< doc-number>

KR20100130646

</ doc-number>

< date>

20101213

</ date>