Formex version 4

Release 6.02 (06 February 2023)

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_chapter
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
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.ELI
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.DOC.SE
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

btx

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

Model

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.

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

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.

Formula

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

Model

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.

Sequence

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

Model

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.

Structure

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

Model

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.

Title

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

Model

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.

Physical reference to another file

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

Model

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.

• DOC.PDF, if the object is a PDF document
• DOC.XML, if the object is a document instance
• FRAGMENT.XML, if the object is a valid XML document part,
• IMAGE, if the object is an image.

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".

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

General rules

Type

The t_area element is defined as a string.

Its value must be one of the following:

• EU - European Union
• EFTA - European Free Trade Association

yes/no boolean value

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

Model

General rules

Type

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

• NO
• YES

Hexadecimal encoding of characters

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

Model

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.

Collection of the OJ

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

Model

General rules

Type

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

• A: an ECSC decision published between 30/12/1952 and 19/04/1958,
• C: the OJ Information and Notices collection,
• L: the OJ Legislation collection,
• P: an OJ of the 'P' series, published from 20/04/1958 until 31/12/1967.
• S: the OJ Supplement collection (call for tenders),
• X: other collection.

Date format

This type defines the ISO 8601 date format.

Model

General rules

Type

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

DOI format for documents

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

Model

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:

• series of the Official Journal,
• sub-series of the Official Journal,
• year of the publication in four digits followed by a dot,
• current number of the OJ issue in three digits followed by a dot,
• the volume number in two digits,
• the number of the start page as defined by the corresponding type (always four positions),
• the sequence of the document on the page expressed in two digits followed by a dot,
• the language of the document according to ISO 639-3 (three letter code).

Example:

doi:10.3001/L_2013.002.01000301.deu

DOI format for general publications

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

Model

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.

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

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:

• the ISSN value (eight positions) followed by a dot,
• series of the Official Journal,
• sub-series of the Official Journal,
• year of the publication in four digits followed by a dot,
• current number of the OJ issue in three digits followed by a dot,
• the language of the document according to ISO 639-3 (three letter code).

Example:

doi:10.3000/19770642.L_2013.002.deu

Name for the case instances

This type defines the composition of an ECR case filename.

Model

General rules

Type

The name is composed as follows:

• ECR: unvarying prefix which stands for 'European Court Reports';
• the year of the publication in four digits;
• the language of the publication in two capital letters;
• the part of the ECR: the value 1 stands for the Court of Justice, 2 for the Court of First Instance, 3 for the Civil Service Tribunal
• a dot;
• two digits for the number of the volume;
• five digits for the first page of the case in the publication; the first digit of this series may be the letter 'a' to indicate that the page number is completed by an asterisk, 's' to indicate coverpages or the letter 'r' to indicate pagination in Roman figures;
• two digits for the sequence on the page;
• a dot;
• the word 'case' in small letters;
• a dot;
• the type suffix 'xml'.

Example:

ECRCJ2005FRA2.010000101.case.xml

Name for the document instances within a case

This type defines the composition of an ECR document filename.

Model

General rules

Type

The name is composed as follows:

• ECR: unvarying prefix which stands for 'European Court Reports';
• the year of the publication in four digits;
• the language of the publication in two capital letters;
• the part of the ECR: the value 1 stands for the Court of Justice, 2 for the Court of First Instance, 3 for the Civil Service Tribunal
• a dot;
• two digits for the number of the volume;
• five digits for the first page of the case in the publication; the first digit of this series may be the letter 'a' to indicate that the page number is completed by an asterisk, 'p' for the list of appeals, 's' to indicate coverpages or the letter 'r' to indicate pagination in Roman figures;
• two digits for the sequence on the page;
• a dot;
• the type suffix 'xml'.

Example:

ECRCJ2005FRA1.010000101.xml

Name for an ECR publication

This type defines the composition of an ECR publication filename.

Model

General rules

Type

The name is composed as follows:

• ECR: unvarying prefix which stands for 'European Court Reports';
• the year of the publication in four digits;
• the language of the publication in two capital letters;
• the part of the ECR: the value 1 stands for the Court of Justice, 2 for the Court of First Instance, 3 for the Civil Service Tribunal
• a dot;
• two digits for the number of the volume;
• a dot;
• the type suffix 'xml'.

Example:

ECRCJ2005FRA.01.xml

Identifier in the financial process

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

Model

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.

ISSN format

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

Model

General rules

Type

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

• N is a digit between 0 and 9,
• X may be a digit or the letter 'X'.

In the electronic document the dash symbol must be omitted.

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

General rules

Type

The t_language element is defined as a string.

Its value must be one of the following:

• BG - Bulgarian
• CA - Catalan
• CS - Czech
• DA - Danish
• DE - German
• EL - Greek
• EN - English
• ES - Spanish
• ET - Estonian
• EU - Basque
• FI - Finish
• FR - French
• GA - Irish
• GL - Galician
• HR - Croatian
• HU - Hungarian
• IS - Icelandic
• IT - Italian
• LT - Lettish
• LV - Latvian
• MT - Maltese
• NL - Dutch
• NO - Norwegian
• PL - Polish
• PT - Portuguese
• RO - Romanian
• SK - Slovak
• SL - Slovenian
• SV - Swedish
• TR - Turkish
• XM - multilingual
• XX - other

Identifier of a legislation summary

This simple type constructs the identifier of a legislation summar.

Model

General rules

Type

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

• a prefix with the fixed value 'LSEU',
• the resource type (INTRO, GLOSSARY) if different from SUMMARY,
• the identifier of the domain, either alfanumeric or numeric,
• the work id,
• four digits representing the year of the production,
• two digits representing the month of the production,
• two digits for the day of the production,
• four digits as a sequential number of production at a given date.

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

OJ number

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

Model

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.

Pagination

This type defines the page numbering scheme.

Model

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:

• c: ConsLeg cover pages,
• e: included forms etc.,
• p: for the table of appeals (from French "pourvoi"),
• s: pages of the OJ cover.

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

Pagination for ECR documents

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

Model

General rules

Type

The pagination is composed as follows:

• the part of the ECR publication in Roman digits followed by a hyphen; this part is optional;
• an optional reference to the parts A or B followed by a hyphen;
• optionally the number of the fascicle followed by a hyphen;
• the real page number in Arabic digits on six positions.

The two first parts are absent before 1990.

Sequence number of a document on the page

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

Model

General rules

Type

The sequence number is expressed by one or two digits.

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

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.

Hexadecimal encoding of symbols for ending quotation marks

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

Model

General rules

Type

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

Hexadecimal encoding of symbols for opening quotation marks

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

Model

General rules

Type

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

Type of a section

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

Model

General rules

Type

The t_sectiontype element is defined as a string.

The following values are allowed :

• 'C0', for documents which are published outside of any section such as Treaties etc.,
• 'C1', for the section I of the OJ C (Resolutions, recommendations, orientations and opinions),
• 'C2', for the section II of the OJ C (Communications),
• 'C3', for the section III of the OJ C (Preparatory Acts),
• 'C4', for the section IV of the OJ C (Information),
• 'C5', for the section V of the OJ C (Notes),
• 'CC', for the corrigenda section of the OJ C,
• 'CI', for the notes to readers published in the OJ C,
• 'CX', for any other section in the OJ C.
• 'L0', for documents which are published outside of any section such as Treaties etc.,
• 'L1', for the section I of the OJ L (Acts adopted in application of the EC/EURATOM Treaties whose publication is obligatory),
• 'L2', for the section II of the OJ L (Acts adopted in application of the EC/EURATOM Treaties whose publication is obligatory),
• 'L3', for the section III of the OJ L (Acts adopted in application of the EU Treaty),
• 'L4', for the section IV of the OJ L (Other acts),
• 'L5', for the section V of the OJ L (this section might be temporary),
• 'LC', for the corrigenda section of the OJ L,
• 'LI', for the notes to readers published in the OJ L,
• 'LX', for any other section in the OJ L.

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

Encoding of the volume of a publication

The simple type defines the way how to identify a volume for an OJ or a Special Edition publication. The value may consist of one or two digits. For the DA and EN versions, the use of ROMAN numerals is allowed in a Special Edition publication.

Model

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; concerning the DA and EN versions, the use of ROMAN numerals is allowed in a Special Edition publication.

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

Used by

ABSTRACT SUMMARY

General rules

Element

The use of the element is optional within the SUMMARY 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:

• Adopted texts are published in the OJ L collection and in Section I of the OJ C collection. It concerns documents such as:

  • decisions,
  • ECSC decisions,
  • directives,
  • ECSC recommendations,
  • regulations,
  • common positions,
  • joint actions,
  • financial regulations,
  • rules of procedure,
  • recommendations,
  • etc.

• Documents relating to preparatory acts are generally published in Section III of the OJ C collection.

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

Used by

General rules

Element

Generally speaking, the structure of an act comprises:

• a title block,
• a preamble,
• the enacting terms,
• and the final part

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.

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

Used by

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

General rules

Element

It contains the following sub-elements:

• the preamble, marked up using one PREAMBLE.GEN element or several P elements depending on its structure,
• an optional table of contents (TOC),
• the enacting terms (ENACTING.TERMS),
• and the optional final part (FINAL).

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

Used by

ADDITIONAL.DOCS.LSEU CONTENTS.LSEU

General rules

Element

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

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

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:

• when an address is given in the form of continuous text within a text block (first example below);

• when an address appears on one single line, and so without clear distinction between its different parts (second example).

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

Example

Stand-alone address

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

Model

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

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

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

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

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

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

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.

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

Used by

General rules

Element

The AGR element is subdivided into the following elements:

• the bibliographical references (BIB.INSTANCE),
• a choice of different elements which might appear in various orders, only the TITLE element is mandatory: an optional table of contents (TOC), the title of the document (TITLE), and an optional group of annotations (GR.ANNOTATION).

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

• an optional preamble (PREAMBLE),
• the enacting terms (ENACTING.TERMS),
• an optional final part (FINAL),

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.

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

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

Amendment

The AMEND element is used to mark up an amendment.

Model

Used by

GR.AMEND

General rules

Element

An amendment may consist of the following elements:

• a title (TITLE),
• an OLD element, which covers the text presented in the left-hand column.
• a NEW element, which covers the text presented in the right-hand column.

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:

• the most accurate element should be taken into account;
• the horizontal structure and the concordance between the position of the paragraphs in the left-hand part and the position of the paragraphs in the right-hand part of the page should be retained as far as possible;
• the logic and the markup within the AMEND element should be retained as far as possible.

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 :

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

Used by

General rules

Element

An annex contains:

• the bibliographical references (BIB.INSTANCE),
• a choice of different elements which might appear in various orders, only the TITLE element is mandatory: an optional table of contents (TOC), the title of the document (TITLE), and an optional group of annotations (GR.ANNOTATION),
• an optional CURR.TITLE element for running titles in the context of European Court Reports,
• the CONTENTS element forming the body of the annex.

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.

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:

• note,
• N.B.,
• remark,
• etc.

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

Model

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

Anonymisation of personal names

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

Model

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:

• BG: Информацията е заличена или заменена в съответствие с правната рамка относно личните данни и/или поверителността.

• CS: Údaje vymazané nebo nahrazené v rámci zajištění ochrany osobních dat a/nebo důvěrné povahy.

• DA: Information er fjernet eller erstattet inden for rammerne af beskyttelse af personoplysninger og/eller fortrolighed.

• DE: Information im Rahmen des Schutzes personenbezogener bzw. vertraulicher Daten entfernt oder ersetzt.

• EL: Πληροφορίες που διεγράφησαν ή αντικαταστάθηκαν στο πλαίσιο της προστασίας των δεδομένων προσωπικού χαρακτήρα και/ή εμπιστευτικότητας.

• EN: Information erased or replaced within the framework of protection of personal data and/or confidentiality.

• ES: Datos suprimidos o sustituidos en el marco de la protección de datos personales y/o confidenciales.

• ET: Teave on kustutatud või asendatud seoses isikuandmete kaitse ja/või konfidentsiaalsusega.

• FI: Henkilötietojen ja/tai tietosuojan suojaamisen puitteissa poistettu tai korvattu tieto.

• FR: Information effacée ou remplacée dans le cadre de la protection des données à caractère personnel et/ou de leur caractère confidentiel.

• GA: Tá an fhaisnéis scriosta nó ionadaithe laistigh den chreat maidir le sonraí pearsanta agus/nó rúndacht a chosaint.

• HR: Informacije su izbrisane ili zamijenjene u okviru zaštite osobnih podataka i/ili povjerljivosti.

• HU: Törölt vagy áthelyezett információ a személyes és/vagy bizalmas jellegű adatok védelme érdekében.

• IT: Dati cancellati o sostituiti nell'ambito della tutela dei dati personali e/o della riservatezza.

• LT: Informacija ištrinta arba pakeista pagal asmens duomenų apsaugos ir (arba) konfidencialumo reikalavimus.

• LV: Informācija dzēsta vai aizstāta, ņemot vērā personas datu aizsardzību un/vai konfidencialitāti.

• MT: Informazzjoni mħassra jew mibdula fil-qafas ta’ protezzjoni ta’ data personali u/jew kunfidenzjalità.

• NL: Informatie gewist of vervangen in het kader van de bescherming van persoonsgegevens en/of vertrouwelijkheid.

• PL: Informacje usunięto lub zastąpiono w ramach ochrony danych osobowych i/lub poufności.

• PT: Informações apagadas ou substituídas no âmbito da proteção de dados pessoais e/ou da confidencialidade.

• RO: Informații șterse sau înlocuite în contextul cadrului legal de protecție a datelor cu caracter personal și/sau a confidențialității.

• SK: Údaje odstránené alebo vymazané v rámci zaistenia ochrany osobných dát a/alebo dôvernosti.

• SL: Informacija je bila izbrisana ali nadomeščena v okviru varstva osebnih in/ali zaupnih podatkov.

• SV: Uppgifterna raderade eller ersatta för att skydda personuppgifter och/eller av sekretesskäl.

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 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-space ( ).

Example

List of appeals

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

Model

Used by

General rules

Element

The element contains the following mandatory sub-elements:

• BIB.APPEAL.TABLE: bibliographic information for the instance,
• TITLE: the title of the list,
• CONTENTS: the contents of the list.

Additional party in a case

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

Model

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).

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

Used by

APPLICANT INTRO.OPINION

General rules

Element

The use of the element is mandatory within the INTRO.OPINION 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

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.

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

Used by

ARGUMENTS CONTENTS.OPINION CONTENTS.RULING

General rules

Element

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

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:

• ALINEA: one or more legal alineas (non-numbered physical paragraphs)
• PARAG: one or more legal paragraphs (numbered physical paragraphs)
• SUBDIV: one or more legal subdivisions (a long article may be subdivided into sections)

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

Model

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.

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.

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

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).

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

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).

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

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:

• ACPCE: ACP - EC Council of Ministers
• ACPEU: ACP-EU Joint Assembly
• AEE: European Environment Agency
• AEEM: European Agency for the Evaluation of Medicinal Products
• BCE: European Central Bank
• BEI: European Investment Bank
• CC: Court of Auditors
• CCEEE: EEA Consultative Committee
• CDR: Committee of the Regions
• CEDEFOP: European Centre for the Development of Vocational Training
• CES: Economic and Social Committee
• CJ: Court of Justice of the European Communities
• CJAELE: EFTA Court
• CMEEE: Joint Committee EEA
• CNSL: European Council
• COLAELE: EFTA Surveillance Authority
• COM: European Commission
• COM-UN: United Nations Economic Commission for Europe
• CPAELE: Standing Committee of the EFTA States
• CPMEEE: Joint Parliamentary Committee
• CS: Council
• CSASS: Association Council
• CSEEE: EEA Council
• EASA: European Aviation Safety Agency
• EASHW: European Agency for Safety and Health at Work
• EDA: European Defence Agency
• EDPS: The European Data Protection Supervisor
• EPOL: Europol
• EPSO: European Personnel Selection Office
• ERA: European Railway Agency
• EUROJUST: Eurojust
• GALILEO: Galileo Supervisory Authority
• HRUFASP: High Representative of the Union for Foreign Affairs and Security Policy
• JC: Joint Committee
• MEDIAT: The European Ombudsman
• OEDT: European Monitoring Centre for Drugs and for Drug Addiction
• OEPRX: European Monitoring Centre for Racism and Xenophobia
• OHMI: Office for Harmonization in the Internal Market
• OP: Office for Official Publications of the European Communities
• OTHER: Others
• PE: European Parliament
• PSC: Political and Security Committee
• RG: Representatives of the Governments of the Member States
• T: Court of First Instance of the European Communities

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

Vertical bar

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

Model

Used by

t_btx.formula

General rules

Element

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

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:

• REF.ECR: reference to an ECR publication;
• PAGE.FIRST.ECR: indicates the first page of the component;
• PAGE.SEQ: specifies the sequence on the page;
• PAGE.LAST.ECR: indicates the last page of the component;
• PAGE.TOTAL: calculates the total number of pages,
• optionally a reference to the correponding core metadata instance (REF.CORE.METADATA,
• optionally a reference to an instance containing metadata other than core metadata (REF.BIB.RECORD.

Model

Used by

APPEAL.TABLE

General rules

Element

All elements are mandatory.

Example

Metadata for a case

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

• REF.ECR: refers to the publication of the volume in which the case was published;
• LG.DOC: specifies the language of the published document;
• LG.CASE: specifies the language in which the case was negotiated;
• DATE: shows the date when the case was closed;
• YEAR: mentions the year in which the case was opened;
• NO.CASE: signals the internal identifier of the case;
• TYPE.CASE: specifies the type of the case;
• NO.CELEX: specifies the identifier under which the case can be found in EUR-Lex, the European legal database system;
• NO.ECLI: the European Case Law Identifier (optional);
• NO.SEQ: contains the sequence number related to the position under which the case is published in a given volume;
• PAGE.FIRST.ECR: mentions the first page of the case in the publication;
• PAGE.SEQ: indicates the sequence of the dossier on the page;
• PAGE.LAST.ECR: mentions the last page of the case in the publication;
• PAGE.TOTAL: indicates the total number of pages taken by the case in the publication;
• AUTHOR: contains the author of the case,
• optionally a reference to the correponding core metadata instance (REF.CORE.METADATA,
• optionally a reference to an instance containing metadata other than core metadata (REF.BIB.RECORD.

Model

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

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:

• REF.ECR: reference to an ECR publication;
• PAGE.FIRST.ECR: indicates the first page of the component;
• PAGE.SEQ: specifies the sequence on the page;
• PAGE.LAST.ECR: indicates the last page of the component;
• PAGE.TOTAL: calculates the total number of pages.

Model

Used by

CHRON.TABLE

General rules

Element

All elements are mandatory.

Example

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:

• REF.ECR: reference to an ECR publication;
• PAGE.FIRST.ECR: indicates the first page of the component;
• PAGE.SEQ: specifies the sequence on the page;
• PAGE.LAST.ECR: indicates the last page of the component;
• PAGE.TOTAL: calculates the total number of pages.

Model

Used by

CHRON.TABLE.NP

General rules

Element

All elements are mandatory.

Example

Metadata for a conclusion

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

• REF.CASE.F1: creates a reference to the case which the conclusion belongs to in the context of part I ECR documents;
• REF.CASE: creates a reference to the case which the conclusion belongs to;
• NO.CELEX: specifies the identifier under which the conclusion can be found in EUR-Lex, the European legal database system;
• NO.CELEX: specifies the identifier under which the Court decision can be found in EUR-Lex, the European legal database system;
• NO.ECLI: the European Case Law Identifier (optional);
• NO.SEQ: contains the sequence number related to the position under which the conclusion is published in a given volume;
• PAGE.FIRST.ECR: mentions the first page of the conclusion in the publication;
• PAGE.SEQ: indicates the sequence of the conclusion on the page;
• PAGE.LAST.ECR: mentions the last page of the conclusion in the publication;
• PAGE.TOTAL: indicates the total number of pages taken by the conclusion in the publication;
• optionally a reference to the correponding core metadata instance (REF.CORE.METADATA;
• optionally a reference to an instance containing metadata other than core metadata (REF.BIB.RECORD.

Model

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

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:

• REF.CASE.F1: creates a reference to the case which the corrigendum belongs to in the context of part I ECR documents;
• REF.CASE: creates a reference to the case instance which describes the composition of the corrigendum;
• NO.SEQ: contains the sequence number related to the position under which the corrigendum is published in a given volume;
• PAGE.FIRST.ECR: mentions the first page of the corrigendum in the publication;
• PAGE.SEQ: indicates the sequence of the corrigendum on the page;
• PAGE.LAST.ECR: mentions the last page of the corrigendum in the publication;
• PAGE.TOTAL: indicates the total number of pages taken by the corrigendum in the publication;
• optionally a reference to the correponding core metadata instance (REF.CORE.METADATA;
• optionally a reference to an instance containing metadata other than core metadata (REF.BIB.RECORD.

Model

Used by

CORRIGENDUM.ECR

General rules

Element

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

Example

Bibliographical data

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

Model

Used by

CORRIG FAM.COMP MOD.ACT

General rules

Element

This element consists of the following:

• references to the publication to which the member of the consolidation family belongs. There are two types of publications:
  • the consolidated acts (BIB.INSTANCE.CONS),
  • other publications (OTH.PUB).
• the document's Celex reference number (NO.CELEX). For technical reasons the NO.CELEX element is declared as optional; its use, however, is compulsory.
• optionally the date of adoption of the act associated with the member of the consolidation family (DATE),
• the title of the document associated with the member (TITLE).

Example