Property term |
Cardinality |
Definition |
EAPO Decision | 1..1 | A conclusion or resolution reached after consideration by an authority
|
Date | 1..1 | Date of the decision |
Identifier | 0..1 | A unique way of identifying a decision. |
Identifier | 1..1 | The Formal Identifier class represents any identifier issued by any authority, whether a
government agency or not. It captures the identifier itself and details of the issuing authority, the
date on which the identifier was issued and so on. |
Identifier Type | 0..1 | . |
Date Of Issue | 0..1 | The date on which the identifier was issued. |
Issuing Authority | 0..1 | An issuing authority can be identified by its name as well as its URI. As this field takes a string
there is considerable room for error so publishers are urged to use a consistent form of the
name. |
Preservation | 0..1 | The decision for preservation of an account or a sum of money. |
To Be Preserved Sum | 0..* | . |
Amount | 0..1 | The total of payment awarded to the claimant, including the principal and, where applicable, interest, contractual penalties and costs;
|
Currency | 0..1 | A system of money in general use in a particular country
|
Issuing Court | 0..1 | The court that takes the decision. |
Authority | 0..1 | . |
Name | 0..1 | . |
Kind Of Authority | 0..1 | Codelist listing all kinds of authorities that can take decisions |
Address | 0..1 | . |
PO Box | 0..1 | . |
Postal Code | 0..1 | . |
Address Line | 0..* | additional unstructered address information or complete unstructured address
|
Line Number | 0..1 | . |
Description | 0..1 | . |
City | 0..1 | City |
Name | 0..1 | . |
Country | 0..1 | The country the address is in. |
Code | 1..1 | Code according to ISO 3166-1. |
Communication | 0..* | . |
Channel | 1..1 | Type of communication channel (e.g. telefone, mobile phone, e-mail, fax, e-codex infrastructure) defined by code-list "Communication Channel"
|
Complete Number | 0..1 | A text string of characters that make up the complete number for this communication.. |
Legal Remedy Decision | 1..1 | a conclusion or resolution reached after consideration by an authority
|
Date | 1..1 | Date of the decision |
Identifier | 0..1 | . |
Identifier | 1..1 | The Formal Identifier class represents any identifier issued by any authority, whether a
government agency or not. It captures the identifier itself and details of the issuing authority, the
date on which the identifier was issued and so on. |
Identifier Type | 0..1 | . |
Date Of Issue | 0..1 | The date on which the identifier was issued. |
Issuing Authority | 0..1 | An issuing authority can be identified by its name as well as its URI. As this field takes a string
there is considerable room for error so publishers are urged to use a consistent form of the
name. |
Issuing Court | 0..1 | The court that takes the decision. |
Authority | 0..1 | . |
Name | 0..1 | . |
Kind Of Authority | 0..1 | Codelist listing all kinds of authorities that can take decisions |
Address | 0..1 | . |
PO Box | 0..1 | . |
Postal Code | 0..1 | . |
Address Line | 0..* | additional unstructered address information or complete unstructured address
|
Line Number | 0..1 | . |
Description | 0..1 | . |
City | 0..1 | City |
Name | 0..1 | . |
Country | 0..1 | The country the address is in. |
Code | 1..1 | Code according to ISO 3166-1. |
Communication | 0..* | . |
Channel | 1..1 | Type of communication channel (e.g. telefone, mobile phone, e-mail, fax, e-codex infrastructure) defined by code-list "Communication Channel"
|
Complete Number | 0..1 | A text string of characters that make up the complete number for this communication.. |
Appeal Legal Remedy | 0..1 | A legal remedy that is lodged against the decision. |
Court | 0..1 | The court where the legal remedy is filed. |
Authority | 0..1 | . |
Name | 0..1 | . |
Kind Of Authority | 0..1 | Codelist listing all kinds of authorities that can take decisions |
Address | 0..1 | . |
PO Box | 0..1 | . |
Postal Code | 0..1 | . |
Address Line | 0..* | additional unstructered address information or complete unstructured address
|
Line Number | 0..1 | . |
Description | 0..1 | . |
City | 0..1 | City |
Name | 0..1 | . |
Country | 0..1 | The country the address is in. |
Code | 1..1 | Code according to ISO 3166-1. |
Communication | 0..* | . |
Channel | 1..1 | Type of communication channel (e.g. telefone, mobile phone, e-mail, fax, e-codex infrastructure) defined by code-list "Communication Channel"
|
Complete Number | 0..1 | A text string of characters that make up the complete number for this communication.. |
Applicant Party | 0..1 | A party that is in some way involved in the legal remedy. |
Language | 0..* | The language that can be used in communication with the party. |
Person | 0..1 | Natural person (individual)
|
Family Name | 1..1 | A family name is usually shared by members of a family. This attribute also carries prefixes or
suffixes which are part of the Family Name, e.g. “de Boer”, “van de Putte”, “von und zu Orlow”.
Multiple family names, such as are commonly found in Hispanic countries, are recorded in the
single Family Name field so that, for example, Miguel de Cervantes Saavedra's Family Name
would be recorded as "Cervantes Saavedra." |
Second Family Name | 0..1 | . |
Given Name | 0..1 | A given name, or multiple given names, are the denominator(s) that identify an individual within
a family. These are given to a person by his or her parents at birth or may be legally recognised
as 'given names' through a formal process. All given names are ordered in one field so that, for
example, the Given Name for Johan Sebastian Bach is 'Johan Sebastian.' |
Date Of Birth | 0..1 | A date that specifies the birth date of a person |
Document | 0..1 | . |
Type | 0..1 | . |
Received Date | 0..1 | . |
Name | 0..1 | Name of the document |
Incorrect Language Indicator | 0..1 | . |
Translation Needed Indicator | 0..1 | . |
Translate To Language | 0..1 | The language of the document. |
Reason Not Processed Description | 0..1 | The reason why the document could not be processed |
Identifier | 0..1 | . |
Identifier | 1..1 | The Formal Identifier class represents any identifier issued by any authority, whether a
government agency or not. It captures the identifier itself and details of the issuing authority, the
date on which the identifier was issued and so on. |
Identifier Type | 0..1 | . |
Date Of Issue | 0..1 | The date on which the identifier was issued. |
Issuing Authority | 0..1 | An issuing authority can be identified by its name as well as its URI. As this field takes a string
there is considerable room for error so publishers are urged to use a consistent form of the
name. |
Legal Entity | 0..1 | . |
Legal Name | 0..* | The legal name of the business. A business might have more than one legal name, particularly
in countries with more than one official language. In such cases, and where the encoding
technology allows, the language of the string should be identified. |
Legal Identifier | 0..1 | he legal status of a business is conferred on it by an authority within a given jurisdiction. The
Legal Identifier is therefore a fundamental relationship between a legal entity and the authority
with which it is registered. The details of the registration are provided as properties of the
Formal Identifier class. There is no restriction on the type of legal identifier. In many countries,
the business register's identifier is the relevant data point. The tax number often fulfils this
function in Spain.
The cardinality of this relationship is 1..1, i.e. a legal entity must have a legal identifier. |
Licence Held | 0..1 | . |
Identifier | 1..1 | The Formal Identifier class represents any identifier issued by any authority, whether a
government agency or not. It captures the identifier itself and details of the issuing authority, the
date on which the identifier was issued and so on. |
Identifier Type | 0..1 | . |
Date Of Issue | 0..1 | The date on which the identifier was issued. |
Issuing Authority | 0..1 | An issuing authority can be identified by its name as well as its URI. As this field takes a string
there is considerable room for error so publishers are urged to use a consistent form of the
name. |
Establishment | 0..1 | The establishment of the legal entity |
Date | 0..1 | The date the legal entity was established |
Place | 0..1 | The place where the legal entity was established |
Geographic Name | 0..1 | Again quoting from ISO 19112, a geographic name is a "spatial reference in the form of a label or
code that identifies a location. “Spain” is an example of a country name; “SW1P 3AD” is an example of a
postcode. Both are geographic names.
The country codes defined in ISO 3166 are further examples of geographic names. As noted in Section
4.1.10, the Publications Office of the European Union recommends the use of ISO 3166-1 codes
for countries in all cases except two:
use 'UK' in preference to the ISO 3166 code GB for the United Kingdom;
use 'EL' in preference to the ISO 3166 code GR for Greece.
The 'place' may be an abstract location such as a jurisdiction as opposed to a physical location.
The geographic name might be a recognised name, such as 'Paris,' which may or may not be
ambiguous in context, or it might be descriptive (such as 'Rhine km 203'). Although geographic
names are always useful, it is recommended that an additional method be used to identify a
location.
Places may have multiple geographic names in a single language or multiple languages. Where
a name is language-specific, that language should be identified along with the name (see
Section 4.9). There is no cardinality restriction on the number of geographic names that can be
used to describe a single location. |
Country | 0..1 | . |
Code | 1..1 | Code according to ISO 3166-1. |
Communication | 0..* | . |
Channel | 1..1 | Type of communication channel (e.g. telefone, mobile phone, e-mail, fax, e-codex infrastructure) defined by code-list "Communication Channel"
|
Complete Number | 0..1 | A text string of characters that make up the complete number for this communication.. |
Address | 0..* | . |
PO Box | 0..1 | . |
Postal Code | 0..1 | . |
Address Line | 0..* | additional unstructered address information or complete unstructured address
|
Line Number | 0..1 | . |
Description | 0..1 | . |
City | 0..1 | City |
Name | 0..1 | . |
Country | 0..1 | The country the address is in. |
Code | 1..1 | Code according to ISO 3166-1. |
Involvement | 0..1 | . |
Role | 0..* | Role of the party involved in a case or event.
|
Representative Party | 0..1 | A related party. |
Person | 0..1 | Natural person (individual)
|
Family Name | 1..1 | A family name is usually shared by members of a family. This attribute also carries prefixes or
suffixes which are part of the Family Name, e.g. “de Boer”, “van de Putte”, “von und zu Orlow”.
Multiple family names, such as are commonly found in Hispanic countries, are recorded in the
single Family Name field so that, for example, Miguel de Cervantes Saavedra's Family Name
would be recorded as "Cervantes Saavedra." |
Second Family Name | 0..1 | . |
Given Name | 0..1 | A given name, or multiple given names, are the denominator(s) that identify an individual within
a family. These are given to a person by his or her parents at birth or may be legally recognised
as 'given names' through a formal process. All given names are ordered in one field so that, for
example, the Given Name for Johan Sebastian Bach is 'Johan Sebastian.' |
Date Of Birth | 0..1 | A date that specifies the birth date of a person |
Document | 0..1 | . |
Type | 0..1 | . |
Received Date | 0..1 | . |
Name | 0..1 | Name of the document |
Incorrect Language Indicator | 0..1 | . |
Translation Needed Indicator | 0..1 | . |
Translate To Language | 0..1 | The language of the document. |
Reason Not Processed Description | 0..1 | The reason why the document could not be processed |
Identifier | 0..1 | . |
Identifier | 1..1 | The Formal Identifier class represents any identifier issued by any authority, whether a
government agency or not. It captures the identifier itself and details of the issuing authority, the
date on which the identifier was issued and so on. |
Identifier Type | 0..1 | . |
Date Of Issue | 0..1 | The date on which the identifier was issued. |
Issuing Authority | 0..1 | An issuing authority can be identified by its name as well as its URI. As this field takes a string
there is considerable room for error so publishers are urged to use a consistent form of the
name. |
Communication | 0..* | . |
Channel | 1..1 | Type of communication channel (e.g. telefone, mobile phone, e-mail, fax, e-codex infrastructure) defined by code-list "Communication Channel"
|
Complete Number | 0..1 | A text string of characters that make up the complete number for this communication.. |
Address | 0..1 | The address of the party. |
PO Box | 0..1 | . |
Postal Code | 0..1 | . |
Address Line | 0..* | additional unstructered address information or complete unstructured address
|
Line Number | 0..1 | . |
Description | 0..1 | . |
City | 0..1 | City |
Name | 0..1 | . |
Country | 0..1 | The country the address is in. |
Code | 1..1 | Code according to ISO 3166-1. |
Other Party | 0..1 | A party that is in some way involved in the legal remedy. |
Language | 0..* | The language that can be used in communication with the party. |
Person | 0..1 | Natural person (individual)
|
Family Name | 1..1 | A family name is usually shared by members of a family. This attribute also carries prefixes or
suffixes which are part of the Family Name, e.g. “de Boer”, “van de Putte”, “von und zu Orlow”.
Multiple family names, such as are commonly found in Hispanic countries, are recorded in the
single Family Name field so that, for example, Miguel de Cervantes Saavedra's Family Name
would be recorded as "Cervantes Saavedra." |
Second Family Name | 0..1 | . |
Given Name | 0..1 | A given name, or multiple given names, are the denominator(s) that identify an individual within
a family. These are given to a person by his or her parents at birth or may be legally recognised
as 'given names' through a formal process. All given names are ordered in one field so that, for
example, the Given Name for Johan Sebastian Bach is 'Johan Sebastian.' |
Date Of Birth | 0..1 | A date that specifies the birth date of a person |
Document | 0..1 | . |
Type | 0..1 | . |
Received Date | 0..1 | . |
Name | 0..1 | Name of the document |
Incorrect Language Indicator | 0..1 | . |
Translation Needed Indicator | 0..1 | . |
Translate To Language | 0..1 | The language of the document. |
Reason Not Processed Description | 0..1 | The reason why the document could not be processed |
Identifier | 0..1 | . |
Identifier | 1..1 | The Formal Identifier class represents any identifier issued by any authority, whether a
government agency or not. It captures the identifier itself and details of the issuing authority, the
date on which the identifier was issued and so on. |
Identifier Type | 0..1 | . |
Date Of Issue | 0..1 | The date on which the identifier was issued. |
Issuing Authority | 0..1 | An issuing authority can be identified by its name as well as its URI. As this field takes a string
there is considerable room for error so publishers are urged to use a consistent form of the
name. |
Legal Entity | 0..1 | . |
Legal Name | 0..* | The legal name of the business. A business might have more than one legal name, particularly
in countries with more than one official language. In such cases, and where the encoding
technology allows, the language of the string should be identified. |
Legal Identifier | 0..1 | he legal status of a business is conferred on it by an authority within a given jurisdiction. The
Legal Identifier is therefore a fundamental relationship between a legal entity and the authority
with which it is registered. The details of the registration are provided as properties of the
Formal Identifier class. There is no restriction on the type of legal identifier. In many countries,
the business register's identifier is the relevant data point. The tax number often fulfils this
function in Spain.
The cardinality of this relationship is 1..1, i.e. a legal entity must have a legal identifier. |
Licence Held | 0..1 | . |
Identifier | 1..1 | The Formal Identifier class represents any identifier issued by any authority, whether a
government agency or not. It captures the identifier itself and details of the issuing authority, the
date on which the identifier was issued and so on. |
Identifier Type | 0..1 | . |
Date Of Issue | 0..1 | The date on which the identifier was issued. |
Issuing Authority | 0..1 | An issuing authority can be identified by its name as well as its URI. As this field takes a string
there is considerable room for error so publishers are urged to use a consistent form of the
name. |
Establishment | 0..1 | The establishment of the legal entity |
Date | 0..1 | The date the legal entity was established |
Place | 0..1 | The place where the legal entity was established |
Geographic Name | 0..1 | Again quoting from ISO 19112, a geographic name is a "spatial reference in the form of a label or
code that identifies a location. “Spain” is an example of a country name; “SW1P 3AD” is an example of a
postcode. Both are geographic names.
The country codes defined in ISO 3166 are further examples of geographic names. As noted in Section
4.1.10, the Publications Office of the European Union recommends the use of ISO 3166-1 codes
for countries in all cases except two:
use 'UK' in preference to the ISO 3166 code GB for the United Kingdom;
use 'EL' in preference to the ISO 3166 code GR for Greece.
The 'place' may be an abstract location such as a jurisdiction as opposed to a physical location.
The geographic name might be a recognised name, such as 'Paris,' which may or may not be
ambiguous in context, or it might be descriptive (such as 'Rhine km 203'). Although geographic
names are always useful, it is recommended that an additional method be used to identify a
location.
Places may have multiple geographic names in a single language or multiple languages. Where
a name is language-specific, that language should be identified along with the name (see
Section 4.9). There is no cardinality restriction on the number of geographic names that can be
used to describe a single location. |
Country | 0..1 | . |
Code | 1..1 | Code according to ISO 3166-1. |
Communication | 0..* | . |
Channel | 1..1 | Type of communication channel (e.g. telefone, mobile phone, e-mail, fax, e-codex infrastructure) defined by code-list "Communication Channel"
|
Complete Number | 0..1 | A text string of characters that make up the complete number for this communication.. |
Address | 0..* | . |
PO Box | 0..1 | . |
Postal Code | 0..1 | . |
Address Line | 0..* | additional unstructered address information or complete unstructured address
|
Line Number | 0..1 | . |
Description | 0..1 | . |
City | 0..1 | City |
Name | 0..1 | . |
Country | 0..1 | The country the address is in. |
Code | 1..1 | Code according to ISO 3166-1. |
Involvement | 0..1 | . |
Role | 0..* | Role of the party involved in a case or event.
|
Representative Party | 0..1 | A related party. |
Person | 0..1 | Natural person (individual)
|
Family Name | 1..1 | A family name is usually shared by members of a family. This attribute also carries prefixes or
suffixes which are part of the Family Name, e.g. “de Boer”, “van de Putte”, “von und zu Orlow”.
Multiple family names, such as are commonly found in Hispanic countries, are recorded in the
single Family Name field so that, for example, Miguel de Cervantes Saavedra's Family Name
would be recorded as "Cervantes Saavedra." |
Second Family Name | 0..1 | . |
Given Name | 0..1 | A given name, or multiple given names, are the denominator(s) that identify an individual within
a family. These are given to a person by his or her parents at birth or may be legally recognised
as 'given names' through a formal process. All given names are ordered in one field so that, for
example, the Given Name for Johan Sebastian Bach is 'Johan Sebastian.' |
Date Of Birth | 0..1 | A date that specifies the birth date of a person |
Document | 0..1 | . |
Type | 0..1 | . |
Received Date | 0..1 | . |
Name | 0..1 | Name of the document |
Incorrect Language Indicator | 0..1 | . |
Translation Needed Indicator | 0..1 | . |
Translate To Language | 0..1 | The language of the document. |
Reason Not Processed Description | 0..1 | The reason why the document could not be processed |
Identifier | 0..1 | . |
Identifier | 1..1 | The Formal Identifier class represents any identifier issued by any authority, whether a
government agency or not. It captures the identifier itself and details of the issuing authority, the
date on which the identifier was issued and so on. |
Identifier Type | 0..1 | . |
Date Of Issue | 0..1 | The date on which the identifier was issued. |
Issuing Authority | 0..1 | An issuing authority can be identified by its name as well as its URI. As this field takes a string
there is considerable room for error so publishers are urged to use a consistent form of the
name. |
Communication | 0..* | . |
Channel | 1..1 | Type of communication channel (e.g. telefone, mobile phone, e-mail, fax, e-codex infrastructure) defined by code-list "Communication Channel"
|
Complete Number | 0..1 | A text string of characters that make up the complete number for this communication.. |
Address | 0..1 | The address of the party. |
PO Box | 0..1 | . |
Postal Code | 0..1 | . |
Address Line | 0..* | additional unstructered address information or complete unstructured address
|
Line Number | 0..1 | . |
Description | 0..1 | . |
City | 0..1 | City |
Name | 0..1 | . |
Country | 0..1 | The country the address is in. |
Code | 1..1 | Code according to ISO 3166-1. |
Reason | 0..1 | The reason for filing the legal remedy. |
Code | 0..1 | . |
Description | 0..1 | .Description of the reason in free format |
PO Condition Code | 0..1 | . |
Evidence | 0..1 | . |
Description | 0..1 | Detail of the evidence
|
Signature | 1..1 | Data in electronic form which are attached to or logically associated with other electronic data and which serve as a method of authentication (Directive 1999/93)
|
Date Of Signing | 1..1 | Time stated in terms of day, month, and year when the act of signing has taken place
|
Name Of Person Signing | 1..1 | Name of natural person who signs the form/document and who is bound by it
|
Place Of Signing | 0..1 | An area with definite or indefinite boundaries
(town, country, building) where the act of signing has taken place. |
Attachment | 1..* | A file that is sent along with a message.
|
Content ID | 1..1 | A unique identifier of the attached file which should be a guid |
Content Type | 1..1 | . |
Content Description | 0..1 | A description of the contents of the attached file |
File Name | 0..1 | The name of the attached file |