OP

Formex version 4

Release 5.59 (18 April 2017)

Manual


Table of contents

t_btx
t_btx.ecr
t_btx.formula
t_btx.seq
t_btx.struct
t_btx.title
t_ref.phys

t_area
t_boolean
t_charcode
t_collection
t_date
t_doi.doc
t_doi.gen
t_doi.oj
t_ecr.case
t_ecr.doc
t_ecr.pub
t_fin.id
t_ISSN
t_language
t_no.doc.lseu
t_no.oj
t_page
t_page.ecr
t_page.sequence
t_prod.id
t_quotation.end
t_quotation.start
t_sectiontype
t_volume

ABSTRACT
ACT
ACT.GEN
ADDITIONAL.DOCS.LSEU
ADDR
ADDR.S
AGAINST
AGE.OJ
AGE.OJ.SUMMARY
AGR
ALINEA
AMEND
ANNEX
ANNOTATION
ANONYMOUS
APPEAL.TABLE
APPELANT
APPLICANT
ARCHIVED
ARGUMENTS
ARTICLE
ASSOCIATED.TO
ASSOCIATES
AUTHOR
BAR
BIB.APPEAL.TABLE
BIB.CASE
BIB.CHRON.TABLE
BIB.CHRON.TABLE.NP
BIB.CONCLUSION
BIB.CORRIG.ECR
BIB.DATA
BIB.DATA.CL
BIB.DECISION.ECR
BIB.DOC
BIB.ECR
BIB.ECR.GENERAL
BIB.GEN.PUB
BIB.INSTANCE
BIB.INSTANCE.CONS
BIB.JUDGMENT
BIB.LSEU
BIB.OJ
BIB.OPINION
BIB.ORDER
BIB.REPORT.HEARING
BIB.RULING
BIB.SE
BIB.SUMMARY
BIB.VOLUME
BLK
BR
CAPTION
CASE
CAT.PLANT
CAT.VEGET
CELL
CHAP.SE
CHRON.TABLE
CHRON.TABLE.NP
CJT
CN
CN.AUT.RATE
CN.CODE
CN.CONV.RATE
CN.DESC
CN.HEADER
CN.RATE
CN.SUP.UNIT
CN.UNIT
COLL
COLL.LETTERS
COM
COMMENT
COMPETITION
COMPETITION.INIT
CONCLUSION
CONS.ACT
CONS.ANNEX
CONS.DOC
CONS.DOC.GEN
CONS.LIST
CONS.OTH
CONS.OTH.DOC
CONSID
CONTENTS
CONTENTS.CONCLUSION
CONTENTS.CORR
CONTENTS.DECISION.ECR
CONTENTS.JUDGMENT
CONTENTS.LSEU
CONTENTS.OPINION
CONTENTS.ORDER
CONTENTS.RULING
CONTENTS.SE
CONTENTS.SUMMARY
CONTENTS.SUMMARY.JUDGMENT
CONTENTS.SUMMARY.SE
COPYRIGHT
CORPUS
CORR
CORR.ACTION
CORRECTION
CORRIG
CORRIG.CL
CORRIG.ECR
CORRIGENDUM.ECR
CRIT
CURR.TITLE
DATE
DATE.ADOPT
DECISION
DECISION.ECR
DECISION.ECR.INIT
DEF.AREA
DEF.AREA.HD
DEF.CN.CODE
DEF.COUNTRY
DEF.DESC
DEF.EXPORT
DEF.FORMA.H
DEF.GEN.OBS
DEF.HEAD.TA
DEF.HEAD.VI
DEF.IMPORT
DEF.INDEX
DEF.OBS.VAR
DEF.OBS.VARX
DEF.OBS.VARX.HD
DEF.OPREF
DEF.PART.RATE
DEF.REM
DEF.SH.TARIC
DEF.SPG
DEF.SUP.UNIT
DEF.TA.CODE
DEF.THIRD.RATE
DEF.VARIETY
DEFENDANTS
DEFINITION
DEGREE
DESC
DESCRIPTION
DIV.CONSID
DIVIDEND
DIVISION
DIVISOR
DLIST
DLIST.ITEM
DOC
DOC.CORR
DOC.CORR.SE
DOC.MAIN.PUB
DOC.NOR
DOC.REF
DOC.SUB.PUB
DOCUMENT.REF
DOCUMENT.REF.CONS
DOI.OJ
DURAB
ECR
ECR.GENERAL
EDITION
EEA
ENACTING.TERMS
ENACTING.TERMS.CJT
ENV.BIBLIO
EVENT
EXPONENT
EXPORT
EXPR
FAM.COMP
FAM.COMP.CL
FIN.ID
FINAL
FINAL.SUMMARY
FMT.VALUE
FMX
FMX.GEN
FORMA.H
FORMULA
FRACTION
FRAGMENT
FT
FULL.POWER
FULL.POWER.FINAL
FULL.POWER.INIT
FUNCTION
GEN.OBS
GENERAL
GR.AMEND
GR.ANNOTATION
GR.CN.UNIT
GR.CONSID
GR.CONSID.INIT
GR.CORRECTION
GR.CORRIG
GR.CORRIG.CL
GR.CORRIG.ECR
GR.DOC.NOR
GR.MOD.ACT
GR.MOD.ACT.CL
GR.NOTES
GR.PLANT
GR.SEQ
GR.TBL
GR.UNIT.VI
GR.VISA
GR.VISA.INIT
HEADER.LIST.AMEND
HEADER.LSEU
HEADER.NEW
HEADER.OLD
HEADER.SUMMARY
HEADER.SUMMARY.SE
HINT
HT
ID.RESP
IE
IMG.CNT
IMPORT
INCL.ELEMENT
INCLUSIONS
IND
INDEX
INDEX.MAT
INFO.CONSLEG
INFO.CONSLEG.CL
INFO.ERROR
INFO.FILTER
INFO.MOD
INFO.PROD
INFO.PROD.CL
INFO.PUBLISHER
INTEGRAL
INTERMEDIATE
INTERNAL.ANNEX
INTERVENERS
INTRO
INTRO.OPINION
ITEM
ITEM.CONT
ITEM.PART
ITEM.PUB
ITEM.REF
ITEM.SUMMARY
ITEM.VOLUME
JOB.CONSLEG
JOINED.CASES
JUDGMENT
JUDGMENT.INIT
JUDGMENT.NP
JURISDICTION
KEYWORD
LAST.MODIFICATION
LAST.OJ
LEFT
LEGAL.VALUE
LETTER
LG
LG.CASE
LG.DOC
LG.OJ
LG.OJ.CL
LG.PROC
LG.PUB
LINK.OJ
LIST
LIST.AMEND
LOC.NOTES
LSEU
LV
MARGIN
MENU.LSEU
MOD.ACT
MOD.ACT.CL
NAME.CASE
NAME.COMMON
NAME.SCIENT
NAME.VAR
NEW
NEW.CORR
NO.CASE
NO.CAT
NO.CAT.GLOBAL
NO.CELEX
NO.COM
NO.CURRENT
NO.DOC
NO.DOC.C
NO.DOC.LSEU
NO.DOC.SUMMARY
NO.DOC.TXT
NO.DOI
NO.DOI.OJ
NO.ECLI
NO.FASCICLE
NO.GR.SEQ
NO.ISBN
NO.ISSN
NO.ISSN.ELECTRONIC
NO.ISSN.PRINT
NO.ITEM
NO.OJ
NO.OJ.SUMMARY
NO.P
NO.PARAG
NO.PUB
NO.SEQ
NO.SPECIE
NOTE
NOTICE
NP
NP.ECR
OBJECT
OBS.VAR
OBS.VARX
OBSOLETE
OJ
OJ.CL
OLD
OLD.CORR
OP.CMP
OP.MATH
OPINION
OPINION.INIT
OPREF
ORDER
ORDER.INIT
ORDER.NP
OTH.PUB
OTH.PUB.CL
OVER
OVERLINE
P
PAGE.CONTENTS
PAGE.FIRST
PAGE.FIRST.ECR
PAGE.HEADER
PAGE.LAST
PAGE.LAST.ECR
PAGE.SEQ
PAGE.SUMMARY
PAGE.TOTAL
PAPER
PAPER.GEN
PARAG
PART.ECR
PARTIES
PARTY.STATUS
PDF
PDF.ECR
PDF.GEN
PERIOD
PL.DATE
PLAINTIFS
PLENIPOTENTIARY
POS.TARIC
PREAMBLE
PREAMBLE.FINAL
PREAMBLE.GEN
PREAMBLE.INIT
PRELIM.RULING
PREFIX
PRESENCE
PRESENCE.INIT
PRINTER
PROD.ID
PRODUCT
PROLOG
PUBLICATION
PUBLICATION.REF
PUBLICATION.REF.SE
PUBLISHER
QUALIF
QUOT.END
QUOT.S
QUOT.START
REF.APPEAL.TABLE
REF.BIB.RECORD
REF.CASE
REF.CASE.F1
REF.CHRON.TABLE
REF.CHRON.TABLE.NP
REF.CONCLUSION
REF.CORE.METADATA
REF.CORRIG.ECR
REF.DECISION.ECR
REF.DOC
REF.DOC.ECR
REF.DOC.OJ
REF.ECR
REF.ECR.DOC
REF.JUDGMENT
REF.JUDGMENT.NP
REF.NOTE
REF.NOTICE
REF.NP.ECR
REF.OJ
REF.OPINION
REF.ORDER
REF.ORDER.NP
REF.ORIGINAL
REF.PDF.ECR
REF.PHYS
REF.REPORT.HEARING
REF.RULING
REF.SUMMARY.JUDGMENT
REFERENCE.TABLE
REFERENCES.LSEU
REFERRED.DOCS.LSEU
RELATED.MATERIAL
REPORT.HEARING
RIGHT
ROOT
ROW
RULING
SE
SECTION
SECTION.SUMMARY
SERIES.SE
SH.TARIC
SIGNATORY
SIGNATURE
SIGNATURE.CASE
SIZE
SPEC.ED
SPECIAL
SPECIE
SPG
STI
STI.ART
STI.BLK
SUBDIV
SUBITEM.SUMMARY
SUBJECT
SUBJECTS
SUBSECTION
SUBSECTION.SUMMARY
SUBSERIES.SE
SUM
SUMMARY
SUMMARY.JUDGMENT
SUMMARY.LSEU
SUMMARY.NP
SUMMARY.PDF
SUP.UNIT
TA.CODE
TARIC
TBL
TERM
THIRD.RATE
TI
TI.ART
TI.BLK
TI.CJT
TI.COLL
TI.CONTENTS
TI.GR.CN.UNIT
TI.GR.PLANT
TI.GR.UNIT.VI
TI.INFO.NO
TI.PAGE
TI.SPECIE
TITLE
TOC
TOC.BLK
TOC.HD
TOC.HD.CONT
TOC.HD.NO
TOC.HD.REF
TOC.ITEM
TOME.SE
TRANS.REF
TXT
TXT.COL
TXT.ROW
TYPE.CASE
UNDER
UNIT.TA
UNIT.VI
VAR.INFO
VECTOR
VISA
VOLUME
VOLUME.ECR
VOLUME.ID
VOLUME.PAPER
VOLUME.REF
YEAR

Legal documents Adopted texts and preparatory acts - Adopted texts and preparatory acts
Guided Approach Help to find the suitable element to mark up a prefixed object - Help to find the suitable element to mark up a prefixed object
Guided Approach Help to find the right Root Element - Help to find the right Root Element
Structuring text blocks with Formex V4 GR.SEQ, P, NP, LIST... elements - GR.SEQ, P, NP, LIST... elements
PDF Summary Generation from Formex instances - Generation from Formex instances


t_btx

[complex type]

btx

This complex type defines the mixed content model which is allowed for the elements with a "t_btx" type attribute.

Model

<xd:complexType name="t_btxmixed="true">
  <xd:sequence>
    <xd:element ref="MARGINminOccurs="0"/>
    <xd:choice minOccurs="0maxOccurs="unbounded">
      <xd:element ref="ACT.GEN"/>
      <xd:element ref="ADDR"/>
      <xd:element ref="ADDR.S"/>
      <xd:element ref="ALINEA"/>
      <xd:element ref="ANNOTATION"/>
      <xd:element ref="ANONYMOUS"/>
      <xd:element ref="ARTICLE"/>
      <xd:element ref="BR"/>
      <xd:element ref="CAT.PLANT"/>
      <xd:element ref="CAT.VEGET"/>
      <xd:element ref="CN"/>
      <xd:element ref="COLL.LETTERS"/>
      <xd:element ref="COMMENT"/>
      <xd:element ref="COMPETITION.INIT"/>
      <xd:element ref="CONSID"/>
      <xd:element ref="CONTENTS"/>
      <xd:element ref="DATE"/>
      <xd:element ref="DIV.CONSID"/>
      <xd:element ref="DIVISION"/>
      <xd:element ref="DLIST"/>
      <xd:element ref="DLIST.ITEM"/>
      <xd:element ref="ENACTING.TERMS"/>
      <xd:element ref="ENACTING.TERMS.CJT"/>
      <xd:element ref="FINAL"/>
      <xd:element ref="FORMULA"/>
      <xd:element ref="FT"/>
      <xd:element ref="FULL.POWER"/>
      <xd:element ref="FULL.POWER.FINAL"/>
      <xd:element ref="FULL.POWER.INIT"/>
      <xd:element ref="GR.AMEND"/>
      <xd:element ref="GR.ANNOTATION"/>
      <xd:element ref="GR.CONSID"/>
      <xd:element ref="GR.CONSID.INIT"/>
      <xd:element ref="GR.NOTES"/>
      <xd:element ref="GR.SEQ"/>
      <xd:element ref="GR.TBL"/>
      <xd:element ref="GR.VISA"/>
      <xd:element ref="GR.VISA.INIT"/>
      <xd:element ref="HT"/>
      <xd:element ref="IE"/>
      <xd:element ref="INCL.ELEMENT"/>
      <xd:element ref="INDEX"/>
      <xd:element ref="ITEM"/>
      <xd:element ref="KEYWORD"/>
      <xd:element ref="LETTER"/>
      <xd:element ref="LIST"/>
      <xd:element ref="LIST.AMEND"/>
      <xd:element ref="LV"/>
      <xd:element ref="NOTE"/>
      <xd:element ref="NP"/>
      <xd:element ref="P"/>
      <xd:element ref="PARAG"/>
      <xd:element ref="PL.DATE"/>
      <xd:element ref="PLENIPOTENTIARY"/>
      <xd:element ref="PREAMBLE"/>
      <xd:element ref="PREAMBLE.FINAL"/>
      <xd:element ref="PREAMBLE.GEN"/>
      <xd:element ref="PREAMBLE.INIT"/>
      <xd:element ref="QUOT.END"/>
      <xd:element ref="QUOT.S"/>
      <xd:element ref="QUOT.START"/>
      <xd:element ref="REF.DOC"/>
      <xd:element ref="REF.DOC.ECR"/>
      <xd:element ref="REF.DOC.OJ"/>
      <xd:element ref="STI.ART"/>
      <xd:element ref="TBL"/>
      <xd:element ref="TI.ART"/>
      <xd:element ref="TI.CJT"/>
      <xd:element ref="TITLE"/>
      <xd:element ref="TOC"/>
      <xd:element ref="TXT"/>
      <xd:element ref="VISA"/>
    </xd:choice>
  </xd:sequence>
</xd:complexType>

Used by

AGE.OJ.SUMMARY ALINEA APPLICANT DECISION.ECR.INIT DEFINITION DESCRIPTION HINT INTRO ITEM.CONT JOINED.CASES JUDGMENT.INIT NAME.COMMON NOTICE OBS.VAR P PREAMBLE.FINAL PREAMBLE.INIT STI.ART TI.GR.CN.UNIT TOC.HD.CONT TXT

General rules

Type

The t_btx element is composed of one to several of the elements present in the model.

[Table of contents]

t_btx.ecr

[complex type]

Structure in the context of European Court Reports

This complex type defines the content which is allowed for the elements with a "t_btx.ecr" type. It is actually a reduced set of elements from t_btx.struct.

Model

<xd:complexType name="t_btx.ecrmixed="true">
  <xd:sequence>
    <xd:element ref="MARGINminOccurs="0"/>
    <xd:choice minOccurs="0maxOccurs="unbounded">
      <xd:element ref="ADDR"/>
      <xd:element ref="ADDR.S"/>
      <xd:element ref="ALINEA"/>
      <xd:element ref="ANNOTATION"/>
      <xd:element ref="ANONYMOUS"/>
      <xd:element ref="ARTICLE"/>
      <xd:element ref="BR"/>
      <xd:element ref="COLL.LETTERS"/>
      <xd:element ref="COMMENT"/>
      <xd:element ref="CONSID"/>
      <xd:element ref="CONTENTS"/>
      <xd:element ref="DATE"/>
      <xd:element ref="DIV.CONSID"/>
      <xd:element ref="DIVISION"/>
      <xd:element ref="DLIST"/>
      <xd:element ref="DLIST.ITEM"/>
      <xd:element ref="ENACTING.TERMS"/>
      <xd:element ref="ENACTING.TERMS.CJT"/>
      <xd:element ref="FINAL"/>
      <xd:element ref="FORMULA"/>
      <xd:element ref="FT"/>
      <xd:element ref="GR.ANNOTATION"/>
      <xd:element ref="GR.CONSID"/>
      <xd:element ref="GR.CONSID.INIT"/>
      <xd:element ref="GR.NOTES"/>
      <xd:element ref="GR.SEQ"/>
      <xd:element ref="GR.TBL"/>
      <xd:element ref="GR.VISA"/>
      <xd:element ref="GR.VISA.INIT"/>
      <xd:element ref="HT"/>
      <xd:element ref="IE"/>
      <xd:element ref="INCL.ELEMENT"/>
      <xd:element ref="INDEX"/>
      <xd:element ref="ITEM"/>
      <xd:element ref="KEYWORD"/>
      <xd:element ref="LETTER"/>
      <xd:element ref="LIST"/>
      <xd:element ref="LIST.AMEND"/>
      <xd:element ref="LV"/>
      <xd:element ref="NOTE"/>
      <xd:element ref="NP"/>
      <xd:element ref="NP.ECR"/>
      <xd:element ref="P"/>
      <xd:element ref="PARAG"/>
      <xd:element ref="PL.DATE"/>
      <xd:element ref="PREAMBLE"/>
      <xd:element ref="PREAMBLE.FINAL"/>
      <xd:element ref="PREAMBLE.GEN"/>
      <xd:element ref="PREAMBLE.INIT"/>
      <xd:element ref="QUOT.END"/>
      <xd:element ref="QUOT.S"/>
      <xd:element ref="QUOT.START"/>
      <xd:element ref="REF.DOC"/>
      <xd:element ref="REF.DOC.ECR"/>
      <xd:element ref="REF.DOC.OJ"/>
      <xd:element ref="STI.ART"/>
      <xd:element ref="TBL"/>
      <xd:element ref="TI.ART"/>
      <xd:element ref="TI.CJT"/>
      <xd:element ref="TITLE"/>
      <xd:element ref="TOC"/>
      <xd:element ref="TXT"/>
      <xd:element ref="VISA"/>
    </xd:choice>
  </xd:sequence>
</xd:complexType>

Used by

CONTENTS.CONCLUSION

General rules

Type

The t_btx.ecr element is composed of one to several of the elements present in the model.

[Table of contents]

t_btx.formula

[complex type]

Formula

This complex type defines the mixed content which is allowed for the elements with a "t_btx.formula" type attribute.

Model

<xd:complexType name="t_btx.formulamixed="true">
  <xd:sequence>
    <xd:element ref="MARGINminOccurs="0"/>
    <xd:choice minOccurs="0maxOccurs="unbounded">
      <xd:element ref="BAR"/>
      <xd:element ref="EXPONENT"/>
      <xd:element ref="EXPR"/>
      <xd:element ref="FMT.VALUE"/>
      <xd:element ref="FRACTION"/>
      <xd:element ref="FUNCTION"/>
      <xd:element ref="HT"/>
      <xd:element ref="IE"/>
      <xd:element ref="IND"/>
      <xd:element ref="INTEGRAL"/>
      <xd:element ref="NOTE"/>
      <xd:element ref="OP.CMP"/>
      <xd:element ref="OP.MATH"/>
      <xd:element ref="OVERLINE"/>
      <xd:element ref="PRODUCT"/>
      <xd:element ref="QUOT.END"/>
      <xd:element ref="QUOT.START"/>
      <xd:element ref="ROOT"/>
      <xd:element ref="SUM"/>
      <xd:element ref="VECTOR"/>
    </xd:choice>
  </xd:sequence>
</xd:complexType>

Used by

DEGREE DIVIDEND DIVISOR EXPONENT IND OVER OVERLINE UNDER VECTOR

General rules

Type

An instance of the t_btx.formula type is composed of one to several of the elements present in the model.

[Table of contents]

t_btx.seq

[complex type]

Sequence

This complex type defines the mixed content model which is allowed for the elements with a "t_btx.seq" type attribute.

Model

<xd:complexType name="t_btx.seqmixed="true">
  <xd:sequence>
    <xd:element ref="MARGINminOccurs="0"/>
    <xd:choice minOccurs="0maxOccurs="unbounded">
      <xd:element ref="ADDR"/>
      <xd:element ref="ADDR.S"/>
      <xd:element ref="ANONYMOUS"/>
      <xd:element ref="BR"/>
      <xd:element ref="DATE"/>
      <xd:element ref="DLIST"/>
      <xd:element ref="FORMULA"/>
      <xd:element ref="FT"/>
      <xd:element ref="GR.TBL"/>
      <xd:element ref="HT"/>
      <xd:element ref="IE"/>
      <xd:element ref="INCL.ELEMENT"/>
      <xd:element ref="INDEX"/>
      <xd:element ref="LIST"/>
      <xd:element ref="LV"/>
      <xd:element ref="NO.CASE"/>
      <xd:element ref="NO.ECLI"/>
      <xd:element ref="NOTE"/>
      <xd:element ref="REF.DOC"/>
      <xd:element ref="REF.DOC.ECR"/>
      <xd:element ref="REF.DOC.OJ"/>
      <xd:element ref="REF.NP.ECR"/>
      <xd:element ref="QUOT.END"/>
      <xd:element ref="QUOT.S"/>
      <xd:element ref="QUOT.START"/>
      <xd:element ref="TBL"/>
      <xd:element ref="TXT"/>
    </xd:choice>
  </xd:sequence>
</xd:complexType>

Used by

ADDR AGAINST COPYRIGHT DEF.AREA.HD DEF.COUNTRY DEF.FORMA.H DEF.GEN.OBS DEF.INDEX DEF.OBS.VARX.HD EDITION EXPORT FORMA.H FULL.POWER.FINAL FULL.POWER.INIT GEN.OBS GR.CONSID.INIT GR.VISA.INIT HEADER.NEW HEADER.OLD IMPORT INDEX.MAT LEFT NAME.CASE NAME.SCIENT NAME.VAR NO.DOC.SUMMARY NO.DOC.TXT NO.GR.SEQ NO.ITEM NO.OJ.SUMMARY NO.P NO.PARAG NO.PUB NO.SPECIE OPREF PARTY.STATUS PERIOD POS.TARIC PREFIX PRESENCE.INIT PUBLISHER RIGHT SERIES.SE SH.TARIC SIZE SPECIAL SPG SUBSERIES.SE SUP.UNIT TA.CODE TERM THIRD.RATE TI.ART TI.COLL TI.CONTENTS TI.INFO.NO TI.PAGE TOC.HD.NO TRANS.REF VISA

General rules

Type

The t_btx.seq element is composed of one to several of the elements present in the model.

[Table of contents]

t_btx.struct

[complex type]

Structure

This complex type defines the content which is allowed for the elements with a "t_btx.struct" type attribute.

Model

<xd:complexType name="t_btx.struct">
  <xd:choice minOccurs="0maxOccurs="unbounded">
    <xd:element ref="ACT.GEN"/>
    <xd:element ref="ADDR.S"/>
    <xd:element ref="ALINEA"/>
    <xd:element ref="ANNOTATION"/>
    <xd:element ref="ARTICLE"/>
    <xd:element ref="CAT.PLANT"/>
    <xd:element ref="CAT.VEGET"/>
    <xd:element ref="CN"/>
    <xd:element ref="COLL.LETTERS"/>
    <xd:element ref="COMMENT"/>
    <xd:element ref="COMPETITION.INIT"/>
    <xd:element ref="CONS.ANNEX"/>
    <xd:element ref="CONSID"/>
    <xd:element ref="CONTENTS"/>
    <xd:element ref="CONTENTS.CORR"/>
    <xd:element ref="DIV.CONSID"/>
    <xd:element ref="DIVISION"/>
    <xd:element ref="DLIST"/>
    <xd:element ref="DLIST.ITEM"/>
    <xd:element ref="ENACTING.TERMS"/>
    <xd:element ref="ENACTING.TERMS.CJT"/>
    <xd:element ref="FINAL"/>
    <xd:element ref="FORMULA"/>
    <xd:element ref="FULL.POWER"/>
    <xd:element ref="FULL.POWER.FINAL"/>
    <xd:element ref="FULL.POWER.INIT"/>
    <xd:element ref="GR.AMEND"/>
    <xd:element ref="GR.ANNOTATION"/>
    <xd:element ref="GR.CONSID"/>
    <xd:element ref="GR.CONSID.INIT"/>
    <xd:element ref="GR.NOTES"/>
    <xd:element ref="GR.SEQ"/>
    <xd:element ref="GR.TBL"/>
    <xd:element ref="GR.VISA"/>
    <xd:element ref="GR.VISA.INIT"/>
    <xd:element ref="INCL.ELEMENT"/>
    <xd:element ref="INDEX"/>
    <xd:element ref="ITEM"/>
    <xd:element ref="LETTER"/>
    <xd:element ref="LIST"/>
    <xd:element ref="LIST.AMEND"/>
    <xd:element ref="LV"/>
    <xd:element ref="NOTE"/>
    <xd:element ref="NP"/>
    <xd:element ref="NP.ECR"/>
    <xd:element ref="P"/>
    <xd:element ref="PARAG"/>
    <xd:element ref="PL.DATE"/>
    <xd:element ref="PLENIPOTENTIARY"/>
    <xd:element ref="PREAMBLE"/>
    <xd:element ref="PREAMBLE.FINAL"/>
    <xd:element ref="PREAMBLE.GEN"/>
    <xd:element ref="PREAMBLE.INIT"/>
    <xd:element ref="QUOT.S"/>
    <xd:element ref="REFERRED.DOCS.LSEU"/>
    <xd:element ref="STI.ART"/>
    <xd:element ref="TARIC"/>
    <xd:element ref="TBL"/>
    <xd:element ref="TI.ART"/>
    <xd:element ref="TI.CJT"/>
    <xd:element ref="TITLE"/>
    <xd:element ref="TOC"/>
    <xd:element ref="VISA"/>
  </xd:choice>
</xd:complexType>

Used by

ABSTRACT ADDITIONAL.DOCS.LSEU ARGUMENTS CAPTION COMMENT COMPETITION.INIT CONSID ENACTING.TERMS.CJT FRAGMENT HEADER.LSEU MENU.LSEU NEW OLD ORDER.INIT PRELIM.RULING PROLOG REFERENCE.TABLE REFERENCES.LSEU REFERRED.DOCS.LSEU RELATED.MATERIAL SUBJECT SUMMARY.LSEU TXT.COL TXT.ROW

General rules

Type

The t_btx.struct element is composed of one to several of the elements present in the model.

[Table of contents]

t_btx.title

[complex type]

Title

This complex type defines the content which is allowed for the elements with a "t_btx.title" type attribute.

Model

<xd:complexType name="t_btx.title">
  <xd:choice minOccurs="0maxOccurs="unbounded">
    <xd:element ref="LIST"/>
    <xd:element ref="NO.DOC.C"/>
    <xd:element ref="NP"/>
    <xd:element ref="P"/>
  </xd:choice>
</xd:complexType>

Used by

STI TI

General rules

Type

The t_btx.title element is composed of one to several of the following elements present in the model.

[Table of contents]

t_ref.phys

[complex type]

Physical reference to another file

This complex type defines an empty element. The attributes describe a physical reference to another file.

Model

<xd:complexType name="t_ref.phys">
  <xd:attribute name="FILEtype="xd:anyURIuse="required"/>
  <xd:attribute name="TYPEuse="required">
    <xd:simpleType>
      <xd:restriction base="xd:string">
        <xd:enumeration value="DOC.PDF"/>
        <xd:enumeration value="DOC.XML"/>
        <xd:enumeration value="FRAGMENT.XML"/>
        <xd:enumeration value="IMAGE"/>
      </xd:restriction>
    </xd:simpleType>
  </xd:attribute>
  <xd:attribute name="IMAGE.TYPE">
    <xd:simpleType>
      <xd:restriction base="xd:string">
        <xd:enumeration value="TIFF"/>
      </xd:restriction>
    </xd:simpleType>
  </xd:attribute>
</xd:complexType>

Used by

ASSOCIATED.TO ASSOCIATES REF.PHYS

General rules

Attributes

The FILE attribute

The FILE attribute is mandatory and contains the URL to the referenced file.

Attributes

The TYPE attribute

The TYPE attribute is mandatory and is used to define the type of the external object. Only one of the listed values may be used.

Attributes

The IMAGE.TYPE attribute

The IMAGE.TYPE attribute specifies the type of the referenced image. For the time being, only the value "TIFF" is allowed. Although the attribute is optional, it has to be used if the value of the TYPE attribute is "IMAGE".

[Table of contents]

t_area

[simple type]

Area

This type defines the values of the AREA attribute, which is used by the CRIT and DEF.AREA elements in order to describe a regional area in the context of common catalogues of varieties of agricultural plant and vegetable species.

Model

<xd:simpleType name="t_area">
  <xd:restriction base="xd:string">
    <xd:enumeration value="EFTA"/>
    <xd:enumeration value="EU"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The t_area element is defined as a string.

Its value must be one of the following:

[Table of contents]

t_boolean

[simple type]

yes/no boolean value

This type defines the values which are allowed for attributes and elements with a "t_boolean" type attribute.

Model

<xd:simpleType name="t_boolean">
  <xd:restriction base="xd:string">
    <xd:enumeration value="NO"/>
    <xd:enumeration value="YES"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The contents of this type must correspond to one of the following values:

[Table of contents]

t_charcode

[simple type]

Hexadecimal encoding of characters

This type defines a pattern for the encoding of Unicode characters.

Model

<xd:simpleType name="t_charcode">
  <xd:restriction base="xd:hexBinary">
    <xd:pattern value="[0-9A-F]{4}"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The values corresponding to the pattern are sequences of 4 hexadecimal digits, so "0-9" and/or "A-F" (upper-case only). Thus the values correspond to a two-byte encoding.

[Table of contents]

t_collection

[simple type]

Collection of the OJ

This type defines the values which are allowed for the elements with a "t_collection" type attribute.

Model

<xd:simpleType name="t_collection">
  <xd:restriction base="xd:string">
    <xd:enumeration value="A"/>
    <xd:enumeration value="C"/>
    <xd:enumeration value="L"/>
    <xd:enumeration value="P"/>
    <xd:enumeration value="S"/>
    <xd:enumeration value="X"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The contents of this type must correspond to one of the following values:

[Table of contents]

t_date

[simple type]

Date format

This type defines the ISO 8601 date format.

Model

<xd:simpleType name="t_date">
  <xd:restriction base="xd:string">
    <xd:pattern value="\d{4}(\d{2}(\d{2})?)?"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The type allows the handling both of complete dates YYYYMMDD and years YYYY.

[Table of contents]

t_doi.doc

[simple type]

DOI format for documents

This type defines the composition of the DOI (Digital Object Identifier) for documents.

Model

<xd:simpleType name="t_doi.doc">
  <xd:restriction base="xd:string">
    <xd:pattern value="doi:10\.\d{4}/[ACLP][_AEGM]\d{4}\.\d{3}\.\d{2}(\d|c|e|s)\d{3}\d{2}\.[a-z]{3}"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The DOI is generally composed of a prefix and a suffix separated by a slash. The prefix value on the document level is 10.3001.

The suffix is composed as follows:

Example:

doi:10.3001/L_2013.002.01000301.deu

[Table of contents]

t_doi.gen

[simple type]

DOI format for general publications

This type defines the composition of the DOI (Digital Object Identifier) for general publications.

Model

<xd:simpleType name="t_doi.gen">
  <xd:restriction base="xd:string">
    <xd:pattern value="doi:10\.\d{4}/.+"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The DOI is generally composed of a prefix and a suffix separated by a slash. The prefix value for publications is 10. followed by 4 digits.

The suffix consists of any kind of character or digit and is of indefinite length.

[Table of contents]

t_doi.oj

[simple type]

DOI format for Official Journal issues

This type defines the composition of the DOI (Digital Object Identifier) for single issues of the Official Journal.

Model

<xd:simpleType name="t_doi.oj">
  <xd:restriction base="xd:string">
    <xd:pattern value="doi:10\.\d{4}/\d{7}(\d|X)\.[CL][_AEGM]\d{4}\.\d{3}\.[a-z]{3}"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The DOI is generally composed of a prefix and a suffix separated by a slash. The prefix value for publications (complete OJ) is 10.3000.

The suffix is composed as follows:

Example:

doi:10.3000/19770642.L_2013.002.deu

[Table of contents]

t_ecr.case

[simple type]

Name for the case instances

This type defines the composition of an ECR case filename.

Model

<xd:simpleType name="t_ecr.case">
  <xd:restriction base="xd:string">
    <xd:pattern value="(ECR(CJ|T1|F1|F2)\d{4}[A-Z]{2}[ABC][12]?\.\d{2}[ars\d]\d{5}\d{2}\.case\.xml)|(n\.a\.)|(ECR_\d{5}[A-Z]{2}\d{4}_SUM_[A-Z]{2}_\d{2}\.xml)|(n\.a\.)"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The name is composed as follows:

Example:

ECRCJ2005FRA2.010000101.case.xml

[Table of contents]

t_ecr.doc

[simple type]

Name for the document instances within a case

This type defines the composition of an ECR document filename.

Model

<xd:simpleType name="t_ecr.doc">
  <xd:restriction base="xd:string">
    <xd:pattern value="(ECR(CJ|T1|F1)\d{4}[A-Z]{2}[ABC][12]?\.\d{2}[aprs\d]\d{5}\d{2}\.xml)|(ECR_\d{5}[A-Z]{2}\d{4}(_INF)?_[A-Z]{2}_\.xml)"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The name is composed as follows:

Example:

ECRCJ2005FRA1.010000101.xml

[Table of contents]

t_ecr.pub

[simple type]

Name for an ECR publication

This type defines the composition of an ECR publication filename.

Model

<xd:simpleType name="t_ecr.pub">
  <xd:restriction base="xd:string">
    <xd:pattern value="(ECR(CJ|T1|F1)\d{4}[A-Z]{2}[ABC][12]?\.\d{2}\.xml)|(n\.a\.)"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The name is composed as follows:

Example:

ECRCJ2005FRA.01.xml

[Table of contents]

t_fin.id

[simple type]

Identifier in the financial process

This type is used for the identification of a document within a financial procedure.

Model

<xd:simpleType name="t_fin.id">
  <xd:restriction base="xd:string">
    <xd:pattern value="\d{1,38}"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The identifier is composed of five digits and will be transmitted on the Request for publication.

In some cases documents of a similar nature are grouped together in a single Request and consequently with a single financial identifier. This identifier has to be used for each of the grouped documents.

[Table of contents]

t_ISSN

[simple type]

ISSN format

This type defines the composition of the International Standard Series Number (ISSN).

Model

<xd:simpleType name="t_ISSN">
  <xd:restriction base="xd:string">
    <xd:pattern value="\d{7}(\d|X)"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The content of this element must correspond to the following format: NNNNNNNX (8 positions) (alsosee: t_ISSN):

In the electronic document the dash symbol must be omitted.

[Table of contents]

t_language

[simple type]

Language

This type defines the values which are allowed for the attributes and elements with a "t_language" type attribute. It is used to describe the language of a document.

Model

<xd:simpleType name="t_language">
  <xd:annotation>
    <xd:documentation>based on ISO 639-1 (ISO 639-3 as comments)</xd:documentation>
  </xd:annotation>
  <xd:restriction base="xd:string">
    <xd:enumeration value="BG"/>
    <xd:enumeration value="CA"/>
    <xd:enumeration value="CS"/>
    <xd:enumeration value="DA"/>
    <xd:enumeration value="DE"/>
    <xd:enumeration value="EL"/>
    <xd:enumeration value="EN"/>
    <xd:enumeration value="ES"/>
    <xd:enumeration value="ET"/>
    <xd:enumeration value="EU"/>
    <xd:enumeration value="FI"/>
    <xd:enumeration value="FR"/>
    <xd:enumeration value="GA"/>
    <xd:enumeration value="GL"/>
    <xd:enumeration value="HR"/>
    <xd:enumeration value="HU"/>
    <xd:enumeration value="IS"/>
    <xd:enumeration value="IT"/>
    <xd:enumeration value="LT"/>
    <xd:enumeration value="LV"/>
    <xd:enumeration value="MT"/>
    <xd:enumeration value="NL"/>
    <xd:enumeration value="NO"/>
    <xd:enumeration value="PL"/>
    <xd:enumeration value="PT"/>
    <xd:enumeration value="RO"/>
    <xd:enumeration value="SK"/>
    <xd:enumeration value="SL"/>
    <xd:enumeration value="SV"/>
    <xd:enumeration value="TR"/>
    <xd:enumeration value="XM"/>
    <xd:enumeration value="XX"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The t_language element is defined as a string.

Its value must be one of the following:

[Table of contents]

t_no.doc.lseu

[simple type]

Identifier of a legislation summary

This simple type constructs the identifier of a legislation summar.

Model

<xd:simpleType name="t_no.doc.lseu">
  <xd:restriction base="xd:string">
    <xd:pattern value="LSEU\-((GLOSSARY\-[A-Z0-9_]+)|(INTRO\-(\d{2})+)|([A-Z]([A-Z]|\d)\d{4}[A-Z]?)|(\d{2}(\d{2}){0,5}_[1-9]\d{0,3})|([4-9](\d{4}|\d{6})))\-\d{4}\-\d{2}\-\d{2}\-\d{4}"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The simple type is based on xs:string and composed by

The value is identical for all language versions of a summary.

[Table of contents]

t_no.oj

[simple type]

OJ number

This simple type is used to describe the OJ numbering scheme.

Model

<xd:simpleType name="t_no.oj">
  <xd:restriction base="xd:string">
    <xd:pattern value="\d{3}[AEIM]?"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

An OJ number is always composed by three digits optionally followed by the 'A' letter (for an annexed OJ), the 'E' letter (for an OJ exclusively published in the electronic format), the 'I' letter for an isolated publication or the 'M' letter for a special publication in Maltese. If necessary, the initial positions must be filled with zeros e.g. OJ 10 will be encoded as 010.

[Table of contents]

t_page

[simple type]

Pagination

This type defines the page numbering scheme.

Model

<xd:simpleType name="t_page">
  <xd:restriction base="xd:string">
    <xd:pattern value="([ceps]{0,1}\-{0,1}\d{1,5}[a-z*]?(/\d{2})?)|([cdilvxCDILVX]+)"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The t_page type takes into account arab and roman numbering.

In some cases the numeric value has to be preceded by one of the following letters:

In the context of the European Court Reports it is possible that the page number is followed by an asterisk.

[Table of contents]

t_page.ecr

[simple type]

Pagination for ECR documents

This type defines the page numbering scheme for the documents published in the European Court Reports.

Model

<xd:simpleType name="t_page.ecr">
  <xd:restriction base="xd:string">
    <xd:pattern value="[ceps]{0,1}(([I]{1,3}\-)?([ABP]\-(\d{1,2}\-)?)?)?[\dcdilvxCDILVX]+\*?(;(([I]{1,3}\-)?([ABP]\-(\d{1,2}\-)?)?)?[\dcdilvxCDILVX]+\*?)*"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The pagination is composed as follows:

The two first parts are absent before 1990.

[Table of contents]

t_page.sequence

[simple type]

Sequence number of a document on the page

This type is used to describe the sequence number of a document on the page.

Model

<xd:simpleType name="t_page.sequence">
  <xd:restriction base="xd:string">
    <xd:pattern value="[1-9][0-9]?"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The sequence number is expressed by one or two digits.

[Table of contents]

t_prod.id

[simple type]

Production identifier

The t_prod.id simple type is used to mark up the identifier of a document or a package of documents during production.

Model

<xd:simpleType name="t_prod.id">
  <xd:restriction base="xd:string">
    <xd:pattern value="\d{11}"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The identifier is composed of eleven digits and will be transmitted on the Request for publication.

In some cases documents of a similar nature are grouped together in a single Request and consequently with a single production identifier. This identifier has to be used for each of the grouped documents.

[Table of contents]

t_quotation.end

[simple type]

Hexadecimal encoding of symbols for ending quotation marks

This type lists the Unicode character codes for ending quotation marks.

Model

<xd:simpleType name="t_quotation.end">
  <xd:restriction base="t_charcode">
    <xd:enumeration value="00AB"/>
    <xd:enumeration value="00BB"/>
    <xd:enumeration value="2018"/>
    <xd:enumeration value="2019"/>
    <xd:enumeration value="201C"/>
    <xd:enumeration value="201D"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The value used by QUOT.END must be member of the enumeration list.

[Table of contents]

t_quotation.start

[simple type]

Hexadecimal encoding of symbols for opening quotation marks

This type lists the Unicode character codes for opening quotation marks.

Model

<xd:simpleType name="t_quotation.start">
  <xd:restriction base="t_charcode">
    <xd:enumeration value="00AB"/>
    <xd:enumeration value="00BB"/>
    <xd:enumeration value="2018"/>
    <xd:enumeration value="2019"/>
    <xd:enumeration value="201A"/>
    <xd:enumeration value="201C"/>
    <xd:enumeration value="201D"/>
    <xd:enumeration value="201E"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The value used by QUOT.START must be member of the enumeration list.

[Table of contents]

t_sectiontype

[simple type]

Type of a section

This simple element is used to describe a type of section.

Model

<xd:simpleType name="t_sectiontype">
  <xd:restriction base="xd:string">
    <xd:enumeration value="C0"/>
    <xd:enumeration value="C1"/>
    <xd:enumeration value="C2"/>
    <xd:enumeration value="C3"/>
    <xd:enumeration value="C4"/>
    <xd:enumeration value="C5"/>
    <xd:enumeration value="CC"/>
    <xd:enumeration value="CI"/>
    <xd:enumeration value="CX"/>
    <xd:enumeration value="L0"/>
    <xd:enumeration value="L1"/>
    <xd:enumeration value="L2"/>
    <xd:enumeration value="L3"/>
    <xd:enumeration value="L4"/>
    <xd:enumeration value="L5"/>
    <xd:enumeration value="LC"/>
    <xd:enumeration value="LI"/>
    <xd:enumeration value="LX"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The t_sectiontype element is defined as a string.

The following values are allowed :

N.N.: These categories entered into force on January 1, 2007.

[Table of contents]

t_volume

[simple type]

Encoding of the volume of a publication

The simple type defines the way how to identify a volume. The value may consist of one or two digits.

Model

<xd:simpleType name="t_volume">
  <xd:restriction base="xd:string">
    <xd:pattern value="[1-9][0-9]?"/>
  </xd:restriction>
</xd:simpleType>

General rules

Type

The values corresponding to the pattern are sequences of 1 or 2 decimal digits, so "0-9". The value "0" is not valid.

[Table of contents]

ABSTRACT

[element]

Part of court report summary

The ABSTRACT element encapsulates the essential motives for a case.

It may only contain one or more of the elements defined in the t_btx.struct complex type.

Model

<xd:element name="ABSTRACTtype="t_btx.struct"/>

Used by

ABSTRACT SUMMARY

General rules

Element

The use of the element is optional within the SUMMARY element.

[Table of contents]

ACT

[element]

Root element for a legal act

The ACT element is the root element used to mark up various legal acts (adopted texts as well as preparatory acts ). These acts may present a regular structure or not.

All these documents are published in different OJ collections and sections, depending on their nature:

These various structures are further explained in a devoted manual.

Annexes or associated documents attached to an act are marked up separately, using other root elements such as AGR, ANNEX, GENERAL etc.

Note that amended proposals do not come under the scope of the ACT element; they must be marked up with the GENERAL root element.

Model

<xd:element name="ACT">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.INSTANCE"/>
      <xd:choice minOccurs="0maxOccurs="unbounded">
        <xd:element ref="GR.ANNOTATION"/>
        <xd:element ref="TOC"/>
      </xd:choice>
      <xd:element ref="TITLE"/>
      <xd:choice minOccurs="0maxOccurs="unbounded">
        <xd:element ref="GR.ANNOTATION"/>
        <xd:element ref="PROLOG"/>
        <xd:element ref="TOC"/>
      </xd:choice>
      <xd:element ref="PREAMBLE"/>
      <xd:element ref="ENACTING.TERMS"/>
      <xd:element ref="FINALminOccurs="0"/>
    </xd:sequence>
    <xd:attribute name="NNCtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

Generally speaking, the structure of an act comprises:

These components are completed by a section containing bibliographic information and optionally by a table of contents.

The BIB.INSTANCE element contains the information needed to identify the document within the publication to which it belongs.

An optional GR.ANNOTATION element.

An optional table of contents (TOC element).

The title is mandatory and is marked up using the TITLE element.

In the case of preparatory acts, a section titled 'Explanatory memorandum' may be present after the title of the document. This section is marked up using the GR.SEQ element. By the same way, the final part (FINAL) is solely mandatory for adopted texts.

The preamble (PREAMBLE) consists of references to the primary legislation and/or to quoted documents (GR.VISA). It is accompanied by a second section (GR.CONSID) which contains the motivation of the act.

The enacting terms (ENACTING.TERMS) contain the adopted articles as well as information on the enter-into-force-date.

The final part (FINAL) gives information on the application, the place and date of the signature as well as the signatory.

Attributes

The NNC attribute

In some special cases, the numbering of footnotes does not restart on every page, but continues from 1 to n. For those cases the attribute NNC [notes numbering continued] takes the value 'YES'. The default value of this attribute is 'NO'. So the attribute should not be used if the numbering of footnotes follows the general rules and restarts on a new page.

[Table of contents]

ACT.GEN

[element]

Legal act primary document presenting a non-regular structure

The ACT.GEN element is used in the context of consolidated documents in order to mark up an act which presents a non-regular structure (in comparison with ACT).

Model

<xd:element name="ACT.GEN">
  <xd:complexType>
    <xd:sequence>
      <xd:choice minOccurs="0">
        <xd:element ref="PREAMBLE.GEN"/>
        <xd:element ref="PmaxOccurs="unbounded"/>
      </xd:choice>
      <xd:element ref="TOCminOccurs="0"/>
      <xd:element ref="ENACTING.TERMS"/>
      <xd:element ref="FINALminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

t_btx t_btx.struct CONS.DOC.GEN GR.SEQ QUOT.S

General rules

Element

It contains the following sub-elements:

[Table of contents]

ADDITIONAL.DOCS.LSEU

[element]

List of additional documents related to a legislative summary

The ADDITIONAL.DOCS.LSEU element is a list of documents (not legislation summaries) which are related to the current legislation summary, but they are not necessarily quoted.

Model

<xd:element name="ADDITIONAL.DOCS.LSEUtype="t_btx.struct"/>

Used by

ADDITIONAL.DOCS.LSEU CONTENTS.LSEU

General rules

Element

The content consists of elements form the generic type t_btx.struct.

[Table of contents]

ADDR

[element]

Inline address

The ADDR element is used to mark up the address, which is given in the form of continuous text within a text block.

Model

<xd:element name="ADDRtype="t_btx.seq"/>

Used by

t_btx t_btx.ecr t_btx.seq ADDR

General rules

Element

The use of the ADDR element depends on the context. An address is marked up with the ADDR.S element when it is presented separately from the text, with each part of this address presented on distinct physical paragraphs.

Thus, the ADDR element is used:

An ADDR element must be contained within a low-level text element (for example, a P element).

Example

<P>Common guidelines and application forms are available in the European Community at

  <ADDR>European Commission, Directorate-General for Education and Culture, Tempus programme - cooperation with the USA and Canada, B7 8/20, B-1049 Brussels (mail address)</ADDR>.</P>

<P>For further information, please contact :</P>

<P>

  <ADDR>European Commission, Nicole Versijp, B-1049 Brussels</ADDR>.</P>

[Table of contents]

ADDR.S

[element]

Stand-alone address

The ADDR.S element is used to mark up an address which is presented separately from the text.

Model

<xd:element name="ADDR.S">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="PminOccurs="2maxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

t_btx t_btx.ecr t_btx.seq t_btx.struct GR.SEQ QUOT.S

General rules

Element

This element concerns addresses which are clearly presented separately from the text. Such an address starts a new line, and the different parts of the address consist of at least two physical paragraphs (P).

When an address appears within a text block, or on only one line without clear distinction between its different parts, the ADDR element must be used.

Example

<P>For EC applicants seeking further information, please contact:</P>

<ADDR.S>

  <P>Nicole Versijp</P>

  <P>European Commission</P>

  <P>Directorate-General for Education and Culture</P>

  <P>B7 8/20</P>

  <P>B-1049 Brussels</P>

  <P>Tel. (32-2) 296 66 64</P>

  <P>fax (32-2) 295 57 19</P>

  <P>E-mail: nicole.versijp@cec.eu.int</P>

</ADDR.S>

[Table of contents]

AGAINST

[element]

Expression which separates the parties in a case

The AGAINST element is used to mark up the expression which separates the conflicting parties in a case.

Model

<xd:element name="AGAINSTtype="t_btx.seq"/>

Used by

AGAINST PARTIES

General rules

Element

The opponents of a case, plaintiffs (PLAINTIFS) and defendants (DEFENDANTS) are generally separated by an expression like en. against, de. gegen, fr. contre etc. This expression is tagged with the AGAINST element.

Example

<PARTIES>

  <PLAINTIFS>

    <P>Martin Miller</P>

  </PLAINTIFS>

  <AGAINST>contre</AGAINST>

  <DEFENDANTS>

    <P>Commission des Communautés européennes</P>

  </DEFENDANTS>

</PARTIES>

[Table of contents]

AGE.OJ

[element]

Age of the OJ (number of years)

The AGE.OJ element is used to mark up the number of the year of publication of the Official Journal concerned.

Model

<xd:element name="AGE.OJ">
  <xd:simpleType>
    <xd:restriction base="xd:string">
      <xd:pattern value="[1-9][0-9]?"/>
    </xd:restriction>
  </xd:simpleType>
</xd:element>

Used by

BIB.OJ

General rules

Element

This element always consists of a one-digit or two-digit numerical value. In the example below, 45 refers to the forty-fifth year of publication. The numbering started in 1958.

Example

<BIB.OJ>

  <COLL>L</COLL>

  <NO.OJ CLASS="NORMAL">73</NO.OJ>

  <AGE.OJ>45</AGE.OJ>

  <DATE ISO="20020315">20020315</DATE>

  <LG>EN</LG>

  <PRINTER>IC</PRINTER>

  <NO.CAT>FXAL02073ENC</NO.CAT>

  <NO.ISSN>03786978</NO.ISSN>

  <PAGE.SUMMARY>

    <PAGE.FIRST>s1</PAGE.FIRST>

    <PAGE.LAST>s2</PAGE.LAST>

    <PAGE.TOTAL>2</PAGE.TOTAL>

  </PAGE.SUMMARY>

  <PAGE.CONTENTS>

    <PAGE.FIRST>1</PAGE.FIRST>

    <PAGE.LAST>31</PAGE.LAST>

    <PAGE.TOTAL>31</PAGE.TOTAL>

  </PAGE.CONTENTS>

</BIB.OJ>

[Table of contents]

AGE.OJ.SUMMARY

[element]

Age of the OJ (number of years) within a PDF summary

The AGE.OJ.SUMMARY element is used to mark up the number of the year of publication of the Official Journal concerned in the context of a PDF summary.

Model

<xd:element name="AGE.OJ.SUMMARYtype="t_btx"/>

Used by

AGE.OJ.SUMMARY HEADER.SUMMARY

General rules

Element

This element is only used in the context of a PDF summary (SUMMARY.PDF) within the HEADER.SUMMARY element.

[Table of contents]

AGR

[element]

General structure of an agreement

The AGR element is used to mark up the general structure of an agreement.

In general, an agreement is characterised by its multilateral nature. The analysis of its content reveals that it is the result of successful negotiations between several parties representing the European Union and one or more other countries.

If the document does not respect these multilateral criteria, it has to be marked up using the GENERAL element as root element.

The title of an agreement may contain the following expressions: 'agreement', 'exchange of letters', 'protocol', 'convention', 'negotiation', 'protocol of understanding' etc.

With regards to the structure, an agreement may be presented in the format of an act or in the format of an exchange of letters.

Model

<xd:element name="AGR">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.INSTANCE"/>
      <xd:choice maxOccurs="unbounded">
        <xd:element ref="GR.ANNOTATION"/>
        <xd:element ref="TITLE"/>
        <xd:element ref="TOC"/>
      </xd:choice>
      <xd:choice>
        <xd:sequence>
          <xd:element ref="PREAMBLEminOccurs="0"/>
          <xd:element ref="ENACTING.TERMS"/>
          <xd:element ref="FINALminOccurs="0"/>
        </xd:sequence>
        <xd:element ref="COLL.LETTERS"/>
      </xd:choice>
    </xd:sequence>
    <xd:attribute name="NNCtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

The AGR element is subdivided into the following elements:

If the agreement follows the structure of an act, the contents consist of:

The following agreement follows such a structure:

If the agreement is presented in the format of an exchange of letters (as shown below), the content is marked up with the COLL.LETTERS element.

Attributes

The NNC attribute

In some special cases, the numbering of footnotes does not restart on every page, but continues from 1 to n. For those cases the attribute NNC [notes numbering continued] takes the value 'YES'. The default value of this attribute is 'NO'. So the attribute should not be used if the numbering of footnotes follows the general rules and restarts on a new page.

[Table of contents]

ALINEA

[element]

Alinea of a legal article

In the context of EU legal texts, alinea is the lowest-level structure component of a legal article.

An alinea is a subdivision of the article and of the legal paragraph which does not have a distinctive sign (number, letter or dash).

Model

<xd:element name="ALINEAtype="t_btx"/>

Used by

t_btx t_btx.ecr t_btx.struct ALINEA ARTICLE ARTICLE GR.SEQ PARAG PARAG QUOT.S SUBDIV SUBDIV

General rules

Element

An alinea may consist of a single sentence, or of several sentences which are grouped together from a legal point of view.

These sentences may be grouped together in the same physical paragraph. An alinea may also contain one or more of the elements defined in the complex type t_btx.

A rule to be applied in order to identify an alinea is that it should be understandable when extracted from its context (legal article or legal paragraph). Thus, the introductory sentence of a list and the list itself must be in the same ALINEA element (see second example below).

Additionally, on all levels, optional comments (COMMENT) may be inserted.

Example

<ALINEA>This Regulation shall enter into force on the day of its publication in the

  <HT TYPE="ITALIC">Official Journal of the European Communities</HT>.</ALINEA>

<ALINEA>

  <P>Member States are invited to send to the Commission and to all other Member States, by 31 August 2002, all the information as required by Article 7(3) of Directive 86/362/EEC and Article 4(3) of Directive 90/642/EEC concerning the 2001 monitoring exercise to ensure, at least by check sampling, compliance with maximum pesticide residue levels including:</P>

  <LIST TYPE="alpha">

    <ITEM>

      <NP>

        <NO.P>(a)</NO.P>

        <TXT>the results of ...</TXT>

      </NP>

    </ITEM>

    <ITEM>

      <NP>

        <NO.P>(b)</NO.P>

        <TXT>information on ...</TXT>

      </NP>

    </ITEM>

  </LIST>

</ALINEA>

[Table of contents]

AMEND

[element]

Amendment

The AMEND element is used to mark up an amendment.

Model

<xd:element name="AMEND">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="TITLEminOccurs="0"/>
      <xd:element ref="OLDminOccurs="0"/>
      <xd:element ref="NEWminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

GR.AMEND

General rules

Element

An amendment may consist of the following elements:

At least one of the two last elements must be provided.

In some cases, amendments are introduced by a title indicating the number of the amendment.

For example, in the English language version, the term 'Amendment No 11' may be used. In this case, the various amendments, each of which being marked up with an AMEND element, are easy to distinguish.

In order to identify the scope of an amendment, the following rules should be applied:

Example

Considering the following example:

A global analysis indicates that the numbered paragraphs are recitals (CONSID). Then, the two first amendments in the example are marked up as :

<AMEND>

  <OLD>

    <CONSID>

      <NP>

        <NO.P>(4)</NO.P>

        <TXT>The integration of refugees into the society of the country in which they are established....</TXT>

      </NP>

    </CONSID>

  </OLD>

  <NEW>

    <P>Unchanged</P>

  </NEW>

</AMEND>

<AMEND>

  <NEW>

    <CONSID>

      <NP>

        <NO.P>(5)</NO.P>

        <TXT>The integration of refugees into the society of the host country could also be helped by supporting the actions taken by non-governmental organisations working to achieve social integration.</TXT>

      </NP>

    </CONSID>

  </NEW>

</AMEND>

[Table of contents]

ANNEX

[element]

Root element for an annex

The ANNEX element is the root element used to mark up annexes. These documents are identified in their title by the words 'annex', 'appendix', 'addendum' etc.

If there is no clear indication characterising the document as an annex, it must be marked up using the GENERAL element as root element.

In the case of complex documents, which contain several annexes or associated documents, the series of annexes may be introduced by a table of contents. This table must be considered as a separate document, marked up using ANNEX as the root element.

Apart from the bibliographical references and the title, annex content may follow various structures. It may consist of tables, or of structured text blocks. An annex may also quote an entire document or document parts.

Model

<xd:element name="ANNEX">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.INSTANCE"/>
      <xd:choice maxOccurs="unbounded">
        <xd:element ref="GR.ANNOTATION"/>
        <xd:element ref="TITLE"/>
        <xd:element ref="TOC"/>
      </xd:choice>
      <xd:element ref="CURR.TITLEminOccurs="0"/>
      <xd:element ref="CONTENTS"/>
    </xd:sequence>
    <xd:attribute name="NNCtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

An annex contains:

If an annex consists of a single quotation of an entire document, this quoted document has to be marked up as a separate instance. A reference (via the INCL.ELEMENT element) to this external document is provided in the content of the first one.

In some cases the distinction between a subtitle of an annex and the title of a GR.SEQ element is not obvious. The inclusion of the 'subtitle' into a GR.SEQ element is then absolutely acceptable.

Attributes

The NNC attribute

In some special cases, the numbering of footnotes does not restart on every page, but continues from 1 to n. For those cases the attribute NNC [notes numbering continued] takes the value 'YES'. The default value of this attribute is 'NO'. So the attribute should not be used if the numbering of footnotes follows the general rules and restarts on a new page.

[Table of contents]

ANNOTATION

[element]

Annotation

From a semantic point of view, there are several types of notes, including footnotes, Nota Bene, remarks etc.

The ANNOTATION element is used to mark up such notes, except the footnotes (see the NOTE element). This kind of notes is referred as "annotation" in the following.

Unlike footnotes, an annotation does not have a callout, and it may generally appear close to text blocks or higher-level structures in order to give explanations about their contents.

An ANNOTATION element can have a title group.

The annotations may be introduced by the following:

Annotations may appear in groups or individually. When there is more than one annotation in the group, the annotation can be numbered.

Model

<xd:element name="ANNOTATION">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="TITLEminOccurs="0"/>
      <xd:choice>
        <xd:element ref="NP"/>
        <xd:element ref="PmaxOccurs="unbounded"/>
      </xd:choice>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

t_btx t_btx.ecr t_btx.struct CONS.ANNEX CONS.DOC CONS.DOC.GEN GR.ANNOTATION GR.SEQ QUOT.S

General rules

Element

The ANNOTATION element contains an optional TITLE, followed by either one numbered paragraph (NP) or an unlimited number of paragraphs (P).

The TITLE element is used only if the title is on a separate line than the text of the annotation.

If a single annotation is introduced by a title highlighted in a font which differs from the standard font, and if this title is on the same line as the text of the annotation (for example, where one of the expressions listed above is used), this title must be identified using an HT element.

Example

<ANNOTATION>

  <TITLE>

    <TI>

      <P>Remark:</P>

    </TI>

  </TITLE>

  <P>This quota is valid only for Belgium and Sweden</P>

</ANNOTATION>

<ANNOTATION>

  <P>

    <HT TYPE="ITALIC">N.B.:</HT> the distances above are given in kilometers.</P>

</ANNOTATION>

[Table of contents]

ANONYMOUS

[element]

Anonymisation of personal names

The element ANONYMOUS is a placeholder for personal data which – due to individual rights – must not be publisher.

Model

<xd:element name="ANONYMOUS">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="NOTE"/>
    </xd:sequence>
    <xd:attribute name="PLACEHOLDERtype="xd:stringuse="optional"/>
  </xd:complexType>
</xd:element>

Used by

t_btx t_btx.ecr t_btx.seq

General rules

Element

If a personal name must not be published, the complete name has to be replaced by the element ANONYMOUS.

The only contents of the element is a note (NOTE) with the following text according to the language:

If in the same document other texts have to be anonymised the note refers to the first one by means of the attribute NOTE.REF instead of NOTE.ID.

Attributes

The attribute PLACEHOLDER

The attribute contains the a text or symbol which replaces the original information. The attribute is optional; in case it is absent the anonymised text is replaced by a no-break-spae (&#xA0;).

Example

<TBL NO.SEQ="0001COLS="2">

  <GR.NOTES>

    <NOTE NOTE.ID="E0002NUMBERING="STAR">

      <P>Information erased within the framework of the protection of individuals with regard to the processing of personal data.</P>

    </NOTE>

  </GR.NOTES>

  <CORPUS>

    <ROW>

      <CELL COL="1">CLAUSEN</CELL>

      <CELL COL="2">Lars</CELL>

    </ROW>

    <ROW>

      <CELL COL="1">

        <IE>        </IE>

      </CELL>

      <CELL COL="2">

        <ANONYMOUS>

          <NOTE NUMBERING="STARNOTE.REF="E0002">          </NOTE>

        </ANONYMOUS>

      </CELL>

    </ROW>

    <ROW>

      <CELL COL="1">MESQUITA</CELL>

      <CELL COL="2">Artur</CELL>

    </ROW>

    <ROW>

      <CELL COL="1">

        <IE>        </IE>

      </CELL>

      <CELL COL="2">

        <ANONYMOUS>

          <NOTE NUMBERING="STARNOTE.REF="E0002">          </NOTE>

        </ANONYMOUS>

      </CELL>

    </ROW>

  </CORPUS>

</TBL>

[Table of contents]

APPEAL.TABLE

[element]

List of appeals

In some volumes of ECR publications the list of appeals is published.

Model

<xd:element name="APPEAL.TABLE">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.APPEAL.TABLE"/>
      <xd:element ref="TITLE"/>
      <xd:element ref="CONTENTS"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

The element contains the following mandatory sub-elements:

[Table of contents]

APPELANT

[element]

Additional party in a case

The APPELANT element is used to mark up the additional parties participating in a case.

Model

<xd:element name="APPELANT">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="PmaxOccurs="unbounded"/>
      <xd:element ref="PARTY.STATUSminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

PARTIES

General rules

Element

The element contains one or more physical paragraphs (P) and an optional description of the status of the party participating in a case (PARTY.STATUS).

[Table of contents]

APPLICANT

[element]

Part of the introduction of an opinion

The APPLICANT element describes the person who introduced a call for opinion.

It may contain one or more of the elements defined in the t_btx complex type.

Model

<xd:element name="APPLICANTtype="t_btx"/>

Used by

APPLICANT INTRO.OPINION

General rules

Element

The use of the element is mandatory within the INTRO.OPINION element.

[Table of contents]

ARCHIVED

[element]

Indication if the summarized act is still active

The ARCHIVED element is used to signal that an act taken into account by a legislation summary is still active or became obsolete and thus was archived.

Model

<xd:element name="ARCHIVED">
  <xd:complexType>
    <xd:attribute name="VALUEdefault="NO">
      <xd:simpleType>
        <xd:restriction base="xd:string">
          <xd:enumeration value="NO"/>
          <xd:enumeration value="YES"/>
        </xd:restriction>
      </xd:simpleType>
    </xd:attribute>
  </xd:complexType>
</xd:element>

Used by

BIB.LSEU

General rules

Element

The content of the element may be only one of the values 'YES' or 'NO', the latter being the default value.

[Table of contents]

ARGUMENTS

[element]

Part of the contents of an opinion or a ruling

The ARGUMENTS element contains the essential arguments for an opinion or a ruling.

It may contain one or more of the elements defined in the t_btx.struct complex type.

Model

<xd:element name="ARGUMENTStype="t_btx.struct"/>

Used by

ARGUMENTS CONTENTS.OPINION CONTENTS.RULING

General rules

Element

The element is optionally used within CONTENTS.OPINION and CONTENTS.RULING.

[Table of contents]

ARTICLE

[element]

Legal article

In the context of European legal texts, a legal article is the basic component of the enacting terms. Articles are easily distinguishable by their standardized title, which consists of the expression "Article" followed by a sequential number.

The title (TI.ART element) is mandatory, and from a layout point of view, it's printed centered above the contents of the article. The subtitle, when present, has to be encoded with the STI.ART element.

Depending on the complexity, the content consists of one of the following structures:

Additionally, on all levels, optional comments (COMMENT) may be inserted.

Model

<xd:element name="ARTICLE">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="TI.ART"/>
      <xd:element ref="STI.ARTminOccurs="0"/>
      <xd:choice minOccurs="0">
        <xd:sequence>
          <xd:element ref="ALINEA"/>
          <xd:choice minOccurs="0maxOccurs="unbounded">
            <xd:element ref="ALINEA"/>
            <xd:element ref="COMMENT"/>
            <xd:element ref="QUOT.S"/>
          </xd:choice>
        </xd:sequence>
        <xd:sequence>
          <xd:element ref="PARAG"/>
          <xd:choice minOccurs="0maxOccurs="unbounded">
            <xd:element ref="COMMENT"/>
            <xd:element ref="PARAG"/>
          </xd:choice>
        </xd:sequence>
      </xd:choice>
      <xd:sequence minOccurs="0">
        <xd:element ref="SUBDIV"/>
        <xd:choice minOccurs="0maxOccurs="unbounded">
          <xd:element ref="COMMENT"/>
          <xd:element ref="SUBDIV"/>
        </xd:choice>
      </xd:sequence>
    </xd:sequence>
    <xd:attribute name="IDENTIFIERuse="required">
      <xd:simpleType>
        <xd:restriction base="xd:string">
          <xd:pattern value="\d{3}(\-\d{3})?[A-Z]*"/>
        </xd:restriction>
      </xd:simpleType>
    </xd:attribute>
  </xd:complexType>
</xd:element>

Used by

t_btx t_btx.ecr t_btx.struct DIVISION ENACTING.TERMS GR.SEQ QUOT.S

General rules

Element

An article may contain various general structures, such as physical paragraphs, lists, tables etc. However, they have to be encapsulated in an allowed child element of the ARTICLE tag, namely ALINEA, PARAG or SUBDIV. For example, if an article contains a list, the corresponding LIST element must be encapsulated in an ALINEA element.

Attributes

The IDENTIFIER attribute

The IDENTIFIER attribute of the ARTICLE element is used to identify the legal sequence number of the current article within the enacting terms.

Basically, its value must be deduced from the article title.

It must at least correspond to the following format: 'xxx'. If necessary, the initial positions must be filled with zeros.

For example, the article which has the title "Article 4", gets '004' as IDENTIFIER attribute value.

For the articles which have specific numbering such as bis (ter, quater, ter bis etc.), the 'xxx' value is extended with uppercase letters 'A' (respectively 'B', 'C', etc.).

For example, the IDENTIFIER attribute value of legal 'Article 1bis' will be '001A' ('001B' for 'Article 1ter',...).

For a quoted legal article, the same rules have to be applied, with respects to the title of the quoted article. For example, if the 'Article 1' quotes in its contents the 'Article 5' of a previously published legal act, the IDENTIFIER attribute value of the quoted article is '005'.

The IDENTIFER attribute of a single article always has the value '001'.

The use of this attribute is mandatory.

Example

The enacting terms below contain articles which follow two different structures. The first article consists of five legal paragraphs, while the fourth one is subdivided into two alineas.

<ENACTING.TERMS>

  <ARTICLE IDENTIFIER="001">

    <TI.ART>Article 1</TI.ART>

    <PARAG IDENTIFIER="001.001">

      <NO.PARAG>1.</NO.PARAG>

      <ALINEA>A provisional anti-dumping duty is hereby imposed on imports of tube and pipe fittings (other than cast fittings, flanges and threaded fittings), of iron or steel ... </ALINEA>

    </PARAG>

    <PARAG IDENTIFIER="001.002">

      <NO.PARAG>2.</NO.PARAG>

      <ALINEA>....</ALINEA>

    </PARAG>

    <PARAG IDENTIFIER="001.003">

      <NO.PARAG>3.</NO.PARAG>

      <ALINEA>Notwithstanding paragraph 1, the provisional anti-dumping duty shall not apply to imports released into free circulation in accordance with Article 2.</ALINEA>

    </PARAG>

    <PARAG IDENTIFIER="001.004">

      <NO.PARAG>4.</NO.PARAG>

      <ALINEA>The release for free circulation in the Community of the product referred to in paragraph 1 shall be subject to the provision of a security, equivalent to the amount of the provisional duty.</ALINEA>

    </PARAG>

    <PARAG IDENTIFIER="001.005">

      <NO.PARAG>5.</NO.PARAG>

      <ALINEA>Unless otherwise specified, the provisions in force concerning customs duties shall apply.</ALINEA>

    </PARAG>

  </ARTICLE>

  <ARTICLE IDENTIFIER="002">...</ARTICLE>

  <ARTICLE IDENTIFIER="003">...</ARTICLE>

  <ARTICLE IDENTIFIER="004">

    <TI.ART>Article 4</TI.ART>

    <ALINEA>This Regulation shall enter into force on the day following that of its publication in the

      <HT TYPE="ITALIC">Official Journal of the European Communities</HT>.</ALINEA>

    <ALINEA>Article 1 of this Regulation shall apply for a period of six months.</ALINEA>

  </ARTICLE>

</ENACTING.TERMS>

The two articles below have both a subtitle. The list in the second paragraph of the second article, as well as its introductory sentence, are encapsulated in an ALINEA tag.

<ENACTING.TERMS>

  <ARTICLE IDENTIFIER="001">

    <TI.ART>Article 1</TI.ART>

    <STI.ART>Purpose</STI.ART>

    <ALINEA>The purpose of this Regulation is to establish an accelerated phasing-in scheme for the application of the double hull or equivalent design requirements of the MARPOL 73/78 Convention to single hull oil tankers.</ALINEA>

  </ARTICLE>

  <ARTICLE IDENTIFIER="002">

    <TI.ART>Article 2</TI.ART>

    <STI.ART>Scope</STI.ART>

    <PARAG IDENTIFIER="002.001">

      <NO.PARAG>1.</NO.PARAG>

      <ALINEA>

        <P>This Regulation shall apply to oil tankers of

          <FT TYPE="NUMBER">5000</FT> tons deadweight and above:</P>

        <LIST TYPE="DASH">

          <ITEM>

            <P>entering into a port or offshore terminal under the jurisdiction of a Member State, irrespective of their flag, or</P>

          </ITEM>

          <ITEM>

            <P>flying the flag of a Member State.</P>

          </ITEM>

        </LIST>

      </ALINEA>

    </PARAG>

    <PARAG IDENTIFIER="002.002">

      <NO.PARAG>2.</NO.PARAG>

      <ALINEA>This Regulation shall not apply to any warship, naval auxiliary or other ship, owned or operated by a State and used, for the time being, only on government non-commercial service. Member States shall, so far as is reasonable and practicable, endeavour to respect this Regulation for the ships referred to in this paragraph.</ALINEA>

    </PARAG>

  </ARTICLE>

  <ARTICLE>....</ARTICLE>

</ENACTING.TERMS>

[Table of contents]

ASSOCIATED.TO

[element]

Association to an accompanying document

The empty element defines the link between an associated document whose title is supposed to appear in the table of contents and the document it is associated to. The element is based on the complex type t_ref.phys.

Model

<xd:element name="ASSOCIATED.TOtype="t_ref.phys"/>

Used by

ASSOCIATED.TO DOC.MAIN.PUB

General rules

Element

Documents such as international agreements may only be published in the Official Journal if they are accompanied by a decision. Later on they are generally treated as autonomous documents. The first aspect, however, justifies to maintain a link to the accompanying document, which itself has a link to the associated document(s) (ASSOCIATES).

[Table of contents]

ASSOCIATES

[element]

Association of a document

The empty element defines the link to an associated document whose title is also supposed to appear in the table of contents. The element is based on the complex type t_ref.phys.

Model

<xd:element name="ASSOCIATEStype="t_ref.phys"/>

Used by

ASSOCIATES DOC.MAIN.PUB

General rules

Element

Documents such as international agreements may only be published in the Official Journal if they are accompanied by a decision. Such a decision – in similar cases it may be a treaty – defines link(s) to associated documents. The associated document itself contains a link to the accompanying instance (ASSOCIATED.TO).

[Table of contents]

AUTHOR

[element]

Author

The AUTHOR element is used to mark up the name of the author of the document, or the publisher of a publication. In the case of the OJ, the author is an institution.

Model

<xd:element name="AUTHORtype="xd:string"/>

Used by

AUTHOR BIB.CASE BIB.DECISION.ECR BIB.DOC BIB.GEN.PUB BIB.JUDGMENT BIB.OPINION BIB.ORDER BIB.RULING BIB.SUMMARY OTH.PUB OTH.PUB.CL

General rules

Element

If there are several authors and/or publishers, each one must be marked up separately.

As the number and names of authoring services can change frequently, the following list only indicates some examples; it is by no means exhaustive:

Although the element is defined as optional, it must not be omitted if the author can be identified.

[Table of contents]

BAR

[element]

Vertical bar

The empty element indicates a single vertical bar which is used in mathematical formulas.

Model

<xd:element name="BAR">
  <xd:complexType/>
</xd:element>

Used by

t_btx.formula

General rules

Element

The element must not be used to indicate absolute values, therefore see EXPR.

[Table of contents]

BIB.APPEAL.TABLE

[element]

Metadata for a list of appeals

The element defines the metadata for describing a list of appeals. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.APPEAL.TABLE">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.ECR"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

APPEAL.TABLE

General rules

Element

All elements are mandatory.

Example

<BIB.ECR.GENERAL>

  <REF.ECR FILE="ECR2003FR.10.xml">

    <YEAR>2003</YEAR>

    <VOLUME.ECR>10</VOLUME.ECR>

  </REF.ECR>

  <PAGE.FIRST.ECR>PI</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>PVI</PAGE.LAST.ECR>

  <PAGE.TOTAL>6</PAGE.TOTAL>

</BIB.ECR.GENERAL>

[Table of contents]

BIB.CASE

[element]

Metadata for a case

The element defines the metadata for describing the publication of a case. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.CASE">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.ECR"/>
      <xd:element ref="LG.DOC"/>
      <xd:element ref="LG.CASE"/>
      <xd:element ref="DATEminOccurs="0"/>
      <xd:element ref="YEARminOccurs="0"/>
      <xd:element ref="NO.CASEminOccurs="0maxOccurs="unbounded"/>
      <xd:element ref="TYPE.CASE"/>
      <xd:element ref="NO.CELEXminOccurs="0"/>
      <xd:element ref="NO.ECLIminOccurs="0"/>
      <xd:element ref="NO.SEQ"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="AUTHORminOccurs="0"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

CASE

General rules

Element

All sub-elements are mandatory except the AUTHOR, DATE, YEAR and NO.CASE elements. The DATE, YEAR and NO.CASE elements should not be used for a case corrigendum. For technical reasons the NO.CELEX element is declared as optional; its use, however, is compulsory.

Example

<BIB.CASE>

  <REF.ECR FILE="ECR1972FR.06.xml">

    <YEAR>1972</YEAR>

    <VOLUME.ECR>06</VOLUME.ECR>

  </REF.ECR>

  <LG.DOC>FR</LG.DOC>

  <LG.CASE>FR</LG.CASE>

  <DATE ISO="19710624">  </DATE>

  <YEAR>1970</YEAR>

  <NO.CASE>53-70</NO.CASE>

  <TYPE.CASE>JUDGMENT-C</TYPE.CASE>

  <NO.CELEX>61970J0053</NO.CELEX>

  <NO.SEQ>0001</NO.SEQ>

  <PAGE.FIRST.ECR>601</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>611</PAGE.LAST.ECR>

  <PAGE.TOTAL>11</PAGE.TOTAL>

  <AUTHOR>CJ</AUTHOR>

</BIB.CASE>

[Table of contents]

BIB.CHRON.TABLE

[element]

Metadata for a chronological list of judgements, orders etc.

The element defines the metadata for describing a chronological list of cases. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.CHRON.TABLE">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.ECR"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

CHRON.TABLE

General rules

Element

All elements are mandatory.

Example

<BIB.ECR.GENERAL>

  <REF.ECR FILE="ECR2003FR.10.xml">

    <YEAR>2003</YEAR>

    <VOLUME.ECR>10</VOLUME.ECR>

  </REF.ECR>

  <PAGE.FIRST.ECR>311</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>326</PAGE.LAST.ECR>

  <PAGE.TOTAL>16</PAGE.TOTAL>

</BIB.ECR.GENERAL>

[Table of contents]

BIB.CHRON.TABLE.NP

[element]

Metadata for a chronological list of not published judgements and orders

The element defines the metadata for describing a chronological list of not published judgments and orders. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.CHRON.TABLE.NP">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.ECR"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

CHRON.TABLE.NP

General rules

Element

All elements are mandatory.

Example

<BIB.ECR.GENERAL>

  <REF.ECR FILE="ECR2003FR.10.xml">

    <YEAR>2003</YEAR>

    <VOLUME.ECR>10</VOLUME.ECR>

  </REF.ECR>

  <PAGE.FIRST.ECR>327</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>329</PAGE.LAST.ECR>

  <PAGE.TOTAL>3</PAGE.TOTAL>

</BIB.ECR.GENERAL>

[Table of contents]

BIB.CONCLUSION

[element]

Metadata for a conclusion

The element defines the metadata for describing the conclusion of a case. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.CONCLUSION">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.CASE.F1minOccurs="0"/>
      <xd:element ref="REF.CASE"/>
      <xd:element ref="NO.CELEXminOccurs="0"/>
      <xd:element ref="NO.ECLIminOccurs="0"/>
      <xd:element ref="NO.SEQ"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

CONCLUSION

General rules

Element

All elements, except REF.CASE.F1, are mandatory. For technical reasons the NO.CELEX element is declared as optional; its use, however, is compulsory.

Example

<BIB.CONCLUSION>

  <REF.CASE FILE="ECR1972FR.010060101.case.xml">

    <NO.CASE>53-70</NO.CASE>

  </REF.CASE>

  <NO.CELEX>61970C0053</NO.CELEX>

  <NO.SEQ>0001.0002</NO.SEQ>

  <PAGE.FIRST.ECR>610</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>611</PAGE.LAST.ECR>

  <PAGE.TOTAL>2</PAGE.TOTAL>

</BIB.CONCLUSION>

[Table of contents]

BIB.CORRIG.ECR

[element]

Metadata for a corrigendum in the context of European Court Reports

The element defines the metadata for describing a corrigendum published in the European Court Reports. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.CORRIG.ECR">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.CASE.F1minOccurs="0"/>
      <xd:element ref="REF.CASE"/>
      <xd:element ref="NO.SEQ"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

CORRIGENDUM.ECR

General rules

Element

All elements, except REF.CASE.F1, are mandatory.

Example

<BIB.CORRIG.ECR>

  <REF.CASE FILE="ECR1998FR.01r005701.case.xml">  </REF.CASE>

  <NO.SEQ>0001.0001</NO.SEQ>

  <PAGE.FIRST.ECR>LVII</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>LVII</PAGE.LAST.ECR>

  <PAGE.TOTAL>1</PAGE.TOTAL>

</BIB.CORRIG.ECR>

[Table of contents]

BIB.DATA

[element]

Bibliographical data

The BIB.DATA element is used to mark up the bibliographical data pertinent to a basic act amendment.

Model

<xd:element name="BIB.DATA">
  <xd:complexType>
    <xd:sequence>
      <xd:choice>
        <xd:element ref="BIB.INSTANCE.CONS"/>
        <xd:element ref="OTH.PUB"/>
      </xd:choice>
      <xd:element ref="NO.CELEXminOccurs="0maxOccurs="unbounded"/>
      <xd:element ref="DATEminOccurs="0"/>
      <xd:element ref="TITLE"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

CORRIG FAM.COMP MOD.ACT

General rules

Element

This element consists of the following:

Example

<BIB.DATA>

  <BIB.INSTANCE.CONS>

    <DATE ISO="20000825">20000825</DATE>

    <LG.OJ>EN</LG.OJ>

    <LG.DOC>EN</LG.DOC>

    <PAGE.FIRST>7</PAGE.FIRST>

    <PAGE.SEQ>1</PAGE.SEQ>

    <PAGE.LAST>47</PAGE.LAST>

    <PAGE.TOTAL>41</PAGE.TOTAL>

    <DOC.TYPE>DECISION</DOC.TYPE>

  </BIB.INSTANCE.CONS>

  <NO.CELEX>300D0520</NO.CELEX>

  <DATE ISO="20000726">20000726</DATE>

  <TITLE>

    <TI>

      <P>

        <HT TYPE="UC">Commission Decision</HT>

      </P>

      <P>of 26 July 2000</P>

      <P>pursuant to Directive 95/46/EC of the European Parliament and of the Council on the adequacy of the protection provided by the safe harbour privacy principles and related frequently asked questions issued by the US Department of Commerce</P>

      <P>(notified under document number C(2000) 2441)</P>

      <P>(Text with EEA relevance)</P>

      <P>(2000/520/EC)</P>

    </TI>

  </TITLE>

</BIB.DATA>

[Table of contents]

BIB.DATA.CL

[element]

Bibliographic data for a member of a consolidation family

The BIB.DATA.CL element is used to mark up the bibliographic data for a member of a consolidation family.

Model

<xd:element name="BIB.DATA.CL">
  <xd:complexType>
    <xd:sequence>
      <xd:choice>
        <xd:sequence>
          <xd:element ref="OJ.CL"/>
          <xd:element ref="SPEC.EDminOccurs="0maxOccurs="unbounded"/>
        </xd:sequence>
        <xd:element ref="OTH.PUB.CL"/>
      </xd:choice>
      <xd:element ref="NO.CELEX"/>
      <xd:element ref="DATE.ADOPTminOccurs="0"/>
      <xd:element ref="TITLEminOccurs="0"/>
    </xd:sequence>
    <xd:attribute name="FILENAMEtype="xd:string"/>
  </xd:complexType>
</xd:element>

Used by

CORRIG.CL FAM.COMP.CL MOD.ACT.CL

General rules

Element

It contains the following sub-elements:

The element must at least consist of a reference to the publication and the CELEX number; the adoption date and the title are optional.

Attributes

The FILENAME attribute

The FILENAME attribute contains the filename of the external file, if it has a special format and does not respect the filename conventions. Its value contains the language code and information on the filename; the two parts are separated by ": ". Various languages codes are separated by ";".

In cases where the filename is the same for all languages, the value is only represented once and the language code is being replaced by "LL".

[Table of contents]

BIB.DECISION.ECR

[element]

Metadata for a Court decision

The element defines the metadata for describing a Court decision within a case. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.DECISION.ECR">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.CASE.F1minOccurs="0"/>
      <xd:element ref="REF.CASE"/>
      <xd:element ref="NO.CELEXminOccurs="0"/>
      <xd:element ref="NO.ECLIminOccurs="0"/>
      <xd:element ref="NO.SEQ"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="AUTHOR"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

DECISION.ECR

General rules

Element

All elements, except REF.CASE.F1, are mandatory. For technical reasons the NO.CELEX element is declared as optional; its use, however, is compulsory.

Example

<BIB.DECISION.ECR>

  <REF.CASE FILE="ECR1972FR.060060101.case.xml">

    <NO.CASE>53-70</NO.CASE>

  </REF.CASE>

  <NO.CELEX>61970J0053</NO.CELEX>

  <NO.SEQ>0001.0001</NO.SEQ>

  <PAGE.FIRST.ECR>602</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>610</PAGE.LAST.ECR>

  <PAGE.TOTAL>9</PAGE.TOTAL>

  <AUTHOR>CJ</AUTHOR>

</BIB.DECISION.ECR>

[Table of contents]

BIB.DOC

[element]

Metadata for a document

The element defines the metadata for describing a document. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.DOC">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="PROD.IDminOccurs="0"/>
      <xd:element ref="FIN.IDminOccurs="0"/>
      <xd:element ref="NO.DOCminOccurs="0maxOccurs="unbounded"/>
      <xd:element ref="DURAB"/>
      <xd:element ref="AUTHORminOccurs="0maxOccurs="unbounded"/>
      <xd:element ref="COMminOccurs="0"/>
      <xd:element ref="DOC.CORRminOccurs="0maxOccurs="unbounded"/>
      <xd:element ref="DOC.CORR.SEminOccurs="0maxOccurs="unbounded"/>
      <xd:element ref="EEAminOccurs="0"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

DOC

General rules

Element

All elements are optional, apart from the DURAB element, which is mandatory.

The NO.DOC element specifies the number of the described document. It may be absent for those documents which do not have a document number or if the document number is unknown. In the latter case OP has to be contacted for clarification. In some cases, this element has to be repeated.

The durability of a document is specified by the DURAB element. If the document has no specification concerning this aspect, the content of the DURAB element is 'NA' (not applicable).

The author of a document or the service which is responsible for the edition of the document is described by the AUTHOR element. It may be absent if the value cannot be derived from the document. In general, however, the value will be available.

The DOC.CORR element must be included if it is a corrigendum for a document originally published in the OJ. The DOC.CORR.SE element must be included if it is a corrigendum for a document published in the special edition. There may be several DOC.CORR elements if the corrigenda correct several original documents. A corrigendum is not considered to be an original document.

The presence of the EEA element indicates that the document is of interest to the EEA (European Economic Area).

Example

<BIB.DOC>

  <NO.DOC FORMAT="NYTYPE="OJ">

    <NO.CURRENT>460</NO.CURRENT>

    <YEAR>2002</YEAR>

    <COM>EC</COM>

  </NO.DOC>

  <DURAB TYPE="EPH">  </DURAB>

  <AUTHOR>COM</AUTHOR>

  <COM>EC</COM>

  <REF.CORE.METADATA>C_2002_9999-ec-publication-v1.0.xml</REF.CORE.METADATA>

</BIB.DOC>

[Table of contents]

BIB.ECR

[element]

Metadata for the publication of a volume of cases

The element defines the metadata for describing a fascicle of court cases. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.ECR">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="YEAR"/>
      <xd:element ref="NO.FASCICLE"/>
      <xd:element ref="PART.ECR"/>
      <xd:element ref="LG.PUB"/>
      <xd:choice>
        <xd:element ref="NO.ISSN"/>
        <xd:sequence>
          <xd:element ref="NO.ISSN.ELECTRONIC"/>
          <xd:element ref="NO.ISSN.PRINTminOccurs="0"/>
        </xd:sequence>
      </xd:choice>
      <xd:element ref="NO.CATminOccurs="0"/>
      <xd:element ref="NO.CAT.GLOBALminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

ECR

General rules

Element

All elements are mandatory except NO.CAT and NO.CAT.GLOBAL.

Example

<BIB.ECR>

  <YEAR>2006</YEAR>

  <NO.FASCICLE>1</NO.FASCICLE>

  <PART.ECR>I</PART.ECR>

  <LG.PUB>FR</LG.PUB>

  <NO.ISSN>10193170</NO.ISSN>

  <NO.CAT>QDAB0601BFRC</NO.CAT>

  <NO.CAT.GLOBAL>QDAB06001FRC</NO.CAT.GLOBAL>

</BIB.ECR>

[Table of contents]

BIB.ECR.GENERAL

[element]

Metadata for the ECR publication fragments which are not related to a case

The element defines the metadata for describing the fragments of an ECR publication which give general instructions and information on its use. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.ECR.GENERAL">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.ECR"/>
      <xd:element ref="LG.DOC"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

ECR.GENERAL

General rules

Element

All elements are mandatory.

Example

<BIB.ECR.GENERAL>

  <REF.ECR FILE="ECR2003FR.10.xml">

    <YEAR>2003</YEAR>

    <VOLUME.ECR>10</VOLUME.ECR>

  </REF.ECR>

  <LG.DOC>FR</LG.DOC>

  <PAGE.FIRST.ECR>1</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>2</PAGE.LAST.ECR>

  <PAGE.TOTAL>2</PAGE.TOTAL>

</BIB.ECR.GENERAL>

[Table of contents]

BIB.GEN.PUB

[element]

Metadata for general publications

The element defines the metadata for describing general publications.

Model

<xd:element name="BIB.GEN.PUB">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="AUTHORminOccurs="0"/>
      <xd:element ref="TITLEminOccurs="0"/>
      <xd:element ref="PUBLISHERminOccurs="0"/>
      <xd:element ref="SIZEminOccurs="0"/>
      <xd:element ref="NO.CATminOccurs="0"/>
      <xd:element ref="NO.DOIminOccurs="0"/>
      <xd:element ref="NO.ISBNminOccurs="0"/>
      <xd:choice minOccurs="0">
        <xd:element ref="NO.ISSN"/>
        <xd:sequence>
          <xd:element ref="NO.ISSN.ELECTRONIC"/>
          <xd:element ref="NO.ISSN.PRINTminOccurs="0"/>
        </xd:sequence>
      </xd:choice>
      <xd:element ref="INFO.PUBLISHERminOccurs="0"/>
      <xd:element ref="PminOccurs="0maxOccurs="unbounded"/>
      <xd:element ref="FMX.GEN"/>
      <xd:element ref="PAPER.GENminOccurs="0"/>
      <xd:element ref="PDF.GENminOccurs="0"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

PUBLICATION

General rules

Element

This element, according to the case, may contain one or more of the following sub-elements:

All elements are optional, apart from the FMX.GEN element, which is mandatory.

[Table of contents]

BIB.INSTANCE

[element]

References of the publication

The BIB.INSTANCE element is used to mark up the references which unambiguously identify a document within the publication.

Model

<xd:element name="BIB.INSTANCE">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="DOCUMENT.REF"/>
      <xd:element ref="SPEC.EDminOccurs="0"/>
      <xd:element ref="EEAminOccurs="0"/>
      <xd:element ref="DATEmaxOccurs="unbounded"/>
      <xd:element ref="LG.DOC"/>
      <xd:element ref="NO.SEQminOccurs="0"/>
      <xd:element ref="PAGE.FIRST"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="INCLUSIONSminOccurs="0"/>
      <xd:element ref="NO.DOCminOccurs="0maxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

ACT AGR ANNEX CJT COMPETITION CONS.DOC CONS.OTH.DOC CORR GENERAL

General rules

Element

This element contains a sequence of these sub-elements:

All elements are mandatory except SPEC.ED, EEA, NO.SEQ, INCLUSIONS and NO.DOC.

Example

The two examples below concern documents published in the OJ L collection for the first one, and in the OJ C collection for the second one. Note the differences about the NO.DOC element:

<BIB.INSTANCE>

  <DOCUMENT.REF FILE="L_2002020EN.01000101.doc.xml">

    <COLL>L</COLL>

    <NO.OJ>020</NO.OJ>

    <YEAR>2002</YEAR>

    <LG.OJ>EN</LG.OJ>

    <PAGE.FIRST>1</PAGE.FIRST>

    <PAGE.SEQ>1</PAGE.SEQ>

    <VOLUME.REF>01</VOLUME.REF>

  </DOCUMENT.REF>

  <DATE ISO="20020122">20020122</DATE>

  <LG.DOC>EN</LG.DOC>

  <NO.SEQ>0001</NO.SEQ>

  <PAGE.FIRST>1</PAGE.FIRST>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST>1</PAGE.LAST>

  <PAGE.TOTAL>1</PAGE.TOTAL>

  <DOC.TYPE>COMMON.POSITION</DOC.TYPE>

  <NO.DOC FORMAT="YNTYPE="INTERNAL">

    <NO.CURRENT>56</NO.CURRENT>

    <YEAR>2001</YEAR>

    <COM>CFSP</COM>

  </NO.DOC>

</BIB.INSTANCE>

<BIB.INSTANCE>

  <DOCUMENT.REF FILE="C_2002004EN.01000101.doc.xml">

    <COLL>C</COLL>

    <NO.OJ>004</NO.OJ>

    <YEAR>2002</YEAR>

    <LG.OJ>EN</LG.OJ>

    <PAGE.FIRST>1</PAGE.FIRST>

    <PAGE.SEQ>1</PAGE.SEQ>

    <VOLUME.REF>01</VOLUME.REF>

  </DOCUMENT.REF>

  <DATE ISO="20020107">20020107</DATE>

  <LG.DOC>EN</LG.DOC>

  <NO.SEQ>0001.0002</NO.SEQ>

  <PAGE.FIRST>12</PAGE.FIRST>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST>12</PAGE.LAST>

  <PAGE.TOTAL>1</PAGE.TOTAL>

  <DOC.TYPE>ANNEX</DOC.TYPE>

</BIB.INSTANCE>

The example below deals with an agreement in the form of an exchange of letters. The objects listed in the INCLUSIONS tag are the image files of the handling signings. Note the NO.SEQ value, which means that the document is an associated one.

<BIB.INSTANCE>

  <DOCUMENT.REF FILE="L_2002071EN.01000101.doc.xml">

    <COLL>L</COLL>

    <NO.OJ>071</NO.OJ>

    <YEAR>2002</YEAR>

    <LG.OJ>EN</LG.OJ>

    <PAGE.FIRST>1</PAGE.FIRST>

    <PAGE.SEQ>1</PAGE.SEQ>

    <VOLUME.REF>01</VOLUME.REF>

  </DOCUMENT.REF>

  <DATE ISO="20020313">20020313</DATE>

  <LG.DOC>EN</LG.DOC>

  <NO.SEQ>0001.0003</NO.SEQ>

  <PAGE.FIRST>10</PAGE.FIRST>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST>31</PAGE.LAST>

  <PAGE.TOTAL>22</PAGE.TOTAL>

  <INCLUSIONS>

    <INCL.ELEMENT TYPE="TIFFFILEREF="L_2002071EN.01001501">    </INCL.ELEMENT>

    <INCL.ELEMENT TYPE="TIFFFILEREF="L_2002071EN.01001502">    </INCL.ELEMENT>

    <INCL.ELEMENT TYPE="TIFFFILEREF="L_2002071EN.01002001">    </INCL.ELEMENT>

    <INCL.ELEMENT TYPE="TIFFFILEREF="L_2002071EN.01002002">    </INCL.ELEMENT>

    <INCL.ELEMENT TYPE="TIFFFILEREF="L_2002071EN.01002501">    </INCL.ELEMENT>

    <INCL.ELEMENT TYPE="TIFFFILEREF="L_2002071EN.01002502">    </INCL.ELEMENT>

    <INCL.ELEMENT TYPE="TIFFFILEREF="L_2002071EN.01003001">    </INCL.ELEMENT>

    <INCL.ELEMENT TYPE="TIFFFILEREF="L_2002071EN.01003002">    </INCL.ELEMENT>

  </INCLUSIONS>

</BIB.INSTANCE>

Specific rules

Element

In the context of consolidated acts, this element has to be used for the bibliographic information on the consolidated act itself. Only the following components have to be used:

All other values are optional.

This element must not be confused with BIB.INSTANCE.CONS which is used to describe the members of the consolidated family, such as the basic act and modifiers.

[Table of contents]

BIB.INSTANCE.CONS

[element]

References of the publication in the context of codification

The BIB.INSTANCE.CONS element is used to mark up the references which unambiguously identify a document within the publication in the context of codification.

Model

<xd:element name="BIB.INSTANCE.CONS">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="DOCUMENT.REF.CONS"/>
      <xd:element ref="SPEC.EDminOccurs="0"/>
      <xd:element ref="EEAminOccurs="0"/>
      <xd:element ref="DATEmaxOccurs="unbounded"/>
      <xd:element ref="LG.DOC"/>
      <xd:element ref="NO.SEQminOccurs="0"/>
      <xd:element ref="PAGE.FIRST"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="NO.DOCminOccurs="0maxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

BIB.DATA

General rules

Element

This element includes the following information:

Example

The example below shows the BIB.INSTANCE.CONS element within a BIB.DATA element:

<BIB.DATA>

  <BIB.INSTANCE.CONS>

    <DOCUMENT.REF.CONS>

      <COLL>L</COLL>

      <NO.OJ>019</NO.OJ>

      <YEAR>2001</YEAR>

      <LG.OJ>EN</LG.OJ>

      <PAGE.FIRST>9</PAGE.FIRST>

      <PAGE.SEQ>1</PAGE.SEQ>

      <VOLUME.REF>01</VOLUME.REF>

    </DOCUMENT.REF.CONS>

    <DATE ISO="20020119">20020119</DATE>

    <LG.DOC>EN</LG.DOC>

    <NO.SEQ>0005</NO.SEQ>

    <PAGE.FIRST>9</PAGE.FIRST>

    <PAGE.SEQ>1</PAGE.SEQ>

    <PAGE.LAST>10</PAGE.LAST>

    <PAGE.TOTAL>2</PAGE.TOTAL>

    <NO.DOC FORMAT="YNTYPE="INTERNAL">

      <NO.CURRENT>110</NO.CURRENT>

      <YEAR>2001</YEAR>

      <COM>CE</COM>

    </NO.DOC>

  </BIB.INSTANCE.CONS>

</BIB.DATA>

[Table of contents]

BIB.JUDGMENT

[element]

Metadata for a judgment

The element defines the metadata for describing a judgment within a case. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.JUDGMENT">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.CASE.F1minOccurs="0"/>
      <xd:element ref="REF.CASE"/>
      <xd:element ref="NO.CELEXminOccurs="0"/>
      <xd:element ref="NO.ECLIminOccurs="0"/>
      <xd:element ref="NO.SEQ"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="AUTHOR"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

JUDGMENT JUDGMENT.NP

General rules

Element

All elements, except REF.CASE.F1, are mandatory. For technical reasons the NO.CELEX element is declared as optional; its use, however, is compulsory.

Example

<BIB.JUDGMENT>

  <REF.CASE FILE="ECR1972FR.060060101.case.xml">

    <NO.CASE>53-70</NO.CASE>

  </REF.CASE>

  <NO.CELEX>61970J0053</NO.CELEX>

  <NO.SEQ>0001.0001</NO.SEQ>

  <PAGE.FIRST.ECR>602</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>610</PAGE.LAST.ECR>

  <PAGE.TOTAL>9</PAGE.TOTAL>

  <AUTHOR>CJ</AUTHOR>

</BIB.JUDGMENT>

[Table of contents]

BIB.LSEU

[element]

Metadata on a legislation summary

The BIB.LSEU element is used to mark up specific metadata of the summary.

Model

<xd:element name="BIB.LSEU">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="NO.DOC.LSEU"/>
      <xd:element ref="LG.DOC"/>
      <xd:element ref="LAST.MODIFICATIONminOccurs="0"/>
      <xd:element ref="ARCHIVED"/>
    </xd:sequence>
    <xd:attribute name="TYPEdefault="SUMMARY">
      <xd:simpleType>
        <xd:restriction base="xd:string">
          <xd:enumeration value="GLOSSARY"/>
          <xd:enumeration value="INTRO"/>
          <xd:enumeration value="SUMMARY"/>
        </xd:restriction>
      </xd:simpleType>
    </xd:attribute>
  </xd:complexType>
</xd:element>

Used by

LSEU

General rules

Element

This element contains a sequence of these sub-elements:

The elements NO.DOC.LSEU, LG.DOC and ARCHIVED are mandatory.

Attributes

The attribute TYPE

The attribute TYPE gives an additional information about the nature of the contents of the document. It therefore can have one of two values: SUMMARY (default) to indicate that the contents is a summary, INTRO for introductory texts, or GLOSSARY for instances which contain a glossary. The information is of high importance for the conversion to XHTML.

[Table of contents]

BIB.OJ

[element]

Bibliographical description

The BIB.OJ element is used to mark up the bibliographical and physical description of an OJ.

Model

<xd:element name="BIB.OJ">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="COLLminOccurs="0"/>
      <xd:element ref="TITLEminOccurs="0"/>
      <xd:choice minOccurs="0">
        <xd:element ref="NO.OJ"/>
        <xd:element ref="SPECIAL"/>
      </xd:choice>
      <xd:element ref="AGE.OJminOccurs="0"/>
      <xd:element ref="DATEminOccurs="0"/>
      <xd:element ref="LAST.OJminOccurs="0"/>
      <xd:element ref="LG.OJ"/>
      <xd:element ref="PRINTER"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
    <xd:attribute name="REPUBLICATIONtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

OJ

General rules

Element

The BIB.OJ provides the following bibliographical informations:

These sub-element may be empty if the contents is unknown or, during a pre-press phase, is not yet fixed.

When the publication is a secondary legislation publication, the bibliographical informations are described using the BIB.SE element.

Attributes

The attribute REPUBLICATION

The attribute REPUBLICATION signals if the give number of the Official Journal is a republication or not. The attribute value "YES" indicates that it is actually a republication, the value "NO" (default value) indicates that it is an original publication. Republications may become necessary when after the publication of the original Journal, it turns out that, due to the protection of personal data, some parts of the contained document had to be anonymised. Also see the element ANONYMOUS.

In the case of a republication the following notice, according to the language, has to be added on the cover page of the OJ:

Example

<BIB.OJ>

  <COLL TYPE="L">  </COLL>

  <NO.OJ CLASS="NORMAL">73</NO.OJ>

  <DATE ISO="20020315">20020315</DATE>

  <AGE.OJ>45</AGE.OJ>

  <LG>EN</LG>

  <PRINTER>OPOCE</PRINTER>

</BIB.OJ>

[Table of contents]

BIB.OPINION

[element]

Metadata for an opinion

The BIB.OPINION element is used to mark up the metadata for an opinion.

Model

<xd:element name="BIB.OPINION">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.CASE.F1minOccurs="0"/>
      <xd:element ref="REF.CASE"/>
      <xd:element ref="NO.CELEXminOccurs="0"/>
      <xd:element ref="NO.ECLIminOccurs="0"/>
      <xd:element ref="NO.SEQ"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="AUTHOR"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

OPINION

General rules

Element

It contains a sequence of these sub-elements:

All elements, except REF.CASE.F1, REF.CORE.METADATA and REF.BIB.RECORD, are mandatory. For technical reasons the NO.CELEX element is declared as optional; its use, however, is compulsory.

Example

<BIB.OPINION>

  <REF.CASE FILE="ECR1959FR.010053301.case.xml">

    <NO.CASE>    </NO.CASE>

  </REF.CASE>

  <NO.SEQ>0001</NO.SEQ>

  <PAGE.FIRST.ECR>533</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>562</PAGE.LAST.ECR>

  <PAGE.TOTAL>30</PAGE.TOTAL>

  <AUTHOR>CJ</AUTHOR>

</BIB.OPINION>

[Table of contents]

BIB.ORDER

[element]

Metadata for an order

The element defines the metadata for describing an order within a case. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.ORDER">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.CASE.F1minOccurs="0"/>
      <xd:element ref="REF.CASE"/>
      <xd:element ref="NO.CELEXminOccurs="0"/>
      <xd:element ref="NO.ECLIminOccurs="0"/>
      <xd:element ref="NO.SEQ"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="AUTHOR"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

ORDER ORDER.NP

General rules

Element

All elements, except REF.CASE.F1, are mandatory. For technical reasons the NO.CELEX element is declared as optional; its use, however, is compulsory.

Example

<BIB.ORDER>

  <REF.CASE FILE="ECR1972FR.060060101.case.xml">

    <NO.CASE>53-70</NO.CASE>

  </REF.CASE>

  <NO.CELEX>61970O0053</NO.CELEX>

  <NO.SEQ>0001.0001</NO.SEQ>

  <PAGE.FIRST.ECR>602</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>610</PAGE.LAST.ECR>

  <PAGE.TOTAL>9</PAGE.TOTAL>

  <AUTHOR>CJ</AUTHOR>

</BIB.ORDER>

[Table of contents]

BIB.REPORT.HEARING

[element]

Metadata for a hearing report

The element defines the metadata for describing a hearing report within a case. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.REPORT.HEARING">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.CASE.F1minOccurs="0"/>
      <xd:element ref="REF.CASE"/>
      <xd:element ref="NO.CELEXminOccurs="0"/>
      <xd:element ref="NO.ECLIminOccurs="0"/>
      <xd:element ref="NO.SEQ"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

REPORT.HEARING

General rules

Element

All elements, except REF.CASE.F1, are mandatory. For technical reasons the NO.CELEX element is declared as optional; its use, however, is compulsory.

Example

<BIB.REPORT.HEARING>

  <REF.CASE FILE="ECR1987FR.020049501.case.xml">

    <NO.CASE>276/85</NO.CASE>

  </REF.CASE>

  <NO.SEQ>0001.0001</NO.SEQ>

  <PAGE.FIRST.ECR>496</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>500</PAGE.LAST.ECR>

  <PAGE.TOTAL>5</PAGE.TOTAL>

</BIB.REPORT.HEARING>

[Table of contents]

BIB.RULING

[element]

Metadata for a ruling

The element defines the metadata for describing a ruling. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.RULING">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.CASE.F1minOccurs="0"/>
      <xd:element ref="REF.CASE"/>
      <xd:element ref="NO.CELEXminOccurs="0"/>
      <xd:element ref="NO.ECLIminOccurs="0"/>
      <xd:element ref="NO.SEQ"/>
      <xd:element ref="PAGE.FIRST.ECR"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST.ECR"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="AUTHOR"/>
      <xd:element ref="REF.CORE.METADATAminOccurs="0"/>
      <xd:element ref="REF.BIB.RECORDminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

RULING

General rules

Element

All elements, except REF.CASE.F1, are mandatory. For technical reasons the NO.CELEX element is declared as optional; its use, however, is compulsory.

Example

<BIB.RULING>

  <REF.CASE FILE="ECR1989FR.010215101.case.xml">

    <NO.CASE>1/78</NO.CASE>

  </REF.CASE>

  <NO.SEQ>0001</NO.SEQ>

  <PAGE.FIRST.ECR>2151</PAGE.FIRST.ECR>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST.ECR>2181</PAGE.LAST.ECR>

  <PAGE.TOTAL>31</PAGE.TOTAL>

  <AUTHOR>CJ</AUTHOR>

</BIB.RULING>

[Table of contents]

BIB.SE

[element]

Metadata for a special edition volume

The element defines the metadata for describing a special edition (secondary legislation) volume.

Model

<xd:element name="BIB.SE">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="LG.PUB"/>
      <xd:element ref="YEAR"/>
      <xd:element ref="CHAP.SE"/>
      <xd:element ref="TOME.SE"/>
      <xd:element ref="PRINTER"/>
      <xd:element ref="NO.CAT"/>
      <xd:choice>
        <xd:element ref="NO.ISSN"/>
        <xd:sequence>
          <xd:element ref="NO.ISSN.PRINT"/>
          <xd:element ref="NO.ISSN.ELECTRONIC"/>
        </xd:sequence>
      </xd:choice>
      <xd:element ref="NO.DOIminOccurs="0"/>
      <xd:element ref="DATE"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

SE

General rules

Element

It contains these sub-elements:

All elements are mandatory except NO.DOI.

Example

<BIB.SE>

  <LG.PUB>SK</LG.PUB>

  <YEAR>2004</YEAR>

  <CHAP.SE>03</CHAP.SE>

  <TOME.SE>05</TOME.SE>

  <PRINTER>JO</PRINTER>

  <NO.CAT>FXAZ04025SKC</NO.CAT>

  <NO.ISSN>17254965</NO.ISSN>

</BIB.SE>

[Table of contents]

BIB.SUMMARY

[element]

Metadata for a summary

The element defines the metadata for describing a summary. It contains a sequence of these sub-elements:

Model

<xd:element name="BIB.SUMMARY">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.CASE.F1minOccurs="0"/>
      <xd:element ref="REF.CASE"/>
      <xd:element ref="NO.CELEXminOccurs="0"/>
      <xd:element ref="NO.ECLIminOccurs="0"/>
      <xd:element ref="NO.SEQ"/>
      <xd:element ref="PAGE.FIRST"/>
      <xd:element ref="PAGE.SEQ"/>
      <xd:element ref="PAGE.LAST"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="AUTHOR"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

SUMMARY.JUDGMENT

General rules

Element

All elements, except REF.CASE.F1, are mandatory. For technical reasons the NO.CELEX element is declared as optional; its use, however, is compulsory.

Example

<BIB.SUMMARY>

  <REF.CASE FILE="ECR1989FR.010012301.case.xml">

    <NO.CASE>259/89</NO.CASE>

  </REF.CASE>

  <NO.SEQ>0001</NO.SEQ>

  <PAGE.FIRST>123</PAGE.FIRST>

  <PAGE.SEQ>1</PAGE.SEQ>

  <PAGE.LAST>124</PAGE.LAST>

  <PAGE.TOTAL>2</PAGE.TOTAL>

  <AUTHOR>CJ</AUTHOR>

</BIB.SUMMARY>

[Table of contents]

BIB.VOLUME

[element]

Metadata for a volume

The element defines the metadata for describing each volume of the OJ.

Model

<xd:element name="BIB.VOLUME">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="VOLUME.IDminOccurs="0"/>
      <xd:element ref="TITLEminOccurs="0"/>
      <xd:element ref="NO.CATminOccurs="0"/>
      <xd:choice minOccurs="0">
        <xd:element ref="NO.ISSN"/>
        <xd:sequence>
          <xd:element ref="NO.ISSN.PRINTminOccurs="0"/>
          <xd:element ref="NO.ISSN.ELECTRONIC"/>
        </xd:sequence>
      </xd:choice>
      <xd:element ref="DOI.OJminOccurs="0"/>
      <xd:element ref="GR.ANNOTATIONminOccurs="0"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="PAGE.SUMMARY"/>
      <xd:element ref="PAGE.CONTENTS"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

VOLUME

General rules

Element

The BIB.VOLUME element is used within the VOLUME element, even when an OJ publication is made of one single volume.

It contains these sub-elements:

The GR.ANNOTATION element is used in the latter context to mark up comments which appear on the first page of the cover. Generally speaking, these are notes indicating that this OJ closes the series for a given year.

Example

<BIB.VOLUME>

  <VOLUME.ID>1</VOLUME.ID>

  <NO.CAT>FXAL02020ENC</NO.CAT>

  <NO.ISSN>03786978</NO.ISSN>

  <PAGE.TOTAL>16</PAGE.TOTAL>

  <PAGE.SUMMARY>

    <PAGE.FIRST>s1</PAGE.FIRST>

    <PAGE.LAST>s2</PAGE.LAST>

    <PAGE.TOTAL>2</PAGE.TOTAL>

  </PAGE.SUMMARY>

  <PAGE.CONTENTS>

    <PAGE.FIRST>1</PAGE.FIRST>

    <PAGE.LAST>13</PAGE.LAST>

    <PAGE.TOTAL>13</PAGE.TOTAL>

  </PAGE.CONTENTS>

</BIB.VOLUME>

[Table of contents]

BLK

[element]

Block of rows

The BLK element is used to mark up information relating to blocks of rows. A block of rows is characterised by:

Model

<xd:element name="BLK">
  <xd:complexType>
    <xd:sequence>
      <xd:sequence minOccurs="0">
        <xd:element ref="TI.BLK"/>
        <xd:element ref="STI.BLKminOccurs="0"/>
      </xd:sequence>
      <xd:choice maxOccurs="unbounded">
        <xd:element ref="ROW"/>
        <xd:element ref="BLK"/>
      </xd:choice>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

BLK CORPUS

General rules

Element

If a block of rows is introduced by a title, the use of the BLK element is mandatory.

As a block of rows may contain other lower-level blocks of rows, the model of the BLK element is recursive.

In some cases, the markup of a table requires the simultaneous use of ASSV or ROWSPAN attributes of the CELL element with BLK elements. In this case, the BLK element and especially its title must be taken into account to compute the value of these attributes.

Example

This table contains lines which are logically grouped together in a BLK element:

This one also contains a BLK element, but an analysis of the context is necessary in so far as few presentation straightforward cues are available:

<TBL COLS="2NO.SEQ="0001">

  <TITLE>

    <TI>

      <P>List of products covered by the specific supply arrangements under Title I for the smaller Aegean islands</P>

    </TI>

  </TITLE>

  <CORPUS>

    <ROW TYPE="HEADER">

      <CELL COL="1TYPE="HEADER">Description</CELL>

      <CELL COL="2TYPE="HEADER">CN code</CELL>

    </ROW>

    <ROW>

      <CELL COL="1">Wheat flour</CELL>

      <CELL COL="2">

        <FT TYPE="CN">1101</FT> and         <FT TYPE="CN">1102</FT>

</CELL>

    </ROW>

    <ROW>

      <CELL COL="1">Durum wheat</CELL>

      <CELL COL="2">10011000</CELL>

    </ROW>

    <ROW>

      <CELL COL="1">Wheat of bread-making quality</CELL>

      <CELL COL="2">10019099</CELL>

    </ROW>

    <BLK>

      <TI.BLK COL.START="1COL.END="1">Feedingstuffs</TI.BLK>

      <ROW>

        <CELL COL="1">— cereals</CELL>

        <CELL COL="2">

          <IE>          </IE>

        </CELL>

      </ROW>

      <ROW>

        <CELL COL="1">— wheat</CELL>

        <CELL COL="2">1001</CELL>

      </ROW>

      <ROW>

        <CELL COL="1">— rye</CELL>

        <CELL COL="2">1002</CELL>

      </ROW>

      <ROW>

        <CELL COL="1">— barley</CELL>

        <CELL COL="2">1003</CELL>

      </ROW>

      <ROW>

        <CELL COL="1">— oats</CELL>

        <CELL COL="2">1004</CELL>

      </ROW>

      <ROW>

        <CELL COL="1">— maize</CELL>

        <CELL COL="2">1005</CELL>

      </ROW>

      <ROW>

        <CELL COL="1">— cotton seeds</CELL>

        <CELL COL="2">12072090</CELL>

      </ROW>

      <ROW>

        <CELL COL="1">— alfalfa and fodder</CELL>

        <CELL COL="2">1214</CELL>

      </ROW>

      <ROW>

        <CELL COL="1">— food industry wastes and residues</CELL>

        <CELL COL="2">

          <FT TYPE="CN">2302</FT> to           <FT TYPE="CN">2308</FT>

</CELL>

      </ROW>

      <ROW>

        <CELL COL="1">— preparations of a kind used in animal fee</CELL>

        <CELL COL="2">230990</CELL>

      </ROW>

    </BLK>

  </CORPUS>

</TBL>

[Table of contents]

BR

[element]

Line break

The BR element is used to explicitly indicate a line break which cannot be deduced from other mark-up.

Model

<xd:element name="BR">
  <xd:complexType/>
</xd:element>

Used by

t_btx t_btx.ecr t_btx.seq

General rules

Element

The BR element may only be used in cases where a line break has to be generated, but cannot be derived from the logical mark-up in the document. See the example below.

Example

<PRELIM.RULING>

  <P>[demande de décision préjudicielle,

    <BR>    </BR>introduite par la Cour administrative (Luxembourg)]</P>

</PRELIM.RULING>

[Table of contents]

CAPTION

[element]

Caption

The CAPTION element is used to mark up the text attached to an included image. This text is usually given in the form of a title underneath the image.

Model

<xd:element name="CAPTIONtype="t_btx.struct"/>

Used by

CAPTION INCL.ELEMENT

General rules

Element

The CAPTION element should only be used when the text appears below the image. If the text is placed on top of the image, a GR.SEQ structure should be created.

The CAPTION element may only contain one or more of the elements defined in the t_btx.struct complex type. Generally, it is composed of one or several P elements.

Example

<CAPTION>

  <P>Figure 1</P>

  <P>Number of activities per site in Belgium</P>

</CAPTION>

[Table of contents]

CASE

[element]

Metadata for a juridical case

The CASE element is used to mark up the metadata for describing a dossier of a juridical case.

Model

<xd:element name="CASE">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.CASE"/>
      <xd:element ref="CURR.TITLEminOccurs="0"/>
      <xd:element ref="TITLEminOccurs="0"/>
      <xd:element ref="PARTIESminOccurs="0"/>
      <xd:element ref="SUBJECTminOccurs="0"/>
      <xd:element ref="PRELIM.RULINGminOccurs="0"/>
      <xd:element ref="INDEXminOccurs="0"/>
      <xd:element ref="JOINED.CASESminOccurs="0"/>
      <xd:element ref="PminOccurs="0maxOccurs="unbounded"/>
      <xd:choice minOccurs="0maxOccurs="unbounded">
        <xd:element ref="DECISION"/>
        <xd:element ref="OBJECT"/>
        <xd:element ref="REF.CONCLUSION"/>
        <xd:element ref="REF.CORRIG.ECR"/>
        <xd:element ref="REF.DECISION.ECR"/>
        <xd:element ref="REF.JUDGMENT"/>
        <xd:element ref="REF.JUDGMENT.NP"/>
        <xd:element ref="REF.OPINION"/>
        <xd:element ref="REF.ORDER"/>
        <xd:element ref="REF.ORDER.NP"/>
        <xd:element ref="REF.REPORT.HEARING"/>
        <xd:element ref="REF.RULING"/>
        <xd:element ref="REF.SUMMARY.JUDGMENT"/>
        <xd:element ref="SUMMARY"/>
      </xd:choice>
      <xd:element ref="PDF.ECRminOccurs="0"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

It contains the following sub-elements:

The order of the elements REF.CONCLUSION, REF.JUDGMENT, REF.ORDER, REF.OPINION and SUMMARY is free. They may also be combined in any order.

Example

<CASE>

  <BIB.CASE>

    <REF.ECR FILE="ECR2005FR1.01.xml">

      <YEAR>2005</YEAR>

      <VOLUME.ECR>1</VOLUME.ECR>

    </REF.ECR>

    <LG.DOC>FR</LG.DOC>

    <LG.CASE>DE</LG.CASE>

    <DATE ISO="20050120">20050120</DATE>

    <YEAR>2001</YEAR>

    <NO.CASE>C-464/01</NO.CASE>

    <TYPE.CASE>JUDGMENT-C</TYPE.CASE>

    <NO.CELEX>62001J0464</NO.CELEX>

    <NO.SEQ>0014</NO.SEQ>

    <PAGE.FIRST>439</PAGE.FIRST>

    <PAGE.SEQ>1</PAGE.SEQ>

    <PAGE.LAST>480</PAGE.LAST>

    <PAGE.TOTAL>42</PAGE.TOTAL>

    <AUTHOR>CJ</AUTHOR>

  </BIB.CASE>

  <TITLE>

    <TI>

      <P>Affaire C-464/01</P>

    </TI>

  </TITLE>

  <PARTIES>

    <PLAINTIFS>

      <P>Johann Gruber</P>

    </PLAINTIFS>

    <AGAINST>contre</AGAINST>

    <DEFENDANTS>

      <P>Bay Wa AG</P>

    </DEFENDANTS>

  </PARTIES>

  <PRELIM.RULING>

    <P>demande de décision préjudicielle, introduite par l'Oberster Gerichtshof (Autriche)</P>

  </PRELIM.RULING>

  <INDEX>

    <KEYWORD>Convention de Bruxelles</KEYWORD>

    <KEYWORD>Article 13, premier alinéa</KEYWORD>

    <KEYWORD>Conditions d’application</KEYWORD>

    <KEYWORD>Notion de ‘contrat conclu par un consommateur ’</KEYWORD>

    <KEYWORD>Achat de tuiles par un agriculteur pour la couverture d’une ferme à usage en partie privé et en partie professionnel</KEYWORD>

  </INDEX>

  <SUMMARY>

    <TITLE>

      <TI>

        <P>Sommaire de l’arrêt</P>

      </TI>

    </TITLE>

    <SUBJECTS>

      <P>

        <KEYWORD>Convention concernant la compétence judiciaire et l’exécution des décisions</KEYWORD>

        <KEYWORD>Compétence en matière de contrats conclus par les consommateurs</KEYWORD>

        <KEYWORD>Notion de «contrat conclu par un consommateur</KEYWORD>

        <KEYWORD>Contrat portant sur un bien destiné à un usage en partie professionnel et en partie privé</KEYWORD>

        <KEYWORD>Exclusion sauf en cas d’usage professionnel marginal</KEYWORD>

        <KEYWORD>Appréciation par le juge national</KEYWORD>

        <KEYWORD>Critères</KEYWORD>

      </P>

      <P>(Convention du

        <DATE ISO="19680927">27 septembre 1968</DATE>, art. 13 à 15)</P>

    </SUBJECTS>

    <ABSTRACT>

      <P>Les règles de compétence énoncées par la convention du

        <DATE ISO="19680927">27 septembre 1968</DATE> concernant la compétence judiciaire et l’exécution des décisions en matière civile et commerciale, telle que modifiée par la convention du         <DATE ISO="19781009">9 octobre 1978</DATE> relative à l’adhésion du royaume de Danemark, de l’Irlande et du Royaume-Uni de Grande-Bretagne et d’Irlande du Nord, par la convention du         <DATE ISO="19821025">25 octobre 1982</DATE> relative à l’adhésion de la République hellénique, par la convention du         <DATE ISO="19890526">26 mai 1989</DATE> relative à l’adhésion du royaume d’Espagne et de la République portugaise et par la convention du         <DATE ISO="19961129">29 novembre 1996</DATE> relative à l’adhésion de la république d’Autriche, de la république de Finlande et du royaume de Suède, doivent être interprétées de la manière suivante:</P>

      <LIST TYPE="DASH">

        <ITEM>

          <P>une personne qui a conclu un contrat portant sur un bien destiné à un usage en partie professionnel et en partie étranger à son activité professionnelle n’est pas en droit de se prévaloir du bénéfice des règles de compétence spécifiques prévues aux articles 13 à 15 de ladite convention, sauf si l’usage professionnel est marginal au point d’avoir un rôle négligeable dans le contexte global de l’opération en cause, le fait que l’aspect extraprofessionnel prédomine étant sans incidence à cet égard;</P>

        </ITEM>

        <ITEM>

          <P>il appartient à la juridiction saisie de décider si le contrat en cause a été conclu pour couvrir, dans une mesure non négligeable, des besoins relevant de l’activité professionnelle de la personne concernée ou si, au contraire, l’usage professionnel ne revêtait qu’un rôle insignifiant; </P>

        </ITEM>

        <ITEM>

          <P>à cet effet, il y a lieu pour ladite juridiction de prendre en considération l’ensemble des éléments de fait pertinents résultant objectivement du dossier; en revanche, il ne convient pas de tenir compte de circonstances ou d’éléments dont le cocontractant aurait pu avoir connaissance lors de la conclusion du contrat, sauf si la personne qui invoque la qualité de consommateur s’est comportée de manière telle qu’elle a légitimement pu faire naître l’impression, dans le chef de l’autre partie au contrat, qu’elle agissait à des fins professionnelles. </P>

          <P>(cf. point 54 et disp.)</P>

        </ITEM>

      </LIST>

    </ABSTRACT>

  </SUMMARY>

  <REF.CONCLUSION>

    <TITLE>

      <TI>

        <P>Conclusions de l’avocat général M. F. G. Jacobs, présentées le

          <DATE ISO="20040916">16 septembre 2004</DATE>

</P>

      </TI>

    </TITLE>

    <REF.ECR.DOC FILE="ECR2005FR1.001044101.xmlNO.SEQ="0014.0001">I-441</REF.ECR.DOC>

  </REF.CONCLUSION>

  <REF.JUDGMENT>

    <TITLE>

      <TI>

        <P>Arrêt de la Cour (deuxième chambre) du

          <DATE ISO="20050120">20 janvier 2005</DATE>

</P>

      </TI>

    </TITLE>

    <REF.ECR.DOC FILE="ECR2005FR1.010045801.xmlNO.SEQ="0014.0002">I-458</REF.ECR.DOC>

  </REF.JUDGMENT>

  <PDF.ECR>

    <REF.PDF.ECR TYPE="SUMMARYPAGE.FIRST="00439PAGE.LAST="00440">//filename//</REF.PDF.ECR>

    <REF.PDF.ECR TYPE="CONCLUSIONPAGE.FIRST="00441PAGE.LAST="00457">//filename//</REF.PDF.ECR>

    <REF.PDF.ECR TYPE="CASEPAGE.FIRST="00458PAGE.LAST="00480">//filename//</REF.PDF.ECR>

  </PDF.ECR>

</CASE>

[Table of contents]

CAT.PLANT

[element]

Catalogue of agricultural plant species

The CAT.PLANT element is used to mark up all the varieties of agricultural plant species.

Model

<xd:element name="CAT.PLANT">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="GR.NOTESminOccurs="0"/>
      <xd:element ref="GR.PLANTmaxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

t_btx t_btx.struct GR.SEQ QUOT.S

General rules

Element

This element includes the following sub-elements:

Any referenced notes must be grouped together within the GR.NOTES element.

In the context of the CAT.PLANT element, the GR.NOTES element may only be used if the referenced notes concern the entire catalogue.

[Table of contents]

CAT.VEGET

[element]

Catalogue of vegetable species

The CAT.VEGET element is used to mark up all the varieties of vegetable species.

Model

<xd:element name="CAT.VEGET">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="GR.NOTESminOccurs="0"/>
      <xd:element ref="SPECIEmaxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

t_btx t_btx.struct GR.SEQ QUOT.S

General rules

Element

This element includes the following sub-elements:

Any referenced notes must be grouped together within the GR.NOTES element.

In the context of the CAT.VEGET element, the GR.NOTES element may only be used if the referenced notes concern the entire catalogue.

[Table of contents]

CELL

[element]

Cell

The CELL element is used to mark up information corresponding to each individual cell. In a table, a cell is the basic element of a row. It is found at the intersection of a row and a column.

Both semantic and layout features may be specified for a cell.

Model

<xd:element name="CELL">
  <xd:complexType mixed="true">
    <xd:complexContent mixed="true">
      <xd:extension base="t_btx">
        <xd:sequence>
          <xd:element ref="TXT.COLminOccurs="0"/>
          <xd:element ref="TXT.ROWminOccurs="0"/>
        </xd:sequence>
        <xd:attribute name="COLtype="xd:positiveIntegeruse="required"/>
        <xd:attribute name="COLSPANtype="xd:positiveInteger"/>
        <xd:attribute name="ROWSPANtype="xd:positiveInteger"/>
        <xd:attribute name="ACCH">
          <xd:simpleType>
            <xd:restriction base="xd:string">
              <xd:pattern value="\d{1,3}\.[BT]\.[BT]"/>
            </xd:restriction>
          </xd:simpleType>
        </xd:attribute>
        <xd:attribute name="ACCV">
          <xd:simpleType>
            <xd:restriction base="xd:string">
              <xd:pattern value="\d{1,3}\.[LR]\.[LR]"/>
            </xd:restriction>
          </xd:simpleType>
        </xd:attribute>
        <xd:attribute name="TYPEdefault="NORMAL">
          <xd:simpleType>
            <xd:restriction base="xd:string">
              <xd:enumeration value="ALIAS"/>
              <xd:enumeration value="HEADER"/>
              <xd:enumeration value="NORMAL"/>
              <xd:enumeration value="NOTCOL"/>
              <xd:enumeration value="TOTAL"/>
            </xd:restriction>
          </xd:simpleType>
        </xd:attribute>
      </xd:extension>
    </xd:complexContent>
  </xd:complexType>
</xd:element>

Used by

ROW

General rules

Element

If, in a cell, several values with the same logical weight are separated by carriage returns (CRLF) in the printed version, it is necessary:

If the content of a cell is empty, the 'is empty' element (IE) is used to explicitly mark up this empty content.

In a table, the header of a column is marked-up with the TXT.COL element and the header of a row with the TXT.ROW element. Both elements are optional, but when in use, the cells should have the TYPE attribute with the value 'HEADER'.

Attributes

The TYPE attribute

The TYPE attribute of the CELL element is used to indicate locally the type of contents of the cells. It overrides the value of the TYPE attribute defined for the row (ROW) which contains the cell.

As the TYPE attribute of the ROW element, it may take the following values:

Furthermore, if the TYPE attribute is used for the ROW which contains the cell, the TYPE attribute must be defined in the cell in order to skip the default value 'NORMAL'.

Attributes

The ACCH attribute

If the group of related cells is physically delimited by a horizontal brace, this symbol must be marked up using the ACCH attribute. The value of the ACCH attribute must correspond to a format of the type 't.l.d', where:

The ACCH attribute must be mentioned in the cell located at the intersection of the row which contains the brace and the first column in the group.

If an association is established in a table cell, with or without a brace, on part of the cell, the ACCV and ACCH attributes may not be used. In this case, the value concerned must be repeated as many times as it is required by the association.

Attributes

The ACCV attribute

If the group of related cells is physically delimited by a vertical brace, this symbol must be marked up using the ACCV attribute. The value of the ACCV attribute must correspond to a format of the type 'ttt.l.d', where:

The ACCV attribute must be mentioned in the cell located at the intersection of the row which contains the brace and the first column in the group.

Attributes

The COL attribute

The mandatory COL attribute is used to specify in which column the cell is located.

Attributes

The COLSPAN attribute

When a cell in a row 'A' must be linked to a group of cells in the same row, the first CELL element of this group has to provide the COLSPAN attribute. The value of the COLSPAN attribute is the number of cells in the group. The COL attribute of the first cell indicates the number of the first column in the group.

The use of the COLSPAN attribute is only allowed to relate the value of a cell in several columns within the same row. Its value must be at least equal to '2'.

Attributes

The ROWSPAN attribute

When a cell in column 'A' is linked to a cell in row 'B' located just below row 'A', the CELL element of this single cell must provide the ROWSPAN attribute. The value of the ROWSPAN attribute is equal to the number of cells in the group. The CELL element relating to the single cell must be placed within the first ROW element in the group. The ROW elements corresponding to the other rows in the group may not contain any CELL elements for the column containing the single cell 'A'.

The use of the ROWSPAN attribute is only authorised to relate the value of a cell in several rows. Its value must be at least equal to '2'.

[Table of contents]

CHAP.SE

[element]

Chapter (Secondary legislation)

The CHAP.SE element is used to mark up a chapter in a secondary legislation publication.

Model

<xd:element name="CHAP.SEtype="xd:string"/>

Used by

BIB.SE CHAP.SE DOC.CORR.SE HEADER.SUMMARY.SE PUBLICATION.REF.SE SPEC.ED

General rules

Element

The CHAP.SE element is used within the SPEC.ED element.

[Table of contents]

CHRON.TABLE

[element]

Chronological list of cases

In some volumes of ECR publications a chronological list of judgements and orders is published.

Model

<xd:element name="CHRON.TABLE">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.CHRON.TABLE"/>
      <xd:element ref="TITLE"/>
      <xd:element ref="CONTENTS"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

The CHRON.TABLE element contains a sequence of these mandatory sub-elements:

[Table of contents]

CHRON.TABLE.NP

[element]

Chronological list of unpublished judgments and orders

In some volumes of ECR publications a chronological list of unpublished judgements and orders is published.

Model

<xd:element name="CHRON.TABLE.NP">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.CHRON.TABLE.NP"/>
      <xd:element ref="TITLE"/>
      <xd:element ref="CONTENTS"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

The CHRON.TABLE.NP element contains a sequence of these mandatory sub-elements:

[Table of contents]

CJT

[element]

Root element for the Court of Justice documents

The CJT element is the root element for marking up documents published in the C series of the Official Journal, in Section I - Communications, under the heading Court of Justice. This heading is divided into three parts, namely:

A distinction may be made between various categories of CJT documents. These are:

Model

<xd:element name="CJT">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.INSTANCE"/>
      <xd:choice maxOccurs="unbounded">
        <xd:element ref="GR.ANNOTATION"/>
        <xd:element ref="TI.CJT"/>
      </xd:choice>
      <xd:element ref="CONTENTS"/>
      <xd:element ref="ENACTING.TERMS.CJTminOccurs="0"/>
    </xd:sequence>
    <xd:attribute name="NNCtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

The CJT element may contain:

The BIB.INSTANCE element contains the bibliographic information for a CJT document.

In some cases, the document is accompanied by an annex. This should be marked up separately, using other root elements such as ANNEX, GENERAL, etc. An annex is not always easy to identify. Sometimes it follows on directly from the document. Sometimes it is separated from it by a thin line. In both cases, the annex must be considered a separate document.

Attention: A cancellation does not contain all necessary components and therefore has to be marked up with a root GENERAL.

Attributes

The NNC attribute

In some special cases, the numbering of footnotes does not restart on every page, but continues from 1 to n. For those cases the attribute NNC [notes numbering continued] takes the value 'YES'. The default value of this attribute is 'NO'. So the attribute should not be used if the numbering of footnotes follows the general rules and restarts on a new page.

[Table of contents]

CN

[element]

Combined nomenclature

The CN element is used to mark up data in the combined nomenclature.

Model

<xd:element name="CN">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="GR.NOTESminOccurs="0"/>
      <xd:element ref="CN.HEADER"/>
      <xd:choice>
        <xd:element ref="GR.CN.UNITmaxOccurs="unbounded"/>
        <xd:element ref="CN.UNITmaxOccurs="unbounded"/>
      </xd:choice>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

t_btx t_btx.struct GR.SEQ QUOT.S

General rules

Element

It includes the following sub-elements:

It is strictly forbidden to use the NOTE element within the CN element. Any referenced notes have to be grouped together within the GR.NOTES element.

The CN element must be defined at the beginning of each nomenclature, which may cover several printed pages.

Example

<CN>

  <CN.HEADER>

    <CN.CODE>Code number</CN.CODE>

    <CN.DESC>Description</CN.DESC>

  </CN.HEADER>

  <CN.UNIT TYPE="OLDHS="YESLEVEL="0">

    <CN.CODE>8901</CN.CODE>

    <CN.DESC>Cruise ships, excursion boats, ferry-boats, cargo ships, barges and similar vessels for the transport of persons or goods:</CN.DESC>

  </CN.UNIT>

</CN>

[Table of contents]

CN.AUT.RATE

[element]

Header of the 'Rate of autonomous duties' column

The CN.AUT.RATE element is used in the combined nomenclature in order to mark up the header of the column containing the autonomous rates.

In the English language version, it contains the text 'Rate of autonomous duties' in the suspensions documents or the text 'autonomous (%)' in the combined nomenclature. In the latter case, the column containing the autonomous rates is in fact a subdivision of the 'Rate of duty' column.

In some documents in the combined nomenclature, for example the OJ L 345 of 31 December 1994, the definition of this column may vary in a certain number of tables. In the English language version, it contains the text 'autonomous (%) or levy (AGR)'.

Furthermore, in the combined nomenclature, the autonomous rates column can be subdivided into periods of application such as six-month and three-month periods. In this case, the PERIOD element must be used to mark up the headers of these new columns.

Model

<xd:element name="CN.AUT.RATE">
  <xd:complexType>
    <xd:choice>
      <xd:element ref="TXT"/>
      <xd:element ref="PERIODmaxOccurs="unbounded"/>
    </xd:choice>
  </xd:complexType>
</xd:element>

Used by

CN.RATE CN.UNIT

General rules

Element

The CN.AUT.RATE element consists of the following sub-elements:

[Table of contents]

CN.CODE

[element]

Combined nomenclature code

The CN.CODE element is used to mark up the combined nomenclature code.

Model

<xd:element name="CN.CODE">
  <xd:complexType mixed="true">
    <xd:complexContent mixed="true">
      <xd:extension base="t_btx.seq">
        <xd:attribute name="ALIAStype="xd:string"/>
      </xd:extension>
    </xd:complexContent>
  </xd:complexType>
</xd:element>

Used by

CN.HEADER CN.UNIT UNIT.TA

General rules

Element

The spaces in the CN codes are not included in the electronic file.

In some cases, such as in documents relating to suspensions, the CN code is preceded by the indication 'ex'. This indication means that the CN code is developed in various TARIC codes. In the context of suspensions, this means that the suspension is only published in the TARIC code and that it does not cover the complete CN product, but only an 'ex'tract of this defined by the Taric codes in question.

Attributes

The ALIAS attribute

The ALIAS attribute of the CN.CODE element is used to define a second header for the column. This is usually a sequence number attributed to the column in order to be able to facilitate reference to this column. This number is given below the main header.

For presentation purposes, the text of this header may contain carriage returns. These returns must be omitted in the electronic file.

Example

<CN.UNIT TYPE="NEWHS="NOLEVEL="2">

  <CN.CODE>01011010</CN.CODE>

  <CN.DESC>Horses

    <NOTE NOTE.REF="E0016">    </NOTE>

</CN.DESC>

  <CN.CONV.RATE>

    <TXT>Free</TXT>

  </CN.CONV.RATE>

  <CN.SUP.UNIT>p/st</CN.SUP.UNIT>

</CN.UNIT>

[Table of contents]

CN.CONV.RATE

[element]

Header of the 'Conventional rates' column

The CN.CONV.RATE element is used to mark up the header of the conventional rates column.

In the English language version, it contains the text 'conventional (%)' (combined nomenclature).

The conventional rates column can be subdivided into application periods such as six-month and three-month periods. In this case, the PERIOD element must be used to mark up the headers of these columns.

Model

<xd:element name="CN.CONV.RATE">
  <xd:complexType>
    <xd:choice>
      <xd:element ref="TXT"/>
      <xd:element ref="PERIODmaxOccurs="unbounded"/>
    </xd:choice>
    <xd:attribute name="ALIAStype="xd:string"/>
  </xd:complexType>
</xd:element>

Used by

CN.RATE CN.UNIT

General rules

Element

The CN.CONV.RATE element contains the following sub-elements:

Attributes

The ALIAS attribute

The ALIAS attribute of the CN.CONV.RATE element is used to define a second header for the column. This is usually a sequence number attributed to the column in order to be able to facilitate reference to this column. This number is given below the main header.

For presentation purposes, the text of this header may contain carriage returns. These returns must be omitted in the electronic file.

Example

<CN>

  <CN.HEADER>

    <CN.CODE ALIAS="1">CN code</CN.CODE>

    <CN.DESC ALIAS="2">Description</CN.DESC>

    <CN.RATE>

      <CN.CONV.RATE ALIAS="3">

        <TXT>Conventional rate of duty (%)</TXT>

      </CN.CONV.RATE>

    </CN.RATE>

    <CN.SUP.UNIT ALIAS="4">Supplementary unit</CN.SUP.UNIT>

  </CN.HEADER>

  <CN.UNIT TYPE="OLDHS="YESLEVEL="0">

    <CN.CODE>0101</CN.CODE>

    <CN.DESC>Live horses, asses, mules and hinnies:</CN.DESC>

  </CN.UNIT>

  <CN.UNIT TYPE="OLDHS="YESLEVEL="1">

    <CN.CODE>010110</CN.CODE>

    <CN.DESC>Pure-bred breeding animals:</CN.DESC>

  </CN.UNIT>

  <CN.UNIT TYPE="NEWHS="NOLEVEL="2">

    <CN.CODE>01011010</CN.CODE>

    <CN.DESC>Horses</CN.DESC>

    <CN.CONV.RATE>

      <TXT>Free</TXT>

    </CN.CONV.RATE>

    <CN.SUP.UNIT>p/st</CN.SUP.UNIT>

  </CN.UNIT>

</CN>

[Table of contents]

CN.DESC

[element]

Header of the 'Description' column

The CN.DESC element is used to mark up the header of the column containing the description of the goods.

In the English language version, the header contains the text 'Description'.

Model

<xd:element name="CN.DESC">
  <xd:complexType mixed="true">
    <xd:complexContent mixed="true">
      <xd:extension base="t_btx.seq">
        <xd:attribute name="ALIAStype="xd:string"/>
        <xd:attribute name="ASSVtype="xd:positiveInteger"/>
      </xd:extension>
    </xd:complexContent>
  </xd:complexType>
</xd:element>

Used by

CN.HEADER CN.UNIT

General rules

Element

The CN.DESC element is composed of standard text.

IMPORTANT: In the lines identified by a code (CN.CODE) which is composed of less than 8 digits, the text of the description is terminated by a colon. This character must never be present in the Formex instance; it exists for presentation purposes only.

Attributes

The ALIAS attribute

The ALIAS attribute is solely used if the CN.DESC element is used to describe a header.

This attribute is used to define a second header for the column. This is usually a sequence number attributed to the column in order to be able to facilitate reference to this column. This number is printed below the main header.

In the context of a description (inside the table), the use of the ALIAS attribute is forbidden.

Attributes

The ASSV attribute

The ASSV attribute is only used in the table itself (not in the context of the header), and only in documents relating to suspensions of the rates of the Common Customs Tariff. In some cases, in fact, the description of the goods and/or the rate of autonomous duties are associated with more than one CN codes. In these cases, the ASSV attribute must be included and its value must correspond to the number of the associated CN codes.

The ASSV attribute is rarely used in the context of suspensions involving aircraft. When several descriptions relate to the same CN code, the descriptions are included in the same CN.DESC element.

Example

<CN.HEADER>

  <CN.CODE>Code number</CN.CODE>

  <CN.DESC>Description</CN.DESC>

</CN.HEADER>

[Table of contents]

CN.HEADER

[element]

Column headers in the combined nomenclature

The CN.HEADER element is used to mark up the column headers in the combined nomenclature.

Model

<xd:element name="CN.HEADER">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="CN.CODE"/>
      <xd:element ref="CN.DESC"/>
      <xd:sequence minOccurs="0">
        <xd:element ref="CN.RATE"/>
        <xd:element ref="CN.SUP.UNITminOccurs="0"/>
      </xd:sequence>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

CN

General rules

Element

The CN.HEADER element is redefined at the beginning of each nomenclature. It contains a sub-element for each header, namely:

Optionally followed by:

Example

<CN.HEADER>

  <CN.CODE ALIAS="1">CN code</CN.CODE>

  <CN.DESC ALIAS="2">Description</CN.DESC>

  <CN.RATE>

    <CN.CONV.RATE ALIAS="3">

      <TXT>Conventional rate of duty (%)</TXT>

    </CN.CONV.RATE>

  </CN.RATE>

  <CN.SUP.UNIT ALIAS="4">Supplementary unit</CN.SUP.UNIT>

</CN.HEADER>

[Table of contents]

CN.RATE

[element]

Header of the 'Rate of duty' column

The CN.RATE element is used to mark up the header which is common to both columns relating to the rates of duties.

In the English language version in the combined nomenclature it contains the text 'Rate of duty'.

Model

<xd:element name="CN.RATE">
  <xd:complexType mixed="true">
    <xd:complexContent mixed="true">
      <xd:extension base="t_btx.seq">
        <xd:sequence>
          <xd:element ref="CN.AUT.RATEminOccurs="0"/>
          <xd:element ref="CN.CONV.RATEminOccurs="0"/>
        </xd:sequence>
        <xd:attribute name="ALIAStype="xd:string"/>
      </xd:extension>
    </xd:complexContent>
  </xd:complexType>
</xd:element>

Used by

CN.HEADER

General rules

Element

The CN.RATE element contains the following information:

Attributes

The ALIAS attribute

The ALIAS attribute is used to define a second header for the column. This is usually a sequence number attributed to the column in order to be able to facilitate reference to this column. This number is printed below the main header.

Example

<CN>

  <CN.HEADER>

    <CN.CODE ALIAS="1">CN code</CN.CODE>

    <CN.DESC ALIAS="2">Description</CN.DESC>

    <CN.RATE>

      <CN.CONV.RATE ALIAS="3">

        <TXT>Conventional rate of duty (%)</TXT>

      </CN.CONV.RATE>

    </CN.RATE>

    <CN.SUP.UNIT ALIAS="4">Supplementary unit</CN.SUP.UNIT>

  </CN.HEADER>

  <CN.UNIT TYPE="OLDHS="YESLEVEL="0">

    <CN.CODE>0101</CN.CODE>

    <CN.DESC>Live horses, asses, mules and hinnies:</CN.DESC>

  </CN.UNIT>

  <CN.UNIT TYPE="OLDHS="YESLEVEL="1">

    <CN.CODE>010110</CN.CODE>

    <CN.DESC>Pure-bred breeding animals:</CN.DESC>

  </CN.UNIT>

  <CN.UNIT TYPE="NEWHS="NOLEVEL="2">

    <CN.CODE>01011010</CN.CODE>

    <CN.DESC>Horses</CN.DESC>

    <CN.CONV.RATE>

      <TXT>Free</TXT>

    </CN.CONV.RATE>

    <CN.SUP.UNIT>p/st</CN.SUP.UNIT>

  </CN.UNIT>

</CN>

[Table of contents]

CN.SUP.UNIT

[element]

Header of the 'Supplementary unit' column

The CN.SUP.UNIT element is used to mark up the header of the column containing the supplementary units, as well as the supplementary units in each CN description.

In the English language version, the header contains the text 'Supplementary unit'.

Model

<xd:element name="CN.SUP.UNIT">
  <xd:complexType mixed="true">
    <xd:complexContent mixed="true">
      <xd:extension base="t_btx.seq">
        <xd:attribute name="ALIAStype="xd:string"/>
      </xd:extension>
    </xd:complexContent>
  </xd:complexType>
</xd:element>

Used by

CN.HEADER CN.UNIT

General rules

Element

Attributes

The ALIAS attribute

The ALIAS attribute of the CN.SUP.UNIT element is only used in the context of a header. It is used to define a second header for the column. This is usually a sequence number attributed to the column in order to be able to facilitate reference to this column. This number is given below the main header.

For presentation purposes, the text of this header may contain carriage returns. These returns must be omitted in the electronic file.

Example

<CN.HEADER>

  <CN.CODE ALIAS="1">CN code</CN.CODE>

  <CN.DESC ALIAS="2">Description</CN.DESC>

  <CN.RATE>

    <CN.CONV.RATE ALIAS="3">

      <TXT>Conventional rate of duty (%)</TXT>

    </CN.CONV.RATE>

  </CN.RATE>

  <CN.SUP.UNIT ALIAS="4">Supplementary unit</CN.SUP.UNIT>

</CN.HEADER>

[Table of contents]

CN.UNIT

[element]

Description of goods

The CN.UNIT element is used in the combined nomenclature in order to mark up the description of goods.

Model

<xd:element name="CN.UNIT">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="CN.CODEminOccurs="0"/>
      <xd:element ref="CN.DESCminOccurs="0"/>
      <xd:element ref="CN.AUT.RATEminOccurs="0"/>
      <xd:element ref="CN.CONV.RATEminOccurs="0"/>
      <xd:element ref="CN.SUP.UNITminOccurs="0"/>
    </xd:sequence>
    <xd:attribute name="TYPEdefault="OLD">
      <xd:simpleType>
        <xd:restriction base="xd:string">
          <xd:enumeration value="OLD"/>
          <xd:enumeration value="NEW"/>
          <xd:enumeration value="MODIF"/>
          <xd:enumeration value="DEL"/>
        </xd:restriction>
      </xd:simpleType>
    </xd:attribute>
    <xd:attribute name="HSdefault="YES">
      <xd:simpleType>
        <xd:restriction base="xd:string">
          <xd:enumeration value="YES"/>
          <xd:enumeration value="NO"/>
        </xd:restriction>
      </xd:simpleType>
    </xd:attribute>
    <xd:attribute name="LEVELtype="xd:nonNegativeIntegeruse="required"/>
  </xd:complexType>
</xd:element>

Used by

CN GR.CN.UNIT

General rules

Element

Depending on the column concerned, this element may contain the following information:

Although all the elements of the model are optional, the CN.UNIT element may never be empty.

There is usually a description. The description is only missing when there is a deleted position, but in this case the CN code is given.

Attributes

The TYPE attribute

The code numbers may be marked up by a special symbol:

This information is given in the TYPE attribute. The corresponding symbol may not be included in the electronic version. The following values are possible:

Attributes

The HS attribute

When the unit comes from the harmonised system, the description of the goods appears in bold type. Otherwise, it is in normal type.

This information is covered by the HS attribute which has two possible values:

Attributes

The LEVEL attribute

The LEVEL attribute is mandatory and is used to identify the level of the unit, which is represented by the number of dashes preceding the description of the goods. If there are no dashes, the value of the LEVEL attribute is equal to '0' (zero).

Example

<CN>

  <CN.HEADER>

    <CN.CODE>Code number</CN.CODE>

    <CN.DESC>Description</CN.DESC>

  </CN.HEADER>

  <CN.UNIT TYPE="OLDHS="YESLEVEL="0">

    <CN.CODE>8901</CN.CODE>

    <CN.DESC>Cruise ships, excursion boats, ferry-boats, cargo ships, barges and similar vessels for the transport of persons or goods:</CN.DESC>

  </CN.UNIT>

  <CN.UNIT TYPE="OLDHS="YESLEVEL="1">

    <CN.CODE>890110</CN.CODE>

    <CN.DESC>Cruise ships, excursion boats and similar vessels principally designed for the transport of persons; ferry-boats of all kinds:</CN.DESC>

  </CN.UNIT>

  <CN.UNIT TYPE="OLDHS="NOLEVEL="2">

    <CN.CODE>89011010</CN.CODE>

    <CN.DESC>Sea-going</CN.DESC>

  </CN.UNIT>

  <CN.UNIT TYPE="OLDHS="YESLEVEL="1">

    <CN.CODE>890120</CN.CODE>

    <CN.DESC>Tankers:</CN.DESC>

  </CN.UNIT>

</CN>

[Table of contents]

COLL

[element]

Collection of the publication

The COLL element is used to mark up the collection to which the publication belongs.

Model

<xd:element name="COLLtype="t_collection"/>

Used by

BIB.OJ COLL DOC.CORR DOCUMENT.REF DOCUMENT.REF.CONS HEADER.SUMMARY OJ.CL PUBLICATION.REF REF.OJ SPEC.ED

General rules

Element

It can only contain the values defined in the t_collection simple type, namely:

[Table of contents]

COLL.LETTERS

[element]

Series of letters in an agreement

When an agreement is published in the format of an exchange of letters, all the letters must be marked up within a COLL.LETTERS element.

Model

<xd:element name="COLL.LETTERS">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="LETTERmaxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

t_btx t_btx.ecr t_btx.struct AGR GR.SEQ QUOT.S

General rules

Element

The COLL.LETTERS element contains one or more LETTER elements.

[Table of contents]

COM

[element]

Community concerned

The COM element is used to mark up the code of the community concerned. The position in which the community concerned is placed in the printed text depends on the type of the document. For regulations, the reference to the community concerned is found between brackets in the title of the document, just before the number of the act.

In other cases, the community concerned can be found in the number of the act.

Model

<xd:element name="COMtype="xd:string"/>

Used by

BIB.DOC COM NO.DOC NO.DOC

General rules

Element

The content of the COM element should correspond to one of the following values, irrespective of the language version of the document:

In exceptional cases the OTHER value may be used. This may only be done with the consent of EUR-OP when the institution or the community concerned is not included in the list of existing values.

For decisions taken by the EEA Joint Committee and decisions taken by the EEA Council, the community concerned is not indicated in the printed text. The COM element must be omitted in these cases.

In all other cases, it is obligatory.

The contents of this list might change in the course of time, so it should not be considered complete.

If a document concerns more than one community, the values have to be integrated in the same COM element, separated by a semicolon ";" and a space.

Example

<NO.DOC FORMAT="NYTYPE="OJ">

  <NO.CURRENT>457</NO.CURRENT>

  <YEAR>2002</YEAR>

  <COM>EC</COM>

</NO.DOC>

[Table of contents]

COMMENT

[element]

Comment within a provision

The COMMENT element is used to mark up the annotations, which supplement provisions in internal regulations.

Model

<xd:element name="COMMENTtype="t_btx.struct"/>

Used by

t_btx t_btx.ecr t_btx.struct ARTICLE ARTICLE ARTICLE COMMENT PARAG SUBDIV SUBDIV SUBDIV

General rules

Element

The element can appear within articles and paragraphs.

[Table of contents]

COMPETITION

[element]

Announcement of a competition

The COMPETITION element is the root element for documents relating to the announcement of a competition. These documents are published in the OJ CA collection.

Model

<xd:element name="COMPETITION">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.INSTANCE"/>
      <xd:element ref="GR.ANNOTATIONminOccurs="0"/>
      <xd:element ref="TITLE"/>
      <xd:element ref="GR.ANNOTATIONminOccurs="0"/>
      <xd:element ref="COMPETITION.INIT"/>
      <xd:element ref="TOCminOccurs="0"/>
      <xd:element ref="CONTENTS"/>
    </xd:sequence>
    <xd:attribute name="NNCtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

The COMPETITION element contains:

The illustration below shows the title, the introductory text and the table of contents:

Attributes

The NNC attribute

In some special cases, the numbering of footnotes does not restart on every page, but continues from 1 to n. For those cases the attribute NNC [notes numbering continued] takes the value 'YES'. The default value of this attribute is 'NO'. So the attribute should not be used if the numbering of footnotes follows the general rules and restarts on a new page.

Example

<COMPETITION>

  <TITLE>

    <TI>

      <P>

        <HT TYPE="UC">Guide for candidates in open competitions organised by the European Parliament</HT>

      </P>

      <P>(2002/C 119 A/01)</P>

    </TI>

  </TITLE>

  <COMPETITION.INIT>

    <P>

      <HT TYPE="BOX">This guide is for information only. In its proceedings the selection board is not required by law to comply with any text other than the notice of competition.</HT>

    </P>

  </COMPETITION.INIT>

  <TOC>

    <TOC.ITEM>

      <NO.ITEM>A.</NO.ITEM>

      <ITEM.CONT>

        <HT TYPE="UC">The work of selection boards</HT>

      </ITEM.CONT>

    </TOC.ITEM>

  </TOC>

</COMPETITION>

[Table of contents]

COMPETITION.INIT

[element]

Introduction to a notice of competition

The COMPETITION.INIT element is used to mark up the introduction to a notice of competition. It concerns one or more sentences that immediately follow the title and that are used to introduce the contents of the document.

Model

<xd:element name="COMPETITION.INITtype="t_btx.struct"/>

Used by

t_btx t_btx.struct COMPETITION COMPETITION.INIT GR.SEQ QUOT.S

General rules

Element

The COMPETITION.INIT element contains mainly P elements, with an extensive use of HT elements to take into account the presentation.

Example

<COMPETITION.INIT>

  <P>The European Parliament’s Secretariat in Luxembourg is holding an open competition to form a shortlist for the recruitment of</P>

  <P>

    <HT TYPE="BOLD">English-language</HT>

  </P>

  <P>

    <HT TYPE="BOLD">INTERPRETERS (LA 7/LA 6)</HT>

  </P>

  <P>(female or male)</P>

  <P>

    <HT TYPE="BOLD">NB: A thorough knowledge of Danish, Dutch, Finnish, Greek, Portuguese, Spanish or Swedish is required</HT>

  </P>

</COMPETITION.INIT>

[Table of contents]

CONCLUSION

[element]

Conclusion of a case

The CONCLUSION element is used to mark up the conclusion of a case.

Model

<xd:element name="CONCLUSION">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.CONCLUSION"/>
      <xd:element ref="CURR.TITLE"/>
      <xd:element ref="TITLE"/>
      <xd:element ref="INTERMEDIATEminOccurs="0"/>
      <xd:element ref="TITLEminOccurs="0"/>
      <xd:element ref="CONTENTS.CONCLUSION"/>
    </xd:sequence>
    <xd:attribute name="NNCtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

The element contains the following information:

Attributes

The NNC attribute

In some special cases, the numbering of footnotes does not restart on every page, but continues from 1 to n. For those cases the attribute NNC [notes numbering continued] takes the value 'YES'. The default value of this attribute is 'NO'. So the attribute should not be used if the numbering of footnotes follows the general rules and restarts on a new page.

[Table of contents]

CONS.ACT

[element]

Consolidated act

The CONS.ACT element is used to mark up a consolidated text within a given chronological period.

Model

<xd:element name="CONS.ACT">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="INFO.CONSLEG"/>
      <xd:element ref="INFO.PROD"/>
      <xd:element ref="CONS.DOC"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

This element may include the following:

[Table of contents]

CONS.ANNEX

[element]

Annex in a consolidated document

The CONS.ANNEX element is used to mark up an annex within consolidated documents. Note that all of the components (the act and the annexed documents) are in the same instance.

Model

<xd:element name="CONS.ANNEX">
  <xd:complexType>
    <xd:sequence>
      <xd:choice maxOccurs="unbounded">
        <xd:element ref="TOC"/>
        <xd:element ref="TITLE"/>
        <xd:element ref="GR.ANNOTATION"/>
        <xd:element ref="ANNOTATION"/>
      </xd:choice>
      <xd:element ref="CONTENTSminOccurs="0"/>
      <xd:element ref="CONS.ANNEXminOccurs="0maxOccurs="unbounded"/>
    </xd:sequence>
    <xd:attribute name="NNCtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

t_btx.struct CONS.ANNEX CONS.DOC QUOT.S

General rules

Element

The CONS.ANNEX element may contain:

Attributes

The NNC attribute

In some special cases, the numbering of footnotes does not restart on every page, but continues from 1 to n. For those cases the attribute NNC [notes numbering continued] takes the value 'YES'. The default value of this attribute is 'NO'. So the attribute should not be used if the numbering of footnotes follows the general rules and restarts on a new page.

Example

<CONS.ANNEX>

  <TITLE>

    <TI>

      <P>

        <HT TYPE="UC">Annex I</HT>

      </P>

    </TI>

    <STI>

      <P>

        <HT TYPE="UC">Safe harbour privacy principles</HT>

      </P>

      <P>issued by the US Department of Commerce on 21 July 2000</P>

    </STI>

  </TITLE>

  <CONTENTS TYPE="NORMAL">

    <GR.SEQ>

      <P>The European Union's comprehensive privacy legislation, the Directive on Data Protection (the Directive), became effective on October 25, 1998.</P>

      <P>To diminish this uncertainty and provide a more predictable framework for such data transfers, the Department of Commerce is issuing this document and Frequently Asked Questions.</P>

    </GR.SEQ>

    <GR.SEQ>

      <TITLE>

        <TI>

          <TXT>

            <HT TYPE="UC">Notice</HT>

          </TXT>

        </TI>

      </TITLE>

      <P>An organization must inform individuals about the purposes for which it collects and uses information about them, how to contact the organization with any inquiries or complaints, the types of third parties to which it discloses the information, and the choices and means the organization offers individuals for limiting its use and disclosure.</P>

    </GR.SEQ>

  </CONTENTS>

</CONS.ANNEX>

[Table of contents]

CONS.DOC

[element]

Consolidated document

The CONS.DOC element is used to mark up the composition of the family and the consolidated document itself.

Model

<xd:element name="CONS.DOC">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.INSTANCE"/>
      <xd:element ref="FAM.COMP"/>
      <xd:element ref="TOCminOccurs="0"/>
      <xd:element ref="TITLE"/>
      <xd:choice minOccurs="0maxOccurs="unbounded">
        <xd:element ref="TOC"/>
        <xd:element ref="GR.ANNOTATION"/>
        <xd:element ref="ANNOTATION"/>
      </xd:choice>
      <xd:element ref="PREAMBLE"/>
      <xd:element ref="ENACTING.TERMS"/>
      <xd:element ref="FINALminOccurs="0"/>
      <xd:element ref="CONS.ANNEXminOccurs="0maxOccurs="unbounded"/>
    </xd:sequence>
    <xd:attribute name="NNCtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

CONS.ACT

General rules

Element

The CONS.DOC element contains:

Attributes

The NNC attribute

In some special cases, the numbering of footnotes does not restart on every page, but continues from 1 to n. For those cases the attribute NNC [notes numbering continued] takes the value 'YES'. The default value of this attribute is 'NO'. So the attribute should not be used if the numbering of footnotes follows the general rules and restarts on a new page.

[Table of contents]

CONS.DOC.GEN

[element]

General structure of consolidated documents

The CONS.DOC.GEN element is used to mark up any type (or any fragment) of a consolidated document, which does not follow a regular structure. Its content model is designed to match any structure of documents or related documents, and so to facilitate the re-use of the Formex V3 original instances.

Model

<xd:element name="CONS.DOC.GEN">
  <xd:complexType>
    <xd:sequence>
      <xd:choice minOccurs="0maxOccurs="unbounded">
        <xd:element ref="TOC"/>
        <xd:element ref="TITLE"/>
        <xd:element ref="GR.ANNOTATION"/>
        <xd:element ref="ANNOTATION"/>
      </xd:choice>
      <xd:choice maxOccurs="unbounded">
        <xd:element ref="CONTENTS"/>
        <xd:element ref="FINAL"/>
        <xd:element ref="PREAMBLE"/>
        <xd:element ref="ENACTING.TERMS"/>
        <xd:element ref="ACT.GEN"/>
      </xd:choice>
      <xd:element ref="CONS.DOC.GENminOccurs="0maxOccurs="unbounded"/>
    </xd:sequence>
    <xd:attribute name="TYPEuse="required">
      <xd:simpleType>
        <xd:restriction base="xd:string">
          <xd:enumeration value="ACT"/>
          <xd:enumeration value="ANNEX"/>
          <xd:enumeration value="GENERAL"/>
          <xd:enumeration value="OTH.ACT"/>
        </xd:restriction>
      </xd:simpleType>
    </xd:attribute>
  </xd:complexType>
</xd:element>

Used by

CONS.DOC.GEN CONS.OTH.DOC

General rules

Element

The CONS.DOC.GEN element consists of three parts:

Attributes

The TYPE attribute

The TYPE attribute is mandatory and is used to specify the structure of the original document. It also gives a clear indication on the original Formex V3 DTD that was used.

It can take one of the following values :

The use rules of the CONS.DOC.GEN element depend on the TYPE attribute values.

For each value of the TYPE attribute, here is a list of the allowed elements:

[Table of contents]

CONS.LIST

[element]

Description of a consolidation family

The CONS.LIST element is used to mark up the descriptions for all members of a consolidation family and for all chronological periods.

Model

<xd:element name="CONS.LIST">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="FAM.COMP.CL"/>
      <xd:sequence maxOccurs="unbounded">
        <xd:element ref="JOB.CONSLEG"/>
        <xd:element ref="EVENTminOccurs="0maxOccurs="unbounded"/>
      </xd:sequence>
    </xd:sequence>
    <xd:attribute name="CONSLEG.REFtype="xd:stringuse="required"/>
    <xd:attribute name="CELEX.BASICtype="xd:stringuse="required"/>
    <xd:attribute name="LEG.VALuse="required">
      <xd:simpleType>
        <xd:restriction base="xd:string">
          <xd:enumeration value="DEC"/>
          <xd:enumeration value="DECDEL"/>
          <xd:enumeration value="DEC.EEA"/>
          <xd:enumeration value="DEC.ECSC"/>
          <xd:enumeration value="DECIMP"/>
          <xd:enumeration value="DIR"/>
          <xd:enumeration value="DIRDEL"/>
          <xd:enumeration value="DIRIMP"/>
          <xd:enumeration value="GENGUID"/>
          <xd:enumeration value="JOINT.ACT"/>
          <xd:enumeration value="OTHER"/>
          <xd:enumeration value="PROC"/>
          <xd:enumeration value="REC.ECSC"/>
          <xd:enumeration value="REG"/>
          <xd:enumeration value="REGDEL"/>
          <xd:enumeration value="REGIMP"/>
          <xd:enumeration value="TREATY"/>
        </xd:restriction>
      </xd:simpleType>
    </xd:attribute>
    <xd:attribute name="CELEX.PREPtype="xd:stringuse="required"/>
    <xd:attribute name="DATE.LASTtype="t_dateuse="required"/>
    <xd:attribute name="LG.EXISTStype="xd:stringuse="required"/>
    <xd:attribute name="PRODUCERtype="xd:stringuse="required"/>
    <xd:attribute name="CREATED.BYtype="xd:stringuse="required"/>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

It contains the following sub-elements:

The element is the root element for this kind of instance. It contains at least the description of the family and one job ticket (JOB.CONSLEG).

Attributes

The CONSLEG.REF attribute

The CONSLEG.REF attribute is mandatory and is used to define the name of the family. The format CCYYTNNNN has to be respected, where

Attributes

The CELEX.BASIC attribute

The CELEX.BASIC attribute is mandatory and contains the CELEX number of the basic act in a consolidation family.

Attributes

The LEG.VAL attribute

The LEG.VAL attribute is mandatory and is used to indicate the legal value of the basic act. The following values are accepted:

Nota bene: In exceptional cases the value OTHER has to be used, but only with the prior approval of the Publications Office.

Attributes

The CELEX.PREP attribute

The CELEX.PREP attribute is mandatory and is used to specify the date when the last information was extracted from CELEX in order to create this list. The date must respect the format YYYYMMDD where:

Attributes

The DATE.LAST attribute

The DATE.LAST attribute is mandatory and is used to specify the publication date of the last modifying act taken into account in this list. Its value has to be constructed according to the t_date format, namely the YYYYMMDD format (see above).

Attributes

The LG.EXISTS attribute

The LG.EXISTS attribute is mandatory and is used to indicate the language versions in which the basic act is available. It can contain the values defined in the t_language simple type. Various codes are separated by ';'.

Attributes

The PRODUCER attribute

The PRODUCER attribute is mandatory and contains the producer of the consolidated family. For the time being, only one value is possible: IS.

Attributes

The CREATED.BY attribute

The CREATED.BY attribute is mandatory and is used to specify the programme which has been used to create this list or the value 'MANUAL'.

[Table of contents]

CONS.OTH

[element]

Consolidated act with a non-regular structure

The CONS.OTH element is used to mark up a consolidated act, which presents a non-regular structure, within a given chronological period.

If the act follows a regular structure, the CONS.ACT element must be used.

Model

<xd:element name="CONS.OTH">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="INFO.CONSLEG"/>
      <xd:element ref="INFO.PROD"/>
      <xd:element ref="CONS.OTH.DOC"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

It contains the following sub-elements:

[Table of contents]

CONS.OTH.DOC

[element]

Consolidated document

The CONS.OTH.DOC element is used to mark up consolidated documents which do not follow a regular structure.

Model

<xd:element name="CONS.OTH.DOC">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.INSTANCE"/>
      <xd:element ref="FAM.COMP"/>
      <xd:element ref="CONS.DOC.GEN"/>
    </xd:sequence>
    <xd:attribute name="NNCtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

CONS.OTH

General rules

Element

It contains the following sub-elements:

Attributes

The NNC attribute

In some special cases, the numbering of footnotes does not restart on every page, but continues from 1 to n. For those cases the attribute NNC [notes numbering continued] takes the value 'YES'. The default value of this attribute is 'NO'. So the attribute should not be used if the numbering of footnotes follows the general rules and restarts on a new page.

[Table of contents]

CONSID

[element]

Recital of a legal act

The CONSID element contains one recital of a legal act. Recitals may be numbered.

Model

<xd:element name="CONSIDtype="t_btx.struct"/>

Used by

t_btx t_btx.ecr t_btx.struct CONSID DIV.CONSID GR.CONSID GR.SEQ QUOT.S

General rules

Element

Depending on the recitals group structure, each recital may begin with the word Whereas (for the english language version). This expression may be marked up using the GR.CONSID.INIT element before the recitals.

When a recital is numbered, the NP element is used to mark up its contents, otherwise the element P has to be used. Generally, if additional structures are necessary, these are marked up with a P element.

Example

This example shows numbered recitals which are preceded by the GR.CONSID.INIT tag:

<GR.CONSID>

  <GR.CONSID.INIT>Whereas:</GR.CONSID.INIT>

  <CONSID>

    <NP>

      <NO.P>(1)</NO.P>

      <TXT>Article 7(2)(b) of Directive 86/362/EEC and Article 4(2)(b) of Directive 90/642/EEC require the Commission to submit to the Standing Committee on Plant Health by 31 December each year a recommendation setting out a coordinated Community monitoring programme to ensure compliance for maximum levels of pesticide residues set out in the Annexes II to the said Directives. Article 1(1) of Commission Regulation (EC) No 645/2000 provides that such recommendations may cover a period of between one and five years.</TXT>

    </NP>

  </CONSID>

  <CONSID>

    <NP>

      <NO.P>(2)</NO.P>

      <TXT>The Commission should progressively work towards a system which would permit the estimation of dietary exposure to actual pesticide, as provided for in the second paragraph of Article 7(3) of Directive 86/362/EEC and the second paragraph of Article 4(3) of Directive 90/642/EEC. To facilitate examination of the feasibility of such estimations, data concerning the monitoring of residues of pesticides in a number of food products which constitute major components of European diets should be available. In view of the resources available at national level for pesticide residue monitoring, Member States are only able to analyse samples of eight products each year within a coordinated monitoring programme. Pesticide uses show changes within the timescale of the five-year rolling programme. Each pesticide should thus generally be monitored in 20 to 30 food products over a series of three-;year cycles.</TXT>

    </NP>

  </CONSID>

  <CONSID>

    <NP>

      <NO.P>(3)</NO.P>

      <TXT>Member States should adopt continuous monitoring methods, since these facilitate the recognition of changes in the occurrence of pesticides.</TXT>

    </NP>

  </CONSID>

</GR.CONSID>

[Table of contents]

CONTENTS

[element]

Contents

The CONTENTS element is used to mark up the contents of a document.

This element is used in various contexts such as:

Model

<xd:element name="CONTENTS">
  <xd:complexType>
    <xd:complexContent>
      <xd:extension base="t_btx.struct">
        <xd:attribute name="TYPEdefault="NORMAL">
          <xd:simpleType>
            <xd:restriction base="xd:string">
              <xd:enumeration value="BOX"/>
              <xd:enumeration value="NORMAL"/>
            </xd:restriction>
          </xd:simpleType>
        </xd:attribute>
      </xd:extension>
    </xd:complexContent>
  </xd:complexType>
</xd:element>

Used by

t_btx t_btx.ecr t_btx.struct ANNEX APPEAL.TABLE CHRON.TABLE CHRON.TABLE.NP CJT COMPETITION CONS.ANNEX CONS.DOC.GEN ECR.GENERAL GENERAL GR.SEQ INTERNAL.ANNEX LETTER QUOT.S REPORT.HEARING

General rules

Element

The element may only contain one or more of the elements defined in the t_btx.struct complex type.

The content of a letter begins after the indication of the place and the date, or after the title of the letter when this information is not given. It ends before the signature or signatures. If there are no signatures, the end of the content coincides with the end of the document.

In agreements with a general structure, the CONTENTS element includes the part of the text which begins after the title of the agreement and ends before any signatures.

Attributes

The TYPE attribute

The attribute TYPE has the value BOX if the text is enclosed in a box. The default value is NORMAL.

Example

Example of a CONTENTS element in a letter:

<LETTER>

  <TITLE>

    <TI>

      <P>Letter No 1</P>

    </TI>

  </TITLE>

  <PL.DATE>

    <P> Brussels,

      <DATE ISO="19910417">17 April 1991</DATE>

</P>

  </PL.DATE>

  <CONTENTS TYPE="NORMAL">

    <P>Sir,</P>

    <P>Please accept, Sir, the assurance of my highest consideration.</P>

  </CONTENTS>

  <SIGNATORY>

    <P>For the Government of Barbados</P>

    <P>

      <INCL.ELEMENT TYPE="EPSFFILEREF="AGR-Letter.2">      </INCL.ELEMENT>

    </P>

  </SIGNATORY>

</LETTER>

[Table of contents]

CONTENTS.CONCLUSION

[element]

Content of a conclusion

The CONTENTS.CONCLUSION element is used to mark up the conclusions of the senior public prosecutor.

Model

<xd:element name="CONTENTS.CONCLUSIONtype="t_btx.ecr"/>

Used by

CONCLUSION CONTENTS.CONCLUSION

General rules

Element

It may only contain one or more of the elements defined in the t_btx complex type.

Example

<CONTENTS.CONCLUSION>

  <TITLE>

    <TI>

      <P>

        <HT TYPE="UC">Conclusions de l'avocat général M. Alain Dutheillet de Lamothe, présentées le

          <DATE ISO="19710609">9 juin 1971</DATE>

</HT>

      </P>

    </TI>

  </TITLE>

  <P>

    <HT TYPE="ITALIC">Monsieur le Président,</HT>

  </P>

  <P>

    <HT TYPE="ITALIC">Messieurs les Juges,</HT>

  </P>

  <P>M. Vinck est un fonctionnaire affecté au service de la Commission.</P>

  <P>Avant la

    <QUOT.START ID="QS0001REF.END="QE0001CODE="00AB">    </QUOT.START> fusion     <QUOT.END ID="QE0001REF.START="QS0001CODE="00BB">    </QUOT.END>, il dirigeait, au sein de l'Euratom, un service spécialisé pour l'exécution de travaux de sécurité dans les installations nucléaires.</P>

  <P>A la suite de la

    <QUOT.START ID="QS0002REF.END="QE0002CODE="00AB">    </QUOT.START> fusion     <QUOT.END ID="QE0002REF.START="QS0002CODE="00BB">    </QUOT.END>, il estima que ce service aurait dû être réorganisé en une division, que lui-même aurait dû être placé à tête de cette division ou éventuellement d'une autre, et en tout cas promu du grade A 4 qu'il détenait au grade A 3.</P>

  <P>En 1968-1969, il adressa en ce sens de nombreuses demandes successives à Commission qui les rejeta toutes.</P>

  <P>Il vous demande par la présente requête d'annuler une décision du 21 mai 1970 par laquelle le président de la Commission a rejeté la demande qu'il lui avait adressée le 16 février 1970.</P>

  <P>La Commission a soulevé

    <QUOT.START ID="QS0003REF.END="QE0003CODE="00AB">    </QUOT.START> in limine litus     <QUOT.END ID="QE0003REF.START="QS0003CODE="00BB">    </QUOT.END> une exception d'irrecevabilité tirée de la tardiveté.</P>

  <P>Cette exception d'irrecevabilité paraît fondée.</P>

  <P>Vous avez jugé en effet à maintes reprises que les recours formés contre des décisions explicites qui sont purement confirmatives de décisions implicites devenues définitives pour n'avoir pas été attaquées dans les délais de recours contentieux, étaient irrecevables.</P>

  <P>Vous avez même été plus loin et vous avez jugé dans un arrêt récent (Bode, du 26 mai 1971) que des recours contre des décisions explicites confirmatives de décisions implicites, même introduits dans les délais, étaient irrecevables pour défaut d'intérêt.</P>

  <P>Cette jurisprudence est, à notre avis, entièrement applicable en l'espèce.</P>

  <P>Par une lettre datée du 16 février 1970, parvenue au plus tard le 18 février, le requérant avait demandé au président de la Commission que soit réparé, sous la forme d'une promotion ou sous la forme de dommages et intérêts, le préjudice de carrière qu'il estimait avoir subi.</P>

  <P>Le président n'ayant pas répondu à cette lettre dans le délai de deux mois prévu par l'article 91, paragraphe 2, second alinéa, le requérant devait donc regarder sa demande comme rejetée le 18 ou le 19 avril et se pourvoir contre cette décision implicite au plus tard avant le 20 ou le 21 juin 1970.</P>

  <P>Or, son recours n'a été déposé au greffe de la Cour que le 28 août 1970, soit plus de deux mois après l'expiration du délai de recours contentieux contre la décision implicite.</P>

  <P>Le requérant fait bien état de l'intervention, le 21 mai 1970, d'une décision explicite rejetant sa demande.</P>

  <P>Mais cette décision est purement confirmative de la décision implicite et elle n'a donc pas eu pour effet d'ouvrir un nouveau délai de recours contentieux.</P>

  <P>Certes, et c'est la particularité de la présente affaire, cette décision explicite est intervenue alors que le délai de recours contre la décision implicite n'était pas expiré.</P>

  <P>Mais cette circonstance est, selon nous, sans influence sur l'application de la jurisprudence que nous vous rappelions tout à l'heure. Dès lors qu'une décision implicite doit être considérée comme acquise, c'est, en application de l'article 91 du statut, à la date à laquelle cette décision est réputée être intervenue, et à cette seule date, que commence à courir le délai de deux mois prévu par cette disposition.</P>

  <P>Nous concluons donc:</P>

  <LIST TYPE="DASH">

    <ITEM>

      <P>au rejet de la requête comme irrecevable,</P>

    </ITEM>

    <ITEM>

      <P>à ce que chacune des parties supporte ses propres dépens.</P>

    </ITEM>

  </LIST>

</CONTENTS.CONCLUSION>

[Table of contents]

CONTENTS.CORR

[element]

Content of a corrigendum

The CONTENTS.CORR element contains a series of corrections which have to be made to the original text.

Model

<xd:element name="CONTENTS.CORR">
  <xd:complexType>
    <xd:choice>
      <xd:element ref="CORRECTIONmaxOccurs="unbounded"/>
      <xd:element ref="GR.CORRECTIONmaxOccurs="unbounded"/>
    </xd:choice>
  </xd:complexType>
</xd:element>

Used by

t_btx.struct CORR QUOT.S

General rules

Element

The content of a corrigendum follows a strict structure, where each correction has to be marked up within a CORRECTION element.

In some cases the reference to the correction or modification is split, the first part referring to several corrections. Then the element GR.CORRECTION has to be used.

[Table of contents]

CONTENTS.DECISION.ECR

[element]

Content of a Court decision

The CONTENTS.DECISION.ECR element contains the provisions of a Court decision.

Model

<xd:element name="CONTENTS.DECISION.ECR">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="GR.SEQmaxOccurs="unbounded"/>
      <xd:element ref="JURISDICTION"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

DECISION.ECR

General rules

Element

The content is composed of an unlimited number of chapters (GR.SEQ), which might be nested, and the JURISDICTION element.

[Table of contents]

CONTENTS.JUDGMENT

[element]

Content of a judgment

The element contains the provisions of a judgment.

Model

<xd:element name="CONTENTS.JUDGMENT">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="GR.SEQmaxOccurs="unbounded"/>
      <xd:element ref="JURISDICTION"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

JUDGMENT

General rules

Element

The content is composed of an unlimited number of chapters (GR.SEQ), which might be nested, and the JURISDICTION element.

Example

<CONTENTS.JUDGMENT>

  <GR.SEQ LEVEL="1">

    <TITLE>

      <TI>

        <P>ARRÊT</P>

      </TI>

    </TITLE>

    <GR.SEQ LEVEL="2">

      <TITLE>

        <TI>

          <P>Points de fait et de droit</P>

        </TI>

      </TITLE>

      <GR.SEQ LEVEL="3">

        <TITLE>

          <TI>

            <NP>

              <NO.P>I —</NO.P>

              <TXT>Exposé des faits</TXT>

            </NP>

          </TI>

        </TITLE>

        <P>Attendu que M. Willem Vinck a été engagé par la Commission de la CEEA, le 5 mai 1958, avec un traitement de base correspondant au grade A5, pour y occuper les fonctions de secrétaire de la direction générale

          <QUOT.START ID="QS0004REF.END="QE0004CODE="00AB">          </QUOT.START> Industrie et économie          <QUOT.END ID="QE0004REF.START="QS0004CODE="00BB">          </QUOT.END>, plus particulièrement chargé des questions de retraitement et de sécurité technique ; que le traitement de base de M. Vinck a, le 1er mai 1961, été porté à un montant correspondant à l'échelon 1 du grade A4 ; que M. Vinck a été titularisé au grade A4 avec effet au 1er janvier 1962 ; attendu que, le 14 mai 1963, M. Vinck a posé sa candidature à un poste de chef de division, de grade A3, à la direction générale           <QUOT.START ID="QS0005REF.END="QE0005CODE="00AB">          </QUOT.START> industrie           <QUOT.END ID="QE0005REF.START="QS0005CODE="00BB">          </QUOT.END> ; que cette candidature n'a pas été retenue;</P>

        <P>que, le 1er juillet et le 11 octobre 1965, M. Vinck a posé à nouveau, sans succès, sa candidature à deux emplois déclarés vacants dans les services de la Commission ;</P>

        <P>attendu que, par note interne du 30 mars 1966, la direction générale

          <QUOT.START ID="QS0006REF.END="QE0006CODE="00AB">          </QUOT.START>Industrie et économie           <QUOT.END ID="QE0006REF.START="QS0006CODE="00BB">          </QUOT.END> a décidé que           <QUOT.START ID="QS0007REF.END="QE0007CODE="00AB">          </QUOT.START> les travaux de sécurité des installations nucléaires sont... exécutés par le service de sécurité, dirigé par M. Vinck ... sous la responsabilité directe du directeur de l'industrie           <QUOT.END ID="QE0007REF.START="QS0007CODE="00BB">          </QUOT.END> ;</P>

        <P>que, le 2 décembre 1966, M. Vinck a demandé que la création du service spécialisé qu'il dirigeait soit officialisée et retenue dans l'organigramme de la Commission ;</P>

        <P>attendu que, par mémorandum du 24 août 1967, confirmé le 25 septembre, M. Vinck a demandé au directeur général de la direction générale

          <QUOT.START ID="QS0008REF.END="QE0008CODE="00AB">          </QUOT.START> Administration et personnel           <QUOT.END ID="QE0008REF.START="QS0008CODE="00BB">          </QUOT.END> que des décisions soient prises à son égard en matière de promotion au grade A 3 au cours de l'année 1967 ;</P>

      </GR.SEQ>

    </GR.SEQ>

  </GR.SEQ>

  <JURISDICTION>

    <INTRO>

      <P>par ces motifs,</P>

      <P>vu les actes de procédure;</P>

      <P>le juge rapporteur entendu en son rapport;</P>

      <P>les parties entendues en leurs plaidoiries;</P>

      <P>l'avocat général entendu en ses conclusions;</P>

      <P>vu le statut des fonctionnaires;</P>

      <P>vu les protocoles sur le statut de la Cour de justice;</P>

      <P>vu le règlement de procédure, en particulier son article 91,</P>

      <P>LA COUR (deuxième chambre),</P>

      <P>rejetant toutes autres conclusions plus amples ou contraires, déclare et arrête:</P>

    </INTRO>

    <LIST TYPE="ARAB">

      <ITEM>

        <NP>

          <NO.P>1)</NO.P>

          <TXT>Le recours est rejeté comme irrecevable;</TXT>

        </NP>

      </ITEM>

      <ITEM>

        <NP>

          <NO.P>2)</NO.P>

          <TXT>Chacune des parties supportera ses propres dépens.</TXT>

        </NP>

      </ITEM>

    </LIST>

  </JURISDICTION>

</CONTENTS.JUDGMENT>

[Table of contents]

CONTENTS.LSEU

[element]

Content of a legislation summary

The element contains the provisions of a legislative summary.

Model

<xd:element name="CONTENTS.LSEU">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="HEADER.LSEUminOccurs="0maxOccurs="unbounded"/>
      <xd:choice minOccurs="0maxOccurs="unbounded">
        <xd:element ref="ADDITIONAL.DOCS.LSEU"/>
        <xd:element ref="REFERENCE.TABLE"/>
        <xd:element ref="REFERENCES.LSEU"/>
        <xd:element ref="REFERRED.DOCS.LSEU"/>
        <xd:element ref="SUMMARY.LSEU"/>
        <xd:element ref="MENU.LSEUminOccurs="0"/>
      </xd:choice>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

LSEU

General rules

Element

It is composed of the following elements:

[Table of contents]

CONTENTS.OPINION

[element]

Content of an opinion

The element contains the provisions of an opinion.

Model

<xd:element name="CONTENTS.OPINION">
  <xd:complexType>
    <xd:sequence>
      <xd:choice>
        <xd:sequence>
          <xd:element ref="TITLE"/>
          <xd:element ref="SUMMARY"/>
          <xd:element ref="ARGUMENTSminOccurs="0"/>
          <xd:element ref="PREAMBLE.GEN"/>
          <xd:element ref="ENACTING.TERMS.CJT"/>
        </xd:sequence>
        <xd:element ref="GR.SEQ"/>
      </xd:choice>
      <xd:element ref="FINAL"/>
      <xd:element ref="INTERNAL.ANNEXminOccurs="0maxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

OPINION

General rules

Element

The content is composed of the following elements:

Example

<CONTENTS.OPINION>

  <TITLE>

    <TI>

      <P>Avis de la Cour</P>

      <P>émis le

        <DATE ISO="19611213">13 décembre 1961</DATE>

</P>

    </TI>

  </TITLE>

  <SUMMARY>

    <TITLE>

      <TI>

        <P>SOMMAIRE DE L'AVIS</P>

      </TI>

    </TITLE>

    <SUBJECTS>

      <NP>

        <NO.P>1.</NO.P>

        <TXT>

          <KEYWORD>Révision du traité C.E.C.A. au sens de l'article 95, alinéa 3</KEYWORD>

          <KEYWORD>Modification des pouvoirs de la Haute Autorité conférés à celle-ci par l'article 65, § 2</KEYWORD>

          <KEYWORD>Limites</KEYWORD>

        </TXT>

      </NP>

    </SUBJECTS>

    <ABSTRACT>

      <NP>

        <NO.P>1.</NO.P>

        <TXT>En principe, l'article 95 ne fait pas obstacle à une adaptation des règles relatives à l'exercice du pouvoir que l'article 65 confère à la Haute Autorité par une modification du paragraphe 2 de cet article, visant à permettre à la Haute Autorité d'autoriser soit des accords d'une autre nature que ceux prévus par le texte actuel, mais poursuivant le même but, soit des accords de même nature que ceux prévus par le texte en vigueur, mais poursuivant un autre but, soit enfin des accords d'une autre nature et poursuivant d'autres buts.</TXT>

        <P>Il est cependant indispensable que le texte révisé, d'une part, précise la nature des accords susceptibles d'autorisation et, d'autre part, définisse clairement le but de ces accords, puisque autrement il s'agirait non pas de l'adaptation de l'exercice d'un pouvoir déjà conféré à la Haute Autorité dans le cadre limité des dérogations consenties par le paragraphe 2 de l'article 65, mais de l'attribution d'un pouvoir dont les limites ne seraient pas définies, donc d'un élargissement tellement vaste et incertain des compétences actuelles qu'il s'agirait d'une modification qualitative et non seulement quantitative de ces compétences, en d'autres termes d'un pouvoir nouveau.</P>

      </NP>

    </ABSTRACT>

  </SUMMARY>

  <PREAMBLE.GEN>

    <PREAMBLE.INIT>

      <P>LA COUR DE JUSTICE</P>

      <P>composée de</P>

      <P>M. A. M. Donner,

        <HT TYPE="ITALIC">président</HT>

</P>

      <P>MM. O. Riese et J. Rueff,

        <HT TYPE="ITALIC">présidents de chambre</HT>

</P>

      <P>MM. L. Delvaux, Ch. L. Hammes, R. Rossi et N. Catalane,

        <HT TYPE="ITALIC">juges</HT>

</P>

      <P>

        <HT TYPE="ITALIC">avocats généraux :</HT> MM. K. Roemer et M. Lagrange</P>

      <P>

        <HT TYPE="ITALIC">greffier :</HT> M. A. Van Houtte</P>

    </PREAMBLE.INIT>

    <GR.VISA>

      <VISA>vu la demande d'avis du 20 juillet 1961 formulée par la Haute Autorité et le Conseil spécial de ministres de la Communauté européenne du charbon et de l'acier au titre de l'article 95, alinéas 3 et 4, du traité instituant la C.E.C.A. ;</VISA>

      <VISA>les avocats généraux entendus;</VISA>

    </GR.VISA>

    <GR.CONSID>

      <CONSID>

        <P>considérant que l'article 95 du traité dispose que les modifications visées au troisième alinéa de cet article sont soumises à l'avis de la Cour, qui est appelée à connaître de la conformité des propositions aux dispositions dudit alinéa;</P>

      </CONSID>

    </GR.CONSID>

    <GR.VISA>

      <VISA>vu l'article 95, alinéas 3 et 4, du traité;</VISA>

      <VISA>vu l'article 108 du règlement de procédure de la Cour de justice des Communautés européennes;</VISA>

    </GR.VISA>

    <PREAMBLE.FINAL>

      <P>ÉMET L'AVIS SUIVANT :</P>

    </PREAMBLE.FINAL>

  </PREAMBLE.GEN>

  <ENACTING.TERMS.CJT>

    <P>Le projet de modification de l'article 65 du traité instituant la Communauté européenne du charbon et de l'acier, tel qu'il est soumis à la Cour par la Haute Autorité et le Conseil spécial de ministres par lettre du 20 juillet 1961, n'est pas conforme aux dispositions de l'article 95, alinéas 3 et 4, du traité, en ce que :</P>

  </ENACTING.TERMS.CJT>

  <FINAL>

    <P>Arrêté à Luxembourg le

      <DATE ISO="19611213">13 décembre 1961</DATE>.</P>

    <SIGNATURE>

      <SIGNATORY>

        <P>DONNER</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>RIESE</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>RUEFF</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>DELVAUX</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>HAMMES</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>ROSSI</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>CATALANO</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>Le greffier</P>

        <P>A. VAN HOUTTE</P>

      </SIGNATORY>

    </SIGNATURE>

  </FINAL>

  <INTERNAL.ANNEX>

    <TITLE>

      <TI>

        <P>ANNEXE I DE L'AVIS</P>

      </TI>

      <STI>

        <P>Questions relatives à la demande d'avis 1-61</P>

      </STI>

    </TITLE>

    <CONTENTS>

      <GR.SEQ LEVEL="1">

        <TITLE>

          <TI>

            <NP>

              <NO.P>A —</NO.P>

              <TXT>Questions quant au texte proposé</TXT>

            </NP>

          </TI>

        </TITLE>

        <NP>

          <NO.P>1.</NO.P>

          <TXT>La Haute Autorité et le Conseil peuvent-ils préciser la nature des accords « concernant l'adaptation aux nouvelles conditions d'écoulement » que les rédacteurs de la proposition ont eus en vue?</TXT>

        </NP>

      </GR.SEQ>

    </CONTENTS>

  </INTERNAL.ANNEX>

</CONTENTS.OPINION>

[Table of contents]

CONTENTS.ORDER

[element]

Content of an order

The element contains the provisions as well as the jurisdiction of an order.

Model

<xd:element name="CONTENTS.ORDER">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="GR.SEQmaxOccurs="unbounded"/>
      <xd:element ref="JURISDICTION"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

ORDER

General rules

Element

The content is composed of an unlimited number of chapters (GR.SEQ), which might be nested, and the JURISDICTION element.

Example

<CONTENTS.ORDER>

  <GR.SEQ LEVEL="1">

    <TITLE>

      <TI>

        <P>Ordonnance</P>

      </TI>

    </TITLE>

    <NP>

      <NO.P>1</NO.P>

      <TXT>Par son pourvoi, M. Zuazaga Meabe demande l’annulation de l’ordonnance du Tribunal de première instance des Communautés européennes du 28 avril 2003, Zuazaga Meabe/OHMI — BBVA(BLUE)(T-15/03, non publiée au Recueil, ci-après l’

        <QUOT.START ID="QS0001REF.END="QE0001CODE="00AB">        </QUOT.START>ordonnance attaquée        <QUOT.END ID="QE0001REF.START="QS0001CODE="00BB">        </QUOT.END>), par laquelle celui-ci a rejeté son recours tendant à l’annulation de la décision de la deuxième chambre de recours de l’Office de l’harmonisation dans le marché intérieur (marques, dessins et modèles)(ci-après l’        <QUOT.START ID="QS0002REF.END="QE0002CODE="00AB">        </QUOT.START>OHMI        <QUOT.END ID="QE0002REF.START="QS0002CODE="00BB">        </QUOT.END>) du         <DATE ISO="20021024">24 octobre 2002</DATE> (affaire R 918/2001-2) (ci-après la         <QUOT.START ID="QS0003REF.END="QE0003CODE="00AB">        </QUOT.START>décision litigieuse        <QUOT.END ID="QE0003REF.START="QS0003CODE="00BB">        </QUOT.END>), rejetant l’opposition de M. Zuazaga Meabe à l’enregistrement de la marque verbale BLUE demandé parBanco Bilbao Vizcaya Argentaria SA(ci-après         <QUOT.START ID="QS0004REF.END="QE0004CODE="00AB">        </QUOT.START>BBVA        <QUOT.END ID="QE0004REF.START="QS0004CODE="00BB">        </QUOT.END>).</TXT>

    </NP>

  </GR.SEQ>

  <JURISDICTION>

    <INTRO>Par ces motifs, la Cour (quatrième chambre) ordonne:</INTRO>

    <LIST TYPE="ARAB">

      <ITEM>

        <NP>

          <NO.P>1)</NO.P>

          <TXT>Le pourvoi est rejeté.</TXT>

        </NP>

      </ITEM>

      <ITEM>

        <NP>

          <NO.P>2)</NO.P>

          <TXT>M. Zuazaga Meabe supporte, outre ses propres dépens, ceux exposés par Banco Bilbao Vizcaya Argentaria SA.</TXT>

        </NP>

      </ITEM>

      <ITEM>

        <NP>

          <NO.P>3)</NO.P>

          <TXT>L’Office de l’harmonisation dans le marché intérieur (marques, dessins et modèles) (OHMI) supporte ses propres dépens.</TXT>

        </NP>

      </ITEM>

    </LIST>

  </JURISDICTION>

</CONTENTS.ORDER>

[Table of contents]

CONTENTS.RULING

[element]

Content of a ruling

The element contains the provisions of a ruling.

Model

<xd:element name="CONTENTS.RULING">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="TITLE"/>
      <xd:element ref="SUMMARY"/>
      <xd:element ref="ARGUMENTSminOccurs="0"/>
      <xd:element ref="PREAMBLE.GEN"/>
      <xd:element ref="ENACTING.TERMS.CJT"/>
      <xd:element ref="FINAL"/>
      <xd:element ref="INTERNAL.ANNEXminOccurs="0maxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

RULING

General rules

Element

The content is composed of the following elements:

Example

<CONTENTS.RULING>

  <TITLE>

    <TI>

      <P>Délibération arrêtée en vertu de l'article 103, alinéa 3, du traité CEEA</P>

    </TI>

    <STI>

      <P>«Projet de convention de l'Agence internationale de l'énergie atomique sur la protection des matières, installations et transports nucléaires»</P>

      <P>Délibération 1/78</P>

    </STI>

  </TITLE>

  <SUMMARY>

    <TITLE>

      <TI>

        <P>Sommaire</P>

      </TI>

    </TITLE>

    <SUBJECTS>

      <NP>

        <NO.P>1.</NO.P>

        <TXT>

          <KEYWORD>CEEA</KEYWORD>

          <KEYWORD>Projets d'accords ou de conventions des États membres</KEYWORD>

          <KEYWORD>Compatibilité avec le traité</KEYWORD>

          <KEYWORD>Appréciation par la Cour</KEYWORD>

          <KEYWORD>Étendue</KEYWORD>

          <KEYWORD>          </KEYWORD>

        </TXT>

        <P>(Traité CEEA, art. 103, alinéa 3)</P>

      </NP>

    </SUBJECTS>

    <ABSTRACT>

      <NP>

        <NO.P>1.</NO.P>

        <TXT>Il résulte de l'article 103, alinéa 3, du traité CEEA que l'appréciation de la Cour sur la compatibilité d'un projet d'accord ou de convention avec les règles du traité doit être portée sous l'angle de vue de toutes les dispositions pertinentes du traité, que celles-ci concernent des questions de fond, de compétence ou de procédure. </TXT>

      </NP>

    </ABSTRACT>

  </SUMMARY>

  <PREAMBLE.GEN>

    <P>La Cour de justice a été saisie, le 7 juin 1978, d'une requête, introduite par le gouvernement du royaume de Belgique, au titre de l'article 103 du traité instituant la Communauté européenne de l'énergie atomique (Euratom).</P>

    <P>Par sa requête, le gouvernement belge sollicite de la Cour une décision sur la question de savoir si, en l'absence de participation concomitante de la Communauté, le royaume de Belgique peut adhérer à la convention sur la protection physique des matières, installations et transports nucléaires, en voie d'élaboration sous l'égide de l'Agence internationale de l'énergie atomique (AIEA).</P>

    <PREAMBLE.FINAL>

      <P>Par ces motifs,</P>

      <P>LA COUR,</P>

      <P>statuant sur la requête du gouvernement du royaume de Belgique en vertu de l'article 103 du traité CEEA, a arrêté la délibération suivante:</P>

    </PREAMBLE.FINAL>

  </PREAMBLE.GEN>

  <ENACTING.TERMS.CJT>

    <NP>

      <NO.P>1)</NO.P>

      <TXT>La participation des États membres à une convention relative à la protection physique des matières, installations et transports nucléaires, telle que la convention en voie de négociation au sein de PAIEA, n'est compatible avec les dispositions du traité CEEA qu'à la condition que, pour les domaines de ses compétences propres, la Communauté en tant que telle soit partie à la convention au même titre que les États.</TXT>

    </NP>

    <NP>

      <NO.P>2)</NO.P>

      <TXT>L'exécution des engagements contractés en vertu de la convention sera assurée, pour la part de la Communauté, dans le cadre du système institutionnel établi par le traité CEEA, conformément à la répartition des compétences entre la Communauté et ses États membres.</TXT>

    </NP>

  </ENACTING.TERMS.CJT>

  <FINAL>

    <SIGNATURE>

      <PL.DATE>

        <P>Fait à Luxembourg le 14 novembre 1978.</P>

      </PL.DATE>

      <SIGNATORY>

        <P>Kutscher</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>Mertens de Wilmars</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>Mackenzie Stuart</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>Donner</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>Pescatore</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>Sørensen</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>O'Keeffe</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>Bosco</P>

      </SIGNATORY>

      <SIGNATORY>

        <P>Touffait</P>

      </SIGNATORY>

    </SIGNATURE>

  </FINAL>

</CONTENTS.RULING>

[Table of contents]

CONTENTS.SE

[element]

Content of a special edition volume

The CONTENTS.SE element is used to mark up the content of a special edition volume.

Model

<xd:element name="CONTENTS.SE">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="TITLE"/>
      <xd:element ref="GR.ANNOTATIONminOccurs="0"/>
      <xd:element ref="PAGE.TOTAL"/>
      <xd:element ref="PAGE.SUMMARY"/>
      <xd:element ref="PAGE.CONTENTS"/>
      <xd:element ref="ITEM.PUBmaxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

SE

General rules

Element

The CONTENTS.SE element contains:

[Table of contents]

CONTENTS.SUMMARY

[element]

Description of the body of the table of contents (Official Journal)

The element describes the body of the table of contents on the OJ cover page(s).

Model

<xd:element name="CONTENTS.SUMMARY">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="EDITION"/>
      <xd:element ref="TI.COLL"/>
      <xd:element ref="TI.INFO.NOminOccurs="0"/>
      <xd:element ref="TI.CONTENTS"/>
      <xd:element ref="TI.PAGE"/>
      <xd:element ref="GR.ANNOTATIONminOccurs="0"/>
      <xd:element ref="SECTION.SUMMARYmaxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

SUMMARY.PDF

General rules

Element

The element contains:

The content consists of at least one section, even if no title indicates this fact.

[Table of contents]

CONTENTS.SUMMARY.JUDGMENT

[element]

Content of a judgment's summary

The element contains the provisions of a summarised judgment.

Model

<xd:element name="CONTENTS.SUMMARY.JUDGMENT">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="TITLE"/>
      <xd:element ref="PminOccurs="0maxOccurs="unbounded"/>
      <xd:element ref="PARTIES"/>
      <xd:choice maxOccurs="unbounded">
        <xd:element ref="GR.SEQ"/>
        <xd:element ref="P"/>
      </xd:choice>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

SUMMARY.JUDGMENT

General rules

Element

The element contains:

Example

<CONTENTS.SUMMARY.JUDGMENT>

  <TITLE>

    <TI>

      <P>

        <HT TYPE="UC">Ordonnance de la Cour</HT> (quatrième chambre)</P>

      <P>

        <DATE ISO="19890126">26 janvier 1989</DATE>

        <NOTE NOTE.ID="E0001NUMBERING="STARTYPE="FOOTNOTE">

          <P>Langue de procédure: le français.</P>

        </NOTE>

      </P>

    </TI>

  </TITLE>

  <P>Dans l'affaire 259/88,</P>

  <PARTIES>

    <PLAINTIFS>

      <P>

        <HT TYPE="BOLD">Ursula Godfroy, née Wagner,</HT> fonctionnaire de la Cour de justice des Communautés européennes, domiciliée à Hagsfelder Weg 5, 7513 Blankenloch, République fédérale d'Allemagne, représentée par Me Edmond Lebrun, avocat au barreau de Bruxelles, ayant élu domicile à Luxembourg, en l'étude de Me Tony Biever, 83, boulevard G.-D.-Charlotte,</P>

      <P>partie requérante,</P>

    </PLAINTIFS>

    <AGAINST>contre</AGAINST>

    <DEFENDANTS>

      <P>

        <HT TYPE="BOLD">Cour de justice des Communautés européennes,</HT> représentée par M. Francis Hubeau, chef de division, en qualité d'agent, assisté de Me Denis Waelbroeck, avocat au barreau de Bruxelles, ayant élu domicile à Luxembourg dans le bureau du premier nommé au Palais de la Cour (n° 1081), Kirchberg,</P>

      <P>partie défenderesse,</P>

    </DEFENDANTS>

  </PARTIES>

  <P>ayant pour objet la réintégration de la partie requérante à l'issue du congé de convenance personnelle expirant le 15 septembre 1972,</P>

  <GR.SEQ LEVEL="1">

    <TITLE>

      <TI>

        <P>LA COUR (quatrième chambre),</P>

      </TI>

    </TITLE>

    <P>composée de MM. T. Koopmans, président de chambre, C. N. Kakouris et M. Dïez de Velasco, juges,</P>

    <P>l'avocat général entendu,</P>

    <P>ordonne:</P>

    <LIST TYPE="ARAB">

      <ITEM>

        <NP>

          <NO.P>1)</NO.P>

          <TXT>Le recours est rejeté comme irrecevable.</TXT>

        </NP>

      </ITEM>

      <ITEM>

        <NP>

          <NO.P>2)</NO.P>

          <TXT>Chacune des parties supportera ses propres dépens.</TXT>

        </NP>

      </ITEM>

    </LIST>

  </GR.SEQ>

</CONTENTS.SUMMARY.JUDGMENT>

[Table of contents]

CONTENTS.SUMMARY.SE

[element]

Description of the body of the table of contents (special edition)

The element describes the body of the table of contents on the special edition cover page(s).

Model

<xd:element name="CONTENTS.SUMMARY.SE">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="EDITION"/>
      <xd:element ref="TI.COLL"/>
      <xd:element ref="ITEM.SUMMARYmaxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

SUMMARY.PDF

General rules

Element

The element contains:

[Table of contents]

COPYRIGHT

[element]

Copyright

The element is used to mark up the copyright of general publications.

Model

<xd:element name="COPYRIGHTtype="t_btx.seq"/>

Used by

COPYRIGHT INFO.PUBLISHER

General rules

Element

It may only contain the elements defined in the complex type t_btx.seq.

[Table of contents]

CORPUS

[element]

Corpus of a table

The CORPUS element is used to mark up the cells containing the data in a table. The method to mark up a table is similar to the HTML method, in so far as the table has to be processed row by row.

Model

<xd:element name="CORPUS">
  <xd:complexType>
    <xd:choice maxOccurs="unbounded">
      <xd:element ref="ROW"/>
      <xd:element ref="BLK"/>
    </xd:choice>
  </xd:complexType>
</xd:element>

Used by

TBL

General rules

Element

The CORPUS element consists of any combination of rows (ROW) and a logical group of rows (BLK).

In complex table structures, the rows may be grouped together in a 'block' and introduced by a title. These groups are encoded with the BLK element. Each BLK element may itself contain other blocks, in order to reflect the hierarchy the author wishes to use.

The CORPUS element is mandatory and must always contain at least one row or one group of rows.

Example

Simple table which consists of two rows:

<TBL COLS="2NO.SEQ="0001">

  <CORPUS>

    <ROW TYPE="HEADER">

      <CELL COL="1TYPE="HEADER">Expert group</CELL>

      <CELL COL="2TYPE="HEADER">First name and surname of the expert</CELL>

    </ROW>

    <ROW>

      <CELL COL="1ROWSPAN="3">Information society</CELL>

      <CELL COL="2">John DANIEL</CELL>

    </ROW>

    <ROW>

      <CELL COL="2">Tarja CRONBERG</CELL>

    </ROW>

    <ROW>

      <CELL COL="2">Jacob VORTMAN</CELL>

    </ROW>

    <ROW>

      <CELL COL="1">Controlled thermonuclear fusion</CELL>

      <CELL COL="2">Heikki KALLI</CELL>

    </ROW>

    <ROW>

      <CELL COL="1">Improving the socioeconomic knowledge base</CELL>

      <CELL COL="2">Helga NOWOTNY</CELL>

    </ROW>

  </CORPUS>

</TBL>

This one consists of rows where some of them are grouped in a block:

<TBL COLS="2NO.SEQ="0001">

  <TITLE>

    <TI>

      <P>List of products covered by the specific supply arrangements under Title I for the smaller Aegean islands</P>

    </TI>

  </TITLE>

  <CORPUS>

    <ROW TYPE="HEADER">

      <CELL COL="1TYPE="HEADER">Description</CELL>

      <CELL COL="2TYPE="HEADER">CN code</CELL>

    </ROW>

    <ROW>

      <CELL COL="1">Wheat flour</CELL>

      <CELL COL="2">

        <FT TYPE="CN">1101</FT> and         <FT TYPE="CN">1102</FT>

</CELL>

    </ROW>

    <ROW>

      <CELL COL="1">Durum wheat</CELL>

      <CELL COL="2">10011000</CELL>

    </ROW>

    <ROW>

      <CELL COL="1">Wheat of bread-making quality</CELL>

      <CELL COL="2">10019099</CELL>

    </ROW>

    <BLK>

      <TI.BLK COL.START="1COL.END="1">Feedingstuffs</TI.BLK>

      <ROW>

        <CELL COL="1">— cereals</CELL>

      </ROW>

      <ROW>

        <CELL COL="1">— wheat</CELL>

        <CELL COL="2">1001</CELL>

      </ROW>

    </BLK>

  </CORPUS>

</TBL>

[Table of contents]

CORR

[element]

Root element for corrigenda

The CORR element is the root element for corrigenda. Corrigenda are published in the 'Corrigenda' section of the C and L collections of the OJ. In some cases, they may be published in other sections (Section III for example).

Model

<xd:element name="CORR">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.INSTANCE"/>
      <xd:choice maxOccurs="unbounded">
        <xd:element ref="GR.ANNOTATION"/>
        <xd:element ref="TITLE"/>
      </xd:choice>
      <xd:element ref="CONTENTS.CORR"/>
    </xd:sequence>
    <xd:attribute name="NNCtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

The element contains a mandatory BIB.INSTANCE sub-element and an optional GR.ANNOTATION sub-element.

The title of a corrigendum provides a reference to the OJ which published the original document. This reference is marked up inside the TITLE element.

A corrigendum contains a series of corrections to be made to the original document. These corrections are encoded with the CONTENTS.CORR element.

Attributes

The NNC attribute

In some special cases, the numbering of footnotes does not restart on every page, but continues from 1 to n. For those cases the attribute NNC [notes numbering continued] takes the value 'YES'. The default value of this attribute is 'NO'. So the attribute should not be used if the numbering of footnotes follows the general rules and restarts on a new page.

[Table of contents]

CORR.ACTION

[element]

Text correction

The element contains the correction that has to be executed in full text.

Model

<xd:element name="CORR.ACTIONtype="xd:string"/>

Used by

CORR.ACTION CORRIG.ECR

General rules

Element

The element must contain only text.

Example

<CORR.ACTION>au point 2, lire le texte comme suit:</CORR.ACTION>

[Table of contents]

CORRECTION

[element]

Grouping of corrections within corrigenda

A correction in a corrigendum generally consists of three parts:

Model

<xd:element name="CORRECTION">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="DESCRIPTION"/>
      <xd:sequence minOccurs="0maxOccurs="unbounded">
        <xd:element ref="OLD.CORRminOccurs="0"/>
        <xd:element ref="NEW.CORRminOccurs="0"/>
      </xd:sequence>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

CONTENTS.CORR GR.CORRECTION

General rules

Element

The description of the correction is marked up using the DESCRIPTION element.

If the document contains several corrections, each of them may be numbered or prefixed by a symbol. The number or the symbol is marked up inside the DESCRIPTION element.

[Table of contents]

CORRIG

[element]

Description of a corrigendum

The CORRIG element is used to mark up the description of a corrigendum.

Model

<xd:element name="CORRIG">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.DATA"/>
      <xd:element ref="GR.CORRIGminOccurs="0"/>
    </xd:sequence>
    <xd:attribute name="RELEVANTdefault="YES">
      <xd:simpleType>
        <xd:restriction base="xd:string">
          <xd:enumeration value="NO"/>
          <xd:enumeration value="YES"/>
        </xd:restriction>
      </xd:simpleType>
    </xd:attribute>
  </xd:complexType>
</xd:element>

Used by

GR.CORRIG

General rules

Element

It contains a mandatory BIB.DATA element for marking up the bibliographical data of the corrigendum and an optional group of corrigenda (GR.CORRIG).

Attributes

The RELEVANT attribute

The RELEVANT attribute is used to indicate whether the contents of the correction are relevant to the consolidation or not. The default value is 'YES'.

[Table of contents]

CORRIG.CL

[element]

Description of a corrigendum within consolidation

The CORRIG.CL element is used to mark up the description of a corrigendum within consolidation.

Model

<xd:element name="CORRIG.CL">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.DATA.CL"/>
      <xd:element ref="GR.CORRIG.CLminOccurs="0"/>
    </xd:sequence>
    <xd:attribute name="RELEVANTdefault="YES">
      <xd:simpleType>
        <xd:restriction base="xd:string">
          <xd:enumeration value="NO"/>
          <xd:enumeration value="YES"/>
        </xd:restriction>
      </xd:simpleType>
    </xd:attribute>
  </xd:complexType>
</xd:element>

Used by

GR.CORRIG.CL

General rules

Element

This element contains a section with bibliographic information (BIB.DATA.CL) and optionally another group of corrigenda (GR.CORRIG.CL), which relates to the corrigendum itself.

Attributes

The RELEVANT attribute

This attribute allows to indicate if the corrigendum has an impact on the consolidation process or not. The values of the attribute may be 'YES' or 'NO'.

[Table of contents]

CORRIG.ECR

[element]

Description of a corrigendum

The CORRIG.ECR element is used to mark up the description of a corrigendum. It is composed of the following sub-elements:

Model

<xd:element name="CORRIG.ECR">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="REF.ORIGINALminOccurs="0"/>
      <xd:element ref="CORR.ACTIONminOccurs="0"/>
      <xd:choice minOccurs="1maxOccurs="1">
        <xd:element ref="GR.SEQ"/>
        <xd:element ref="NP"/>
        <xd:element ref="P"/>
      </xd:choice>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

GR.CORRIG.ECR

General rules

Element

The CORRIG.ECR element must contain only one of the GR.SEQ, NP and P elements. The REF.ORIGINAL and CORR.ACTION elements may be integrated in full text. In this case they are optional and the content has to be marked-up with the GR.SEQ element.

Example

<CORRIG.ECR>

  <REF.ORIGINAL PAGE="I-4939NO.CASE="C-155/98 P">Page I-4939, affaire C-155/98 P:</REF.ORIGINAL>

  <CORR.ACTION>au point 7, lire le texte comme suit:</CORR.ACTION>

  <P>

    <QUOT.START ID="QS0001REF.END="QE0001CODE="00AB">    </QUOT.START>À cet égard, le demandeur en intervention expose qu'il a été nommé fonctionnaire stagiaire de la Commission le 1er décembre 1994. Considérant qu'il possédait des qualifications exceptionnelles susceptibles de justifier son classement au grade LA 6, il a contesté et introduit, devant le Tribunal de première instance, un recours en annulation contre la décision du 12 mars 1996 de l'autorité investie du pouvoir de nomination le classant définitivement au grade LA 7, échelon 3. Ce recours est inscrit sous le numéro de rôle T-289/97.    <QUOT.END ID="QE0001REF.START="QS0001CODE="00BB">    </QUOT.END>

</P>

</CORRIG.ECR>

[Table of contents]

CORRIGENDUM.ECR

[element]

Description of a corrigendum published in the European Court Reports

The CORRIGENDUM.ECR element is used to mark up a corrigendum published in the European Court Reports.

Model

<xd:element name="CORRIGENDUM.ECR">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="BIB.CORRIG.ECR"/>
      <xd:element ref="CURR.TITLEminOccurs="0"/>
      <xd:element ref="TITLE"/>
      <xd:choice minOccurs="0maxOccurs="unbounded">
        <xd:element ref="GR.ANNOTATION"/>
        <xd:element ref="TOC"/>
      </xd:choice>
      <xd:element ref="GR.CORRIG.ECRmaxOccurs="unbounded"/>
    </xd:sequence>
    <xd:attribute name="NNCtype="t_booleandefault="NO"/>
  </xd:complexType>
</xd:element>

Used by

General rules

Element

It contains the following sub-elements:

All elements are mandatory except for the CURR.TITLE element which is optional.

Attributes

The NNC attribute

The NNC attribute signals if the numbering of notes is continued from preceding documents. The default value is 'NO'.

Example

<CORRIGENDUM.ECR>

  <BIB.CORRIG.ECR>

    <REF.CASE FILE="ECR1998FR.01r005701.case.xml">    </REF.CASE>

    <NO.SEQ>0001.0001</NO.SEQ>

    <PAGE.FIRST>LVII</PAGE.FIRST>

    <PAGE.SEQ>1</PAGE.SEQ>

    <PAGE.LAST>LVII</PAGE.LAST>

    <PAGE.TOTAL>1</PAGE.TOTAL>

  </BIB.CORRIG.ECR>

  <TITLE>

    <TI>

      <P>Corrigendum</P>

    </TI>

  </TITLE>

  <GR.CORRIG.ECR>

    <TITLE>

      <TI>

        <P>(Volume 1998) </P>

      </TI>

    </TITLE>

    <CORRIG.ECR>

      <REF.ORIGINAL PAGE="I-4939NO.CASE="C-155/98 P">Page I-4939, affaire C-155/98 P:</REF.ORIGINAL>

      <CORR.ACTION>au point 7, lire le texte comme suit:</CORR.ACTION>

      <P>

        <QUOT.START ID="QS0001REF.END="QE0001CODE="00AB">        </QUOT.START>À cet égard, le demandeur en intervention expose qu'il a été nommé fonctionnaire stagiaire de la Commission le 1er décembre 1994. Considérant qu'il possédait des qualifications exceptionnelles susceptibles de justifier son classement au grade LA 6, il a contesté et introduit, devant le Tribunal de première instance, un recours en annulation contre la décision du 12 mars 1996 de l'autorité investie du pouvoir de nomination le classant définitivement au grade LA 7, échelon 3. Ce recours est inscrit sous le numéro de rôle T-289/97.        <QUOT.END ID="QE0001REF.START="QS0001CODE="00BB">        </QUOT.END>

</P>

    </CORRIG.ECR>

    <CORRIG.ECR>

      <REF.ORIGINAL PAGE="I-4943NO.CASE="C-155/98 P">Page I-4943, affaire C-155/98 P:</REF.ORIGINAL>

      <CORR.ACTION>au point 2, lire le texte comme suit:</CORR.ACTION>

      <P>

        <QUOT.START ID="QS0002REF.END="QE0002CODE="00AB">        </QUOT.START>Procédure — Intervention — Personnes intéressées — Litige ayant un objet comparable à un autre litige pendant devant le Tribunal — Nonadmission à intervenir — Violation des droits de la défense — Absence        <QUOT.END ID="QE0002REF.START="QS0002CODE="00BB">        </QUOT.END>

</P>

    </CORRIG.ECR>

    <CORRIG.ECR>

      <REF.ORIGINAL PAGE="I-4947NO.CASE="C-155/98 P">Page I-4947, affaire C-155/98 P:</REF.ORIGINAL>

      <CORR.ACTION>au point 7, lire le texte comme suit:</CORR.ACTION>

      <P>

        <QUOT.START ID="QS0003REF.END="QE0003CODE="00AB">        </QUOT.START>À cet égard, le demandeur en intervention expose qu'il a été nommé fonctionnaire stagiaire de la Commission le 1er mars 1996. Considérant qu'il possédait des qualifications exceptionnelles susceptibles de justifier son classement au grade A 6, il a contesté et introduit, devant le Tribunal de première instance, un recours en annulation contre la décision du 12 mars 1997 de l'autorité investie du p^uv-orrue nomination le classant définitivement au grade A 7. Ce recours est inscrit sous le numéro de rôle T-147/96.        <QUOT.END ID="QE0003REF.START="QS0003CODE="00BB">        </QUOT.END>

</P>

    </CORRIG.ECR>

  </GR.CORRIG.ECR>

</CORRIGENDUM.ECR>

[Table of contents]

CRIT

[element]

Admission criteria for varieties of vegetable or agricultural plant species per Member State

The CRIT element is used to mark up the admission criteria per country for each variety of vegetable or agricultural plant species.

Model

<xd:element name="CRIT">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="QUALIFminOccurs="0"/>
      <xd:element ref="ID.RESPminOccurs="0"/>
    </xd:sequence>
    <xd:attribute name="AREAtype="t_areause="required"/>
    <xd:attribute name="COUNTRYuse="required">
      <xd:simpleType>
        <xd:restriction base="xd:string">
          <xd:enumeration value="AT"/>
          <xd:enumeration value="BE"/>
          <xd:enumeration value="BG"/>
          <xd:enumeration value="CH"/>
          <xd:enumeration value="CY"/>
          <xd:enumeration value="CZ"/>
          <xd:enumeration value="DE"/>
          <xd:enumeration value="DK"/>
          <xd:enumeration value="EE"/>
          <xd:enumeration value="EL"/>
          <xd:enumeration value="ES"/>
          <xd:enumeration value="FI"/>
          <xd:enumeration value="FR"/>
          <xd:enumeration value="HR"/>
          <xd:enumeration value="HU"/>
          <xd:enumeration value="IE"/>
          <xd:enumeration value="IS"/>
          <xd:enumeration value="IT"/>
          <xd:enumeration value="LI"/>
          <xd:enumeration value="LT"/>
          <xd:enumeration value="LU"/>
          <xd:enumeration value="LV"/>
          <xd:enumeration value="MT"/>
          <xd:enumeration value="NL"/>
          <xd:enumeration value="NO"/>
          <xd:enumeration value="PL"/>
          <xd:enumeration value="PT"/>
          <xd:enumeration value="RO"/>
          <xd:enumeration value="SE"/>
          <xd:enumeration value="SI"/>
          <xd:enumeration value="SK"/>
          <xd:enumeration value="UK"/>
        </xd:restriction>
      </xd:simpleType>
    </xd:attribute>
  </xd:complexType>
</xd:element>

Used by

UNIT.VI

General rules

Element

The element contains the following information:

Attributes

The AREA attribute

The AREA attribute is mandatory and is used to indicate the regional area of the concerned country. The allowed values, defined in the t_area simple type, are:

Attributes

The COUNTRY attribute

The COUNTRY attribute is mandatory and is used to indicate the member state or the EFTA country which has officially admitted the variety. The allowed values are constrained by the model. The values are based on ISO 3166 (two-byte version).

[Table of contents]

CURR.TITLE

[element]

Current title in ECR documents

The element CURR.TITLE specifies the current title which will be put at the top of all pages. It may only be used for documents published in the context of European Court Reports.

Model

<xd:element name="CURR.TITLE">
  <xd:complexType>
    <xd:choice>
      <xd:sequence>
        <xd:element ref="LEFT"/>
        <xd:element ref="RIGHT"/>
      </xd:sequence>
      <xd:element ref="PAGE.HEADER"/>
    </xd:choice>
  </xd:complexType>
</xd:element>

Used by

ANNEX CASE CONCLUSION CORRIGENDUM.ECR DECISION.ECR GENERAL JUDGMENT OPINION ORDER REPORT.HEARING RULING SUMMARY.JUDGMENT

General rules

Element

It is composed of these two mandatory sub-elements:

Example

<CURR.TITLE>

  <LEFT>CONCLUSIONS DE L'AVOCAT GÉNÉRAL</LEFT>

  <RIGHT>AFFAIRE C-123/02</RIGHT>

</CURR.TITLE>

[Table of contents]

DATE

[element]

Date

The DATE element is used to mark up full dates (day, month and year), as well as range dates (start date and end date).

Model

<xd:element name="DATE">
  <xd:complexType mixed="true">
    <xd:complexContent mixed="true">
      <xd:extension base="t_btx.seq">
        <xd:attribute name="ISOtype="t_dateuse="required"/>
      </xd:extension>
    </xd:complexContent>
  </xd:complexType>
</xd:element>

Used by

t_btx t_btx.ecr t_btx.seq BIB.CASE BIB.DATA BIB.INSTANCE BIB.INSTANCE.CONS BIB.OJ BIB.SE DOC.CORR DOC.MAIN.PUB DOC.SUB.PUB HEADER.SUMMARY HEADER.SUMMARY.SE KEYWORD LAST.MODIFICATION OJ.CL OTH.PUB OTH.PUB.CL PUBLICATION.REF REF.DOC.ECR SPEC.ED

General rules

Element

The DATE element contains only the date comprising the day, the month and the year. A date can be expressed in full-text.

The connecting words and any spaces surrounding the date are not part of the DATE element.

In no case the DATE element may be empty. If no value is available on text level, it has to be filled by the value of the ISO attribute.

All dates in a document which fulfill the abovementioned conditions have to be marked up. The only exception from this rule is a date within a REF.DOC.OJ element.

Attributes

The ISO attribute

The ISO attribute is mandatory and its value has to be constructed according to the t_date format, namely the YYYYMMDD format, where:

The ISO attribute indicates the full date, even if the date is not explicitly complete in the document. If the full date cannot be deduced from the context, the use of the DATE element is forbidden (see the last example below).

Example

The date below is fully expressed :

<P>Saturday,

  <DATE ISO="20020226">january 26th, 2002</DATE>.</P>

In the two following examples, the start dates and the end dates may be marked up using DATE tags:

<P>and from

  <DATE ISO="20020203">3</DATE> to   <DATE ISO="20020210">february 10th, 2002</DATE>.</P>

<P>and from

  <DATE ISO="20020211">february 11th</DATE> to   <DATE ISO="20020303">march 3rd, 2002</DATE>.</P>

On the other hand, the range date expressed here cannot be deduced from the context, the DATE element could then not be used:

<P>From June until within September...</P>

[Table of contents]

DATE.ADOPT

[element]

The adoption date

The element contains the date of adoption.

Model

<xd:element name="DATE.ADOPTtype="t_date"/>

Used by

BIB.DATA.CL DATE.ADOPT

General rules

Element

The date format is defined in the t_date simple type.

[Table of contents]

DECISION

[element]

Court of Justice decision

The DECISION element is used to mark up a Court of Justice decision.

Model

<xd:element name="DECISION">
  <xd:complexType>
    <xd:sequence>
      <xd:element ref="TITLE"/>
      <xd:element ref="PmaxOccurs="unbounded"/>
    </xd:sequence>
  </xd:complexType>
</xd:element>

Used by

CASE

General rules

Element

The element contains the title of a decision (TITLE) and an unlimited number of paragraphs (P).

[Table of contents]