Overview

In connection with registration, there may be a need to attach supporting documents. In e-TL, this can be done by submitting electronic documents to the document repository. Subsequently, these documents are referenced in the notification document that is submitted for registration.

It may happen that the need for supporting documents is first determined during the registration process, or that the document could not be obtained in time. In such cases, the notification will normally be registered with a deadline. Documents can then be submitted to the document repository afterwards, and you can subsequently send information to the Registration Court regarding the location in the document repository.

Documents can be of the following types: JPEG, XML, GML (Geography Markup Language), and PDF.

If documents are in other electronic formats, they must be converted to one of the specified formats before being submitted to the document repository. The maximum size for documents that can be submitted will be determined at a later stage.

Documents can be referenced in two places within a notification:

  1. A document reference can be linked to BilagReferenceSamling under AnmeldelseInformation. These documents are always included in the review.

  2. A document reference can be linked to AnmelderBilagReferenceSamling under AnmelderInformation. Here, it is possible to indicate whether the document should be included in the review or not.

Documents that are part of the document being registered will be transferred to be part of the currently registered rights. Documents that are only included in the review will be removed once the registration result is available. These documents will be deleted.

Documents can only be deleted if they have not been used in a notification. DSS may delete documents if they have remained unused in a notification for an extended period or if the content leads DSS to decide not to retain the document for other reasons.

A service has been created to retrieve UUIDs for documents of type 38 – GML files. The actual GML files must be retrieved using BilagHent.

Endpoints

BilagHent

Endpoint URL: Bilagsbank/BilagHent

Description

Used to retrieve a copy of a document from the document repository.

Input

BilagHent.xsd

Output

BilagHentSvar.xsd

Error Handling

If the requested document is not found in the repository, e-TL returns a SOAP fault.

Security

Simple web service (i.e., based on HTTP)

Interaction Pattern

Request-response

Invocation Effect

Idempotent

BilagIndsend

Endpoint URL: Bilagsbank/BilagIndsend

Description

Used to submit notification documents to e-TL, which are to be referenced in a notification that is subsequently submitted via one of the notification operations. The digital signature identifies who owns the document. Only this person can subsequently delete the document.

Input

BilagIndsend.xsd

Output

BilagIndsendSvar.xsd

Error Handling

If the actor does not receive the activation receipt within the agreed response time, the activation of the service must be repeated. If a document is submitted that does not meet the document requirements, the sender receives a SOAP fault.

Security

Simple web service (i.e., based on HTTP)

Interaction Pattern

Request-response

Invocation Effect

Traceable

BilagSlet

Endpoint URL: Bilagsbank/BilagSlet

Description

Used to delete a document in the document repository.

Input

BilagSlet.xsd

Output

BilagSletSvar.xsd

Error Handling

If the requested document is not found in the repository, e-TL returns a SOAP fault.

Security

Simple web service (i.e., based on HTTP)

Interaction Pattern

Request-response

Invocation Effect

Idempotent

GMLListeHent

Endpoint URL: Bilagsbank/GMLListeHent

Description

Retrieves a list of UUIDs for the GML files available in e-TL. If a date is specified, only documents created on or after that date are returned.

Input

GMLListeHent.xsd

Output

GMLListeHentSvar.xsd

Error Handling

If an error occurs, e-TL returns a SOAP fault. If there are no documents of type 38, an empty result set is returned.

Security

Simple web service (i.e., based on HTTP)

Interaction Pattern

Request-response

Invocation Effect

Idempotent