ÿþ<!--This entity may be identified by the PUBLIC identifier: ******************************************************************************** PUBLIC "-//EPO//EP PATENT DOCUMENT 1.3//EN" "ep-patent-document-v1-3.dtd" ******************************************************************************** ******************************************************************************** * Based upon ST.36 xx-patent-document v1.0 2005 March ******************************************************************************** * Based upon PUBLIC "-//WIPO//XX PATENT DOCUMENT 1.0//EN" "xx-patent-document-v1-0.dtd" ******************************************************************************** * Based upon http://www.wipo.int/scit/en/standards/st36-xml-dtd.htm ******************************************************************************** * CONTACTS ********************************* for all general questions: epoline@epo.org The Hague: Paul Brewin - pbrewin@epo.org Vienna: Ute Koplin - ukoplin@epo.org Keri Rowles - krowles@epo.org ********************************* * NOTES ********************************* - This DTD is intended for the EPO's publication contractors for: - the production of EP A and B Patent Documents, - EP MIMOSA (the latter may need some modifications to this DTD) - It is not intended for any other purpose than the above *** PCT ANNEX F Compliance - For details about PCT Annex F and about all Annex F DTDs see: http://pcteasy.wipo.int/efiling_standards/EFPage.htm - This ST.36 based EP DTD has one-to-one compliance with ELEMENTS in the following areas: - doc-page, abstract, description, claims and drawings are the same as those found in the (future) application-body.dtd version 1.4 (and the current 1.3 with a few minor exceptions). with the following exceptions which will need to be Annex F to be changed: * added sup and sub elements to b i and u - (PFC pending) * added o - overscore to several elements - (PFC pending) * added formula-text element to chemistry and maths - (PFC pending) * added value graph to attribute img-content of img (PFC pending) * several changes made to citations, nplcit, book, etc (PFCpending) - see below but EPO only user so far of these elements - another exception is the use of <doc-page> which has been removed from most higher elements as not required by the EPO publication system - the one exception is the search report; it has also been left for the whole document. - Certain areas need to be "cleaned up" by the Trilateral/WIPO XML Work Group - note that ST.36 allows different syntax and therefore, for example, this DTD allows for multiple claims. - the search-report-data has a number of differences with the Annex F search-report-v1-3.dtd which needs updating and corrections (PFC). - for bibliographic data and SDOBI there is no direct equivalent in Annex F but many elements are re-used, eg. address data. The EPO will use SDOBI in this DTD. - other notes and details can be found within the DTD *** the above notes refer to Annex F versions and xx-patent-document versions which do NOT include the recommended PFCs noted; it is hoped that these will be agreed during 2006/7 for a new release of the above by 2007. *** EPO PatXML authoring software: should be compliant with this DTD as far as the abstract, description, claims and drawings, with the exceptions above, are concerned but not all elements are used so far and probably never will be. PatXML to upgrade to this DTD (when Annex F updated also) and PatXML for examiners should update also. - This DTD will be maintained and updated only by the EPO; the DTD updates and further documentation will be posted on the epoline.org site. - The DTD has been validated with XML Spy and Near&Far etc. *** IMPORTANT for the EP BULLETIN - the EBD files (see http://ebd2.epoline.org/jsp/index.jsp) use the ep-bulletin dtd - the SDOBI section in this DTD MUST match the same section in the ep-bulletin dtd and vice versa *** IMPORTANT: Note to EPO editors: do NOT modify this file using Near & Far, XMLSpy etc, use a text editor (eg Textpad) to preserve elements in the order of this DTD. Then save as a PC and UTF-8 file. ANY CHANGES: notify epoline, epidos and all contractors etc. Change management documentation needs to be produced ?** ****************************************************************************************************** * REVISION HISTORY FOR VERSION 1.2 Note: this data indicates all changes made to version 1.1 in order to create 1.2 ****************************************************************************************************** ********************************* * DATE: 2006-09-19 v. 1.2 PB - Changes to the Inter. Search Report etc based on changes proposed by the PCT in PCT/EF/PFC 06/001 (none of this is in prod. yet at EPO): Change: <!ATTLIST annex-c-bis annex-c-tables (1 | 2 ) #REQUIRED > TO: <!ATTLIST annex-c-bis e-tables-missing (yes | no ) #REQUIRED format-error (yes | no ) #REQUIRED > <!ATTLIST sequence-listing-material-type material-type (1 | 2) #IMPLIED > TO: <!ATTLIST sequence-listing-material-type sequence-listing (yes | no ) 'yes' table (yes | no ) #REQUIRED > <!ATTLIST sequence-listing-material-format material-format (1 | 2) #IMPLIED > TO: <!ATTLIST sequence-listing-material-format paper (yes | no ) #REQUIRED electronic (yes | no ) 'yes' > <!ATTLIST sequence-listing-filing-time time-of-filing (1 | 2 | 3 | 4) #IMPLIED > TO: <!ATTLIST sequence-listing-filing-time in-application (yes | no ) #REQUIRED together-with-application (yes | no ) #REQUIRED furnished-for-search (yes | no ) #REQUIRED > ********************************* * DATE: 2007-07-04 v. 1.2 PB - Changes for EPC2000 PHASE 2 This DTD contains ONLY changes required for PHASE 2 of EPC2000 Phase 3 changes are commented out and MAY change. Phase 2 changes are: - added sequence attribute to root element - added B075EP + sub-tags - added B090EP + sub-tags - added B690 + sub-tags - added natural language equivalent names BUT these have NOT been included in the bibliographic-data tag set yet (we don not need them in publication) - comments etc improved for SR data (NO tag changes) ********************************* * DATE: 2007-12-11 v. 1.2 PB - Changes for EPC2000 PHASE 2 - removed B690 + sub-tags on advice of WIPO - we keep the version (1.2) - B0755EP - list of attribute values - small changes to comments eg Rule numbers ****************************************************************************************************** * REVISION HISTORY FOR VERSION 1.3 Note: this data indicates all changes made to version 1.2 in order to create 1.3 ****************************************************************************************************** * DATE: 2007-12-17 v. 1.3 PB - Added EPC 2000 PHASE 3 a) and b) data: - added <!ELEMENT B012EP (B0120EP+) > - changed <!ELEMENT B0900EP (B091EP+, B092EP?,B093EP?)> - added <!ELEMENT B453EP (B4530EP+) > Search report changes: - Updated Search Report comments and processing due to EPC 2000 - Improved Search Report layout comments ******************************** * DATE: 2008-02-12 v1.3 PB - changed <!ELEMENT B012EP (B0120EP+) > - added <B270> - corrected <B453EP> model Search report changes: - changed incomplete-search to srep-incomplete-search for consistency (PFC to be agreed) - added srep-declaration to handle better EPO Rule 63 Declaration cases (PFC to be agreed) ******************************************************************************* * SECTION I - DECLARATION, ENT. REFs, etc ******************************************************************************* --> <!ENTITY % name_group "((name | (prefix?,(last-name | orgname),first-name?, middle-name?,suffix?,iid?,role?,orgname?,department?,synonym*)), registered-number?)" > <!ENTITY % address_group "((address-1?,address-2?,address-3?,mailcode?,pobox?,room?, address-floor?,building?,street?,city?,county?,state?,postcode?, country) | text)" > <!ENTITY % MathExpression "(mi | mn | mo | mtext | ms | mspace | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction | ci | csymbol | cn | integers | reals | rationals | naturalnumbers | complexes | primes | exponentiale | imaginaryi | notanumber | true | false | emptyset | pi | eulergamma | infinity | apply | fn | lambda | reln | interval | list | matrix | matrixrow | set | vector | piecewise | semantics | declare)*" > <!ENTITY % PresExpression "(mi | mn | mo | mtext | ms | mspace | mprescripts | none | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction | ci | csymbol | cn | integers | reals | rationals | naturalnumbers | complexes | primes | exponentiale | imaginaryi | notanumber | true | false | emptyset | pi | eulergamma | infinity | apply | fn | lambda | reln | interval | list | matrix | matrixrow | set | vector | piecewise | semantics | declare)*" > <!ENTITY % twoPresExpression "(mi | mn | mo | mtext | ms | mspace | mprescripts | none | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction | ci | csymbol | cn | integers | reals | rationals | naturalnumbers | complexes | primes | exponentiale | imaginaryi | notanumber | true | false | emptyset | pi | eulergamma | infinity | apply | fn | lambda | reln | interval | list | matrix | matrixrow | set | vector | piecewise | semantics | declare)*" > <!ENTITY % threePresExpression "(mi | mn | mo | mtext | ms | mspace | mprescripts | none | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction | ci | csymbol | cn | integers | reals | rationals | naturalnumbers | complexes | primes | exponentiale | imaginaryi | notanumber | true | false | emptyset | pi | eulergamma | infinity | apply | fn | lambda | reln | interval | list | matrix | matrixrow | set | vector | piecewise | semantics | declare)*" > <!ENTITY % prscrPresExpression "(mi | mn | mo | mtext | ms | mspace | mprescripts | none | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction | ci | csymbol | cn | integers | reals | rationals | naturalnumbers | complexes | primes | exponentiale | imaginaryi | notanumber | true | false | emptyset | pi | eulergamma | infinity | apply | fn | lambda | reln | interval | list | matrix | matrixrow | set | vector | piecewise | semantics | declare)*" > <!ENTITY % mtrPresExpression "(mi | mn | mo | mtext | ms | mspace | mprescripts | none | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction | ci | csymbol | cn | integers | reals | rationals | naturalnumbers | complexes | primes | exponentiale | imaginaryi | notanumber | true | false | emptyset | pi | eulergamma | infinity | apply | fn | lambda | reln | interval | list | matrix | matrixrow | set | vector | piecewise | semantics | declare)*" > <!ENTITY % mtdPresExpression "(mi | mn | mo | mtext | ms | mspace | mprescripts | none | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction | ci | csymbol | cn | integers | reals | rationals | naturalnumbers | complexes | primes | exponentiale | imaginaryi | notanumber | true | false | emptyset | pi | eulergamma | infinity | apply | fn | lambda | reln | interval | list | matrix | matrixrow | set | vector | piecewise | semantics | declare)*" > <!--............................................................. Recursive definition for content of expressions. Include presentation constructs at lowest level so presentation layout schemata hold presentation or content elements. Include content constructs at lowest level so content elements hold PCDATA or presentation elements at leaf level (for permitted substitutable elements in context) --> <!ENTITY % ContentExpression "(csymbol | ci | cn | apply | reln | lambda | condition | declare | sep | semantics | annotation | annotation-xml | integers | reals | rationals | naturalnumbers | complexes | primes | exponentiale | imaginaryi | notanumber | true | false | emptyset | pi | eulergamma | infinity | interval | list | matrix | matrixrow | set | vector | piecewise | lowlimit | uplimit | bvar | degree | logbase | momentabout | domainofapplication | inverse | ident | domain | codomain | image | abs | conjugate | exp | factorial | arg | real | imaginary | floor | ceiling | not | ln | sin | cos | tan | sec | csc | cot | sinh | cosh | tanh | sech | csch | coth | arcsin | arccos | arctan | arccosh | arccot | arccoth | arccsc | arccsch | arcsec | arcsech | arcsinh | arctanh | determinant | transpose | card | quotient | divide | power | rem | implies | vectorproduct | scalarproduct | outerproduct | setdiff | fn | compose | plus | times | max | min | gcd | lcm | and | or | xor | union | intersect | cartesianproduct | mean | sdev | variance | median | mode | selector | root | minus | log | int | diff | partialdiff | divergence | grad | curl | laplacian | sum | product | limit | moment | exists | forall | neq | factorof | in | notin | notsubset | notprsubset | tendsto | eq | leq | lt | geq | gt | equivalent | approx | subset | prsubset | mi | mn | mo | mtext | ms | mspace | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction)*" > <!ENTITY % semanticsContentExpression "(csymbol | ci | cn | apply | reln | lambda | condition | declare | sep | semantics | annotation | annotation-xml | integers | reals | rationals | naturalnumbers | complexes | primes | exponentiale | imaginaryi | notanumber | true | false | emptyset | pi | eulergamma | infinity | interval | list | matrix | matrixrow | set | vector | piecewise | lowlimit | uplimit | bvar | degree | logbase | momentabout | domainofapplication | inverse | ident | domain | codomain | image | abs | conjugate | exp | factorial | arg | real | imaginary | floor | ceiling | not | ln | sin | cos | tan | sec | csc | cot | sinh | cosh | tanh | sech | csch | coth | arcsin | arccos | arctan | arccosh | arccot | arccoth | arccsc | arccsch | arcsec | arcsech | arcsinh | arctanh | determinant | transpose | card | quotient | divide | power | rem | implies | vectorproduct | scalarproduct | outerproduct | setdiff | fn | compose | plus | times | max | min | gcd | lcm | and | or | xor | union | intersect | cartesianproduct | mean | sdev | variance | median | mode | selector | root | minus | log | int | diff | partialdiff | divergence | grad | curl | laplacian | sum | product | limit | moment | exists | forall | neq | factorof | in | notin | notsubset | notprsubset | tendsto | eq | leq | lt | geq | gt | equivalent | approx | subset | prsubset | mi | mn | mo | mtext | ms | mspace | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction)*" > <!-- ******************************************************************************* * SECTION II - DTD ******************************************************************************* ep-patent-document EPO usage: Required attribute usage IN THIS ORDER is: - id must follow these examples: id="EP12345678NWA1", "EP12345678A9W1": country, appl.no., kind - file: this can have TWO values depending on the document instance: 1. for the EBD it will simply be the plain application number: file="04102952.1" see ep-bulletin.dtd 2. for the full patent document in the PRB and the RTB the value will need to be changed to file="EP04102952NWA1.xml" in route element ep-patent-document BUT we may change this to file naming conventions mentioned in ST.36. - lang attribute value must be in lower case, eg. en, fr, de - country code attribute values must be in upper case (WIPO ST.3) , eg. DE, ES, FR, US, WO - doc-number - the publication number - the kind attribute value must be in upper case, eg. A1, B1 - correction-code (e.g. W1) must ONLY be populated in the case of a correction, in upper case - date-publ - the publication date, e.g. date-publ="20050105" - sequence - for EPC2000 and, for now, ONLY for B3 docs. ="1" - status - for the EPO this will be either n (new), c (corrected), r (replacement) - dtd-version, e.g. dtd-version="ep-patent-document-v1-3" ATTRIBUTES NOT USED: - date-produced - file-reference-id (may be in PatXML files) and will be the applicant's reference - not required by EPO Having all these attributes at this level helps processing, stylesheet set up, etc. NOTES: - we do NOT use the <bibliographic-data> element and elements; we use <SDOBI> - it is unlikely we will use <table-external-doc> (USPTO element) - because of various usage in the EPO we have CHANGED the dtd to make description and claims non-mandatory; for example A3 files have only bibliographic data and abstract. The contractor may change this to required etc for more validation, eg. an A1 document MUST have abstract, description, claims and search report. We have also changed the order of elements. So we have: - SDOBI (created by the EPO, must not be changed) - abstract (created by the applicant and/or contractor) - description (created by the applicant and/or contractor) - claims (created by the applicant and/or contractor) - amended-claims (created by the applicant and/or contractor) - amended-claims-statement (created by the applicant and/or contractor) - drawings (created by the applicant and/or contractor) - search-report-data (created by the EPO) - We have eliminated <doc-page> as an alternative to some elements Example: <ep-patent-document id="EP07450020A1" file="EP07450020NWA1.xml" lang="de" country="EP" doc-number="1878631" kind="A1" date-publ="20080116" status="n" dtd-version="ep-patent-document-v1-3"> --> <!ELEMENT ep-patent-document (doc-page+ | ((bibliographic-data | SDOBI),abstract*, description?,claims*,amended-claims*,amended-claims-statement*, drawings?,search-report-data*, ep-reference-list?)) > <!ATTLIST ep-patent-document id ID #IMPLIED file CDATA #IMPLIED lang CDATA #REQUIRED country CDATA #REQUIRED doc-number CDATA #IMPLIED kind CDATA #IMPLIED correction-code CDATA #IMPLIED date-publ CDATA #IMPLIED status CDATA #IMPLIED sequence CDATA #IMPLIED dtd-version CDATA #IMPLIED date-produced CDATA #IMPLIED file-reference-id CDATA #IMPLIED > <!-- ********************************* DOC-PAGE ********************************* doc-page - DOCument or PAGE This is primarily to be used when data for the whole or major sections of an application are in image format OR other formats such as pdf. Page range attributes are given when required pp - page range ppf - first page ppl - last page (for pdf). The 'img' may also be used for complete pages, e.g. in drawings EPO Required usage: - in the EP publication process this tag is only likely to be used for the search report; then we use: - id="srep0001" - file="srep0001.tif" - in all other cases use: - id="docp0001" - file="docp0001.tif" ** Note: ocr attribute added NOT ANNEX F compatible - for OCR project? CHECK Example: <search-report-data id="srep" srep-office="EP" date-produced="20050308"> <doc-page id="srep0001" file="srep0001.tif" he="231" wi="159" type="tif" /> <doc-page id="srep0002" file="srep0002.tif" he="231" wi="159" type="tif"/> </search-report-data> --> <!ELEMENT doc-page EMPTY > <!ATTLIST doc-page id ID #IMPLIED file CDATA #REQUIRED wi CDATA #REQUIRED he CDATA #REQUIRED type (jpg | pdf | tif) #REQUIRED alt CDATA #IMPLIED pp CDATA #IMPLIED ppf CDATA #IMPLIED ppl CDATA #IMPLIED ocr CDATA #IMPLIED color (color | bw) #IMPLIED orientation (portrait | landscape) "portrait" > <!-- ******************************************************************************* * SDOBI section extracted to ep-bulletin dtd from next line on ******************************************************************************* ********************************* SDOBI - BIBLIOGRAPHY SUB-DOCUMENT ********************************* The elements under <SDOBI> are for use mainly by the EPO and for backward compatibility. These tags are used for the EP BULLETIN and EBD data on the epoline website; see: http://ebd2.epoline.org/jsp/index.jsp and for title page data These tags correspond very closely to the ST.32 SGML tags. Of course, now it is XML all tags now must have an end tag (unlike SGML). Floating tags are not allowed in XML and therefore <BCHG> and <ECHG> and <BR> do not appear in <SDOBI>. <BR> has been replaced by UTF-8 character <BCHG> and <ECHG> have been replaced - in bibliographic data ONLY - and for EP purposes by ep-chg-info and (ep-chg+) and attribute values - see below Where an id attribute has been added to a B tag this is used for the change reference. ******************************************************************************* * B TAG NOTES ******************************************************************************* - A non exhaustive list of changes to the "B-tags" with respect to ST.32 and/or or eppat.dtd(Version 1, Release 6, Level 0) follows. - Note: NOT all tags in this DTD are used in the EP Bulletin/EBD data; the others are kept in for compatibility with ep-patent-document.dtd - All tags that ARE in the EBD file are indicated as: * EBD ** New B-tags in ST.36 and not in ST.32: ELEMENT B151 - Correction code elements, modified old EP tags ELEMENT B152 now ICE elements ELEMENT B153 ELEMENT B154 ELEMENT B1541 ELEMENT B1542 ELEMENT B155 ELEMENT B1551 ELEMENT B1552 ELEMENT B211EP - Application number in EPOQUE format ELEMENT B311EP - Priority application number in EPOQUE format ELEMENT B510EP - IPC Reform ELEMENT B542EP - Title of invention in original language code. ELEMENT B599EP (in ST.32) ELEMENT B721EP - Name with all original language characters ** Old ST.32 B-tags removed from ST.36: ELEMENT B528US ELEMENT B578US ELEMENT B583US ELEMENT B584US ELEMENT B712US ELEMENT B732US ELEMENT B748US ELEMENT bchg ELEMENT echg ELEMENT jptags ELEMENT ustags ELEMENT xxtags ** Changed ST.36 model: - B009EP added <text> element for multiple language text - B725EP added <text> element for multiple language text - B561 and B562 (citation) models changed to simply include <text> we will include patcit and nplcit when/if possible. This does NOT effect current practice. ** EPC2000 additions - see above --> <!ELEMENT SDOBI (B000?,B100,B200?,B300?,B400?,B500?,B600?,B700?,B800?,B900?) > <!ATTLIST SDOBI lang CDATA #IMPLIED > <!--* EBD B000 ********************************* B000 - OFFICE SPECIFIC DATA ********************************* --> <!ELEMENT B000 (eptags?) > <!-- ********************************* EPTAGS ********************************* The following tags are for the specific use of the EPO - and may be changed at the discretion of the EPO. --> <!ELEMENT eptags (B001EP?,B002EP?,B003EP?,B004EP?,B005EP?,B006EP?,B007EP?,B008EP?, B009EP?,B010EP?,B012EP?,B015EP?,B020EP?,B021EP?,B030EP?, B050EP?,B053EP*,B060EP?,B061EP?,B070EP?,B075EP?,B078EP?,B080EP?, B090EP?) > <!--* EBD B001EP Select. mask for states involved (lists all designated states for that patent) Example: <B001EP>ATBECHDEDKESFRGBGRITLILUNLSEMCPTIESILTLVFIROMKCYALTRBGCZEEHUPLSK..HR............</B001EP> --> <!ELEMENT B001EP (#PCDATA) > <!--* EBD B002EP ********************************* * B002EP - CHANGE INFORMATION ********************************* NOTE: Marking changes in the description, claims etc will be different--> <!ELEMENT B002EP (ep-chg-info) > <!ATTLIST B002EP id ID #IMPLIED > <!ELEMENT ep-chg-info (ep-chg+) > <!--ep-chg: Reference to elements where data has changed - idref = reference to the id ep-chg value - btag = the actual tag where data has changed eg. B240 - date = date of change - status = type of change here: n = new data, inserted data r = replacement data d = deleted data Example: <B002EP> <ep-chg-info> <ep-chg idref="ep-chg0001" btag="B542" date="20041118" status="r"/> <ep-chg idref="ep-chg0002" btag="B542" date="20041118" status="r"/> <ep-chg idref="ep-chg0003" btag="B542" date="20041118" status="r"/> </ep-chg-info> </B002EP> In this example the title has been replaced in the three languages: <B540> <B541>de</B541> <B542 id="ep-chg0001">Verfahren zum Aufschäumen eines metallischen Werkstoffes</B542> <B541>en</B541> <B542 id="ep-chg0002">Process for foaming metallic articles</B542> <B541>fr</B541> <B542 id="ep-chg0003">Procédé pour le moussage d'articles métalliques</B542> </B540> ep-chg is recursive to allow for history of changes - changes to changes - possibly to be used in the EP register; recursion will not be used in the EBD. --> <!ELEMENT ep-chg (ep-chg*) > <!ATTLIST ep-chg idref IDREF #REQUIRED btag CDATA #REQUIRED date CDATA #REQUIRED status CDATA #REQUIRED > <!--*** End *** * EBD B003EP This field contains an '*' (asterisk) for the EURO-PCT applications for which no A-document has been published by the EPO. --> <!ELEMENT B003EP (#PCDATA) > <!--* EBD B004EP Re-establishments of rights indicator It contains the code of the decision after a request for re-establishment of rights. The values used by the EPO are: 2 : Request not accepted 3 : Request accepted Note: Used together with <B238>. --> <!ELEMENT B004EP (#PCDATA) > <!ATTLIST B004EP id ID #IMPLIED > <!--* EBD B005EP Producer / Printer id. --> <!ELEMENT B005EP (#PCDATA) > <!--* EBD B006EP Indicator for international application This tag identifies the type of International applications. The values used by the EPO are: - 9120 : Entering the European phase - 9121 : Not Entering the European phase --> <!ELEMENT B006EP (#PCDATA) > <!ATTLIST B006EP id ID #IMPLIED > <!--* EBD B007EP Reserved for EPO use: for the internal EPO program version, eg. DIM360 (Ver 1.5 26 Jan 2004) - 1100000/0 --> <!ELEMENT B007EP (#PCDATA) > <!--* EBD B008EP Small change indicator This tag identifies "small changes" which area actually not printed in the EPO Bulletin such as removing the country code in the postcode. Currently and when present it contains the value 8. --> <!ELEMENT B008EP (#PCDATA) > <!--* EBD B009EP Text from B725EP tag in the three EPO official languages" This tag will contain the text stored in tag <B725EP> in EPO official languages ie. German, English and French to print in the EPO Bulletin. See Tag <B720>. Example: <B009EP> <text>Die Erfinder haben auf ihre Nennung verzichtet</text> <text>The inventors have agreed to waive their entitlement to designation</text> <text>Les inventeurs ont renoncé leur désignation</text> </B009EP> --> <!ELEMENT B009EP (text+) > <!--If no structure is possible, enter text (without markup) <!ELEMENT text (#PCDATA) > --> <!--* EBD B010EP Other rights and legal means of execution --> <!ELEMENT B010EP (B011EP+) > <!ATTLIST B010EP id ID #IMPLIED > <!--* EBD B011EP Serial number date and states --> <!ELEMENT B011EP (date,dnum,ctry*) > <!-- **** EPC2000 - PHASE 3 a) **** Grouping tag for NEW REVOCATION PROCEDURE (ART 105a) REVR These memo's used on request for revocation from proprietor This new procedure caters for revocation from the proprietor outside of the opposition procedure. ep-revocation-procedures --> <!ELEMENT B012EP (B0120EP+) > <!-- Repeatable tag for procedure info. ep-revocation-procedure --> <!ELEMENT B0120EP (B0121EP?,B0122EP?,B0123EP?,B0124EP?,B0125EP?,B0126EP?, B0127EP?)> <!-- REVR01 Revocation request filed on (date) ep-revocation-procedure-date --> <!ELEMENT B0121EP (date) > <!-- REVR02 Kind of revocation 01 = filed during opposition period 02 = filed after opposition period ep-revocation-procedure-kind --> <!ELEMENT B0122EP (#PCDATA) > <!-- REVR03 Decision on revocation request 01 = Admissible 02 = Inadmissible 03 = Deemed not filed ep-revocation-procedure-decision --> <!ELEMENT B0123EP (#PCDATA) > <!ATTLIST B0123EP id ID #IMPLIED > <!-- REVR04 Paid on (date) ep-revocation-procedure-paid --> <!ELEMENT B0124EP (date) > <!-- REVR05 Language ep-revocation-procedure-lang --> <!ELEMENT B0125EP (#PCDATA) > <!-- REVR06 Date of dispatch of the decision ep-revocation-date-dispatch --> <!ELEMENT B0126EP (date) > <!-- REVR07 Date of legal effect ep-revocation-legal-effect --> <!ELEMENT B0127EP (date) > <!ATTLIST B0127EP id ID #IMPLIED > <!--* EBD B015EP Number of documents to be printed --> <!ELEMENT B015EP (#PCDATA) > <!--B020EP Biblio rec. creation --> <!ELEMENT B020EP (#PCDATA) > <!--B021EP Biblio. rec. correction --> <!ELEMENT B021EP (#PCDATA) > <!--B030EP Legal status data --> <!ELEMENT B030EP (#PCDATA) > <!--* EBD B050EP Free text data Example: <B050EP> <B051EP>de</B051EP> <B052EP>Derzeit sind die WIPO-Publikationsdaten A3 nicht verfügbar.</B052EP> <B051EP>en</B051EP> <B052EP>WIPO A3 publication data is not currently available.</B052EP> <B051EP>fr</B051EP> <B052EP>L'OMPI données de publication A3 ne sont pas actuellement disponibles.</B052EP> </B050EP> --> <!ELEMENT B050EP (B051EP,B052EP)+ > <!ATTLIST B050EP id ID #IMPLIED > <!--* EBD B051EP Language --> <!ELEMENT B051EP (#PCDATA) > <!--* EBD B052EP Free text --> <!ELEMENT B052EP (#PCDATA) > <!--* EBD B053EP Free text remarks. Example: <B053EP>This application was filed on 28 - 02 - 2002 as a divisional application to the application mentioned under INID code 62.</B053EP> --> <!ELEMENT B053EP (#PCDATA) > <!--B060EP Check data --> <!ELEMENT B060EP (#PCDATA) > <!--B061EP Data relating to fees --> <!ELEMENT B061EP (#PCDATA) > <!--* EBD B070EP B publication technical field (subsequently filed technical information) Example: <B070EP>The file contains technical information submitted after the application was filed and not included in this specification</B070EP> --> <!ELEMENT B070EP (#PCDATA) > <!-- ** EPC2000 - Phase 2 Group tag for (possible) multiple: PETITION FOR REVIEW Description: New procedure enabling any party to appeal proceedings adversely affected by the decision of the Board of Appeal to file a petition for review of the decision by the Enlarged Board of Appeal (EBA) ep-petition-reviews--> <!ELEMENT B075EP (B0750EP+) > <!-- ** EPC2000 - Phase 2 Repetitive grouping tag for petitons EPASYS: PREV01 Petition for review number (As we can have multiple petitions for review) Comprises a unique number for a given year. Eg R0001/08 ep-petition-review--> <!ELEMENT B0750EP (B0751EP?, B0752EP?, B0753EP?,B0755EP?,B0756EP?)> <!ATTLIST B0750EP id ID #IMPLIED review-number CDATA #REQUIRED> <!-- ** EPC2000 - Phase 2 REFN04 and NOAP0R ep-petition-review-appeal-number --> <!ELEMENT B0751EP (#PCDATA)> <!-- ** EPC2000 - Phase 2 PREV03 Date of notice of petition (May be included at a later date) ep-petition-review-date--> <!ELEMENT B0753EP (date) > <!-- ** EPC2000 - Phase 2 PREV02 Petitioner code Can contain values: OPnn, APPR from EPASYS ep-petition-review-petitioner-code --> <!ELEMENT B0752EP (#PCDATA)> <!-- ** EPC2000 - Phase 2 PREV05 Date of Decision ep-petition-review-decision-date--> <!ELEMENT B0755EP (date) > <!-- ** EPC2000 - Phase 2 PREV06 Kind of decision : R01 to R12 Board with 3 Members R01:Petition for review obviously inadmissible (not deemed to be filed) or simultaneously obviously inadmissible and obviously unsubstantiated. R02: Petition for review obviously unsubstantiated only. [R03: free] Board with 5 Members R04: Petition for review inadmissible. R05: Rejection of the petition for review. R06: Petition for review allowed and re-opening of the Appeal Procedure with total refund of the fee for the petition for review. R07: Petition for review allowed and re-opening of the Appeal Procedure with partial refund of the fee for the petition for review. [R08: free] Board with 3 or 5 Members R09: Withdrawal of the petition for review. R10: Petition for review deemed to be withdrawn. R11: other kind of disposal. [R12: free] ep-petition-review-kind--> <!ELEMENT B0756EP (#PCDATA)> <!--* EBD B078EP Date of 'no oppo. filed' --> <!ELEMENT B078EP (date) > <!ATTLIST B078EP id ID #IMPLIED > <!--* EBD B080EP Public notification Example: <B080EP> <B081EP>1</B081EP> <B082EP><snm>Amato Martinez Garza, Luis Alejandro</snm> <iid>04469850</iid> <adr><str>Fernando Montes de Oca 44</str> <city>Colonia Condesa D.F. 06140</city> <ctry>MX</ctry></adr> </B082EP> <B083EP>NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 69(1) EPC</B083EP> </B080EP> --> <!ELEMENT B080EP (B081EP,B082EP,B083EP?) > <!ATTLIST B080EP id ID #IMPLIED > <!--* EBD B081EP Inspection place Code Meaning 1 The Hague 2 Munich 3 Berlin --> <!ELEMENT B081EP (#PCDATA) > <!--* EBD B082EP EPO code relation --> <!ELEMENT B082EP (ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*,adr?, dtxt*,rctry?,nctry?) > <!--* EBD B083EP Free text --> <!ELEMENT B083EP (#PCDATA) > <!-- ** EPC2000 - PHASE 2 and 3 LIMITATION PROCEDURE Grouping tag for different combined events ep-limitation-procedures --> <!ELEMENT B090EP (B0900EP+) > <!--** EPC2000 - PHASE 2 Grouping tag for different events with limitation sequence number ="1" ep-limitation-procedure --> <!ELEMENT B0900EP (B091EP+, B092EP?,B093EP?)> <!ATTLIST B0900EP limitation-sequence CDATA #REQUIRED id ID #IMPLIED lang CDATA #IMPLIED begin-date CDATA #IMPLIED end-date CDATA #IMPLIED > <!-- ** EPC2000 - PHASE 2 LIMP01 Date of filing <B0911EP><date> LIMP02 Limitation kind (01,02) <B0912EP> LIMP03 Decision code (01- 05) <B0913EP><text> LIMP04 Date of payment <B0914EP><date> ep-limitation-filing --> <!ELEMENT B091EP (B0911EP,B0912EP?,B0913EP?,B0914EP?) > <!ATTLIST B091EP id ID #IMPLIED > <!--LIMP01 Filed on (date) ep-limitation-filing-date--> <!ELEMENT B0911EP (date) > <!-- ** EPC2000 - Phase 2 LIMP02 Limitation kind: 01 = filed during opposition period (9 months) 02 = filed after opposition period (9 months) ep-limitation-kind--> <!ELEMENT B0912EP (#PCDATA) > <!-- ** EPC2000 - Phase 2 LIMP03 Decision code: 01 = admissible 02 = inadmissible 03 = deemed not filed 04 = deemed not filed, opposition pending/filed 05 = withdrawn ep-limitation-filing-decision--> <!ELEMENT B0913EP (#PCDATA) > <!-- ** EPC2000 - Phase 2 LIMP04 Date of payment ep-limitation-payment-date--> <!ELEMENT B0914EP (date) > <!-- **** EPC2000 - PHASE 3 a) **** REJECTION OF LIMITATION FIELDS ep-limitation-rejection --> <!ELEMENT B092EP (B0921EP,B0922EP,B0923EP?,B0924EP?) > <!ATTLIST B092EP id ID #IMPLIED > <!-- REJL01 Kind of rejection: 01 = substantive refusal 02 = inadmissible for formal reasons (R.94) 03 = no (late) reply to subset report 04 = RALL (request allowed) requirements not fulfilled ep-limitation-rejection-kind --> <!ELEMENT B0921EP (#PCDATA) > <!-- REJL02 Decision dispatched on (date) ep-limitation-rejection-dispatch-date--> <!ELEMENT B0922EP (date) > <!-- REJL03 Legal effect on (date) ep-limitation-rejection-legal-date --> <!ELEMENT B0923EP (date) > <!-- ** NOT used REJL04 Legal effect bulletin issue number ep-limitation-rejection-bulletin-number --> <!ELEMENT B0924EP (bnum) > <!-- **** EPC2000 - PHASE 3 a) **** LIMITATION REQUEST ALLOWED ep-limitation-allowed --> <!ELEMENT B093EP (B0931EP,B0932EP?,B0933EP?) > <!ATTLIST B093EP id ID #IMPLIED > <!-- RALL01 Dispatched on (date) ep-limitation-allowed-dispatch-date --> <!ELEMENT B0931EP (date) > <!-- RALL02 Translation received on (date) ep-limitation-allowed-trans-date --> <!ELEMENT B0932EP (date) > <!-- RALL03 Full payment received on (date) ep-limitation-allowed-payment-date --> <!ELEMENT B0933EP (date) > <!--* EBD B100 ********************************* * B100 - DOCUMENT IDENTIFICATION ********************************* WIPO ST.9: INID: (10) Identification of the patent, SPC or patent document --> <!ELEMENT B100 (B110,B120?,B130,B131EP?,B132EP?,B133EP?,B140,B150?,B190,B195?) > <!--* EBD B110 WIPO ST.9: INID: (11) Number of the patent, SPC or patent document Doc. number REQUIRED EPO and PCT publication number --> <!ELEMENT B110 (#PCDATA) > <!ATTLIST B110 id ID #IMPLIED > <!--* EBD B120 WIPO ST.9: INID: (12) Plain language designation of the kind of document B120 used as a groupimg tag --> <!ELEMENT B120 (B121,B121EP?) > <!--* EBD B121 Plain lang. designation, Example: <B120><B121>EUROPEAN PATENT SPECIFICATION</B121></B120> --> <!ELEMENT B121 (#PCDATA) > <!--* EBD B121EP Any Descriptive text for B121 (EPO); this is normally as follows: Examples: <B120> <B121>EUROPEAN PATENT APPLICATION</B121> <B121EP>published in accordance with Art. 158(3) EPC</B121EP> </B120> or <B121>EUROPEAN PATENT APPLICATION</B121> <B121EP>published in accordance with Art. 153(4) EPC</B121EP> or <B121>NEW EUROPEAN PATENT SPECIFICATION</B121> <B121EP>After limitation procedure (B3-1)</B121EP> --> <!ELEMENT B121EP (#PCDATA) > <!--* EBD B130 WIPO ST.9: INID: (13) Kind-of-document code according to WIPO Standard ST.16 REQUIRED The values used by the EPO are: A1 Application published with search report A2 Application published without search report A3 Separate publication of the search report A8 Correction - reprint of the title page of an A-document A9 Correction - complete reprint of an A-document B1 Granted patent B2 Amended patent B8 Correction - reprint of the title page of a B-document B9 Correction - complete reprint of a B-document --> <!ELEMENT B130 (#PCDATA) > <!ATTLIST B130 id ID #IMPLIED > <!--Ext. kind of doc. code (EPO) --> <!ELEMENT B131EP (#PCDATA) > <!--* EBD B132EP Original kind code used eg. when there is a <B130>A9</B130> EPC2000 Phase 3 b) sequence attribute added--> <!ELEMENT B132EP (#PCDATA) > <!ATTLIST B132EP sequence CDATA #IMPLIED > <!--* EBD B133EP New kind code --> <!ELEMENT B133EP (#PCDATA) > <!--* EBD B140 Doc. date (publication or issue) REQUIRED --> <!ELEMENT B140 (date) > <!--* EBD B150 WIPO ST.9: INID: (15) Patent correction information See also. WIPO ST.50 Example: <B150> <B151>W1</B151> <B155> <B1551>de</B1551> <B1552>Beschreibung</B1552> <B1551>en</B1551> <B1552>Description</B1552> <B1551>fr</B1551> <B1552>Description</B1552> </B155> </B150> --> <!ELEMENT B150 (B151?,B152?,B153?,B154?,B155?) > <!--* EBD B151 Supplementary correction code The values used by the EPO are: - DL - Deletion (cancellation) of a previously announced correction - YF - Replacement of electronic file (no reprint will be made, only electronic data is changed) - Wn - Reprint required - n = the Nth reprint. --> <!ELEMENT B151 (#PCDATA) > <!--* EBD B152 Issue date of announced correction being cancelled. --> <!ELEMENT B152 (date) > <!--* EBD B153 INID Codes affected --> <!ELEMENT B153 (#PCDATA) > <!--* EBD B154 Standard notes Example: <B154> <B1541>de</B1541> <B1542>Gesamtes Dokument ersetzt</B1542> <B1541>en</B1541> <B1542>Entire document replaced</B1542> <B1541>fr</B1541> <B1542>Document entièrement remplacé</B1542> </B154> --> <!ELEMENT B154 (B1541,B1542)+ > <!--* EBD B1541 Note language --> <!ELEMENT B1541 (#PCDATA) > <!--* EBD B142 Note text --> <!ELEMENT B1542 (#PCDATA) > <!--* EBD B155 Affected parts of the document --> <!ELEMENT B155 (B1551,B1552)+ > <!--* EBD B1551 Part language --> <!ELEMENT B1551 (#PCDATA) > <!--* EBD B1552 Part text --> <!ELEMENT B1552 (#PCDATA) > <!--* EBD B190 WIPO ST.9: INID: (19) WIPO Standard ST.3 code, or other identification, of the office or organization publishing the document REQUIRED Country or organisation which actually publishes the document. The values used by EPO are: - EP European Patent Office. - WO WIPO --> <!ELEMENT B190 (#PCDATA) > <!--Source furnishing record --> <!ELEMENT B195 (#PCDATA) > <!--* EBD B200 ********************************* * B200 ********************************* WIPO ST.9: INID: (20) Data concerning the application for a patent Used as a grouping tag --> <!ELEMENT B200 (B210,B210EP?,B211EP?,B220,B225?,B230?,B240?,B250?,B250EP?,B251EP?, B260?,B270?) > <!--* EBD B210 WIPO ST.9: INID: (21) Number(s) assigned to the application(s), The application number REQUIRED --> <!ELEMENT B210 (#PCDATA) > <!--Application number in unstandardised form (EPO) --> <!ELEMENT B210EP (#PCDATA) > <!--Application number in EPOQUE format e.g. SE19960003073D--> <!ELEMENT B211EP (#PCDATA) > <!--* EBD B220 WIPO ST.9: INID: (22) Date(s) of filing the application(s) Application filing date REQUIRED --> <!ELEMENT B220 (date) > <!ATTLIST B220 id ID #IMPLIED > <!--Receiving office data --> <!ELEMENT B225 (dnum,date?,(ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*), adr?,dtxt*,rctry?,nctry?) > <!--* EBD B230 ********************************* * B230 - OTHER DATES ********************************* WIPO ST.9: INID: (23) Other date(s), including date of filing complete specification following provisional specification and date ofexhibition Grouping tag --> <!ELEMENT B230 (B231?,B232?,B233?,B234?,B235?,B236?,B237?,B238EP?,B238?,B239?) > <!--Other Dates Exhibition fili --> <!ELEMENT B231 (date) > <!--Complete spec. fil. Date --> <!ELEMENT B232 (date) > <!--Receipt Date nat. office --> <!ELEMENT B233 (date) > <!--Receipt Date nat. office --> <!ELEMENT B234 (date) > <!--* EBD B235 Date of refusal of application --> <!ELEMENT B235 (date) > <!ATTLIST B235 id ID #IMPLIED > <!--* EBD B236 Date of withdrawal of application --> <!ELEMENT B236 (date) > <!ATTLIST B236 id ID #IMPLIED > <!--* EBD B237 Date of application deemed withdrawn --> <!ELEMENT B237 (date) > <!ATTLIST B237 id ID #IMPLIED > <!--* EBD B238EP Date of receipt of request for restablishment of rights --> <!ELEMENT B238EP (date) > <!ATTLIST B238EP id ID #IMPLIED > <!--* EBD B238 Date of decision for re-establishment of rights --> <!ELEMENT B238 (date) > <!ATTLIST B238 id ID #IMPLIED > <!--* EBD B239 Date of revocation --> <!ELEMENT B239 (date) > <!ATTLIST B239 id ID #IMPLIED > <!--* EBD B240 ********************************* * B240 ********************************* WIPO ST.9: INID: (24) Date from which industrial property rights may have effect Grouping tag --> <!ELEMENT B240 (B241?,B242?,B243?,B244?,B245?,B245EP?,B246?,B248?) > <!--* EBD B241 Date of request for examination --> <!ELEMENT B241 (date) > <!ATTLIST B241 id ID #IMPLIED > <!--* EBD B242 Date of despatch of 1st. exam. report --> <!ELEMENT B242 (date) > <!ATTLIST B242 id ID #IMPLIED > <!--* EBD B243 Date of 'patent maintained as amended' --> <!ELEMENT B243 (date) > <!ATTLIST B243 id ID #IMPLIED > <!--* EBD B244 Request for conversion to natl. appl. --> <!ELEMENT B244 (date,ctry+) > <!ATTLIST B244 id ID #IMPLIED > <!--* EBD B245 Date of suspension (Rule 13) / interruption (Rule 90) of proceedings --> <!ELEMENT B245 (date) > <!ATTLIST B245 id ID #IMPLIED > <!--* EBD B245EP Indicates the type of suspension or Interruption. The values used by EPO are, according to EPC rules,: - 1 Suspension (Rule 14) - 2 Applicant died (Rule 142(1)(a)) - 3 Legal incapacity of applicant (Rule 142(1)(a)) - 4 Legal prevention (Rule 142(1)(b)) - 5 Representative died (Rule 142(1)(c)) - 6 Legal incapacity of representative (Rule 142(1)(c)) --> <!ELEMENT B245EP (#PCDATA) > <!ATTLIST B245EP id ID #IMPLIED > <!--* EBD B246 Date of resumption of proceedings --> <!ELEMENT B246 (date) > <!ATTLIST B246 id ID #IMPLIED > <!--Date of notification rights after appeal --> <!ELEMENT B248 (date) > <!--* EBD B250 ********************************* * B250 ********************************* WIPO ST.9: INID: (25) Language in which the published application was originally filed --> <!ELEMENT B250 (#PCDATA) > <!ATTLIST B250 id ID #IMPLIED > <!--Admissable non-EPO language (EPO) --> <!ELEMENT B250EP (#PCDATA) > <!--* EBD B251EP Procedure language (EPO) --> <!ELEMENT B251EP (#PCDATA) > <!ATTLIST B251EP id ID #IMPLIED > <!--* EBD B260 ********************************* * B260 ********************************* WIPO ST.9: INID: (26) Language in which the application is published --> <!ELEMENT B260 (#PCDATA) > <!ATTLIST B260 id ID #IMPLIED > <!-- ** EPC2000 - PHASE 3 a) ********************************* * B270 ********************************* WIPO ST.9 INID code (27) - Previously filed application This relates to new INID code (27) under WIPO ST.9; where the provisional wording is: Reference to a previously filed application for the purposes of obtaining a filing date under the Patent Law Treaty (PLT) Article 5(7). Same details may also appear in priority (INID code 30) if the earlier application is used as priority. New MEMO's: (EPASYS) EAPP01 Earlier application number (dnum) EAPP02 Date of filing of above (date) EAPP03 Filing office of above (ctry) <previously-filed-application> --> <!ELEMENT B270 (dnum,date,ctry,kind?,dtxt*) > <!ATTLIST B270 id ID #IMPLIED > <!--* EBD B300 ********************************* * B300 - FOREIGN PRIORITY DATA ********************************* WIPO ST.9: INID: (30) Data relating to priority under the Paris Convention Grouping tag Example: <B300> <B310>150799</B310> <B320><date>19990106</date></B320> <B330><ctry>JP</ctry></B330> </B300> --> <!ELEMENT B300 ((B310,B310EP?,B311EP?,B320,B330,B340?)*,(B345?,B345EP?)*) > <!ATTLIST B300 id ID #IMPLIED > <!--* EBD B310 WIPO ST.9: INID: (31) Number(s) assigned to priority application(s) --> <!ELEMENT B310 (#PCDATA) > <!--Priority appli. number in unstandardised form (EPO) --> <!ELEMENT B310EP (#PCDATA) > <!--Priority application number in EPOQUE format e.g. AU19790053732 --> <!ELEMENT B311EP (#PCDATA) > <!--* EBD B320 WIPO ST.9: INID: (32) Date(s) of filing of priority application(s). --> <!ELEMENT B320 (date) > <!--* EBD B320 WIPO ST.9: INID: (33) WIPO Standard ST.3 code identifying the national industrial property office allotting the priority application number or the organization allotting the regional priority application number; for international applications filed under the PCT, the code "WO" is to be used --> <!ELEMENT B330 (ctry) > <!--WIPO ST.9: INID: (34) For priority filings under regional or international arrangements, the WIPO Standard ST.3 code identifying at least one country party to the Paris Convention for which the regional or international application was made --> <!ELEMENT B340 (ctry) > <!--Patent family info. --> <!ELEMENT B345 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--Document kind code; e.g., A1 (INID 13, ST.32:B130) <!ELEMENT kind (#PCDATA) >--> <!--INPADOC pat.family info. (EPO) --> <!ELEMENT B345EP (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--* EBD 400 ********************************* * B400 - DATE(S) OF MAKING * AVAILABLE TO THE PUBLIC ********************************* WIPO ST.9: INID: (40) Date(s) of making available to the public Grouping tag --> <!ELEMENT B400 (B405?,B410?,B420?,B430?,B440?,B450?,B451EP?,B452EP?,B453EP?,B460?, B470?,B472?,B476?,B477?,B480?) > <!--* EBD 405 Pat. bull./gaz. info. Example: <B405><date>20050105</date><bnum>200501</bnum></B405> --> <!ELEMENT B405 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--WIPO ST.9: INID: (41) Date of making available to the public by viewing, or copying on request, an unexamined patent document, on which no grant has taken place on or before the said date --> <!ELEMENT B410 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--WIPO ST.9: INID: (42) Date of making available to the public by viewing, or copying on request, an examined patent document, on which no grant has taken place on or before the said date --> <!ELEMENT B420 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--* EBD B430 WIPO ST.9: INID: (43) Date of making available to the public by printing or similar process of an unexamined patent document, on which no grant has taken place on or before the said date --> <!ELEMENT B430 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!ATTLIST B430 id ID #IMPLIED > <!--WIPO ST.9: INID: (44) Date of making available to the public by printing or similar process of an examined patent document, on which no grant or only a provisional grant has taken place on or before the said date --> <!ELEMENT B440 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--* EBD B450 WIPO ST.9: INID: (45) Date of making available to the public by printing or similar process of a patent document on which grant has taken place on or before the said date EPO usage: B documents; includes Bulletin number Example: <B450> <date>20020724</date> <bnum>200230</bnum> </B450> --> <!ELEMENT B450 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!ATTLIST B450 id ID #IMPLIED > <!--* EBD B451EP Date of announcement of intention to grant without preceding Examination report.. (Communication pursuant to Rule 51(4) EPC) --> <!ELEMENT B451EP (date) > <!ATTLIST B451EP id ID #IMPLIED > <!--* EBD B452EP Date of intention to grant --> <!ELEMENT B452EP (date) > <!ATTLIST B452EP id ID #IMPLIED > <!-- **** EPC2000 - PHASE 3 b) **** Under INID code: (45) Date of publication and mention of the limitation decision: ep-limitation-decisions --> <!ELEMENT B453EP (B4530EP+) > <!-- kind code, date, Bulletin number attribute: eg. sequence="1" ep-limitation-decision --> <!ELEMENT B4530EP (kind,date,bnum) > <!ATTLIST B4530EP id ID #IMPLIED sequence CDATA #IMPLIED limitation-sequence CDATA #IMPLIED > <!-- WIPO ST.9: INID: (46) Date of making available to the public the claim(s) only of a patent document --> <!ELEMENT B460 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--WIPO ST.9: INID: (47) Date of making available to the public by viewing, or copying on request, a patent document on which grant has taken place on or before the said date. --> <!ELEMENT B470 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--* EBD B472 Term of grant Example: <B472> <B475> <date>20040425</date><ctry>ES</ctry><date>20040114</date> <ctry>FI</ctry><date>20040114</date><ctry>GB</ctry><date>20040414</date> <ctry>GR</ctry><date>20040414</date><ctry>SE</ctry> </B475> </B472> --> <!ELEMENT B472 (B473?,B474?,B475?) > <!--Disclaimer date --> <!ELEMENT B473 (date) > <!--Term of grant --> <!ELEMENT B474 (#PCDATA) > <!--* EBD B475 Lapse of patent See B472 for example --> <!ELEMENT B475 (dnum?,date?,ctry?,kind?,bnum?,dtxt*)+ > <!ATTLIST B475 id ID #IMPLIED > <!--Invalidation of patent --> <!ELEMENT B476 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--* EBD B477 Document printed as amended, third level of publication (e.g. EPO 'B2') Date of publication (B2) and issue number of the EPO Bulletin in which the mention of the document printed as amended is published. Example: <B477> <date>20020821</date> <bnum>200234</bnum> </B477> --> <!ELEMENT B477 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!ATTLIST B477 id ID #IMPLIED > <!--* EBD B480 WIPO ST.9: INID: (48) Date of issuance of a corrected patent document --> <!ELEMENT B480 (date?,bnum?) > <!--* EBD B500 ********************************* * B500 TECHNICAL INFORMATION ********************************* WIPO ST.9: INID: (50) Technical information --> <!ELEMENT B500 (B510?,B510EP?,B520*,B530?,B540?,B550?,B560?,B570?,B580?,B590?, B599EP?) > <!--* EBD B510 ********************************* * B510 - IPC DATA ********************************* WIPO ST.9: INID: (51) International Patent Classification or, in the case of a design patent, as referred to in subparagraph 4(c) of this Recommendation, International Classification for Industrial Designs Notes: - B510 will be used to the end of 2005, week 52 for IPC ed. 7 coding - From week 1, 2006 B510 will NOT be used in XML files (it will be used in the "old" SGML files still vailable on the ebd website) - the new B510EP element will be used (see below). - Backfile data will NOT be changed to B510EP or to the new IPC 8 because it is published data in the public domain. In these files B510 will remain of course. --> <!ELEMENT B510 (B516?,B511,(B512 | B513 | B514 | B515)*,B517EP?) > <!ATTLIST B510 id ID #IMPLIED > <!--* EBD B516 International Patent Classification Edition, version of IPC --> <!ELEMENT B516 (#PCDATA) > <!--* EBD B511 Main classification --> <!ELEMENT B511 (#PCDATA) > <!--* EBD B512 Further classification --> <!ELEMENT B512 (#PCDATA) > <!--* EBD B513 Additional information --> <!ELEMENT B513 (#PCDATA) > <!--* EBD B514 Linked indexing code --> <!ELEMENT B514 (#PCDATA) > <!--* EBD B515 Unlinked indexing code --> <!ELEMENT B515 (#PCDATA) > <!--* EBD B517EP Non-obligatory suppl. class. (EPO) --> <!ELEMENT B517EP (#PCDATA) > <!--********************************* * B510EP - NEW IPC CODING FOR 2006 ********************************* New coding for ST.8 new version of IPC. For 2006 onwards --> <!ELEMENT B510EP (classification-ipcr+) > <!ATTLIST B510EP id ID #IMPLIED sequence CDATA #IMPLIED > <!--******************************* * IPC DATA - NEW IPC8 ******************************* International Patent Classification (IPC) data; - to be implemented in 2006 - use B510 for until week 52, 2005 - see: http://www.wipo.int/scit/en/standards/pdf/03-08-01.pdf: Industrial property offices are asked to implement this new version of Standard ST.8 for all patent documents with a publication date from January 1, 2006, onwards. For patent documents published prior to that date, the previous version of the Standard should continue to be used. . . . This recording convention provides that symbols of the International Patent Classification (IPC) should be presented on machine-readable records for the exchange of information in machine-readable form in a fixed-length field in 50 positions, each part of the Int. Cl. symbol being recorded in specific positions and in the manner prescribed. - this can be recorded within the <text> tag. Position(s) Content Values 1 Section A-H 2 to 3 Class 01-99 4 Subclass A-Z 5 to 8 Main Group (right aligned) 1-9999, blank 9 Separating character / ("Slash") 10 to 15 Subgroup (left aligned) 00-999999 blank 16 to 19 For future use 4 blanks 20 to 27 Version indicator YYYYMMDD date format 28 Classification level C, A, S 29 First or later position of symbol F, L 30 Classification value (inventive or non-inventive) I, N 31 to 38 Action date YYYYMMDD date format 39 Original or reclassified data BRVD 40 Source of classification data H M G 41-42 Generating office AA ZZ (ST.3) 43-50 For future use 8 blanks EPO usage: - we will NOT use the detailed element markup as listed below (it is far too heavy) - we will use "a fixed-length field in 50 positions" as specified above EPO layout: - for the title page to be determined Example: <B510EP> <classification-ipcr sequence="1"> <text>B28B...5/00........20060101AFI20070601BHEP........</text> </classification-ipcr> </B510EP> --> <!ELEMENT classification-ipcr ((section,class,subclass,main-group?,subgroup?, ipc-version-indicator,classification-level?,symbol-position?, classification-value?,action-date?,classification-status?, classification-data-source?,generating-office?) | text) > <!ATTLIST classification-ipcr id ID #IMPLIED sequence CDATA #IMPLIED > <!--Positions 1 to 19: Recording of the parts of the IPC symbols IPC symbols are defined in Part 5 of the WIPO Handbook on Industrial Property Information and Documentation and in the latest version of the Guide to the IPC. --> <!ELEMENT section (#PCDATA) > <!ELEMENT class (#PCDATA) > <!ATTLIST class class-type CDATA #IMPLIED > <!ELEMENT subclass (#PCDATA) > <!ELEMENT main-group (#PCDATA) > <!ELEMENT subgroup (#PCDATA) > <!--Positions 20 to 27: Version indicator Although in the paper publications a version indicator may contain four or six digits, the version indicator in machinereadable records contains eight digits, namely YYYYMMDD with Y for year, M for month and D for day. --> <!ELEMENT ipc-version-indicator (date) > <!--Position 28 : Classification level Offices are expected to classify each subject matter only in one level (core or advanced). However, both levels need to be completely represented in the master classification database and thus a level indicator is needed. The level indicator is also useful for indicating situations where an office does not classify in either the core or the advanced level classification, i.e., when an office only assigns classifications to the subclass level. The level indicator enables to make the difference between core, advanced and subclass levels. The letters C (Core), A (Advanced) and S (Subclass) are used for this one-digit field. Levels: ipcr-advanced, ipcr-core --> <!ELEMENT classification-level (#PCDATA) > <!--Position 29: First or later position of symbols The position of the first invention information classification can be recognized by this field. The letters F and L are used for first and later position, respectively. --> <!ELEMENT symbol-position (#PCDATA) > <!--Position 30: Classification value (inventive or non-inventive) The difference between invention information and other information is important for the retrieval of the information. The letters I and N are used for the invention and non-invention information, respectively. --> <!ELEMENT classification-value (#PCDATA) > <!--Positions 31-38: Action date The date of assigning the classification symbol (action date) is represented by eight digits, namely YYYYMMDD. This date can be used to check if a classification needs to be reviewed after revision of the scheme, e.g., in case of creating new subdivisions. --> <!ELEMENT action-date (date) > <!--Position 39: Original and reclassified data Original data is the first data assigned to the document. In case of a publishing office assigning classification symbols at the core level, another office may also assign symbols at the advanced level as original data. Reclassified data is data changed due to a change in the classification schemes. Various data is data changed due to an incidental reclassification of an individual document, such as the correction of a mistake. Deleted data is data which has to be deleted from the Master Classification Database, due to a change in assigning of classification symbols to a document. The indication of the different types of data is marked by the letters B for the basic or original data, R for reclassified data, V for various incidental changes, and D for data to be deleted. Possible status: original-classification, reclassified, various-classification, deleted-classification --> <!ELEMENT classification-status (#PCDATA) > <!--Position 40: Source of classification data The following sources of classification data are foreseen: - Intellectual classification by persons, value H for human generated data. - Machine classification by the propagation of earlier intellectual classification through the use of common priorities in the patent application. The value M is used in this case and will facilitate later corrections. - Classification symbols generated by software using automatic analysis of the content of the patent document. The letter G is used to indicate this source of generated data. --> <!ELEMENT classification-data-source (#PCDATA) > <!--Positions 41-42: Generating Office Since part of the original data in the advanced level and the reclassified data can be delivered by offices other than the publishing office, the information source of such data is recorded by a field of two characters. The country or office code CC, as defined by WIPO Standard ST.3, must be used. --> <!ELEMENT generating-office (country) > <!--Country: use ST.3 country code; e.g. DE, FR, GB, NL, etc. Also includes EP, WO. Always in upper case. For stateless use XA. --> <!--********************************* * B520 to B530 NOT USED BY EPO ********************************* WIPO ST.9: INID: (52) Domestic or national classification --> <!ELEMENT B520 (B527,B526?,B521,(B522 | B523 | B524 | B525)*) > <!--Country code (ST.3) --> <!ELEMENT B527 (#PCDATA) > <!--Edition, version --> <!ELEMENT B526 (#PCDATA) > <!--Domestic or National classification Main classification --> <!ELEMENT B521 (#PCDATA) > <!--Further classification --> <!ELEMENT B522 (#PCDATA) > <!--Additional information --> <!ELEMENT B523 (#PCDATA) > <!--Linked indexing code --> <!ELEMENT B524 (#PCDATA) > <!--Unlinked indexing code --> <!ELEMENT B525 (#PCDATA) > <!----> <!ELEMENT B530 (#PCDATA) > <!--* EBD B540 ********************************* * B540 - TITLE ********************************* WIPO ST.9: INID: (54) Title of the invention --> <!ELEMENT B540 (B541?,B542,B542EP?)+ > <!ATTLIST B540 id ID #IMPLIED > <!--* EBD B541 Lang. of title (ISO 639) --> <!ELEMENT B541 (#PCDATA) > <!--* EBD B542 Title of invention --> <!ELEMENT B542 (#PCDATA) > <!ATTLIST B542 id ID #IMPLIED > <!--Title of invention in original language code.--> <!ELEMENT B542EP (#PCDATA) > <!--Keywords and descriptors --> <!ELEMENT B550 (B551?,B552*)* > <!--Lang. of keywords and descriptors --> <!ELEMENT B551 (#PCDATA) > <!--Keywords and descriptors --> <!ELEMENT B552 (#PCDATA) > <!--* EBD B560 ********************************* * B560 - CITATIONS ********************************* WIPO ST.9: INID: (56) List of prior art documents, if separate from descriptive text --> <!ELEMENT B560 ((B561,B563?,B564*)*,(B562,B563?,B564*)*,B561EP?,B565?,B565EP?,B566?, B566EP?,B567?,B568?,B569?) > <!--* EBD B561 Patent document citation Model much simplified. EPO Required usage: Use this tag for B doc. title page citations only under INID code (56). We take the data "as is" from EPASYS. In the future it may be tagged closer. Example: <B560> <B561> <text>FR-A- 2 765 554</text> </B561> </B560> --> <!ELEMENT B561 (text) > <!--Category of cited doc office dependent --> <!ELEMENT B563 (#PCDATA) > <!--Claim to which cited doc is relevant --> <!ELEMENT B564 (#PCDATA) > <!--* EBD B562 Non-patent literature (NPL) doc. citation. EPO Required usage: Use this tag for B doc title page citations only under INID code (56) We take the data "as is" from EPASYS. In the future it may be tagged closer. Examples: <B562><text>HELLAKER J ET AL: "REAL-TIME TRAVELLER INFORMATION - IN EVERYONE'S POCKET? A PILOT TEST USING HAND-PORTABLE GSM TERMINALS" PROCEEDINGS OF THE VEHICLE NAVIGATION AND INFORMATIONS SYSTEMS CONFERENCE,US,NEW YORK, IEEE, Bd. -, 12. Oktober 1993 (1993-10-12), Seiten 49-52, XP000448510</text></B562> <B562><text>R.B. BAARKER: "PROBE MOUNTING FOR NEAR-SURFACE MEASUREMENTS" IBM TECHNICAL DISCLOSURE BULLETIN, Bd. 22, Nr. 2, Juli 1979 (1979-07), Seite 481 XP002136032</text></B562> --> <!ELEMENT B562 (text) > <!--Number of copies of citations (EPO) --> <!ELEMENT B561EP (#PCDATA) > <!--Date of completion of search report --> <!ELEMENT B565 (date) > <!--* EBD B565EP Date of drawing up suppl.search report (EPO) --> <!ELEMENT B565EP (date) > <!ATTLIST B565EP id ID #IMPLIED > <!--Date of mailing of search report --> <!ELEMENT B566 (date) > <!--* EBD B566EP Date of despatch of correction to search report (EPO) --> <!ELEMENT B566EP (date) > <!ATTLIST B566EP id ID #IMPLIED > <!--Place of search, international search authority --> <!ELEMENT B567 ((ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*),adr?, dtxt*,rctry?,nctry?) > <!--Publ. of search report --> <!ELEMENT B568 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--Search report examiner --> <!ELEMENT B569 (ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*) > <!--******************************** * B570 ABSTRACT & CLAIMS DATA * B570-B582 not used by EPO ******************************** Abstract or claim EPO usage: - Use <abstract> or <claims> for this data and NOT B tags. The abstract is printed on title pages at INID code (57) --> <!ELEMENT B570 (B571?,B572?,B575*,B576?,B577) > <!--Language of abstract (ISO 639) --> <!ELEMENT B571 (#PCDATA) > <!--Abstract doc. info. --> <!ELEMENT B572 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--Lang. of claims (ISO 639) --> <!ELEMENT B575 (#PCDATA) > <!--Claims doc. info. --> <!ELEMENT B576 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--Number of claims --> <!ELEMENT B577 (#PCDATA) > <!--********************************* * Field of search ********************************* IPC --> <!ELEMENT B580 (B581 | B582)* > <!--IPC --> <!ELEMENT B581 (#PCDATA) > <!--National classification --> <!ELEMENT B582 (#PCDATA) > <!--* EBD B590 Spec. & drawings --> <!ELEMENT B590 (B591?,B592?,B595?,B596?,B597?,B598*) > <!--Lang. of spec. (ISO 639) --> <!ELEMENT B591 (#PCDATA) > <!--Number of text pages --> <!ELEMENT B592 (#PCDATA) > <!--Number of drawing sheets --> <!ELEMENT B595 (#PCDATA) > <!--Number of figures --> <!ELEMENT B596 (#PCDATA) > <!--No. of attached image files --> <!ELEMENT B597 (#PCDATA) > <!--* EBD B598 Figure number on first (title) page --> <!ELEMENT B598 (#PCDATA) > <!--Subsequently filed technical data --> <!ELEMENT B599EP (#PCDATA) > <!--Subsequently filed technical data * EBD B600 ********************************* * B600 RELATED PATENTS OR APPLICATIONS ********************************* WIPO ST.9: INID: (60) References to other legally or procedurally related domestic or previously domestic patent documents including unpublished applications therefor --> <!ELEMENT B600 (B610 | B620 | B620EP | B630 | B640 | B645 | B650 | B655 | B660 | B665 | B670)* > <!--* EBD B610 WIPO ST.9: INID: (61) Number and, if possible, filing date of the earlier application, or number of the earlier publication, or number of earlier granted patent, inventors certificate, utility model or the like to which the present patent document is an addition --> <!ELEMENT B610 (parent) > <!ATTLIST B610 id ID #IMPLIED > <!--* EBD B620 WIPO ST.9: INID: (62) Number and, if possible, filing date of the earlier application from which the present patent document has been divided up --> <!ELEMENT B620 (parent) > <!ATTLIST B620 id ID #IMPLIED > <!--* EBD B620EP Other types of relationship (EPO) --> <!ELEMENT B620EP (parent | B621EP | B622EP) > <!ATTLIST B620EP id ID #IMPLIED > <!--Relation for app.no. --> <!ELEMENT B621EP (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--Relation for pub.no. --> <!ELEMENT B622EP (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--WIPO ST.9: INID: (63) Number and filing date of the earlier application of which the present patent document is a continuation --> <!ELEMENT B630 (B631 | B632 | B633) > <!--Continuation --> <!ELEMENT B631 (parent) > <!--Continuation-in-part --> <!ELEMENT B632 (parent) > <!--Continuing reissue --> <!ELEMENT B633 (parent) > <!--WIPO ST.9: INID: (64) Number of the earlier publication which is reissued --> <!ELEMENT B640 (parent) > <!--Reexamination --> <!ELEMENT B645 (parent) > <!--WIPO ST.9: INID: (65) Number of a previously published patent document concerning the same application --> <!ELEMENT B650 (parent) > <!--Document previously published by another country/organisation --> <!ELEMENT B655 (parent) > <!--WIPO ST.9: INID: (66) Number and filing date of the earlier application of which the present patent document is a substitute, i.e., a later application filed after the abandonment of an earlier application for the same invention --> <!ELEMENT B660 (parent) > <!--Pat. correction info. --> <!ELEMENT B665 (B666,B667,B668?) > <!--Document being corrected --> <!ELEMENT B666 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--Type of correction --> <!ELEMENT B667 (#PCDATA) > <!--Descriptive text relating to correction --> <!ELEMENT B668 (#PCDATA) > <!--WIPO ST.9: INID: (67) Number and filing date of a patent application, or number of a granted patent, on which the present utility model application or registration (or a similar industrial property right, such as a utility certificate or utility innovation) is based --> <!ELEMENT B670 (parent) > <!--* EBD B700 ********************************* * B700 PARTIES CONCERNED WITH * THE DOCUMENT ********************************* WIPO ST.9: INID: (70) Identification of parties concerned with the patent or SPC --> <!ELEMENT B700 (B710?,B720?,B730?,B740?,B745?,B780?,B790?) > <!--* EBD B710 ********************************* * APPLICANTS ********************************* WIPO ST.9: INID: (71) Name(s) of applicant(s) --> <!ELEMENT B710 (B711+) > <!ATTLIST B710 id ID #IMPLIED > <!--* EBD B711 Applicant name and address --> <!ELEMENT B711 ((ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*),adr?, dtxt*,rctry?,nctry?,B711EP?,B713EP?,(B716EP?,B717EP?,B718EP?)*) > <!--Applicant name and addr. for correspondence (EPO) --> <!ELEMENT B711EP ((ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*),adr?, dtxt*,rctry?,nctry?) > <!--Applicant Authorisation no. Art.133(3) (EPO) --> <!ELEMENT B713EP (#PCDATA) > <!--Des. Contr. States for applicant (EPO) --> <!ELEMENT B716EP (ctry+) > <!--Des. extension states for applicant (EPO) --> <!ELEMENT B717EP (ctry+) > <!--* EBD B718EP Effective date for transfer of rights (EPO) --> <!ELEMENT B718EP (date) > <!ATTLIST B718EP id ID #IMPLIED > <!--* EBD B720 ********************************* * B720 INVENTORS ********************************* WIPO ST.9: INID: (72) Name(s) of inventor(s) if known to be such --> <!ELEMENT B720 (B721+,B721EP?) > <!ATTLIST B720 id ID #IMPLIED > <!--* EBD B721 Inventor name and address --> <!ELEMENT B721 ((ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*),adr?, dtxt*,rctry?,nctry?,B724EP?,B725EP?,B726EP?,B727EP?,B728EP?,B729EP?) > <!--Waiver by the inventor of information pursuant to Rule 17(3), EPC (EPO) --> <!ELEMENT B724EP (#PCDATA) > <!--* EBD B725EP The EPO text data stored here can be: When there is only one inventor and he has agreed to waive his entitlement to designation - De "Der Erfinder hat auf seine Nennung verzichtet" - En "The inventor has agreed to waive his entitlement to designation" - Fr "L'inventeur a rennoncé à sa désignation" When there are several inventors and they all have agreed to waive their entitlement to designation - De "Die Erfinder haben auf ihre Nennung verzichtet" - En "The inventors have agreed to waive their entitlement to designation" - Fr "Les inventeurs ont rennoncé à leur désignation" When there are several inventors and one of them has agreed to waive his entitlement to designation - De "Der andere Erfinder hat auf seine Nennung verzichtet" - En "The other inventor has agreed to waive his entitlement to designation" - Fr "L'autre inventeur a rennoncé à sa désignation" When there are several inventors and some of them have agreed to waive their entitlement to designation - De "Die andere Erfinder haben auf ihre Nennung verzichtet" - En "The other inventors have agreed to waive their entitlement to designation" - Fr "Les autres inventeurs ont rennoncé à leur désignation" --> <!ELEMENT B725EP (text+) > <!--Origin of applicant's rights if not inventor: as employee (EPO) --> <!ELEMENT B726EP (#PCDATA) > <!--Origin of applicant's rights if not inventor: under agreement (EPO) --> <!ELEMENT B727EP (#PCDATA) > <!--Origin of applicant's rights if not inventor: as co-inventor (EPO) --> <!ELEMENT B728EP (#PCDATA) > <!--Origin of applicant's rights if not inventor: as successor in title (EPO) --> <!ELEMENT B729EP (#PCDATA) > <!--Name with all original language characters "respected". Single string with $ separated multiple values and, optionally, * to indicate surname. e.g. LARS OLF *LOEFMAN$KENTH *GAMHED$KENNETH *EK--> <!ELEMENT B721EP ((ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*),adr?, dtxt*,rctry?,nctry?,B724EP?,B725EP?,B726EP?,B727EP?,B728EP?,B729EP?) > <!--* EBD B730 ********************************* * B730 GRANTEES ********************************* WIPO ST.9: INID: (73) Name(s) of grantee(s), holder(s), assignee(s) or owner(s) --> <!ELEMENT B730 (B731+) > <!ATTLIST B730 id ID #IMPLIED > <!--* EBD B731 Grantee name and address --> <!ELEMENT B731 ((ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*),adr?, dtxt*,rctry?,nctry?,(B736EP?,B737EP?,B738EP?)*) > <!--Designated states for grantee (EPO) --> <!ELEMENT B736EP (ctry+) > <!--Designated extension states for grantee (EPO) --> <!ELEMENT B737EP (ctry+) > <!--* EBD B738EP Effective date for transfer of rights (EPO) --> <!ELEMENT B738EP (date) > <!ATTLIST B738EP id ID #IMPLIED > <!--* EBD B740 ********************************* * B740 REPRESENTATIVES ********************************* WIPO ST.9: INID: (74) Name(s) of attorney(s) or agent(s) --> <!ELEMENT B740 (B741+) > <!ATTLIST B740 id ID #IMPLIED > <!--* EBD B741 Attorney name and address --> <!ELEMENT B741 ((ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*),adr?, dtxt*,rctry?,nctry?,B742EP?) > <!--General AUTHOR. no. (EPO) --> <!ELEMENT B742EP (#PCDATA) > <!--********************************* * Persons acting upon the document ********************************* --> <!ELEMENT B745 (B746,B747*) > <!--Primary examiner name --> <!ELEMENT B746 (ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*) > <!--Assistant examiner name --> <!ELEMENT B747 (ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*) > <!--* EBD B780 ********************************* * B780 OPPOSITION DATA ********************************* --> <!ELEMENT B780 (B781*,(B787 | B788 | B789)?) > <!--* EBD B781 Opponent data EPO usage: <B781>Opponent data <dnum><text>Serial number of the opposition <date>Date of opposition Date of receipt for 'filed' and 'admissible' oppositions Date of legal effect for 'inadmissible' and 'deemed not to be filed' oppositions <kind>Kind code of the result from the examination on admissibility. Code Meaning 0 Opposition filed 1 Admissible opposition 2 Inadmissible opposition 3 Deemed not to be filed 4 Opposition withdrawn 5 Intervention Art. 105 EPC 6 Intervention admissible 7 Intervention inadmissible 8 Intervention deemed not to be filed 9 Intervention withdrawn <snm>Name <iid>EPO number of the Opponent Example: <B781> <dnum><text>01</text></dnum> <date>20040726</date> <kind>1</kind> <snm>SIMEM S.R.L.</snm> <iid>00166150</iid> <adr> <str>Via Ronchi, 44 -</str> <city>37046 MINERBE (Verona)</city> <ctry>IT</ctry> </adr> <B784> <snm>Gatti, Enrico</snm> <iid>00135662</iid> <adr> <str>Via E. Zambianchi, 3</str> <city>24121 Bergamo</city> <ctry>IT</ctry> </adr> </B784> </B781> --> <!ELEMENT B781 ((dnum,date,kind),((ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,( odv,did)*),adr?,dtxt*,rctry?,nctry?),B784?,(B785 | B786)?) > <!ATTLIST B781 id ID #IMPLIED > <!--* EBD B784 Attorney or agent info. --> <!ELEMENT B784 ((ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*),adr?, dtxt*,rctry?,nctry?) > <!--Oppo. deemed not to have been filed --> <!ELEMENT B785 (date) > <!--Opposition inadmissable --> <!ELEMENT B786 (date) > <!--* EBD B787 Date of reject. of oppo. --> <!ELEMENT B787 (date) > <!ATTLIST B787 id ID #IMPLIED > <!--* EBD B788 Date of term. of oppo. --> <!ELEMENT B788 (date) > <!ATTLIST B788 id ID #IMPLIED > <!--No opposition filed --> <!ELEMENT B789 (#PCDATA) > <!--* EBD B790 ********************************* * B790 LICENCE DATA ********************************* EPO usage: <B790> <B791> <dnum><text>Serial number of the licence <date>Date of legal effect of the licence <kind>Kind of licence <snm>Name <iid>EPO number of the Licensee ... <B796>Designated states concerned <ctry>Country code Example: <B790> <B791> <dnum><text>0100</text></dnum><date>20040225</date><kind>E</kind> <snm>Environmental Minerals (UK) LTD</snm> <iid>00009110</iid> <adr> <str>Cambridge House 21, High Street</str> <city>Linton, Cambs. CB1 6HS</city> <ctry>GB</ctry> </adr> <B796><ctry>AT</ctry><ctry>BE</ctry><ctry>CH</ctry><ctry>CY</ctry> </B796> </B791> </B790> --> <!ELEMENT B790 (B791*) > <!ATTLIST B790 id ID #IMPLIED > <!--* EBD B791 Licence data, name and address --> <!ELEMENT B791 ((dnum,date,kind?),((ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,( odv,did)*),adr?,dtxt*,rctry?,nctry?),(B794?,B796?)) > <!--Attorney or agent info. --> <!ELEMENT B794 ((ttl?,fnm?,snm?,sfx?,iid?,irf?,onm?,syn*,oid?,(odv,did)*),adr?, dtxt*,rctry?,nctry?) > <!--* EBD B796 Design. ctry for license --> <!ELEMENT B796 (ctry+) > <!--* EBD B800 ********************************* * B800 DATA RELATED TO INTERNATIONAL * CONVENTIONS ********************************* WIPO ST.9: INID: (80) (90) Identification of data related to International Conventions other than the Paris Convention, and to legislation with respect to SPCs --> <!ELEMENT B800 (B810?,B820?,B830?,B840?,B844EP?,B850?,B860?,B870?,B880?,B890?)+ > <!--WIPO ST.9: INID: (81) Designated State(s) according to the PCT --> <!ELEMENT B810 (ctry+) > <!--PCT elected states --> <!ELEMENT B820 (ctry+) > <!--* EBD B830 WIPO ST.9: INID: (83) Information concerning the deposit of microorganisms, e.g., under the Budapest Treaty Example: <B830> <B831>Declaration under Rule 28(4) EPC (expert solution)</B831> </B830> --> <!ELEMENT B830 (B831,B832?,B833?) > <!--* EBD 831 Deposit file number --> <!ELEMENT B831 (#PCDATA) > <!--Authority where deposit was made --> <!ELEMENT B832 (#PCDATA) > <!--Date of deposit --> <!ELEMENT B833 (date) > <!--* EBD 840 WIPO ST.9: INID: (84) Designated Contracting States under regional patent conventions --> <!ELEMENT B840 (ctry+) > <!ATTLIST B840 id ID #IMPLIED > <!--* EBD 844EP States to which the patent is extended (EPO) EPO usage: <B844EP> States to which the application/patent is extended <B845EP> Extended state data <ctry> Country code <date> Payment date <B846EP> Date of withdrawal Example: <B844EP> <B845EP> <ctry>RO</ctry> <date>20010509</date> </B845EP> <B845EP> <ctry>SI</ctry> <date>20010509</date> </B845EP> </B844EP> --> <!ELEMENT B844EP (B845EP+) > <!ATTLIST B844EP id ID #IMPLIED > <!--Extended state data (EPO) --> <!ELEMENT B845EP (ctry,date?,B846EP?) > <!--* EBD 846EP End date (withdrawal) --> <!ELEMENT B846EP (date) > <!--WIPO ST.9: INID: (85) Date of commencement of the national phase pursuant to PCT Article 23(1) or 40(1) --> <!ELEMENT B850 (date) > <!--* EBD 860 WIPO ST.9: INID: (86) Filing data of the PCT international application, i.e., international filing date, international application number, and, optionally, the language in which the published international application was originally filed; or, in the case of design patents, registration data of the Hague Agreement international application, i.e., international registration date and international registration number --> <!ELEMENT B860 (B861,B862?,B863?,B864?) > <!ATTLIST B860 id ID #IMPLIED > <!--* EBD 861 Document identification --> <!ELEMENT B861 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--* EBD 862 Filing language (ISO 639) --> <!ELEMENT B862 (#PCDATA) > <!--PCT section 371 date --> <!ELEMENT B863 (date) > <!--PCT section 102(e) date --> <!ELEMENT B864 (date) > <!--* EBD 870 WIPO ST.9: INID: (87) Publication data of the PCT international application, i.e., international publication date, international publication number, and, optionally, the language in which the international application is published Example: <B870> <B871> <dnum><pnum>WO2000040576</pnum></dnum> <date>20000713</date> <bnum>200028</bnum> </B871> </B870> --> <!ELEMENT B870 (B871,B872?) > <!ATTLIST B870 id ID #IMPLIED > <!--* EBD 871 Document identification --> <!ELEMENT B871 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--PCT pub. lang. (ISO 639) --> <!ELEMENT B872 (#PCDATA) > <!--* EBD 880 WIPO ST.9: INID: (88) Date of deferred publication of the search report INID (88) on A3 docs. Print: date and bulletin number - bnum. --> <!ELEMENT B880 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!ATTLIST B880 id ID #IMPLIED > <!--CMEA agreement --> <!ELEMENT B890 (B891,B892?) > <!--Havana Agreement doc.id. --> <!ELEMENT B891 (dnum?,date?,ctry?,kind?,bnum?,dtxt*) > <!--Havana Agreement date property rights --> <!ELEMENT B892 (date) > <!--Miscellaneous --> <!ELEMENT B900 (B910?) > <!--WIPO ST.9: INID: (91) Date on which an international application filed under the PCT no longer has an effect in one or several designated or elected States due to failure to enter the national or regional phase or the date on which it has been determined that it had failed to enter the national or regional phase --> <!ELEMENT B910 (date) > <!-- * EBD ********************************* * SDOBI ELEMENTS KEPT FOR * BACKWARD COMPATIBILITY ********************************* --> <!-- SDOBI Country of residence --> <!ELEMENT rctry (ctry)> <!-- SDOBI Describes parent document. ST.32 equivalency = PARENT --> <!ELEMENT parent (dnum? , cdoc* , pdoc* , psta? , ppub?)> <!-- SDOBI : id of patent associated with parent --> <!ELEMENT ppub (dnum? , date? , ctry? , kind? , bnum? , dtxt*)+> <!-- SDOBI : parent status code --> <!ELEMENT psta (#PCDATA)> <!-- SDOBI : parent doc. id. --> <!ELEMENT pdoc (dnum? , date? , ctry? , kind? , bnum? , dtxt*)+> <!-- SDOBI Country of nationality --> <!ELEMENT nctry (ctry)> <!-- SDOBI : Components of an address --> <!ELEMENT cdoc (dnum? , date? , ctry? , kind? , bnum? , dtxt*)+> <!-- SDOBI : Descriptive text --> <!ELEMENT dtxt (#PCDATA)> <!-- SDOBI : Components of a doc and extdoc (doc, extdoc). Document number --> <!ELEMENT dnum (text? | (anum? , pnum?))> <!ELEMENT pnum (#PCDATA)> <!ELEMENT anum (#PCDATA)> <!-- SDOBI : Bulletin number --> <!ELEMENT bnum (#PCDATA)> <!-- SDOBI : Components of an address --> <!ELEMENT adr ((ttl? , fnm? , snm? , sfx? , iid? , irf? , onm? , syn* , oid? , (odv , did)*)? , omc? , pbox? , str* , city? , cnty? , state? , ctry? , pcode? , (ead* , tel* , fax*))> <!-- SDOBI : Telephone number --> <!ELEMENT tel (#PCDATA)> <!-- SDOBI : Postal code or zip code --> <!ELEMENT pcode (#PCDATA)> <!-- SDOBI : Country (ST.3) --> <!ELEMENT ctry (#PCDATA)> <!-- SDOBI : County, parish, department, etc. --> <!ELEMENT cnty (#PCDATA)> <!-- SDOBI : Str., house no. or name, --> <!ELEMENT str (#PCDATA)> <!-- SDOBI : Post Office box number --> <!ELEMENT pbox (#PCDATA)> <!-- SDOBI : Organization mail code --> <!ELEMENT omc (#PCDATA)> <!-- SDOBI : Identifying no. of div. --> <!ELEMENT did (#PCDATA)> <!-- SDOBI : Division of organization --> <!ELEMENT odv (#PCDATA)> <!-- SDOBI : Identifying no. of org. --> <!ELEMENT oid (#PCDATA)> <!-- SDOBI : Synonym, cross reference --> <!ELEMENT syn (#PCDATA)> <!-- SDOBI : Organization name --> <!ELEMENT onm (#PCDATA)> <!-- SDOBI : Individual ref. number(filing, etc.) --> <!ELEMENT irf (#PCDATA)> <!-- SDOBI : Suffix (e.g., II, Jr., Esq. et al.) --> <!ELEMENT sfx (#PCDATA)> <!-- SDOBI : Family, last, surname or organisation --> <!ELEMENT snm (#PCDATA)> <!-- SDOBI : Given and middle name(s) or initials --> <!ELEMENT fnm (#PCDATA)> <!-- SDOBI : Components of a name (nam) Title (e.g., Mr., Mrs.) --> <!ELEMENT ttl (#PCDATA)> <!-- ******************************* Common elements taken out of context ******************************* --> <!-- Individual id --> <!ELEMENT iid (#PCDATA) > <!--Document kind code; e.g., A1 (INID 13, ST.32:B130) --> <!ELEMENT kind (#PCDATA) > <!--Date: components of a date. Format: YYYYMMDD --> <!ELEMENT date (#PCDATA) > <!--If no structure is possible, enter text (without markup) --> <!ELEMENT text (#PCDATA) > <!--Electronic address use for other than email --> <!ELEMENT ead (#PCDATA) > <!--Fax number --> <!ELEMENT fax (#PCDATA) > <!--City or town name --> <!ELEMENT city (#PCDATA) > <!--Region of country; e.g., state, province, etc. --> <!ELEMENT state (#PCDATA) > <!--Country: use ST.3 country code; e.g. DE, FR, GB, NL, etc. Also includes EP, WO. Always in upper case. For stateless use XA. --> <!ELEMENT country (#PCDATA) > <!-- ******************************************************************************* * END FOR COPYING THIS SECTION * INTO/FROM ep-patent-document.dtd ******************************************************************************* --> <!-- ******************************************************************************* ABSTRACT (SUB-DOCUMENT) ******************************************************************************* ST.36/ANNEX F compliance: - element doc-page removed - for PUBLICATION purposes it will not be used EPO: EPC Article 85 - The abstract The abstract shall merely serve for use as technical information; it may not be taken into account for any other purpose, in particular not for the purpose of interpreting the scope of the protection sought nor for the purpose of applying Article 54, paragraph 3. Rule 33 - Form and content of the abstract (1) The abstract shall indicate the title of the invention. Note: this rule does NOT comply with Annex F so we do not have it in the DTD. Applicants may still enter the title. (3) The abstract shall preferably not contain more than one hundred and fifty words. EPO required usage: - id="abst" - lang="en" de fr EPO Style: - The abstract is published on the title page after the INID code (57) - The heading "Abstract" etc, is NOT printed - Any title above the abstract is NOT printed (use title at B540). Example: <abstract id="abst" lang="de"> --> <!ELEMENT abstract ((abst-problem,abst-solution) | p+) > <!ATTLIST abstract id ID #IMPLIED lang CDATA #IMPLIED status CDATA #IMPLIED > <!-- abst-problem The alleged problem that the invention purports to solve Recommended id="absp" Unlikely to be used by the EPO --> <!ELEMENT abst-problem (p+) > <!ATTLIST abst-problem id ID #IMPLIED > <!-- abst-solution The solution to the alleged problem that the invention purports to solve. Recommended id="abss" Unlikely to be used by the EPO --> <!ELEMENT abst-solution (p+) > <!ATTLIST abst-solution id ID #IMPLIED > <!-- ******************************************************************************* DESCRIPTION (SUB-DOCUMENT) ******************************************************************************* : The description must disclose the invention in a manner sufficiently clear and complete for it to be carried out by a person skilled in the art (PCT Rule 5). EPO See EPC Rule 42 - Content of the description EPO required usage: - id="desc" - lang - element doc-page removed - for PUBLICATION purposes it will not be used - In very rare cases there may be multiple descriptions we will treat as one description use heading tag where this occurs - The headings within the description are PCT headings. These elements must NOT be used by contractors - use the element: <heading> with the exception of older PatXML files - PatXML files: if <invention-title> is present REMOVE IT for publication - the actual title is at tag <B542> EPO Style: Depending on language code the heading will be, in bold, left justified, with breaks around: en - Description de - Beschreibung fr - Description Example: <description id="desc" lang="de"> --> <!ELEMENT description (invention-title?,(technical-field | background-art | disclosure | description-of-drawings | best-mode | mode-for-invention | industrial-applicability | sequence-list-text | ( heading*,p+)+)+) > <!ATTLIST description id ID #IMPLIED lang CDATA #IMPLIED status CDATA #IMPLIED > <!-- ******************************* HEADINGS ******************************* EPO required usage: - id="h0001", "h0002", etc. - level="1" etc MAY be used and are used in PatXML files EPO PatXML uses: - For level 1: left justified, bold, line break - For level 2: left justified, underlined, line - For level 3: left justified, line break, but the rendering tags are included within the <heading>; eg. <b> - For ALL other headings entered by the contractor just use <heading> using bold etc as entered by the applicant BUT left justified, DO NOT USE level attribute UNLESS it is a PatXML file which can be left "as is". --> <!ELEMENT heading (#PCDATA | b | i | u | o | sup | sub | smallcaps)* > <!ATTLIST heading id ID #IMPLIED level (1 | 2 | 3) #IMPLIED > <!-- ******************************* PARAGRAPH ******************************* EPO Required usage: - In case of standard paragraphs in the description: id="p0001", "p0002", etc. - In case of abstracts: id="pa01", "pa02", etc. (more than three is rare) - In case of amended-claims-statement: id="pc0001", "pc0002", etc. - In case of search reports: id="ps0001", "ps0002", etc. - num = 0001, 0002, etc. EPO style: - always left justified - precede by para. number in bold as so: [0001] - para. text indented 7mm from [0001] - see espacenet for examples --> <!ELEMENT p (#PCDATA | b | i | u | o | sup | sub | smallcaps | br | pre | dl | ul | ol | crossref | figref | patcit | nplcit | bio-deposit | img | chemistry | maths | tables | table-external-doc)* > <!ATTLIST p id ID #IMPLIED num CDATA #REQUIRED > <!-- ********************************* * FORMATTING TAGS WITHIN <p> ** Added 2006-02-08 - sup and sub to b, i, u (PFC pending) ********************************* Bold formatting for text --> <!ELEMENT b (#PCDATA | i | u | o | smallcaps | sup | sub )* > <!--Italic formatting for text --> <!ELEMENT i (#PCDATA | b | u | o | smallcaps | sup | sub )* > <!--Underscore: style - single is default ** Added 2006-02-08 ** REMOVED replaced by <o> - see below 2006-05-31 - attribute overscore (PFC pending) --> <!ELEMENT u (#PCDATA | b | i | smallcaps | sup | sub )* > <!ATTLIST u style (single | double | dash | dots ) "single" > <!-- overscore: style - single is default ** Added 2006-05-31 (PFC pending) --> <!ELEMENT o (#PCDATA | b | i | smallcaps | sup | sub )* > <!ATTLIST o ostyle (single | double | dash | dots | leftarrow | rightarrow | leftrightarrow ) "single" > <!--Small capitals --> <!ELEMENT smallcaps (#PCDATA | b | u | o | i)* > <!-- Superscripted text --> <!ELEMENT sup (#PCDATA | b | u | o | i | sup2 | sub2)* > <!-- Superscripted text 2nd level --> <!ELEMENT sup2 (#PCDATA | b | u |o | i)* > <!-- Subscripted text --> <!ELEMENT sub (#PCDATA | b | u | o | i | sup2 | sub2)* > <!-- Subscripted text 2nd level --> <!ELEMENT sub2 (#PCDATA | b | u | o | i)* > <!-- br - break, line break within a paragraph, etc --> <!ELEMENT br EMPTY > <!-- ******************************* LISTS ******************************* DEFINTION LISTS ******************************* EPO required usage: - For dl elements in the main part of the document: id="dl0001" - If parent element is abstract: id="dla01" BUT contractors should, if possible, not use in abstracts. (It is not used in PatXML in abstracts) - tsize: this is optional and not used in PatXML files (similar to HTML). - Old SGML files have the value of the length of the first <dt> this can be removed - For new processing tsize is not required; layout will depend on style sheet - This follows HTML practice Example: Old file: <DL TSIZE=10> <DT>Fig. 1<DD>shows a 3D surface plot .. <DT>Fig. 2a<DD>is a schematic diagram ... </DL> New file <dl id="dl0001"> <dt>fig. 1</dt><dd>shows a 3d surface plot ..</dd> <dt>fig. 2a</dt><dd>is a schematic diagram ...</dd> </dl> --> <!ELEMENT dl (dt,dd)+ > <!ATTLIST dl id ID #IMPLIED tsize CDATA #IMPLIED compact (compact) #IMPLIED > <!--Term to be defined Recommended id="dt0001",etc EPO required usage: NOT USED IN EPO. --> <!ELEMENT dt (#PCDATA | b | i | u | o | sup | sub | smallcaps)* > <!ATTLIST dt id ID #IMPLIED > <!-- Definition description --> <!ELEMENT dd (#PCDATA | b | i | u | o | sup | sub | smallcaps | br | pre | patcit | nplcit | bio-deposit | crossref | figref | img | ul | ol | chemistry | maths)* > <!-- ******************************* ORDERED LISTS: ******************************* EPO required use: - For ol elements in the main part of the document id="ol0001" - If parent element is abstract:id="ola01";BUT contractors should, if possible, not use in abstracts just type in the numbers as text. EPO PatXML style ONLY for three levels and ONLY in the description: - level 1 use arablic numbers 1, 2, 3, ... - level 2 use lower alpha a, b, c, ... - level 3 use lower roman i, ii, iii, ... Early PatXML files <ol> is nested as above. Example (from PatXML version 1.4) : <ol id="ol0001" ol-style="1."> <ol id="ol0001" ol-style="a."> <ol id="ol0001" ol-style="i."> Contractors: For all other cases (ie non-PatXML) leave the style empty and insert the actual numbering in the text after <li>: EPO style: indent whole list 6mm from left margin Example: <ol id="ol0001" ol-style=""> <li>1.1 List item 1.1</li> </ol> --> <!ELEMENT ol (li+) > <!ATTLIST ol id ID #IMPLIED compact (compact) #IMPLIED ol-style CDATA #IMPLIED > <!-- ******************************* UNORDERED LISTS: ******************************* List-style may be empty for lists with no bullet or other symbol default list-style is 'bullets'. EPO required usage: - for ul element in the description: id="ul0001" - If parent element is abstract: id="ula01"; BUT contractors should, if possible, not use in abstracts just type in the numbers as text (not used in PatXML) - list-style: "none" means "none" or other type of symbol; that is if the applicant used some other symbol use this and then in the body of the text enter that symbol - bullet and dash may be used - compact EPO style: indent whole list 6mm from left margin Example: <ul id="ul0001" list-style="bullet"> --> <!ELEMENT ul (li+) > <!ATTLIST ul id ID #IMPLIED list-style (bullet | dash | none) "bullet" compact (compact) #IMPLIED > <!-- LIST ITEM EPO required usage: - DO NOT USE ID --> <!ELEMENT li (#PCDATA | b | i | u | o | sup | sub | smallcaps | br | pre | patcit | nplcit | bio-deposit | crossref | figref | img | dl | ul | ol | chemistry | maths)* > <!ATTLIST li id ID #IMPLIED num CDATA #IMPLIED > <!-- ******************************* REFERENCES: ******************************* A reference to a figure. May be in PatXML files. For discussion with contractor ?** Example:"...as shown in <figref idref='f0001'>Fig.1</figref>..." --> <!ELEMENT figref (#PCDATA | b | i | u | o | sup | sub | smallcaps)* > <!ATTLIST figref idref IDREFS #IMPLIED num CDATA #IMPLIED > <!-- Cross reference to any other element with an identifier (id) In PatXML files can be to a table only. --> <!ELEMENT crossref (#PCDATA | b | i | u | o | sup | sub | smallcaps)* > <!ATTLIST crossref idref IDREF #REQUIRED > <!-- ******************************* IMAGE DATA ******************************* Image is used for any kind of image: drawings, art work, figures, complex work units (math, tables, chemistry), etc. EPO Required usage: the following attributes must be used in this order: - id - file - wi (in mm) - note wi and he can be in any order (old Datimtex files are he and wi) - he (in mm) - img-content="drawing" (default - may be other - see below) - img-format="tif" (default - no other) - orientation="portrait" (default for PATXML files - may be landscape) - inline may be used - alt is NOT used - id and file values: - For figures within the DRAWINGS section: id="if0001", etc. file="imgf0001.tif" (where f = figure) - For images within the DESCRIPTION and CLAIMS section: id="ib0001", etc. file ="imgb0001.tif" (where b = body) - For images within the BODY of the ABSTRACT section eg a chemical formula id="ia01", etc. file ="imga0001.tif" (where a = abstract) - For the figure to accompany the ABSTRACT section (abstract drawing): Taken from the drawings section NOT in PatXML files. id="iaf01", etc. file ="imgaf001.tif" (where af = abstract figure) Example: <img id="if0001" file="imgf0001.tif" wi="155" he="230" img-content="drawing" img-format="tif"/> Note: where images occur, possibly, in other sections, eg. search report data use similar logic. --> <!ELEMENT img EMPTY > <!ATTLIST img id ID #IMPLIED file CDATA #REQUIRED wi CDATA #REQUIRED he CDATA #REQUIRED img-content (drawing | photograph | character | dna | undefined | chem | table | math | program-listing | graph | flowchart) "drawing" img-format (jpg | tif | st33 | st35) #REQUIRED orientation (portrait | landscape) "portrait" inline (yes | no) "no" alt CDATA #IMPLIED > <!-- ******************************* SEQUENCE LISTING FREE TEXT ******************************* WIPO ST.25: "36. Where the sequence listing part of the description contains free text, any such free text shall be repeated in the main part of the description in the language thereof. It is recommended that the free text in the language of the main part of the description be put in a specific section of the description called "Sequence Listing Free Text". Recommended id="seqt" ?** need to check for examples and usage --> <!ELEMENT sequence-list-text (heading*,p+)+ > <!ATTLIST sequence-list-text id ID #IMPLIED > <!-- ******************************* CLAIMS (SUB-DOCUMENT) ******************************* Defines the matter for which protection is sought ST.36/ANNEX F compliance: - element doc-page removed - for PUBLICATION purposes it will not be used EPO EPC Article 84 The claims The claims shall define the matter for which protection is sought. They shall be clear and concise and be supported by the description. EPO required usage, - Since there are multiple types of claims we will number them: - id="claims01" - this is the default and the most common in A docs. For the translated versions in B docs "claims02" and "claims03" - lang - for claims for different contracting states also use claims01, claims02 etc. - claim-type - this is used only for Claims for different contracting states, eg. claim-type="Claim(s) for the following Contracting State(s): AT, BE" - this text used for the heading. Patentansprüche für folgende Vertragsstaaten Patentansprüche für folgenden Vertragsstaat Revendications pour les Etats contractants suivants Revendications pour l'Etat contractant suivant EPO Style: Depending on language code the heading will be, in bold, left justified, with breaks around: en - Claims de - Patentanspräche fr - Revendications Examples: Claims in B docs: <claims id="claims01" lang="en"> <claims id="claims02" lang="de"> <claims id="claims03" lang="fr"> Claims for contracting states: <claims id="claims01" lang="en" claim-type="Claim(s) for the following Contracting State(s): AT, BE"> <claims id="claims02" lang="en" claim-type="Claim(s) for the following Contracting State(s): GB"> <claims id="claims03" lang="de"> See: Rules for Contractos for full details --> <!ELEMENT claims (claim+) > <!ATTLIST claims id ID #IMPLIED lang CDATA #IMPLIED claim-type CDATA #IMPLIED status CDATA #IMPLIED > <!-- ******************************* THE ACTUAL CLAIMS ******************************* EPO required usage (as specified in ST.36, para. ): - If the parent element is claims and there is only ONE set of claims: - id="c-fr-0001", c-fr-0002, etc. - num = 0001, 0002, etc. EPO style: - arabic numerals, bold, full stop; eg. 1. - block indent all text after the number Example: <claims id="claims01" lang="en"> <claim id="c-en-0001" num="0001"> <claim-text>Here is the first claim ... </claim-text> </claim> </claims> Notes: - If parent element is claims and there are MULTIPLE sets of claims (for EP-B docs) then: - id="c-en-01-0001", c-en-01-0002, etc. - num="0001", 0002, etc. - id="c-de-01-0001", c-de-01-0002, etc. - num"="0001", 0002, etc. - id="c-fr-01-0001", c-fr-01-0002, etc. - num="0001", 0002, etc. - If parent element is amended-claims and there is only ONE set then use "aclaims"; in the unlikely event of multiple amended claims use: "aclaims01" etc, the actual claims will be numbered (for single occurrence): - id="ac-en-0001", ac-en-0002, etc. - num="0001", 0002, etc. *** Note for data capture: if the claims are numbered incorrectly by the applicant: THEIR NUMBERING MUST BE KEPT FOR A-DOCUMENTS and the num attribute will be: num=""; the actual claim number must be placed within the <claim-text> --> <!ELEMENT claim (claim-text+) > <!ATTLIST claim id ID #IMPLIED num CDATA #REQUIRED claim-type CDATA #IMPLIED > <!-- ******************************* THE TEXT WITHIN CLAIMS ******************************* The text of the claim; also used for sub-para indentation. This has the same model as <p> but no lists; for lists use <claim-text> and any amrk required for the list within the text. EPO style: line break, blank line and indent any 2nd level <claim-text>; blank line after last nested claim see for example claim 1 EP 0 743 242 B1 --> <!ELEMENT claim-text (#PCDATA | claim-text | claim-ref | b | i | u | o | sup | sub | smallcaps | br | pre | crossref | figref | img | chemistry | maths | tables)* > <!--Reference to a claim --> <!ELEMENT claim-ref (#PCDATA) > <!ATTLIST claim-ref idref IDREFS #REQUIRED > <!-- ******************************* AMENDED CLAIMS (SUB-DOCUMENT) ******************************* ST.36/ANNEX F compliance: - element doc-page removed - for PUBLICATION purposes it will not be used Amended content of original application; for an example see EP 1236699 A1 EPO required usage: - id = "aclaims" - lang="en" or "fr" or "de" - amend-claim-type; this can have one of the following two values: PCT or EPC The actual text, whatever the wording or language, of the heading must be captured as entered by the applicant within the <heading> tag; so we wll have for example: <aclaims id="aclaims" lang="en" amend-claim-type="PCT"> <heading>Amended claims under Art. 19.1 PCT</heading> <claim id="ac-en-0001" num="0001"><claim-text>... ?** add in language examples The heading "Claims" will not be used in this case but the heading as above. ?** Not in current PatXML files --> <!ELEMENT amended-claims (heading?,claim+,amended-claims-statement*)+ > <!ATTLIST amended-claims id ID #IMPLIED lang CDATA #REQUIRED country CDATA #IMPLIED amend-claim-type CDATA #IMPLIED status CDATA #IMPLIED > <!-- ******************************* AMENDED CLAIMS STATEMENT ******************************* ST.36/ANNEX F compliance: - element doc-page removed - for PUBLICATION purposes it will not be used Amendment statement (PCT Article 19.1, PCT Rule 46.4). eg. See EP 1367825 A1 and PCT/JP02/02111. Only one type of heading and these are always PCT. EPO usage: - id="asclaims" - lang The actual text, whatever the wording or language, of the heading must be captured as entered by the applicant within the <heading> tag; so we will have for example: <asclaims id="asclaims" lang="en"> <claims-statement> <heading>Statement under Art. 19.1 PCT</heading> <p>In the claim 12 of the claims, an electroless plating method ... fr - Déclaration selon l'art. 19.1 PCT de - add German ?** Only in EP A Docs If the parent element is amended-claims and there are MULTIPLE sets of amended-claims UNLIKELY) then: id="asclaims01", asclaims02", etc ?** Not in current PatXML files --> <!ELEMENT amended-claims-statement (claims-statement+) > <!ATTLIST amended-claims-statement id ID #IMPLIED lang CDATA #IMPLIED status CDATA #IMPLIED > <!ELEMENT claims-statement (heading*,p+)+ > <!-- ******************************* DRAWING (SUB-DOCUMENT) & FIGURES ******************************* ST.36/ANNEX F compliance: - element doc-page removed - for PUBLICATION purposes it will not be used DRAWINGS shall be required when they are necessary for the understanding of the invention. EPO See: EPC Rule 46 - Form of the drawings EPO Required usage: - id="draw" - lang EPO style: - new page, - no heading used --> <!ELEMENT drawings (figure+) > <!ATTLIST drawings id ID #IMPLIED lang CDATA #IMPLIED status CDATA #IMPLIED > <!-- FIGURE A drawing (figure), necessary for the understanding of the invention EPO Required usage: - id="f0001", "f0002", etc - num="0001" or as entered by the applicant. Example: <figure id="f0001" num="0001"> <figure id="f0001" num="1a"> figure-labels (figure captions) not used for now Notes: - In PatXML the applicant can number the figure as they wish, eg num="2a" - Contract should capture the number as entered by the applicant --> <!ELEMENT figure (img) > <!ATTLIST figure id ID #IMPLIED num CDATA #REQUIRED figure-labels CDATA #IMPLIED > <!-- ******************************* DOCUMENT ID ******************************* Document identification refers to patents (and patent applications) only. See WIPO ST.14 --> <!ELEMENT document-id (country,doc-number,kind?,name?,date?) > <!ATTLIST document-id lang CDATA #IMPLIED > <!--Country: use ST.3 country code; e.g. DE, FR, GB, NL, etc. Also includes EP, WO. Always in upper case. Also can use "stateless" --> <!--The number of the referenced patent (or application) document --> <!ELEMENT doc-number (#PCDATA) > <!--Document kind code; e.g., A1 (INID 13, ST.32:B130) --> <!--Name: If no distinction or detail can be given. Also to be used for: personal (natural person) and corporate (legal entity) names --> <!ELEMENT name (#PCDATA) > <!ATTLIST name name-type (legal | natural) #IMPLIED > <!--Date: components of a date. Format: YYYYMMDD --> <!--If no structure is possible, enter text (without markup) --> <!-- ******************************* BIO-DEPOSIT *******************************. Biological deposit citation (INID 83, ST.32:B830) According to PCT Rule 13bis, EPC Rule 32 This covers all bio data references long and short within the description and/or claims Recommended id=biod0001, biod0002, etc. Used in PatXML files --> <!ELEMENT bio-deposit (depositary,bio-accno,date?,term?,dtext?) > <!ATTLIST bio-deposit id ID #IMPLIED num CDATA #REQUIRED url CDATA #IMPLIED dnum CDATA #IMPLIED > <!--Information regarding the facility storing the biological deposit. (ST.32:B832) --> <!ELEMENT depositary (#PCDATA | address)* > <!--Biological accession number: (ST.32:B831) The identification assigned to the biological material by the depository --> <!ELEMENT bio-accno (#PCDATA) > <!--Identifies the period of time during which the depository must be able to furnish samples of the biological material. --> <!ELEMENT term (#PCDATA) > <!-- ******************************* ADDRESSBOOK GROUP: ******************************* Holds name and contact information for individuals/organizations also used in NPL citations The LANG attribute is REQUIRED for certain document types, e.g., the JPO PCT Request where names and addresses may be repeated in two different languages. If no structure possible use text. --> <!ELEMENT addressbook ((%name_group;,address,phone*,fax*,email*,url*,ead*,dtext?) | text) > <!ATTLIST addressbook id ID #IMPLIED lang CDATA #IMPLIED > <!--Title: e.g., Mr., Mrs., Dr. etc --> <!ELEMENT prefix (#PCDATA) > <!--Last, family, surname --> <!ELEMENT last-name (#PCDATA) > <!--Organisation name or company name --> <!ELEMENT orgname (#PCDATA) > <!--First or given name(s), initial(s) --> <!ELEMENT first-name (#PCDATA) > <!--Middle name(s) or initial(s) --> <!ELEMENT middle-name (#PCDATA) > <!--Name suffix (e.g., II, Jr., Dip., Ing., BA, etc.) --> <!ELEMENT suffix (#PCDATA) > <!-- Individual id --> <!--Role; e.g., President, Chairman, etc. --> <!ELEMENT role (#PCDATA) > <!--Department, division, section, etc. name --> <!ELEMENT department (#PCDATA) > <!--Synonym --> <!ELEMENT synonym (#PCDATA) > <!--Registered number --> <!ELEMENT registered-number (#PCDATA) > <!--Address components: Address formats differ from country to country If no structure possible use text --> <!ELEMENT address %address_group; > <!--Address, first line --> <!ELEMENT address-1 (#PCDATA) > <!--Address, second line --> <!ELEMENT address-2 (#PCDATA) > <!--Address, third line --> <!ELEMENT address-3 (#PCDATA) > <!--Organizational mail code --> <!ELEMENT mailcode (#PCDATA) > <!--Post Office Box number --> <!ELEMENT pobox (#PCDATA) > <!--Address room; e.g., Room 55B --> <!ELEMENT room (#PCDATA) > <!--Address floor; e.g., 10th --> <!ELEMENT address-floor (#PCDATA) > <!--Building information in address; e.g., Hoffman building --> <!ELEMENT building (#PCDATA) > <!--Street may contain house number or name --> <!ELEMENT street (#PCDATA) > <!--City or town name --> <!--County, parish, department, etc (mainly UK, USA) --> <!ELEMENT county (#PCDATA) > <!--Region of country; e.g., state, province, etc. --> <!--Postal code or zip code --> <!ELEMENT postcode (#PCDATA) > <!--Telephone number --> <!ELEMENT phone (#PCDATA) > <!--Fax number --> <!--Email address --> <!ELEMENT email (#PCDATA) > <!--Universal Resource Locator; e.g. www.wipo.int --> <!ELEMENT url (#PCDATA) > <!--Electronic address use for other than email --> <!--Descriptive text --> <!ELEMENT dtext (#PCDATA) > <!-- ******************************* CHEMISTRY ******************************* Chemical formulae, ring structures, Markush structures, etc. ** Added 2006-02-08 - <formula-text> as alternative to image for very simple chemical "formulaes" where it would be useful to indentify them as such. EPO required usage: - For now treat as image or text data. - Depending on industry support we may use, e.g. CML later - For chemistry elements in the main part of the document: id="chem0001". - For chemistry elements in the abstract:id="chema01"; - num = 0001, 0002, etc. --> <!ELEMENT chemistry (img | formula-text | (chem,img?)) > <!ATTLIST chemistry id ID #IMPLIED num CDATA #REQUIRED > <!--This is a pointer to an external DTD for chemical markup - to be determined. For EPO probably CML; http://www.xml-cml.org/ ?** --> <!ELEMENT chem EMPTY > <!ATTLIST chem id ID #IMPLIED file CDATA #REQUIRED chem-type CDATA #IMPLIED > <!-- NEW data element for v.1.1: fomula-text allows the data entry of very simple formulae without the verbosity of full mark up of maths and when available for chemistry --> <!ELEMENT formula-text (#PCDATA | b | i | u | o | sup | sub | smallcaps)* > <!-- ********************************* TABLES ********************************* This is image data or coded according to OASIS Exchange model with modified cell 'entry' and 'title' content. EPO required usage: - id="tabl0001" etc. - If parent element is abstract: id="tabla01"; - num="0001" etc. - tables may be images or marked up. Mark up should be the default --> <!--The parameter entities defined by the CALS table model as published (as part of the Example DTD) in MIL-HDBK-28001, have been removed and replaced by the corresponding values, to simplify reading. LS --> <!ELEMENT tables (img | table) > <!ATTLIST tables id ID #IMPLIED num CDATA #REQUIRED > <!ELEMENT table (title?,tgroup+) > <!ATTLIST table frame (top | bottom | topbot | all | sides | none) #IMPLIED colsep NMTOKEN #IMPLIED rowsep NMTOKEN #IMPLIED pgwide NMTOKEN #IMPLIED > <!ELEMENT title (#PCDATA | b | i | u | o | sup | sub | smallcaps)* > <!ELEMENT tgroup (colspec*,thead?,tbody) > <!ATTLIST tgroup cols NMTOKEN #REQUIRED colsep NMTOKEN #IMPLIED rowsep NMTOKEN #IMPLIED align (left | right | center | justify | char) #IMPLIED > <!ELEMENT colspec EMPTY > <!ATTLIST colspec colnum NMTOKEN #IMPLIED colname NMTOKEN #IMPLIED colwidth CDATA #IMPLIED colsep NMTOKEN #IMPLIED rowsep NMTOKEN #IMPLIED align (left | right | center | justify | char) #IMPLIED char CDATA #IMPLIED charoff NMTOKEN #IMPLIED > <!ELEMENT thead (row+) > <!ATTLIST thead valign (top | middle | bottom) #IMPLIED > <!ELEMENT row (entry+) > <!ATTLIST row rowsep NMTOKEN #IMPLIED valign (top | middle | bottom) #IMPLIED > <!ELEMENT entry (#PCDATA | b | i | u | o | sup | sub | smallcaps | br | patcit | nplcit | bio-deposit | crossref | figref | img | dl | ul | ol | chemistry | maths)* > <!ATTLIST entry colname NMTOKEN #IMPLIED namest NMTOKEN #IMPLIED nameend NMTOKEN #IMPLIED morerows NMTOKEN #IMPLIED colsep NMTOKEN #IMPLIED rowsep NMTOKEN #IMPLIED align (left | right | center | justify | char) #IMPLIED char CDATA #IMPLIED charoff NMTOKEN #IMPLIED valign (top | middle | bottom) #IMPLIED > <!ELEMENT tbody (row+) > <!ATTLIST tbody valign (top | middle | bottom) #IMPLIED > <!-- ******************************************************************************* SEARCH REPORT (SR) DATA ******************************************************************************* Notes: - the SR can be standalone (as sent to the applicant) or part of the actual publication (A1, A3, A9) where srep-for-pub is used. - We MAY have a separate SR DTD but many elements are also in other areas of the DTD - The EPO will generate all data for the search report from the EPO SDMS, EPASYS and DATIMTEX databases. - It must not be changed by contractors except for the route element - Instructions will be given for layout/rendering; some are contained in ths DTD within ++++++ marks. These contain the text to be generated by any style sheet. Otherwise see "Rules for Contractors" *** IMPORTANT: - SRs elements have yet to be tested in production; there may be some changes. - A lot of the comments and elements here relate to PCT procedures (ISR) and NOT EPO. Since we also process the PCT ISR we will leave in the comments etc but we MAY have a separate DTD for the ISR (PCT forms 210, 237 etc). ******************************************************************************* search-report-data: EPO required usage: - id="srep" - lang="en" or "fr" or "de" - srep-office="EP" - date-produced = date finished by the examiner - srep-type= (DETERMINES LAYOUT OF SR together with language, explained more below) - "ep-sr" - normal SR layout - "ep-rule45-sr" or "ep-rule63-sr" - "ep-rule46-sr" or "ep-rule64-sr" - "ep-Rule46supplmentary-sr" or "ep-Rule64supplmentary-sr" - "ep-Rule45declaration-sr" - layout for Declaration (no citations, old Form 1504) or "ep-Rule63declaration-sr" - "ep-supplementary-sr" (always after an ISR) - "isr" - International Search Report layout - status="n" in most cases --> <!ELEMENT search-report-data (doc-page+ | (srep-info?,srep-for-pub?, srep-search-opinion?,srep-written-opinion?)) > <!ATTLIST search-report-data id ID #IMPLIED lang CDATA #IMPLIED srep-office CDATA #REQUIRED date-produced CDATA #REQUIRED srep-type CDATA #IMPLIED status CDATA #IMPLIED > <!-- ********************************* SR INFO - For the EPO Old Form 1507 ********************************* srep-info +++++++++++++++++++++++++++++++++++++++ ** EPO - Old Form 1507 MOST OF THIS IS NOT PART OF PUBLICATION new layout: <srep-info> generates - EPO logo and address header - followed by: COMMUNICATION OF THE EUROPEAN SEARCH REPORT - followed by correspondence address (see below) +++++++++++++++++++++++++++++++++++++++ PCT ISR PCT covers Forms: 201, 210, 220, 237 etc Stylesheet (for new layout) generates (for PCT) at the beginning: PATENT COOPERATION TREATY (PCT) INTERNATIONAL SEARCH REPORT (ISR) - PART 1 (PCT Articles 18 and Rules 43 and 44) FOR FURTHER ACTION see Notification of Transmittal of ISR (Form PCT/ISA/220) as well as, where applicable, abstract information below. **This will need modifying depending on stytesheet and output required ** SREP - INFO DETAILS This is a repetition of data found elsewhere but we put it here also for convenience, formatting, etc The order has changed from the paper form. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT srep-info (doc-page+ | (correspondence-address?,file-reference-id?, application-reference+,date-of-earliest-priority?,applicant-name, srep-established?,srep-protest-fees?,srep-request-date?, srep-request-number?,srep-prior-art-docs*,srep-basis?, srep-claims-info?,srep-unity-of-invention?,srep-invention-title, srep-abstract,srep-figure-to-publish,srep-info-admin,srep-other-info?, text*)) > <!ATTLIST srep-info total-page-count CDATA #IMPLIED > <!-- +++++++++++++++++++++++++++++++++++++++ Date mailed +++++++++++++++++++++++++++++++++++++++ ** EPO - Old Form 1507; new layout: Date or Datum ** PCT use other elements --> <!ELEMENT srep-info-admin (authorized-officer?,srep-office?,date-search-report-mailed?, date-opinion-completed?) > <!-- Date of mailing:--> <!-- Form PCT/ISA/237 (cover sheet) (April 2005) +++++++++++++++++++++++++++++++++++++++ Date of completion of this opinion +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT date-opinion-completed (date) > <!-- Applicant's or agent's file reference, if desired, --> <!ELEMENT file-reference-id (#PCDATA) > <!-- +++++++++++++++++++++++++++++++++++++++ ** EPO - Old Form 1507; new layout: <application-reference> <document-id> - application number followed by: The name of the applicant (without address information) (ST.32:B711) Example: <applicant-name><name>IVECO S.P.A.</name></applicant-name> --> <!ELEMENT applicant-name %name_group; > <!-- +++++++++++++++++++++++++++++++++++++++ PCT ISR Form PCT/ISA/220 (October 2005) NOTIFICATION OF TRANSMITTAL OF THE INTERNATIONAL SEARCH REPORT AND THE WRITTEN OPINION OF THE INTERNATIONAL SEARCHING AUTHORITY, OR THE DECLARATION +++++++++++++++++++++++++++++++++++++++ Old form check boxes 1 and 2 +++++++++++++++++++++++++++++++++++++++ srep-established: PCT: If yes: The applicant is hereby notified that the international search report and the written opinion of the International Searching Authority have been established and are transmitted herewith. Filing of amendments and statement under Article 19: The applicant is entitled, if he so wishes, to amend the claims of the international application (see Rule 46): When? The time limit for filing such amendments is normally two months from the date of transmittal of the international search report. Where? Directly to the International Bureau of WIPO, 34 chemin des Colombettes 1211 Geneva 20, Switzerland, Facsimile No.: +41 22 338 82 70 For more detailed instructions, see below. if no: The applicant is hereby notified that no international search report will be established and that the declaration under Article 17(2)(a) to that effect and the written opinion of the International Searching Authority are transmitted herewith. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT srep-established EMPTY > <!ATTLIST srep-established srep-established (yes | no) "yes" > <!-- ********************************* SR ABSTRACT ********************************* srep-abstract +++++++++++++++++++++++++++++++++++++++ ** EPO: The European Patent Office herewith transmits the European search report for the above-mentioned European patent application. If applicable, the documents cited in the European search report can be viewed and/or downloaded by clicking on the citations listed. yes = The abstract was not modified by the Search Division no = The ABSTRACT was modified by the Search Division and the definitive text is as follows: [Retrieve/insert text from DATIMTEX] +++++++++++++++++++++++++++++++++++++++ PCT ISR PCT/ISA/210. Old 5. Search Report Abstract - will be different from abstract and will replace it. (followed by:) The text is approved as submitted by the applicant [attribut]e "yes" (default)] (or) The text has been established according to Rule 38.2(b), ]by this ISA as it appears below. The applicant may, within one month from the date of mailing of this ISR, submit comments to this ISA. a revised abstract if present [attribute "no"] +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT srep-abstract (abstract?) > <!ATTLIST srep-abstract abs-approval (yes | no) "yes" > <!-- ********************************* SR TITLE ********************************* srep-invention-title +++++++++++++++++++++++++++++++++++++++ ** EPO: yes = The TITLE given by the applicant has been approved by the Search Division no = The TITLE was modified by the Search Division and is as follows: [Retrieve/insert text from EPASYS] +++++++++++++++++++++++++++++++++++++++ PCT ISR PCT/ISA/210. Old 4. Title followed by: The text is approved as submitted by the applicant - [attribute "yes" (default)] or The text has been established by this ISA to read as follows: [a revised title if present - attribute "no")] +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT srep-invention-title (invention-title?) > <!ATTLIST srep-invention-title title-approval (yes | no) "yes" > <!-- ********************************* SR FIGURE TO PUBLISH ********************************* srep-figure-to-publish +++++++++++++++++++++++++++++++++++++++ ** EPO: The following figure will be published together with the abstract: [figure-to-publish, fig-number] +++++++++++++++++++++++++++++++++++++++ PCT ISR PCT/ISA/210. Old 6. The figure of the drawings to be published with the abstract is: Figure No. followed by text of attribute value: 1 = as suggested by the applicant. 2 = because the applicant failed to suggest a figure. 3 = because this figure better characterizes the invention. or: 4 = None of the figures is to be published with the abstract (Old PCT/ISA/210 - 6 a and b) +++++++++++++++++++++++++++++++++++++++ Example: <srep-figure-to-publish figinfo="1"> <figure-to-publish> <fig-number>1</fig-number> </figure-to-publish> </srep-figure-to-publish> --> <!ELEMENT srep-figure-to-publish (figure-to-publish?) > <!ATTLIST srep-figure-to-publish figinfo (1 | 2 | 3 | 4) #REQUIRED > <!-- Figure of the drawings which should accompany the abstract Also used in bib. data. --> <!ELEMENT figure-to-publish (fig-number+) > <!-- Also at EP: <B598> PCT/RO/101 Box IX: the number of the figure which should accompany the abstract. --> <!ELEMENT fig-number (#PCDATA) > <!-- ********************************* END OF OLD EPO FORM 1507 The following text is generated (EN) after </srep-figure-to-publish>: +++++++++++++++++++++++++++++++++++++++ ** EPO REFUND OF THE SEARCH FEE: if applicable, under the EPC Rules Relating to Fees, Article 10, a separate communication from the Receiving Section on the refund of the search fee will be sent later. This is then, usually, followed by the actual SR on a new page old form 1503 - plus, if present the 1503 extensions as shown below. ******************************* SR - CLAIMS INFO ******************************* EPO: Claims incurring fees (1507) - see below PCT: (Old PCT/ISA/210 - Box No. II) Observations where certain claims were found unsearchable This ISR has not been established in respect of certain claims under Article 17(2)(a) for the following reasons: (followed by one of the following three reasons:) --> <!ELEMENT srep-claims-info (clms-reason-1?,clms-reason-2?,clms-reason-3?, clms-incurring-fees-1?,clms-incurring-fees-2?) > <!--Claims Nos.: (insert value from cliaim-no) because they relate to subject matter not required to be searched by this Authority, namely: --> <!ELEMENT clms-reason-1 (claim-num+,claim-remark) > <!--Claim numbers --> <!ELEMENT claim-num (#PCDATA) > <!--Remarks on these claims --> <!ELEMENT claim-remark (p+) > <!--Claims Nos.: (insert value from claim-no) because they relate to parts of the international application that do not comply with the prescribed requirements to such an extent that no meaningful international search can be carried out, specifically: --> <!ELEMENT clms-reason-2 (claim-num+,claim-remark) > <!--Claim number(s) (insert value from claim-no) because they are dependent claims and are not drafted in accordance with the second and third sentences of PCT Rule 6.4(a) --> <!ELEMENT clms-reason-3 (claim-num+) > <!-- ******************************* SR - EPO - CLAIMS INCURRING FEES ******************************* EPO: Added: 2005-06-17 These elements to process EPO SR FORM 1503 - Claims incurring fees; for example see: EP 00127241 +++++++++++++++++++++++++++++++++++++++ ** EPO: CLAIMS INCURRING FEES REVENDICATIONS DONNANT LIEU AU PAIEMENT DE TAXES The present European patent application comprised at the time of filing more than ten claims. La présente demande de brevet européen comportait lors de son dépôt plus de dix revendications (old box 1) Only part of the claims have been paid within the prescribed time limit. The present European search report has been drawn up for the first ten claims and for those claims for which claims fees have been paid, namely claim(s): Then follows contents of <claim-num> +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT clms-incurring-fees-1 (claim-num+) > <!-- EPO: +++++++++++++++++++++++++++++++++++++++ ** EPO: Claims incurring fees (old box 2); text: No claims fees have been paid within the prescribed time limit. The present European search report has been drawn up for the first ten claims. This is an empty element if present the text above is generated. --> <!ELEMENT clms-incurring-fees-2 EMPTY > <!-- ********************************* UNITY OF INVENTION (old 1503 SHEET D/B) ********************************* srep-unity-of-invention +++++++++++++++++++++++++++++++++++++++ ** EPO: LACK OF UNITY OF INVENTION The Search Division considers that the present European patent application does not comply with the requirements of unity of invention and relates to several inventions or groups of inventions, namely: MANGELNDE EINHEITLICHKEIT DER ERFINDUNG Nach Auffassung der Recherchenabteilung entspricht die vorliegende europäische Patentanmeldung nicht den Anforderungen an die Einheitlichkeit der Erfindung und enthalt mehrere Erfindungen oder Gruppen von Erfindungen, nämlich: ABSENCE D'UNITE D'INVENTION La division de la recherche estime que la présente demande de brevet européen ne satisfait pas a l'exigence relative a l'unité d'invention et concerne plusieurs inventions ou pluralités d'inventions, a savoir: +++++++++++++++++++++++++++++++++++++++ After this add <p> data; usually a numbered list relating to claims followed by text Example: srep-unity-of-invention> <p id="pu0001" num="0001"> 1. claims: 1-3,11,12 <br/> Magnetooptical recording medium of the MSR land/groove type having grooves with greater width than the lands, groove depth less or equal than 60 nm and track pitch less or equal than 0.7 micrometers. </p> <p id="pu0002" num="0002"> 2. claims: 4-10 <br/> Optical recording medium and associated recording/reproducing device of the land/groove type with the width of a groove mark being smaller than the width of a land mark. </p> <srep-search-fees> <srep-fee-1/> </srep-search-fees> </srep-unity-of-invention> +++++++++++++++++++++++++++++++++++++++ ** PCT: (Old PCT/ISA/210 - Box No. III) Observations where unity of invention is lacking This ISA found multiple inventions in this international application, as follows: (use text data) --> <!ELEMENT srep-unity-of-invention (p*,srep-search-fees,search-fee-protest?) > <!ELEMENT srep-search-fees (srep-fee-1?,srep-fee-2?,srep-fee-3?,srep-fee-4?) > <!-- +++++++++++++++++++++++++++++++++++++++ ** EPO srep-fee-1: All further search fees have been paid within the fixed time limit. The present European search report has been drawn up for all claims. Alle weiteren Recherchengebühren wurden innerhalb der gesetzten Frist entrichtet. Der vorliegende europäische Recherchenbericht wurde für alle Patentansprüche erstellt. Toutes les nouvelles taxes de recherche ayant été acquittées dans es délais impartis, le présent rapport de recherche européenne a été établi pour toutes es revendications. +++++++++++++++++++++++++++++++++++++++ ** PCT 210, Box III: As all required additional search fees were timely paid by the applicant, this ISR covers all searchable claims. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT srep-fee-1 EMPTY > <!-- +++++++++++++++++++++++++++++++++++++++ ** EPO srep-fee-2: As all searchable claims could be searched without effort justifying an additional fee, the Search Division did not invite payment of any additional fees. Da für alle recherchierbaren Ansprüche die Recherche ohne einen Arbeitsaufwand durchgeführt werden konnte, der eine zusätzliche Recherchengebühr gerechtfertigt hatte, hat die Recherchenabteilung nicht zur Zahlung einer solchen Gebühr aufgefordert. Comme toutes les recherches portant sur es revendications qui s'y prêtaient ont pu être effectuées sans effort particulier justifiant une taxe additionnelle, Ia division de la recherche na sollicité le paiement d aucune taxe de cette nature. +++++++++++++++++++++++++++++++++++++++ ** PCT: As all searchable claims could be searched without effort justifying an additional fee, this ISA did not invite payment of any additional fees. Da für alle recherchierbaren Ansprüche die Recherche ohne einen Arbeitsaufwand durchgeführt werden konnte, der eine zusätzliche Recherchengebühr gerechtfertigt hatte, hat die Recherchenabteilung nicht zur Zahlung einer solchen Gebühr aufgefordert. Comme toutes les recherches portant sur es revendications qui s'y prêtaient ont pu être effectuées sans effort particulier justifiant une taxe additionnelle, Ia division de la recherche na sollicité le paiement d'aucune taxe de cette nature. --> <!ELEMENT srep-fee-2 EMPTY > <!-- +++++++++++++++++++++++++++++++++++++++ ** EPO srep-fee-3: Only part of the further search fees have been paid within the fixed time limit The present European search report has been drawn up for those parts of the European patent application which relate to the inventions in respect of which search fees have been paid, namely claims: Nur ein Teil der weiteren Recherchengebühren wurde innerhalb der gesetzten Frist entrichtet. Der vorliegende europäische Recherchenbericht wurde für die Teile der Anmeldung erstellt, die sich auf Erfindungen beziehen, für die Recherchengebühren entrichtet worden sind, nämlich Patentansprüche: Une partie seulement des nouvelles taxes de recherche ayant été acquittée dans les délais impartis, le présent rapport de recherche européenne a été établi pour les parties qui se rapportent aux inventions pour lesquelles les taxes de recherche ont été acquittées, a savoir les revendications: +++++++++++++++++++++++++++++++++++++++ ** PCT: As only some of the required additional search fees were timely paid by the applicant, this ISR covers only those claims for which fees were paid, specifically claim number(s): --> <!ELEMENT srep-fee-3 (claim-num+) > <!-- +++++++++++++++++++++++++++++++++++++++ ** EPO srep-fee-4: None of the further search fees have been paid within the fixed time limit. The present European search report has been drawn up for those parts of the European patent application which relate to the invention first mentioned in the claims, namely claims: Keine der weiteren Recherchengebühren wurde innerhalb der gesetzten Frist entrichtet. Der vorliegende europäische Recherchenbericht wurde für die Teile der Anmeldung erstellt, die sich auf die zuerst in den Patentansprüchen erwähnte Erfindung beziehen, nämlich Patentansprüche: Aucune nouvelle taxe de recherche n'ayant été acquittée dons les délais impartis, le présent rapport de recherche européenne a été établi pour les parties de Ia demande de brevet européen qui se rapportent a l'invention mentionnée en premier lieu dans les revendications, a savoir les revendications: +++++++++++++++++++++++++++++++++++++++ ** PCT: No required additional search fees were timely paid by the applicant. Consequently, this ISR is restricted to the invention first mentioned in the claims; it is covered by claim number(s): --> <!ELEMENT srep-fee-4 (claim-num+) > <!-- Box III, PCT/ISA/210 Remark on protest (only for PCT use) Attribute values generate following text: 1 = The additional search fees were accompanied by the applicant's protest and, where applicable, the payment of a protest fee. 2 = The additional search fees were accompanied by the applicant's protest but the applicable protest fee was not paid within the time limit specified in the invitation. 3 = No protest accompanied the payment of additional search fees --> <!ELEMENT search-fee-protest EMPTY > <!ATTLIST search-fee-protest protest (1 | 2 | 3 ) #REQUIRED > <!-- ********************************* ACTUAL SR with citations etc (old 1503) ********************************* --> <!-- srep-for-pub +++++++++++++++++++++++++++++++++++++++ ** EPO: NEW layout for publication depends on srep-type for "ep-sr" we have (depending on language): - EUROPEAN SEARCH REPORT (left justified, bold, 12 point) - EUROPÄISCHER RECHERCHENBERICHT - RAPPORT DE RECHERCHE EUROPEENNE followed by, on the same line, right justified, bold, 12pt: - Application number: - Nummer der Anmeldung: - Numéro de la demande: - followed by IPC +++++++++++++++++++++++++++++++++++++++ PCT: The Heading for PCT ISR is: INTERNATIONAL SEARCH REPORT (ISR) - PART 2 Repeat international application number (?) IPC, FIELDS and DATABASES SEARCHED CLASSIFICATION OF SUBJECT MATTER --> <!ELEMENT srep-for-pub (doc-page+ | (classification-ipc?,classifications-ipcr?, classification-national?,srep-fields-searched,srep-citations, srep-incomplete-search?,srep-declaration?,srep-admin?,srep-patent-family?)) > <!-- IPC +++++++++++++++++++++++++++++++++++++++ ** EPO: after the header we have the following left justified, bold: 11 pt: - Classifciation of the application (IPC) - Klassifikation der Anmeldung (IPC) - Classement de la demande (IPC) followed by the classes and then , on the same line, - Technical fields searched (IPC): - Recherchierte Sachgebiete (IPC): - Domaines techniques recherches (IPC) Note: not exactly same as PCT Classifciation of the application Note: new IPCR from 2006 +++++++++++++++++++++++++++++++++++++++ Example <classifications-ipcr> <classification-ipcr sequence="1"> <text>H04B 10/24 99991231A</text> </classification-ipcr> <classification-ipcr sequence="2"> <text>H04B 10/00 99991231A</text> </classification-ipcr> </classifications-ipcr> <srep-fields-searched> <minimum-documentation> <classifications-ipcr> <classification-ipcr> <text>H04B</text> </classification-ipcr> </classifications-ipcr> </minimum-documentation> </srep-fields-searched> --> <!ELEMENT srep-fields-searched (minimum-documentation,other-documentation*, database-searched?) > <!--Minimum documentation searched --> <!ELEMENT minimum-documentation (classification-ipc?,classifications-ipcr?, classification-national?) > <!--Documentation searched other than minimum documentation ** Not used by EPO --> <!ELEMENT other-documentation (#PCDATA) > <!--Database(s) searched ** Not used by EPO --> <!ELEMENT database-searched (text | nplcit) > <!-- ********************************* CITATIONS GROUP ********************************* +++++++++++++++++++++++++++++++++++++++ ** EPO Stylesheet, generates header, centred, bold, 11pt: DOCUMENTS CONSIDERED TO BE RELEVANT (Citation, category, relevant claims, * relevant passage *) DOCUMENTS CONSIDERES COMME PERTINENTS (Citation, catégorie, revendication concernée, * parties pertinentes *) EINSCHLÄGIGE DOKUMENTE (Kennzeichnung, Kategorie, Betrittt Anspruoh, * massgeblichen Teile *) +++++++++++++++++++++++++++++++++++++++ Use <text> for NONE, where there are no citations found The end tag </citation> generates (THERE ARE exceptions to this - Lack of Unity cases): - The present search report has been drawn up for all claims - Der vorliegende Recherchenbericht wurde für alle Patentanspruche erstellt - Le present rapport a été etabli pour toutes lea revendications and then the categories --> <!ELEMENT srep-citations (text | citation+) > <!-- ******************************* CITATIONS ******************************* Grouping tag for patent literature (patcit) or non-patent literature (nplcit) plus data related to those citations. Recommended id='cit0001', 'cit0002', etc. For the SR: id='sr-cit0001', 'sr-cit0002' Note: id is in ANNEX F version 1.3 version of the isr srep-phase is NOT --> <!ELEMENT citation ((patcit | nplcit),(rel-passage*,category*, rel-claims*)*,corresponding-docs*,classification-ipc?,classifications-ipcr?, classification-national?,doi?) > <!ATTLIST citation id ID #IMPLIED srep-phase CDATA #IMPLIED > <!-- ******************************* PATCIT ******************************* PATENT CITATIONS: (ST.32:see B561 for B documents only) Patent Citation within paragraph and SR Notes: Tags arranged according to WIPO ST.14 order. This can be free text data without any structure (text). Attributes (recommended): id - pcit0001, pcit0002, etc. for the SR: sr-pcit0001 num - 0001, 0002, etc. dnum - use full number as one string, eg, "US5401234A"; file - file name eg. if actual file is stored on local systems dnum-type - type of document number (e.g., application number, publication number) url - where possible give full web link to patent eg to espacenet EPO and PatXML usage: id - pcit0001, pcit0002, etc. for the SR: sr-pcit0001 num - 0001, 0002, etc. dnum - use full number as one string, eg, "US5401234A"; dnum-type - type of document number; only used if NOT publication number; otherwise values are (in PatXML): appno and pctno url - for the SR generate link to espacenet Examples: <patcit id='pcit0001' num="0001" dnum='US4793675A' dnum-type='appno'> <document-id> <country>US</country> <doc-number>4793675</doc-number> <kind>A</kind> <name>Handa</name> <date>19881227</date> </document-id> </patcit> For the SR: <srep-citations> <citation id="sr-cit0001"> <patcit id='sr-pcit0001' num="0001" dnum='US6089831A' url="http://v3.espacenet.com/textdoc?DB=EPODOC&IDX=US6089831&CY=ep"> <document-id> <country>US</country> <doc-number>6089831</doc-number> <kind>A</kind> <name>ALT MATHIAS ET AL</name> <date>20000718</date> </document-id> </patcit> <rel-passage> <passage> column 3, line 66 - column 6, line 35; figure 2 </passage> </rel-passage> <category>A</category> <rel-claims>1,4,8,15,16,20,29, 30</rel-claims> </citation> <srep-citations> EPO style: - <country>, <doc-number>: bold - <name>: uppercase, brackets eg. (SMITH) - reformat date to: dd.mm.yyyy eg. 27.12.1988 Notes: - It is NOT expected that the applicant will create the tagged data unless using PatXML or similar (eg. CAF application). - Contractor should capture as specified here --> <!ELEMENT patcit (text | (document-id,rel-passage*)) > <!ATTLIST patcit id ID #IMPLIED num CDATA #IMPLIED dnum CDATA #IMPLIED dnum-type CDATA #IMPLIED file CDATA #IMPLIED url CDATA #IMPLIED > <!-- Relevant passage group within patent; most used in search reports see example above --> <!ELEMENT rel-passage (text | (passage+,(category,rel-claims?)*)) > <!-- Passage within the cited patent literature see example above --> <!ELEMENT passage (#PCDATA) > <!-- Category - see example above Categories indicating cited documents (references) of particular relevance, for the EPO: Category X: particularly relevant if taken alone; Y: particularly relevant if taken combined with another document of the same category A: technological background O: non-written disclosure P: intermediate document T: theory or principle underlying the invention E: earlier patent document, but published on ,or after the filing date; D: document cited in the application L: document cited for other reasons &: member of the same patent family, corresponding document For translations see relevant documentation (Rules) or examples in espacenet --> <!ELEMENT category (#PCDATA) > <!--Relevant claims see example above --> <!ELEMENT rel-claims (#PCDATA) > <!-- ******************************* NPLCIT ******************************* Non-Patent Literature (NPL) CITation; Notes: This can be free text data without any structure -<text>(#PCDATA) which is NOT recommended or it can be highly structured data which is marked up (generally) according to ST.14 and ISO 690 layout. This is one of the most diffcult areas to standardise as there is no concensus regarding the best way to layout a bibliographic citation. We generally adopt to WIPO ST.14 and AACR2 This part of the DTD has used many different sources for element names and DTD structure and reference: AACR2 / MARC ISO 12083 - Electronic manuscript prep. and markup. DTD Association of American Publishers (AAP) Z39.59 DTD European Working Group for SGML (EWS) MAJOUR DTD SuperJournal Full Article DTD www.superjournal.ac.uk/sj Elsevier DTD Medline DTD (NLM) Attributes (recommended): id - ncit0001, ncit0002, etc for the SR: sr-ncit0001 num - 0001, 0002 npl-type - The TYPE of citation is office specific (recommended):; a - Abstract citation of no specific kind b - Book citation i - Bilogical abstract citation c - Chemical abstracts citation e - Database citation d - Derwent citation p - Patent cited within NPL group j - Patent Abstracts of Japan citation (REC 067) s - Serial / Journal / Periodical citation w - World Wide Web / Internet search citation medium - the type of medium e.g., online, dvd, cd (CD-ROM), mt (magnetic tape), disk, file - file name on local systems eg. XP number in EPO url - where possible give full web link to document EPO and PatXML usage: id="ncit0001" for the SR: id="sr-ncit0001" num="0001" npl-type="s" etc --> <!ELEMENT nplcit ((text | article | book | online | othercit), rel-passage*) > <!ATTLIST nplcit id ID #IMPLIED num CDATA #IMPLIED lang CDATA #IMPLIED file CDATA #IMPLIED npl-type CDATA #IMPLIED medium CDATA #IMPLIED url CDATA #IMPLIED > <!-- ******************************* ARTICLE CITATION ******************************* Article citations within a 'host' document After patent citations the most common citations are articles within serials (periodicals, magazines), books and electronic (eg. internet) sources). This is a very complex and varied area to standardise. The tag set below is drawn from a number of sources as is the order of the tags (which in any case can be changed depending on the stylesheet used). EPO and PatXML usage: id="ncit0001" or id="sr-ncit0001" num="0001" npl-type="s" The order of tags is (generally) that of WIPO ST.14 / ISO 690 layout: Examples: DROP, J.G. Integrated Circuit Personalization at the Module Level. IBM tech. dis. bull. October 1974, Vol.17, No.5, pages 1344 and 1345, ISSN 2345-6789. [XPnnnnnnnnnnn]. As a *Search Report* citation the markup is: <citation id="sr-cit0012"> <nplcit id='sr-ncit0012' num='0012' npl-type='s' file='XP1234456'> <article> <author> <name>DROP, J.G.</name> </author> <atl>Integrated Circuit Personalization at the Module Level</atl> <serial> <sertitle>IBM Tech. Dis. Bull.</sertitle> <pubdate>October 1974</pubdate> <vid>Vol. 17</vid> <ino>No. 5</ino> <issn>2345-6789</issn> </serial> <refno>XP1234456</refno> </article> <rel-passage> <passage>pages 1344 and 1345</passage> </rel-passage> </nplcit> </citation> Outside the SR it would be (after </serial>): <location> <pp>pages. 1344 and 1345</pp> </location> BIOLOGICAL ABSTRACTS, vol. 1, 1996 Philadelphia, PA, US; abstract no. 193987, SEVENIER, ROBERT ET AL: "Ethylene production and involvement during the first steps of durum wheat (Triticum durum) anther culture." XP002133847 <citation id="sr-cit0001"> <nplcit id="sr-ncit0001" num="0001" npl-type"i"> <article> <author><name>SEVENIER, ROBERT ET AL</name><author> <atl>"Ethylene production and involvement during the first steps of durum wheat (Triticum durum) anther culture."</atl> <serial> <sertitle>BIOLOGICAL ABSTRACTS</sertitle> <imprint><text>Philadelphia, PA, US</text></imprint> <pubdate>1996</pubdate> <vid>vol. 1</vid> </serial> <absno>abstract no. 193987</absno> <refno>XP002133847</refno> </article> </nplcit> </citation> Note: it is NOT expected that the applicant will create the tagged data - it can be generated from a 'pull down' data entry form (eg. in Word) or generated from internal SR databases or use PatXML. In the EPO for the SR we extract from the SDMS database. . --> <!ELEMENT article (text | (author*,atl?,subname*,(serial | book),absno?,location?, class*,keyword*,cpyrt?,artid?,refno*)) > <!--Author author: Person or corporate body responsible for the intellectual or artistic content of a document. [ISO 690:1987] There is no distinguishing between personal and corporate authors <author> followed by name or addressbook information use the ID attribute if, for example, there is a need to distinguish between multiple authors. Can also include affiliation details Recommended id="auth01", etc. --> <!ELEMENT author (%name_group; | addressbook) > <!ATTLIST author id ID #IMPLIED > <!--Article title --> <!ELEMENT atl (#PCDATA) > <!--Subordinate responsibility; e.g., editor, translator, etc. --> <!ELEMENT subname (%name_group; | addressbook) > <!ATTLIST subname subname-type (editor | translator | other-subname-type) "editor" > <!--Edition statement eg. 2nd edition --> <!ELEMENT edition (#PCDATA) > <!--Serial citation data: Serial: Publication, in any medium, issued in successive parts, usually having numeric or chronological designations, and intended to be continued indefinitely. [Adapted from ISO 3297:1986] This describes the volume or issue as a whole and not a particular article within it. --> <!ELEMENT serial (sertitle,alttitle?,subname*,issue?,imprint?,pubdate?,descrip?, notes?,pubid?,vid?,ino?,doi?,issn?,isbn?,cpyrt?) > <!-- Serial title; the host document: host document: Document containing contributions or separately identifiable component parts that are not physically or bibliographically independent. [ISO 690:1987] --> <!ELEMENT sertitle (#PCDATA) > <!--Alternate title for serial; e.g. BMJ = British Medical Journal --> <!ELEMENT alttitle (#PCDATA) > <!--Issue designation; Examples: - Annual - 1971- - 1890-1972 --> <!ELEMENT issue (#PCDATA) > <!--Imprint: Publication / creation data Place of publication : publisher, date(s) of publication usually only date of publication is used for journal citations --> <!ELEMENT imprint (text | (address?,name,pubdate*)) > <!--Publication date used in npl citations, may be structured or unstructured --> <!ELEMENT pubdate (#PCDATA | sdate | edate | time)* > <!--Start date used in pubdate --> <!ELEMENT sdate (#PCDATA) > <!--End date used in pubdate --> <!ELEMENT edate (#PCDATA) > <!--Time; format HHMM --> <!ELEMENT time (#PCDATA) > <!-- This element is used for the physical description of a book or serial; it pagination, size, whether it is illustrated, etc - generally NOT used in citations in patents. Therefore there is no detailed breakdown of the possible lower elements such as physical size. Example: xxvi, 233 p.: ill; 27cm --> <!ELEMENT descrip (#PCDATA) > <!--Notes about the serial; e.g. Continues Journal of XYZ 1910-1998, published in French and English, etc. --> <!ELEMENT notes (#PCDATA) > <!--Publisher's unique id --> <!ELEMENT pubid (#PCDATA) > <!--Volume id/number --> <!ELEMENT vid (#PCDATA) > <!--Issue number --> <!ELEMENT ino (#PCDATA) > <!-- The Digital Object Identifier (DOI) is a system for identifying content objects in the digital environment. DOIs are names assigned to any entity for use on digital networks. They are used to provide current information, including where they (or information about them) can be found on the Internet. Information about a digital object may change over time, including where to find it, but its DOI will not change. The DOI system provides a framework for persistent identification, managing intellectual content, managing metadata, linking customers with content suppliers, facilitating electronic commerce, and enabling automated management of media. DOIs can be used for any form of management of any data, whether commercial or non-commercial. see: http://www.doi.org/index.html ** Added 09-03-2006 PB (PFC) --> <!ELEMENT doi (#PCDATA) > <!--International Standard Serial Number --> <!ELEMENT issn (#PCDATA) > <!--International Standard Book Number --> <!ELEMENT isbn (#PCDATA) > <!--Copyright info. Copyright of publisher of serial --> <!ELEMENT cpyrt (#PCDATA) > <!-- ******************************* BOOK (MONOGRAPH) CITATION ******************************* Non-serial bibliographic item, i.e. an item either complete in one part or complete (or intended to be completed) in a finite number of separate parts. [ISO 690:1987] As mentioned the style and manner of actual display/printing varies greatly (even between standards!). Generally in the order specified by WIPO ST.14 and ISO 690 and AACR2 rules for layout EPO and PatXML usage: id="ncit0001" num="0001" npl-type="b" Example: (citation from ST.14). WALTON, Herrmann. Microwave Quantum Theory. London: Sweet and Maxwell, 1973, Vol.2, ISBN 5-1234-5678-9, pages 138 to 192, especially pages 146 to 148. As a *Search Report* citation the markup is: <srep-citations> <citation> <nplcit id='ncit0013' num='0013' type='b'> <book> <author> <name>WALTON, Herrman</name> </author> <book-title>Microwave quantum theory</book-title> <imprint> <address> <text>London</text> </address> <name>Sweet and Maxwell</name> <pubdate>1973</pubdate> </imprint> <vid>Vol. 2</vid> <isbn>ISBN 5-1234-5678-9</isbn> </book> </nplcit> <rel-passage>pages 138 to 192, especially pages 146 to 148</rel-passage> </citation> </srep-citations> In other citations the <rel-passage> would be replaced by the <location> tag after <vid>. --> <!ELEMENT book (text | (author*,(book-title+ | conference),(subtitle?,subname*, edition?,imprint?,vid?,ino?,descrip?,series?,notes?,absno?,location*,pubid?, bookno?,class*,keyword*,cpyrt?,doi?,issn?,isbn*,refno*))) > <!--The title of the cited book --> <!ELEMENT book-title (#PCDATA) > <!-- ******************************* CONFERENCE CITATION ******************************* There is no standard way of citing conference proceedings; date of the conf. may come before or after place, for example. The tags are specified in a set order where it is not possible or correct then simply use <text>. Note: not in current version of PatXML --> <!ELEMENT conference (text | (conftitle, confdate?,confno?,confplace?,confsponsor*)) > <!--Conference title --> <!ELEMENT conftitle (#PCDATA) > <!--Conference date; if there is only one date or it is unclear use date; otherwise use start and end dates - sdate, edate --> <!ELEMENT confdate (date | (sdate, edate)) > <!--Conference number --> <!ELEMENT confno (#PCDATA) > <!--Conference place --> <!ELEMENT confplace (#PCDATA | address)* > <!--Conference sponsor --> <!ELEMENT confsponsor (#PCDATA | addressbook)* > <!-- ******************************* Book subtitle --> <!ELEMENT subtitle (#PCDATA) > <!-- ******************************* SERIES ******************************* Series statement --> <!ELEMENT series (text | (mst,msn?,issn?)) > <!--Monographic series title --> <!ELEMENT mst (#PCDATA) > <!--Monographic series number --> <!ELEMENT msn (#PCDATA) > <!--Abstract number --> <!ELEMENT absno (#PCDATA) > <!-- ******************************* LOCATION ******************************* Location of the reference within the cited work --> <!ELEMENT location (text|(serpart?,sersect?,chapter?,pp*,column?,para?,line?)) > <!--Part within a serial or book; or the book part --> <!ELEMENT serpart (#PCDATA) > <!--Serial section or book; or the book section --> <!ELEMENT sersect (#PCDATA) > <!--Chapter; normally in a book. Example: Chapter 2 --> <!ELEMENT chapter (#PCDATA) > <!--Cited document page numbers --> <!ELEMENT pp (#PCDATA | ppf | ppl)* > <!--Cited document page first --> <!ELEMENT ppf (#PCDATA) > <!--Cited document page last --> <!ELEMENT ppl (#PCDATA) > <!--Cited document column numbers --> <!ELEMENT column (#PCDATA | colf | coll)* > <!--Cited document column first --> <!ELEMENT colf (#PCDATA) > <!--Cited document column last --> <!ELEMENT coll (#PCDATA) > <!--Referenced paragraph within cited work --> <!ELEMENT para (#PCDATA | paraf | paral)* > <!--Cited paragraph first --> <!ELEMENT paraf (#PCDATA) > <!--Cited paragraph last --> <!ELEMENT paral (#PCDATA) > <!--Referenced line within cited work --> <!ELEMENT line (#PCDATA | linef | linel)* > <!--Cited document line first --> <!ELEMENT linef (#PCDATA) > <!--Cited document line last --> <!ELEMENT linel (#PCDATA) > <!-- ******************************* Book number --> <!ELEMENT bookno (#PCDATA) > <!--Keyword; e.g., from a Thesaurus or class. scheme (ST.32:B550) --> <!ELEMENT keyword (#PCDATA) > <!--Reference number (general); for the EPO this is the XP number --> <!ELEMENT refno (#PCDATA) > <!ATTLIST refno id ID #IMPLIED > <!-- Article unique ID - assigned by a eg. publisher to an article --> <!ELEMENT artid (#PCDATA) > <!-- ******************************* ONLINE CITATION ******************************* Online citations Revised according to ISO-690-2 - Electronic documents and parts thereof. Please refer to this standard for definitions and examples. See: http://www.nlc-bnc.ca/iso/tc46sc9/standard/690-2e.htm#Contents The tagging in fact is a mixture of article and book tags together with specific electronic source tags. 'online' is taken to mean ANY kind of electronic documentation: databases, internet, CD-Roms, DVD, email, etc EXAMPLES:; * Complete monograph Kirk-Othmer Encyclopedia of Chemical Technology [online]. 3rd ed. New York : John Wiley, 1984 [cited 3 January 1990]. Available from: DIALOG Information Services, Palo Alto (Calif.). <nplcit id='ncit0001' num='0001' type="e" medium='online'> <online> <online-title>Kirk-Othmer Encyclopedia of Chemical Technology </online-title> <edition>3rd ed.</edition> <imprint> <address> <text>New York</text> </address> <name>John Wiley</name> <pubdate>19840000</pubdate> </imprint> <avail>DIALOG Information Services, Palo Alto (Calif.).</avail> <datecit> <date>19900103</date> </datecit> </online> </nplcit> * Article on the Internet: Clark, Carol. On the Threshold of a Brave New World. In Blueprint of the Body [online]. CNN.com, 2000. [cited 24 August 2000;10:25 EST]. In-depth specials. Available from: [http://www.cnn.com/SPECIALS/2000/genome/story/overview/] <nplcit id='ncit0002' num='0002' type='e' medium='online'> <online> <author> <name>Clark, Carol</name> </author> <online-title>On the Threshold of a Brave New World</online-title> <imprint> <name>CNN.com, </name> <pubdate>2000</pubdate> </imprint> <series> <text>In-depth specials</text> </series> <avail>Available from: [http://www.cnn.com/SPECIALS/2000/genome/story/overview/]</avail> <datecit> <date>[cited 24 August 2000;10:25 EST]</date> </datecit> </online> </nplcit> * Personal communication (e-mail) Thacker, Jane. MPEG-21 project stream on digital item identification [online]. Message to: [iso.tc46.sc9@nlc-bnc.ca]. 3 October 2000; 13:33 EST [cited 6 October 2000; 13:10 EST]. Message-ID: [002f01c02d60$051a64a0$22a2580c@vaio]. Personal communication. <nplcit id='ncit0003' num='0003' type='e' medium='online'> <online> <author> <name>Thacker, Jane</name> </author> <online-title>MPEG-21 project stream on digital item identification </online-title> <subname> <name>Message to: <iso.tc46.sc9@nlc-bnc.ca></name> </subname> <pubdate>3 October 2000; 13:33 EST</pubdate> <notes>Personal communication</notes> <avail>Message-ID: <002f01c02d60$051a64a0$22a2580c@vaio></avail> <datecit><date>6 October 2000; 13:10 EST</date></datecit> </online> </nplcit> Note: not covered in current version of PatXML --> <!ELEMENT online (text | (author*,online-title*,hosttitle?,subname*,edition?,( serial | book)?,imprint?,pubdate?,vid?,ino?,history?,series?,hostno?,absno?,location?, notes?,avail*,class*,keyword*,cpyrt?,doi?,issn?,isbn?,datecit?,srchterm*, srchdate?,refno*)) > <!-- author --> <!--The title within the electronic resource, equal to <atl> and <book-title> --> <!ELEMENT online-title (#PCDATA) > <!--Title of the host document/database --> <!ELEMENT hosttitle (#PCDATA) > <!-- subnane --> <!--History of the article (not serial) --> <!ELEMENT history (text | (received | accepted | revised | misc)) > <!--Date article was received --> <!ELEMENT received (date) > <!--Date article was accepted --> <!ELEMENT accepted (date) > <!--Date article was revised --> <!ELEMENT revised (date) > <!--Miscellaneous information relating to the history of the article; see ISO 12083 --> <!ELEMENT misc (#PCDATA | date)* > <!--Numeration within host document --> <!ELEMENT hostno (#PCDATA) > <!--Availability and access - REQUIRED use for URL, online database, ftp address, email, etc.; Examples: - Available from Internet: http://www.epoline.org - Available from DIALOG Information Systems, Palo Alto (Calif.) - Available from: <http://www.ejb.org/content/vol2/issue3/full/3/index.html>. - Available from Bell and Howell Information and Learning via e-mail to: <umi@ppp.nasionet.net>. --> <!ELEMENT avail (#PCDATA) > <!--Date cited - date on which the citation was cited. May be different from srchdate below --> <!ELEMENT datecit (date) > <!--Search terms --> <!ELEMENT srchterm (#PCDATA) > <!--Date of search/retrieval YYYYMMDD --> <!ELEMENT srchdate (date) > <!-- ******************************* OTHER CITATIONS ******************************* Other citations - free form --> <!ELEMENT othercit (#PCDATA | b | i | u | o | sup | sub)* > <!-- ******************************* SR - INCOMPLETE SEARCH ******************************* --> <!-- The element is to process EPO SR (old) FORM 1503 partial SR - Incomplete Search (sheet C (old style)); for example see: EP 99305342, 07108155 Note: model altered after consultations internally 2005-06-16 - srep- added for consistency 2008-02-06 PB (needs WIPO PFC) +++++++++++++++++++++++++++++++++++++++ ** EPO layout: INCOMPLETE SEARCH The Search Division considers that the present application, or one or more of the claims, does/do not comply with the EPC to such an extent that a meaningful search into the state of the art cannot be carried out, or can only be carried out partially for these claims: UNVOLLSTÄNDIGE RECHERCHE Die Recherchenabteilung ist der Auffassung, dass ein oder mehrere Anspruche, den Vorschriften den EPU in einem solchen Umfang nicht entspricht bzw. entsprechen, dass sinnvolle Ermittlungen über den Stand der Technik für diese Ansprüche nicht, bzw. nur teilweise, möglich sind. RECHERCHE INCOMPLETE La division de la recherche estime que la présente demande de brevet, oo une ou plusieurs revendications, ne sont pas conformes aux dispositions de la CBE au point qu'une recherche significative sur I' état de la technique ne peut être effectuée, ou seulement partiellement, au regard de ces revendications. then one of the the following data elements --> <!ELEMENT srep-incomplete-search (text | limitation-of-search+) > <!-- EPO: EPC Rule 45, EPC 2000 Rule 63, cases Most often the examiner uses a so-called Sheet C to enter the various reasons. This is a bit complicated and why we have changed the model and added the grouping element <limitation-of-search> which is repeatable. <text> can be used for any leading text. The attributes are implied and therefore need not necessarily be used if it is a simple case and sheet C is not used; otherwise: use: - sequence="1" etc to keep the order and "2" could generate: "Further limitation of the search" - reason-type="reasonpatentability" or "reasonobscurity" or "remark" --> <!ELEMENT limitation-of-search (text?,claims-searched*,claims-searched-incompletely*, claims-not-searched*,reason-limited-search*) > <!ATTLIST limitation-of-search sequence CDATA #IMPLIED reason-type CDATA #IMPLIED > <!-- +++++++++++++++++++++++++++++++++++++++ ** EPO layout: Claims searched completely: Vollständig recherchierte Ansprüche: Revendications ayant fait l objet de recherches complètes: --> <!ELEMENT claims-searched (#PCDATA) > <!-- +++++++++++++++++++++++++++++++++++++++ ** EPO layout: Claims searched incompletely: Unvollständig recherchierte Ansprüche: Revendications ayant fait l objet de recherches incomplètes: --> <!ELEMENT claims-searched-incompletely (#PCDATA) > <!-- +++++++++++++++++++++++++++++++++++++++ ** EPO layout: Claims not searched: Nicht recherchierte Ansprüche: Revendications n ayant pas fait l objet de recherches: --> <!ELEMENT claims-not-searched (#PCDATA) > <!-- +++++++++++++++++++++++++++++++++++++++ ** EPO layout: Reason for the limitation of the search: Grund für die Beschrankung der Recherche: Raison pour la limitation de la recherche: EPO usage: - This must have some text in it and use the <p> tag - the optional <heading> tag can be used for text such as: "Reason for the limitation of the search" - if p id is used then number as <p id="prs0001" num=0001", "prs0002" num="0002", etc. --> <!ELEMENT reason-limited-search (heading?,p+) > <!-- srep-declaration ******************************* SR - DECLARATION ******************************* EPC Rule 45 (old EPC) 63 (EPC2000) Declaration cases (old Form 1504 (P04F37)) - in route element srep-type="ep-Rule45declaration-sr" - in route element srep-type="ep-Rule63declaration-sr" from 13.12.2007 - these have no citations just old Form 1504 (see EP 04291864) so <srep-fields-searched><minimum-documentation/> is EMPTY <srep-citations><text/> is EMPTY - use this data element and boilerplate text (see below), heading, follwed by text of the examiner Note: model added for better handling of these cases 2008-02-06 PB (needs WIPO PFC) +++++++++++++++++++++++++++++++++++++++ ** EPO (new) layout: DECLARATION Application number: 99109696.7 which under Rule 45 of the European Patent Convention shall be considered, for the purposes of subsequent proceedings, as the European search report after 13.12.2007: which under Rule 63 of the European Patent Convention shall be considered, for the purposes of subsequent proceedings, as the European search report Classification of the application: G06F17/30 The Search Division considers that the present application, does not comply with the provisions of the EPC to such an extent that it is not possible to carry out a meaningful search into the state of the art on the basis of all claims <heading>Reason:</heading> ERKLÄRUNG die nach Regel 45 des Europäischen Patentübereinkommens für das weitere Verfahren als europäischer Recherchenbericht gilt after 13.12.2007: ERKLÄRUNG die nach Regel 63 des Europäischen Patentübereinkommens für das weitere Verfahren als europäischer Recherchenbericht gilt Die Recherchenabteilung ist der Auffassung, dass die vorliegende Patentanmeldung den Vorschriften des EPÜ in einem solchen Umfang nicht entspricht, dass sinnvolle Ermittlungen über den Stand der Technik auf der Grundlage aller Patentansprüche nicht möglich sind. <heading>Grund:</heading> DECLARATION Numéro de Ia demande qui selon Ia règle 45 de Ia Convention sur le brevet européen est considerée, aux fins de Ia procedure ulterieure, comme le rapport de Ia recherche européenne after 13.12.2007: qui selon Ia règle 63 de Ia Convention sur le brevet européen est considerée, aux fins de Ia procedure ulterieure, comme le rapport de Ia recherche européenne Classement de la demande La division de Ia recherche estime que Ia presente demande de brevet n est pas conforme aux dispositions de Ia CBE au point qu une recherche significative sur I état de Ia technique ne peut être effectuée au regard de toutes es revendications <heading>Raison:</heading> followed by text entered by examiner as: <p id="pd0001" num="0001">, <p id="pd0002" num="0002">, etc. --> <!ELEMENT srep-declaration (heading?,p+) > <!-- srep-admin ******************************* SR - ADMINISTRATIVE DETAILS ******************************* +++++++++++++++++++++++++++++++++++++++ ** EPO (new) layout: Examiner: Gourier. P, The Hague Date of completion of the search: 15.02.2000 ** END OF SEARCH REPORT ** +++++++++++++++++++++++++++++++++++++++ Example: <srep-admin> <examiners> <primary-examiner> <name>Schroeder, R</name> </primary-examiner> </examiners> <srep-office> <addressbook> <text>DH/text> </addressbook> </srep-office> <date-search-completed><date>20050309</date></date-search-completed> </srep-admin> +++++++++++++++++++++++++++++++++++++++ PCT example layout: ISA/Examiner: EPO DE LAERE, Ann PB 5818, Patentlaan 2 NL 2280 HV Rijswijk Tel. +31 - 70 340 2040 Fax. +31 - 70 340 3016 Search completed: 10 August 1992 ISR mailed: 24 August 1992 +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT srep-admin (examiners?,srep-office?,date-search-completed,date-search-report-mailed?) > <!-- International Search Authority; international search to be carried out by --> <!ELEMENT srep-office (addressbook) > <!--Date of completion of search report. This is mandatory for EP SRs --> <!ELEMENT date-search-completed (date) > <!--Date of mailing of search report. (ST.32:B566) --> <!ELEMENT date-search-report-mailed (date) > <!--(ST.32:B568) --> <!ELEMENT search-report-publication (document-id+) > <!--Search report examiner. (ST.32:B569) --> <!ELEMENT searcher (%name_group; | addressbook) > <!--Persons acting on the document. (ST.32:B745) --> <!ELEMENT examiners (primary-examiner?,assistant-examiner?,authorized-officer?) > <!--Primary Examiner. (ST.32:B746) --> <!ELEMENT primary-examiner (%name_group;,electronic-signature?) > <!-- ******************************* SR - PATENT FAMILY (old EP forms PO459, 460, 461) ******************************* +++++++++++++++++++++++++++++++++++++++ ** EPO layout: ANNEX - PATENT FAMILY INFORMATION This section lists the patent family members relating to the patent documents cited above. The members are as contained in the European Patent Office computer file on: <date-search-completed> The European Patent Office is in no way liable for these particulars which are merely given for the purpose of information. ANHANG - PATENTTAMILIEN INFORMATION In diesem Anhang sind die Mitglieder der Patentfamilien der im obengenannten Patentdokumente angegeben. Die Angaben über die Familienmitglieder entsprechen dem Stand der Datei des Europäischen Patentamts am: <date-search-completed> Diese Angaben dienen nur zur Unterlichtung und erfolgen ohne Gewähr. ANNEXE AU RAPPORT DE RECHERCHE EUROPEENNE La présente annexe indique les membres de Ia famille de brevets relatifs aux documents brevets cites dans le rapport de reoherohe européenne visé oi-dessus. Lesdits members sent oontenua au fiohier informatique de l'Office européen dee brevets a la date du Lea renseignements tournis sont donnée a titre indicatif et n engagent pas la responsabilité de l'Office européen des brevets. +++++++++++++++++++++++++++++++++++++++ PCT: This is the old 210 (patent family annex) Patent family information according to WIPO ST.14 +++++++++++++++++++++++++++++++++++++++ Example: <srep-patent-family> <patent-family> <priority-application> <document-id> <country>US</country> <doc-number>6089831</doc-number> <kind>A</kind> <date>20000718</date> </document-id> </priority-application> <family-member> <document-id> <country>DE</country> <doc-number>19515895</doc-number> <kind>A1</kind> <date>19961031</date> </document-id> </family-member> </patent-family> </srep-patent-family> --> <!ELEMENT srep-patent-family (text?,patent-family+) > <!-- Patent family and corresponding-docs - see example above These are also "&" cases. ** PB 2006-03-02 --> <!ELEMENT corresponding-docs ((patcit | nplcit),(rel-passage*,category*, rel-claims*)*) > <!-- ******************************************************************************* END OF EP SR The following elements (to maths section) are for PCT (ISR) use only and are kept in if EPO use this DTD to process ISR data or need to be added to the EP SR. ******************************************************************************* --> <!-- +++++++++++++++++++++++++++++++++++++++ PCT ISR Form PCT/ISA/220 (January 2004) Old form check box 3 +++++++++++++++++++++++++++++++++++++++ srep-protest-fees: With regard to the protest against payment of (an) additional fee(s) under Rule 40.2, the applicant is notified that: if yes: the protest together with the decision thereon has been transmitted to the International Bureau together with the applicant's request to forward the texts of both the protest and the decision thereon to the designated Offices. if no: no decision has been made yet on the protest; the applicant will be notified as soon as a decision is made. - Sytlesheet note: this data is followed by Reminders and Notes (if printed) otherwise put a link in to the relevant text. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT srep-protest-fees EMPTY > <!ATTLIST srep-protest-fees srep-protest (yes | no) "yes" > <!--Date of request for search eg. on PCT Form 201 --> <!ELEMENT srep-request-date (date) > <!--Search request number eg. on PCT Form 201. --> <!ELEMENT srep-request-number (#PCDATA) > <!-- +++++++++++++++++++++++++++++++++++++++ This part preceded by - on old PCT/ISA/210 : This international search report has been prepared by this ISA and is transmitted to the applicant according to Article 18. A copy is being transmitted to the International Bureau. This international search report consists of a total of ______ sheets. It is also accompanied by a copy of each prior art document cited in this report. (This text will need modification for electronic transmission of the SR). If the attribute value is "yes" then the prior art may accompany the SR as paper, image data, or xml (application-body) data. THIS HAS TO BE WORKED OUT! +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT srep-prior-art-docs (doc-page | prior-art-xml-doc)* > <!ATTLIST srep-prior-art-docs prior-art (yes | no) #REQUIRED > <!--XML version prior art document, if any To be checked may be application-body. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT prior-art-xml-doc EMPTY > <!ATTLIST prior-art-xml-doc id ID #IMPLIED file CDATA #REQUIRED lang CDATA #IMPLIED carriers (internal-electronic | external-electronic | paper) #IMPLIED status CDATA #IMPLIED > <!-- +++++++++++++++++++++++++++++++++++++++ PCT ISR PCT/ISA/210 Box 1::Basis of the Report +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT srep-basis (basis-language-for-search,sequence-list-basis?) > <!-- +++++++++++++++++++++++++++++++++++++++ PCT ISR PCT/ISA/210 (Box 1a) Basis of the Report With regard to the language, the international search was carried out on the basis of: (check box ) the international application in the language in which it was filed = attribute value = "no" (check box) a translation of the international application into _____ which is the language of a translation furnished for the purposes of international search (Rules 12.3(a) and 23.1(b)) if "yes" then lang attribute may be used +++++++++++++++++++++++++++++++++++++++ EPO --> <!ELEMENT basis-language-for-search EMPTY > <!ATTLIST basis-language-for-search translation (yes | no) "no" lang CDATA #IMPLIED> <!-- PCT/ISA/210 ((Box 1b) Basis of the Report)) +++++++++++++++++++++++++++++++++++++++ Nucleotide and/or amino acid sequence(s) +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT sequence-list-basis (material-of-sequence-list, presentation-of-statements?,additional-info?) > <!-- (PCT/ISA/210 Box No. I Nucleotide and/or amino acid sequence(s) (Continuation of item1.b of the first sheet)) (PCT/ISA/237 Box No. I, No. 2,3,4). +++++++++++++++++++++++++++++++++++++++ 1. With regard to any nucleotide and/or amino acid sequence disclosed in the international application and necessary to the claimed invention, the international search was carried out on the basis of: (PCT/ISA/237 Box No. I) Basis of this opinion 2. With regard to any nucleotide and/or amino acid sequence disclosed in the international application and necessary to the claimed invention, this opinion has been established on the basis of: (PCT/IPEA/409 Supplemental Box Relating to Sequence Listing) 1. With regard to any nucleotide and/or amino acid sequence disclosed in the international application and necessary to the claimed invention, this report was established on the basis of: (PCT/IPEA/408 Supplemental Box Relating to Sequence Listing) 1. With regard to any nucleotide and/or amino acid sequence disclosed in the international application and necessary to the claimed invention, this opinion was established on the basis of: +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT material-of-sequence-list (sequence-listing-material-type, sequence-listing-material-format,sequence-listing-filing-time) > <!-- +++++++++++++++++++++++++++++++++++++++ a. type of material if 1 = a sequence-listing if 2 = table(s) related to the sequence listing +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT sequence-listing-material-type EMPTY > <!ATTLIST sequence-listing-material-type material-type (1 | 2) #IMPLIED > <!-- +++++++++++++++++++++++++++++++++++++++ b. format of material if 1 = on paper if 2 = in electronic form +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT sequence-listing-material-format EMPTY > <!ATTLIST sequence-listing-material-format material-format (1 | 2) #IMPLIED > <!-- +++++++++++++++++++++++++++++++++++++++ c. time of filing/furnishing in-application = contained in the international application as filed together-with-application = filed together with the international application in electronic form furnished-for-search = furnished subsequently to this Authority for the purposes of search and/or examination as-amended = received by this Authority as an amendment* on ___________ (Only Forms PCT/IPEA/408 and 409 (April 2005) +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT sequence-listing-filing-time (#PCDATA) > <!ATTLIST sequence-listing-filing-time time-of-filing (1 | 2 | 3 | 4) #IMPLIED in-application (yes | no ) #REQUIRED together-with-application (yes | no ) #REQUIRED furnished-for-search (yes | no ) #REQUIRED as-amended (yes | no ) #IMPLIED > <!-- +++++++++++++++++++++++++++++++++++++++ (PCT/ISA/210 Box 1, 2 and PCT/ISA/237 ) In addition, in the case that more than one version or copy of a sequence listing and/or table relating thereto has been filed or furnished, the required statements that the information in the subsequent or additional copies is identical to that in the application as filed or does not go beyond the application as filed, as appropriate, were furnished. (PCT/IPEA/409 and PCT/IPEA/408 ) (Supplemental Box Relating to Sequence Listing) 2. In addition, in the case that more than one version or copy of a sequence listing and/or table(s) relating thereto has been filed or furnished, the required statements that the information in the subsequent or additional copies is identical to that in the application as filed or does not go beyon the application as filed, as appropriate, were furnished. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT presentation-of-statements EMPTY > <!--This is a place marker since there may be other information added at a later stage which has not been forseen. --> <!ELEMENT srep-other-info (srep-information+) > <!ELEMENT srep-information (#PCDATA) > <!ATTLIST srep-information srep-code CDATA #IMPLIED > <!-- ******************************* SR WRITTEN OPINION - GENERIC FOR ALL OFFICES EP SR OPINION DATA (FORM 1703) added 28-03-2006 PB ******************************* The PCT srep-written-opinion (see below) is very PCT specific and does not meet the requirements of the EP search opinion which is more free text based; thus we make it more generic for other offices also. EP EESR - Extended European Search Report - THE EUROPEAN SEARCH OPINION That part of the EESR which is the Search Division's opinion on the allowability of the application and the invention to which it relates This data is currently sent to the applicant and is NOT printed as part of an A1, A3 or A9. It is EP data only therefore we create a specific data element. Attribute opinion-type to be used to indicate any different types (office specific) For paragraph id use <p id="pw0001" num="0001"> --> <!ELEMENT srep-search-opinion ((doc-page+) | (heading*,p+)+) > <!ATTLIST srep-search-opinion id ID #IMPLIED opinion-type CDATA #IMPLIED lang CDATA #IMPLIED > <!-- ******************************* PCT SR DATA - MAY remove here as not used as part of EP SR ONLY used for PCT Form 237 ******************************* Note: these are PCT processing instructions +++++++++++++++++++++++++++++++++++++++ PCT WRITTEN OPINION OF THE INTERNATIONAL SEARCHING AUTHORITY (ISA) (PCT Rule 43bis.1) (old FORM PCT/ISA/237) (The following data is taken from srep-info area): - Correspondence address - Date of mailing (day/month/year) - Applicant's or agent's file reference - International application No. - International filing date (day/month/year) - Priority date (day/month/year) - International Patent Classification (IPC) or both national classification and IPC - Applicant name (followed by the text:) FOR FURTHER ACTION If a demand for international preliminary examination is made, this opinion will be considered to be a written opinion of the International Preliminary Examining Authority ( IPEA ) except that this does not apply where the applicant chooses an Authority other than this one to be the IPEA and the chosen IPEA has notified the International Bureau under Rule 66.1bis(b) that written opinions of this International Searching Authority will not be so considered. If this opinion is, as provided above, considered to be a written opinion of the IPEA, the applicant is invited to submit to the IPEA a written reply together, where appropriate, with amendments, before the expiration of 3 months from the date of mailing of Form PCT/ISA/220 or before the expiration of 22 months from the priority date, whichever expires later. For further options, see Form PCT/ISA/220. The followed by office address etc. see <srep-admin> +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT srep-written-opinion (doc-page+ | (basis-of-srep-opinion, priority-opinion?,non-establishment-of-opinion?,unity-of-invention?, pct-rule43bis-statement,opinion-citations,defect-in-application?, observation-on-application?,text*)) > <!-- Form PCT/ISA/237 (Box No. I) (April 2005) Basis of this opinion --> <!ELEMENT basis-of-srep-opinion (translation-of-appl?,sequence-list-basis?) > <!-- +++++++++++++++++++++++++++++++++++++++ Basis of this opinion 1. With regard to the language, this opinion has been established on the basis of: (check box) the international application in the language in which it was filed (check box) a translation of the international application into ____________ , which is the language of a translation furnished for the purposes of international search (under Rules 12.3 and 23.1(b)). +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT translation-of-appl EMPTY > <!ATTLIST translation-of-appl translation (yes | no) 'no' lang CDATA #IMPLIED > <!-- Followed by <sequence-list-basis> data --> <!--(PCT/ISA/237 - Box II) - Priority --> <!ELEMENT priority-opinion (earlier-appl?,claim-invalid?,additional-info?) > <!ATTLIST priority-opinion varid CDATA #IMPLIED > <!-- +++++++++++++++++++++++++++++++++++++++ (PCT/ISA/237 - Box II) +++++++++++++++++++++++++++++++++++++++ Priority This text is from the OLD Form 237: 1. The following document has not yet been furnished: Attribute value: 1 = copy of the earlier application whose priority has been claimed (Rules 43bis.1 and 66.7(a)). 2 = translation of the earlier application whose priority has been claimed (Rules 43bis.1 and 66.7(b)). Consequently it has not been possible to consider the validity of the priority claim. This opinion has nevertheless been established on the assumption that the relevant date is the claimed priority date. From the NEW 237 (2005): (Check box 1): The validity of the priority claim has not been considered because the International Searching Authority does not have in its possession a copy of the earlier application whose priority has been claimed or, where required, a translation of that earlier application. This opinion has nevertheless been established on the assumption that the relevant date (Rules 43bis.1 and 64.1) is the claimed priority date. +++++++++++++++++++++++++++++++++++++++ We leave the element as below (in case old data is processed); for the new case the attribute value will always be "1". --> <!ELEMENT earlier-appl EMPTY > <!ATTLIST earlier-appl prio-code (1 | 2) #REQUIRED > <!-- +++++++++++++++++++++++++++++++++++++++ (PCT/ISA/237 - Box II) (Check box 2) This opinion has been established as if no priority had been claimed due to the fact that the priority claim has been found invalid (Rules 43bis.1 and 64.1). Thus for the purposes of this opinion, the international filing date indicated above is considered to be the relevant date. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT claim-invalid EMPTY > <!-- +++++++++++++++++++++++++++++++++++++++ (PCT/ISA/237 - Box III) +++++++++++++++++++++++++++++++++++++++ Non-establishment of opinion with regard to novelty, inventive step and industrial applicability. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT non-establishment-of-opinion (invention-not-examined, not-annex-c-compliant) > <!-- +++++++++++++++++++++++++++++++++++++++ The questions whether the claimed invention appears to be novel, to involve an inventive step (to be non obvious), or to be industrially applicable have not been examined in respect of: +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT invention-not-examined ((entire-application | claim-num+), non-estab-reason-1?,non-estab-reason-2?,non-estab-reason-3?, non-estab-reason-4?) > <!-- +++++++++++++++++++++++++++++++++++++++ The entire international application. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT entire-application EMPTY > <!-- If not entre-application then the Claim Nos are inserted. +++++++++++++++++++++++++++++++++++++++ The said international application, or the said claims Nos. (insert rel-claims) relate to the following subject matter which does not require an international preliminary examination (specify) +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT non-estab-reason-1 (claim-num*,p+) > <!-- +++++++++++++++++++++++++++++++++++++++ The description, claims or drawings (indicate particular elements below) or said claims Nos (insert rel claims) are so unclear that no meaningful opinion could be formed (specify): +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT non-estab-reason-2 (claim-num*,p+) > <!-- +++++++++++++++++++++++++++++++++++++++ The claims, or said claims Nos. (insert rel claim nos) are so inadequately supported by the description that no meaningful opinion could be formed (specify). +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT non-estab-reason-3 (claim-num*,p+) > <!-- +++++++++++++++++++++++++++++++++++++++ No international search report has been established for said claims Nos. (rel-claims) +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT non-estab-reason-4 (claim-num+) > <!--(PCT/ISA/237 - Box III) --> <!ELEMENT not-annex-c-compliant (annex-c?,annex-c-bis?,additional-info?) > <!-- +++++++++++++++++++++++++++++++++++++++ (check box) a meaningful opinion could not be formed without the sequence listing; the applicant did not, within the prescribed time limit: 1 = furnish a sequence listing on paper complying with the standard provided for in Annex C of the Administrative Instructions, and such listing was not available to the International Searching Authority in a form and manner acceptable to it. 2 = furnish a sequence listing in electronic form complying with the standard provided for in Annex C of the Administrative Instructions, and such listing was not available to the International Searching Authority in a form and manner acceptable to it. 3 = pay the required late furnishing fee for the furnishing of a sequence listing in response to an invitation under Rule 13ter.1(a)or(b). +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT annex-c EMPTY> <!ATTLIST annex-c applicant-did-not (1 | 2 | 3 ) #REQUIRED > <!-- +++++++++++++++++++++++++++++++++++++++ (PCT/ISA/237 and PCT/IPEA/408 ) +++++++++++++++++++++++++++++++++++++++ e-tables-missing = a meaningful opinion could not be formed without the tables related to the sequence listings; the applicant did not, within the prescribed time limit, furnish such tables in electronic form complying with the technical requirements provided for in Annex C-bis of the Administrative Instructions, and such tables were not available to the International Searching Authority in a form and manner acceptable to it. format-error = the tables related to the nucleotide and/or amino acid sequence listing, if in electronic form only, do not comply with the technical requirements provided for in Annex C-bis of the Administrative Instructions. (PCT/IPEA/409 ) The tables related to the nucleotide and/or amino acid sequence listing do not comply with the technical requirements provided for in Annex C-bis of the Administrative Instructions in that the computer readable form: +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT annex-c-bis EMPTY > <!ATTLIST annex-c-bis e-tables-missing (yes | no ) #REQUIRED format-error (yes | no ) #REQUIRED > <!-- (Form PCT/ISA/237 (Box No. IV Lack of unity of invention) (April 2005) Lack of unity of invention (PCT/IPEA/408 - Box No. IV) Lack of unity of invention) --> <!ELEMENT unity-of-invention (invitation-pay-additional-fees?, not-unity-of-invention?,compliance-unity-invention, opinion-established-regarding) > <!-- +++++++++++++++++++++++++++++++++++++++ In response to the invitation (Form PCT/ISA/206) to pay additional fees the applicant has, within the appicable time limit: Attribute values: (PCT/ISA/237 ) 1 = do not use in 237 2 = paid additional fees 3 = paid additional fees under protest and, where applicable, the protest fee 4 = paid additional fees under protest but the applicable protest fee was not paid 5 = not paid additional fees (PCT/IPEA/409, Box IV and PCT/IPEA/408 ) 1 = restricted the claims 2 = paid additional fees 3 = paid additional fees under protest and, where applicable, the protest fee 4 = paid additional fees under protest but the applicable protest fee was not paid 5 = neither restricted the claims nor paid additional fees +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT invitation-pay-additional-fees EMPTY > <!ATTLIST invitation-pay-additional-fees unity-fee-code (1 | 2 | 3 | 4 | 5) #REQUIRED > <!-- +++++++++++++++++++++++++++++++++++++++ (PCT/ISA/237 ) - Box No. IV Lack of unity of invention (2) This Authority found that the requirement of unity of invention is not complied with and chose not to invite the applicant to pay additional fees. (PCT/IPEA/409 ) This Authority found that the requirement of unity of invention is not complied with and chose, according to Rule 68.1, not to invite the applicant to restrict or pay additional fees. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT not-unity-of-invention EMPTY > <!-- +++++++++++++++++++++++++++++++++++++++ (PCT/ISA/237 ) - Box No. IV Lack of unity of invention (3) This Authority considers that the requirement of unity of invention in accordance with Rule 13.1, 13.2 and 13.3 is yes = complied with no = not complied with for the following reasons: +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT compliance-unity-invention (p*) > <!ATTLIST compliance-unity-invention unity-complied (yes | no) #REQUIRED > <!--(PCT/ISA/237 ) - Box No. IV Lack of unity of invention 4. +++++++++++++++++++++++++++++++++++++++ Consequently, this opinion has been established in respect of the following parts of the international application: entire-application = all parts claim-num = the parts relating to claims Nos. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT opinion-established-regarding (entire-application | claim-num+) > <!--(PCT/ISA/237 - Box V) +++++++++++++++++++++++++++++++++++++++ Reasoned statement under Rule 43bis.1(a)(i) with regard to novelty, inventive step or industrial applicability; citations and explanations supporting such statement. 1. Statement Novelty Inventive step Industrial applicability +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT pct-rule43bis-statement (novelty-valid,novelty-not-valid, inventive-step-valid,inventive-step-not-valid,applicability-valid, applicability-not-valid,citations-explanations?) > <!ELEMENT novelty-valid (claim-num*) > <!ELEMENT novelty-not-valid (claim-num*) > <!ELEMENT inventive-step-valid (claim-num*) > <!ELEMENT inventive-step-not-valid (claim-num*) > <!ELEMENT applicability-valid (claim-num*) > <!ELEMENT applicability-not-valid (claim-num*) > <!-- PCT 237 Box V, 2. and 409 +++++++++++++++++++++++++++++++++++++++ Citations and explanations: +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT citations-explanations ((citation+,filing-date,priority-date?) | p+) > <!ELEMENT filing-date (date) > <!-- +++++++++++++++++++++++++++++++++++++++ Rule 70.10: Any published application ... shall be accompanied by ... its claimed priority date (if any). In respect of the priority date of any such document, the report may indicate that, in the opinion of the International Preliminary Examining Authority, such date has not been validly claimed. +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT priority-date (#PCDATA) > <!ATTLIST priority-date priority-valid (yes | no) "yes" > <!-- (PCT/IPEA/408 - Box No. VI Certain documents cited) --> <!ELEMENT opinion-citations (certain-published-documents | non-written-disclosures)* > <!-- +++++++++++++++++++++++++++++++++++++++ (PCT/ISA/237 ) 1. Certain published documents (Rules 43bis.1 and 70.10) (PCT/IPEA/409 and PCT/IPEA/408 ) 1. Certain published documents (Rule 70.10) +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT certain-published-documents ((citation+,filing-date,priority-date?) | text) > <!-- +++++++++++++++++++++++++++++++++++++++ (PCT/ISA/237 ) 2. Non-written disclosures (Rules 43bis.1 and 70.9) (PCT/IPEA/409 and PCT/IPEA/408 ) 2. Non-written disclosures (Rule 70.9) +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT non-written-disclosures (kind-of-disclosure,date, date-of-written-disclosure) > <!--Kind of non-written disclosure --> <!ELEMENT kind-of-disclosure (#PCDATA) > <!--Date of written disclosure Referring to non-written disclosure (day/month/year) --> <!ELEMENT date-of-written-disclosure (date) > <!-- +++++++++++++++++++++++++++++++++++++++ (Form PCT/ISA/237 (Box No. VI) (April 2005), Box No. VII ) Certain defects in the international application The following defects in the form or contents of the international application have been noted: +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT defect-in-application (p+) > <!-- +++++++++++++++++++++++++++++++++++++++ (Form PCT/ISA/237 (Box No. VI) (April 2005), Box No. VIII ) Certain observations on the international application. The following observations on the clarity of the claims, description, and drawings or on the question whether the claims are fully supported by the description, are made: +++++++++++++++++++++++++++++++++++++++ --> <!ELEMENT observation-on-application (p+) > <!-- ******************************************************************************* ******************************* MATHEMATICS ******************************* This is image data or coded according to mathml, version 2 ** Added 2006-02-08 - <text> as alternative to image for very simple maths which do not need rendition and the "heavy coding" of mathml, eg. 2 x 2 = 4 The top-level element "math" contains MathML encoded mathematics. The "math" element has the browser info attributes if it is also the browser interface element. EPO required usage: - id="math0001" - If parent element is abstract: id="matha01" - num="0001", 0002, etc. OR - use the value given by the applicant, usually in parenthesis to the (right) side of the formula, eg. (1) - old SGML files: <DF NUM="(1)"> becomes <maths id="math0001" num="(1)"> if there is no number: <maths id="math0001" num=""> --> <!ELEMENT maths (img | formula-text | (math,img?)) > <!ATTLIST maths id ID #IMPLIED num CDATA #REQUIRED > <!ELEMENT math %MathExpression; > <!ATTLIST math display (block | inline) "inline"> <!--Presentation elements contain PCDATA or malignmark constructs.--> <!ELEMENT mi (#PCDATA | mglyph | malignmark)* > <!ATTLIST mi xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED fontsize CDATA #IMPLIED fontweight (normal | bold) #IMPLIED fontstyle (normal | italic) #IMPLIED fontfamily CDATA #IMPLIED color CDATA #IMPLIED mathvariant CDATA #IMPLIED mathsize CDATA #IMPLIED mathcolor CDATA #IMPLIED mathbackground CDATA #IMPLIED > <!ELEMENT mglyph EMPTY > <!ATTLIST mglyph alt CDATA #IMPLIED fontfamily CDATA #IMPLIED index CDATA #IMPLIED > <!ELEMENT malignmark EMPTY > <!ATTLIST malignmark edge (left | right) #IMPLIED > <!ELEMENT mn (#PCDATA | mglyph | malignmark)* > <!ATTLIST mn xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED fontsize CDATA #IMPLIED fontweight (normal | bold) #IMPLIED fontstyle (normal | italic) #IMPLIED fontfamily CDATA #IMPLIED color CDATA #IMPLIED mathvariant CDATA #IMPLIED mathsize CDATA #IMPLIED mathcolor CDATA #IMPLIED mathbackground CDATA #IMPLIED > <!ELEMENT mo (#PCDATA | mglyph | malignmark)* > <!ATTLIST mo xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED fontsize CDATA #IMPLIED fontweight (normal | bold) #IMPLIED fontstyle (normal | italic) #IMPLIED fontfamily CDATA #IMPLIED color CDATA #IMPLIED mathvariant CDATA #IMPLIED mathsize CDATA #IMPLIED mathcolor CDATA #IMPLIED mathbackground CDATA #IMPLIED form (prefix | infix | postfix) #IMPLIED fence (true | false) #IMPLIED separator (true | false) #IMPLIED lspace CDATA #IMPLIED rspace CDATA #IMPLIED stretchy (true | false) #IMPLIED symmetric (true | false) #IMPLIED maxsize CDATA #IMPLIED minsize CDATA #IMPLIED largeop (true | false) #IMPLIED movablelimits (true | false) #IMPLIED accent (true | false) #IMPLIED > <!ELEMENT mtext (#PCDATA | mglyph | malignmark)* > <!ATTLIST mtext xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED fontsize CDATA #IMPLIED fontweight (normal | bold) #IMPLIED fontstyle (normal | italic) #IMPLIED fontfamily CDATA #IMPLIED color CDATA #IMPLIED mathvariant CDATA #IMPLIED mathsize CDATA #IMPLIED mathcolor CDATA #IMPLIED mathbackground CDATA #IMPLIED > <!ELEMENT ms (#PCDATA | mglyph | malignmark)* > <!ATTLIST ms xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED fontsize CDATA #IMPLIED fontweight (normal | bold) #IMPLIED fontstyle (normal | italic) #IMPLIED fontfamily CDATA #IMPLIED color CDATA #IMPLIED mathvariant CDATA #IMPLIED mathsize CDATA #IMPLIED mathcolor CDATA #IMPLIED mathbackground CDATA #IMPLIED lquote CDATA #IMPLIED rquote CDATA #IMPLIED > <!ELEMENT mspace EMPTY > <!ATTLIST mspace width CDATA #IMPLIED height CDATA #IMPLIED depth CDATA #IMPLIED linebreak CDATA #IMPLIED xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT mrow %PresExpression; > <!ATTLIST mrow xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT mprescripts EMPTY > <!ELEMENT none EMPTY > <!ELEMENT mfrac %twoPresExpression; > <!ATTLIST mfrac xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED bevelled CDATA #IMPLIED numalign CDATA #IMPLIED denomalign CDATA #IMPLIED linethickness CDATA #IMPLIED > <!ELEMENT msqrt %PresExpression; > <!ATTLIST msqrt xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT mroot %twoPresExpression; > <!ATTLIST mroot xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT menclose %PresExpression; > <!ATTLIST menclose xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED notation CDATA "longdiv" > <!ELEMENT mstyle %PresExpression; > <!ATTLIST mstyle xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED fontsize CDATA #IMPLIED fontweight (normal | bold) #IMPLIED fontstyle (normal | italic) #IMPLIED fontfamily CDATA #IMPLIED color CDATA #IMPLIED mathvariant CDATA #IMPLIED mathsize CDATA #IMPLIED mathcolor CDATA #IMPLIED mathbackground CDATA #IMPLIED form (prefix | infix | postfix) #IMPLIED fence (true | false) #IMPLIED separator (true | false) #IMPLIED lspace CDATA #IMPLIED rspace CDATA #IMPLIED stretchy (true | false) #IMPLIED symmetric (true | false) #IMPLIED maxsize CDATA #IMPLIED minsize CDATA #IMPLIED largeop (true | false) #IMPLIED movablelimits (true | false) #IMPLIED accent (true | false) #IMPLIED lquote CDATA #IMPLIED rquote CDATA #IMPLIED linethickness CDATA #IMPLIED scriptlevel CDATA #IMPLIED scriptsizemultiplier CDATA #IMPLIED scriptminsize CDATA #IMPLIED background CDATA #IMPLIED veryverythinmathspace CDATA #IMPLIED verythinmathspace CDATA #IMPLIED thinmathspace CDATA #IMPLIED mediummathspace CDATA #IMPLIED thickmathspace CDATA #IMPLIED verythickmathspace CDATA #IMPLIED veryverythickmathspace CDATA #IMPLIED open CDATA #IMPLIED close CDATA #IMPLIED separators CDATA #IMPLIED subscriptshift CDATA #IMPLIED superscriptshift CDATA #IMPLIED accentunder (true | false) #IMPLIED align CDATA #IMPLIED rowalign CDATA #IMPLIED columnalign CDATA #IMPLIED columnwidth CDATA #IMPLIED groupalign CDATA #IMPLIED alignmentscope CDATA #IMPLIED side (left | right | leftoverlap | rightoverlap) #IMPLIED rowspacing CDATA #IMPLIED columnspacing CDATA #IMPLIED rowlines CDATA #IMPLIED columnlines CDATA #IMPLIED width CDATA #IMPLIED frame (none | solid | dashed) #IMPLIED framespacing CDATA #IMPLIED minlabelspacing CDATA #IMPLIED equalrows CDATA #IMPLIED equalcolumns CDATA #IMPLIED displaystyle (true | false) #IMPLIED rowspan CDATA #IMPLIED columnspan CDATA #IMPLIED edge (left | right) #IMPLIED selection CDATA #IMPLIED bevelled CDATA #IMPLIED height CDATA #IMPLIED depth CDATA #IMPLIED > <!ELEMENT merror %PresExpression; > <!ATTLIST merror xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT mpadded %PresExpression; > <!ATTLIST mpadded xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED width CDATA #IMPLIED height CDATA #IMPLIED depth CDATA #IMPLIED lspace CDATA #IMPLIED > <!ELEMENT mphantom %PresExpression; > <!ATTLIST mphantom xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT mfenced %PresExpression; > <!ATTLIST mfenced xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED open CDATA #IMPLIED close CDATA #IMPLIED separators CDATA #IMPLIED > <!ELEMENT msub %twoPresExpression; > <!ATTLIST msub xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED subscriptshift CDATA #IMPLIED > <!ELEMENT msup %twoPresExpression; > <!ATTLIST msup xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED superscriptshift CDATA #IMPLIED > <!ELEMENT msubsup %threePresExpression; > <!ATTLIST msubsup xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED subscriptshift CDATA #IMPLIED superscriptshift CDATA #IMPLIED > <!ELEMENT munder %twoPresExpression; > <!ATTLIST munder xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED accentunder (true | false) #IMPLIED > <!ELEMENT mover %twoPresExpression; > <!ATTLIST mover xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED accent (true | false) #IMPLIED > <!ELEMENT munderover %threePresExpression; > <!ATTLIST munderover xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED accent (true | false) #IMPLIED accentunder (true | false) #IMPLIED > <!ELEMENT mmultiscripts %prscrPresExpression; > <!ATTLIST mmultiscripts xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED subscriptshift CDATA #IMPLIED superscriptshift CDATA #IMPLIED > <!ELEMENT mtable %mtrPresExpression; > <!ATTLIST mtable xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED align CDATA #IMPLIED rowalign CDATA #IMPLIED columnalign CDATA #IMPLIED columnwidth CDATA #IMPLIED groupalign CDATA #IMPLIED alignmentscope CDATA #IMPLIED side (left | right | leftoverlap | rightoverlap) #IMPLIED rowspacing CDATA #IMPLIED columnspacing CDATA #IMPLIED rowlines CDATA #IMPLIED columnlines CDATA #IMPLIED width CDATA #IMPLIED frame (none | solid | dashed) #IMPLIED framespacing CDATA #IMPLIED minlabelspacing CDATA #IMPLIED equalrows CDATA #IMPLIED equalcolumns CDATA #IMPLIED displaystyle (true | false) #IMPLIED > <!ELEMENT mtr %mtdPresExpression; > <!ATTLIST mtr xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED rowalign CDATA #IMPLIED columnalign CDATA #IMPLIED groupalign CDATA #IMPLIED > <!ELEMENT mlabeledtr %mtdPresExpression; > <!ATTLIST mlabeledtr xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED rowalign CDATA #IMPLIED columnalign CDATA #IMPLIED groupalign CDATA #IMPLIED > <!ELEMENT mtd %PresExpression; > <!ATTLIST mtd xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED rowalign CDATA #IMPLIED columnalign CDATA #IMPLIED groupalign CDATA #IMPLIED rowspan CDATA #IMPLIED columnspan CDATA #IMPLIED > <!ELEMENT maligngroup EMPTY > <!ATTLIST maligngroup xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED groupalign CDATA #IMPLIED > <!ELEMENT maction %PresExpression; > <!ATTLIST maction xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED actiontype CDATA #IMPLIED selection CDATA #IMPLIED > <!--Content elements: tokens (may contain embedded presentation constructs)--> <!ELEMENT ci (#PCDATA | mglyph | mi | mn | mo | mtext | ms | mspace | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction)* > <!ATTLIST ci xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED type CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT csymbol (#PCDATA | mglyph | mi | mn | mo | mtext | ms | mspace | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction)* > <!ATTLIST csymbol xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED encoding CDATA "" type CDATA #IMPLIED definitionURL CDATA "" > <!ELEMENT cn (#PCDATA | mglyph | sep | mi | mn | mo | mtext | ms | mspace | mrow | mfrac | msqrt | mroot | menclose | mstyle | merror | mpadded | mphantom | mfenced | msub | msup | msubsup | munder | mover | munderover | mmultiscripts | mtable | mtr | mlabeledtr | mtd | maligngroup | malignmark | maction)* > <!ATTLIST cn xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED type CDATA #IMPLIED base CDATA "10" definitionURL CDATA "" encoding CDATA "" > <!ELEMENT sep EMPTY > <!ELEMENT integers EMPTY > <!ATTLIST integers xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT reals EMPTY > <!ATTLIST reals xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT rationals EMPTY > <!ATTLIST rationals xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT naturalnumbers EMPTY > <!ATTLIST naturalnumbers xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT complexes EMPTY > <!ATTLIST complexes xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT primes EMPTY > <!ATTLIST primes xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT exponentiale EMPTY > <!ATTLIST exponentiale xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT imaginaryi EMPTY > <!ATTLIST imaginaryi xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT notanumber EMPTY > <!ATTLIST notanumber xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT true EMPTY > <!ATTLIST true xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT false EMPTY > <!ATTLIST false xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT emptyset EMPTY > <!ATTLIST emptyset xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT pi EMPTY > <!ATTLIST pi xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT eulergamma EMPTY > <!ATTLIST eulergamma xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT infinity EMPTY > <!ATTLIST infinity xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!--Content elements: special--> <!ELEMENT apply %ContentExpression; > <!ATTLIST apply xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT reln %ContentExpression; > <!ATTLIST reln xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT lambda %ContentExpression; > <!ATTLIST lambda xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!--Content elements: other--> <!ELEMENT condition %ContentExpression; > <!ATTLIST condition xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT declare %ContentExpression; > <!ATTLIST declare xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED type CDATA #IMPLIED scope CDATA "local" nargs CDATA "1" occurrence CDATA "function-model" definitionURL CDATA "" encoding CDATA "" > <!--Content elements: semantics--> <!ELEMENT semantics %semanticsContentExpression; > <!ATTLIST semantics xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT annotation (#PCDATA) > <!ATTLIST annotation xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED encoding CDATA "" > <!ELEMENT annotation-xml ANY > <!ATTLIST annotation-xml xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED encoding CDATA "" > <!--Content elements: constructors--> <!ELEMENT interval %ContentExpression; > <!ATTLIST interval xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED closure CDATA "closed" > <!ELEMENT list %ContentExpression; > <!ATTLIST list xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED order CDATA "numeric" > <!ELEMENT matrix %ContentExpression; > <!ATTLIST matrix xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT matrixrow %ContentExpression; > <!ATTLIST matrixrow xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT set %ContentExpression; > <!ATTLIST set xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED type CDATA #IMPLIED > <!ELEMENT vector %ContentExpression; > <!ATTLIST vector xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT piecewise (piece*,otherwise?) > <!ATTLIST piecewise xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT piece %ContentExpression; > <!ATTLIST piece xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT otherwise %ContentExpression; > <!ATTLIST otherwise xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!--Content elements: quantifiers--> <!ELEMENT lowlimit %ContentExpression; > <!ATTLIST lowlimit xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT uplimit %ContentExpression; > <!ATTLIST uplimit xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT bvar %ContentExpression; > <!ATTLIST bvar xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT degree %ContentExpression; > <!ATTLIST degree xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT logbase %ContentExpression; > <!ATTLIST logbase xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT momentabout %ContentExpression; > <!ATTLIST momentabout xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT domainofapplication %ContentExpression; > <!ATTLIST domainofapplication xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED > <!ELEMENT inverse EMPTY > <!ATTLIST inverse xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT ident EMPTY > <!ATTLIST ident xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT domain EMPTY > <!ATTLIST domain xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT codomain EMPTY > <!ATTLIST codomain xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT image EMPTY > <!ATTLIST image xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT abs EMPTY > <!ATTLIST abs xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT conjugate EMPTY > <!ATTLIST conjugate xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT exp EMPTY > <!ATTLIST exp xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT factorial EMPTY > <!ATTLIST factorial xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT arg EMPTY > <!ATTLIST arg xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT real EMPTY > <!ATTLIST real xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT imaginary EMPTY > <!ATTLIST imaginary xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT floor EMPTY > <!ATTLIST floor xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT ceiling EMPTY > <!ATTLIST ceiling xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT not EMPTY > <!ATTLIST not xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT ln EMPTY > <!ATTLIST ln xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT sin EMPTY > <!ATTLIST sin xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT cos EMPTY > <!ATTLIST cos xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT tan EMPTY > <!ATTLIST tan xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT sec EMPTY > <!ATTLIST sec xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT csc EMPTY > <!ATTLIST csc xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT cot EMPTY > <!ATTLIST cot xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT sinh EMPTY > <!ATTLIST sinh xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT cosh EMPTY > <!ATTLIST cosh xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT tanh EMPTY > <!ATTLIST tanh xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT sech EMPTY > <!ATTLIST sech xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT csch EMPTY > <!ATTLIST csch xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT coth EMPTY > <!ATTLIST coth xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT arcsin EMPTY > <!ATTLIST arcsin xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT arccos EMPTY > <!ATTLIST arccos xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT arctan EMPTY > <!ATTLIST arctan xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT arccosh EMPTY > <!ATTLIST arccosh xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT arccot EMPTY > <!ATTLIST arccot xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPLIED other CDATA #IMPLIED definitionURL CDATA "" encoding CDATA "" > <!ELEMENT arccoth EMPTY > <!ATTLIST arccoth xlink:href CDATA #IMPLIED xlink:type CDATA #IMPLIED class CDATA #IMPLIED style CDATA #IMPLIED id ID #IMPLIED xref IDREF #IMPL