natgillin/translations-raw huggingface dataset:
Prioriteringen af de forskellige sikkerhedsaspekter og graden af deres opfyldelse kan variere.
Although the element coordinate within the geo object section is conditional, the geo coordinates shall be given in WGS84 in format [d]d mm.mmm[m] N (latitude) and [d][d]d mm.mmm[m] E (longitude).
Gennemførligheden af en bestemt foranstaltning kan ligeledes være begrænset af den tekniske gennemførelseskapacitet.
This is to refer the NtS messages geographically.
I forbindelse med NtS er alle oplysninger offentligt tilgængelige.
The target group section consists of target group code and direction code.
Der er derfor ikke behov for at sikre NtS-dataene i databeskyttelsesmæssig henseende.
If both have the value ALL the whole section shall be omitted if there are no other specific target groups within the message.
Den enkelte udbyder skal derfor selv afgøre, i hvor høj grad dette aspekt skal gennemføres i den pågældende tjeneste.
If just one of these two is given the other must be filled with the default value ALL because both elements are mandatory.
NtS Web Service skal overholde WS-I Basic Profile 1.1.
Further information concerning target groups can be found in the NtS Encoding Guide for editors.
Denne profil »indeholder retningslinjer for interoperabilitet for et sæt centrale generiske webtjenestespecifikationer såsom SOAP, WSDL og UDDI«.
The validity_period shall be used by applications to select the messages, which are to be displayed to users for a requested time.
De mest relevante standarder heri er:
If subject_code is INFSER (Info service) the validity period is used to specify the time the Info service Message is displayed to the users, not for the period of validity of the provided information (e.g. 1 month).
Web Services Description Language (WSDL)
The following functions may be offered to NtS editors depending on national requirements:
NtS WS-svarmeddelelsen er en NtS-meddelelse, der er defineret i XML Schema Definition (XSD) i tillæg C til denne forordning fra Kommissionen.
NtS applications may offer NtS editors to save draft NtS messages (not all mandatory content has to be provided in order to save draft messages)
SOAP er en applikationsprotokol for datatransmission mellem IT-systemer og er standardiseret af World Wide Web Consortium (W3C).
Different user roles may apply to different editors (e.g. editors that are allowed to enter/alter notices, publishers that are allowed to publish notices (in addition to editing)
De specifikke elementer for NtS Web Service er defineret i de tilknyttede WSDL-specifikationer i tillæg D til denne forordning fra Kommissionen.
The NtS XML Message Structure and the content and purpose of data elements are defined and further explained in Appendix C: NtS XML Schema Definition (XSD).
NtS-skemastandarden (XSD) er ledsaget af en vigtig erklæring
The NtS Expert Group identified the web service technology as an appropriate means to provide the Notices to Skippers.
Da antallet af potentielle udbydere af NtS Web Service afhænger af antallet af deltagende medlemsstater, og da WSDL-specifikationen er en integrerende del af standarden, er der imidlertid ikke umiddelbart behov for en uafhængig registrering af NtS Web Service.
This chapter constitutes the specification of the web service for the provision of the Notices to Skippers, short NtS Web Service.
Kodningsmetoden »Document-literal wrapped« anvendes i forbindelse med NtS Web Service, da den gør det muligt at foretage en validering på grundlag af et XML-skema, og de operationelle navne, der er defineret i WSDL-specifikationen, anvendes direkte som XML-tagnavne i SOAP-meddelelserne.
Particular emphasis was placed on the use of well-established international standards.
Versionsoplysningerne vedrørende NtS Web Service er opdelt i to afsnit:
One goal of the conceptual design was to ensure a good balance between flexibility and robustness of the resulting web service.
selve webtjenesteversionen
The filter parameters provided in the requests are essentially the criteria specified in the NtS standard (waterway section with optional river km, time of validity, date of publication of the notice).
den version af NtS-skemaet, der anvendes af webtjenesten
This seems sufficiently expressive considering the use cases of the web service and at the same time limits the complexity of the implementation.
Afsnittet om selve webtjenesten er opdelt i to dele:
The core result is a contract for the web service, in which the requests and responses are specified.
den store version af webtjenesten
The consumers of the web service can rely on this contract and the providers have to comply with it.
den mindre version af webtjenesten
This contract is specified using the international standard WSDL.
Den store version er angivet som et positivt heltal for den store version af webtjenesten.
Every participating Member State shall implement one or more web services for the different message types of the NtS (FTM, WRM, ICEM, WERM) and provide them via the internet (‘NtS Message Service’),
Den mindre version er angivet som et ikkenegativt heltal for den mindre version af webtjenesten i den store version.
The technical details of the implementation of the NtS WS, e.g. choice of appropriate data pools, applications and platforms, are not in the scope of this specification and are in the responsibility of each individual participating Member State.
Afsnittet vedrørende NtS-skemaet indeholder den version af NtS-skemaet, som er defineret af NtS-ekspertgruppen.
In order to define a secure communication one has to consider various security aspects and protection objectives.
Den version af NtS Web Service, der er specificeret her, er således version 2.0.4.0, hvor version 2.0 er selve webtjenesteversionen, og version 4.0 er den anvendte version af NtS-skemaet.
Depending on the circumstances not all of these aspects have to be considered.
Det er ikke nødvendigt at anføre versionsoplysninger i forespørgsler eller svar fra NtS Web Service.
The priority of the various security aspects and the degree of their fulfilment can vary.
Det forventes kun, at få versioner af tjenesterne vil være online på samme tid.
Also the feasibility of a certain measure can be limited by the capabilities of the technical implementation.
De forskellige versioner skal have forskellige URL-adresser.
In the context of NtS all information are public.
Hver instans i en NtS Web Service-gennemførelse skal således understøtte en specifik version af NtS Web Service.
So there is no need to secure the NtS data themselves in terms of data protection.
Navneområder i NtS Web Service er baseret på RIS-ekspertgruppernes websted: http://www.ris.eu/.
Therefore every provider has to decide on its own in how far this aspect will be implemented in its service.
Navneområderne indeholder en partikel, der angiver den tilknyttede tjeneste og versionsoplysninger.
The NtS Web Service has to comply with the WS-I Basic Profile 1.1.
For den specificerede tjeneste anvendes således følgende navneområder:
This profile ‘provides interoperability guidance for a core set of non-proprietary web services specifications, such as SOAP, WSDL and UDDI’.
I anmodninger og svar i NtS Web Service anvendes XML-elementer i kvalificeret form, dvs. med et eksplicit navneområdepræfiks, og XML-attributter i ukvalificeret form, dvs. uden et navneområdepræfiks.
The response message of the NtS WS is an NtS message which is defined in XML Schema Definition (XSD) in Appendix C of this Commission Regulation.
Det anbefales at bruge intuitive navneområdepræfikser såsom »nts« af hensyn til læsbarheden.
SOAP is an application protocol for data transmission among IT-Systems and is standardised by the World Wide Web Consortiums (W3C).
ISRS Location Code er forklaret i kapitel 2 i NtS Encoding Guide for udviklere af applikationer samt i RIS Index Encoding Guide.
The specific elements for the NtS Web Service are defined inline in the corresponding WSDL specifications in Appendix D of this Commission Regulation.
Ved søgning i en NtS Web Service kan kunden søge forskellige objekter, f.eks. farvandsafsnit, profiler eller sluser.
The schema of the NtS standard (XSD) is included with an import statement.
Hvis de tilsvarende parametre — ID-elementerne — anvendes, skal de indeholde ISRS Location Codes.
UDDI (Universal Description, Discovery and Integration) is noted here as a central, possibly international registry for web services, where the NtS Web Service could be registered.
Disse parametre angives typisk i ID-elementer, som hver indeholder en eller to ID-elementer.
In this registry potential consumers of the web service could search and find the service.
Ved brug af disse parametre skal følgende generelle konventioner overholdes:
But since the potential providers of the NtS Web Service are limited by the participating Member States and the WSDL specification is an integral part of the standard, the need for an independent registration of the NtS Web Service is not apparent.
ISRS Location Codes skal angives med 20 tegn, dvs. uden afkortning med efterstillede nuller.
The encoding method Document-literal wrapped is used for the NtS Web Service, because it allows for validation against an XML schema and the operation names defined in the WSDL specification are used directly as XML tag names in the SOAP messages.
Hvis to ID-elementer anvendes i et ID-element, skal begge ISRS Location Codes vedrøre den samme vandvej.
The version information of the NtS Web Service consists of two sections:
Dette betyder, at koderne indeholder en række identiske cifre fra fairway_section-delen i ISRS Location Code.
version of the web service itself,
Koden for farvandsstrækning samt farvandshektometeren definerer en vandvejsstrækning angivet som et par ID-elementer.
version of the NtS schema used by the web service.
I forbindelse med vandvejsstrækninger (et par ID-elementer i fairway_section geo_object) i NtS-meddelelser skal følgende tages i betragtning i forhold til ISRS Location Codes:
The section of the web service itself consists of two parts:
1-2 cifre (Country code):
major version of the web service,
skal være identiske i ID-parret, men
minor version of the web service.
Forskellige landekoder kan imidlertid defineres i et ID-par, hvis tilgrænsende lande benytter samme kode for farvandsstrækning for en bestemt vandvej og det samme system til fastlæggelse af hektometer.
The major version is given as a positive integer denoting the major version of the web service.
3-5 cifre (UN Location code):
The minor version is given as a non-negative integer denoting the minor version of the web service within the major version.
er ikke relevante, indholdet i ID-parret kan være forskelligt.
The section of the NtS schema contains the version of the NtS schema as defined by the NtS Expert Group.
6-10 cifre (Fairway section code):
Hence, the version of the NtS Web Service specified here is 2.0.4.0, where 2.0 is the version of the web service itself and 4.0 is the version of the NtS schema used.
[undtagelse]: Hvis de belgiske ISRS-koder anvendes i NtS WS, bør der kun benyttes cifrene 6-8 til at identificere farvandsafsnittet, da NtS-meddelelserne vil blive offentliggjort for forskellige afsnit i et farvand.
Explicit version information is not necessary in the requests or responses of the NtS Web Service.
11-15 cifre (Object Reference Code):
There are only a few versions of the services expected to be online at the same time.
16-20 cifre (Fairway Hectometre):
Different versions shall be provided with different URLs.
Består af fem cifre, der definerer hektometeren, og indholdet i ID-parret vil således normalt være forskelligt.
Hence, each instance of an NtS Web Service implementation shall support one specific version of the NtS Web Service.
Eksempel: »00235« for farvand 23,5 km, »00001« for farvand 0,1 km
The namespaces in the NtS Web Service are based on the web domain of the RIS Expert Groups, http://www.ris.eu/
[undtagelse]: I Nederlandene er der ikke altid en direkte forbindelse mellem farvandshektometeren og farvandets fysiske kilometer på grund af definitionen af farvandsstrækningens start i netværksmodellen og i den virkelige verden.
The namespaces contain a particle indicating the corresponding service and version information.
I sådanne tilfælde begynder objektreferencekoden for objekter af typen »dismar« med Kxxxx (xxxx omfatter de fysiske kilometer, f.eks. NLSVG00130K000300191 (3 km)).
Hence, the service specified here uses the following namespace:
For andre objekttyper er der imidlertid ingen direkte forbindelse til farvandets fysiske kilometer i ISRS-koderne.
NtS Message Service: http://www.ris.eu/nts.ms/2.0.4.0
Broen Sas van Gent i samme farvand på 2,5 km har f.eks. ISRS-koden NLSVG001300521600186.
For higher transparency of XML documents it is recommended to define namespaces in the outmost suitable element in the schemas as well as the instance documents and not to use local namespace definitions in nested elements.
For Kanaal Gent-Terneuzen beregnes den fysiske 0,0 km fra grænsen mellem Belgien og Nederlandene, og farvandshektometeren 0,0 beregnes fra starten af kanalen i Gent.
Requests and responses in the NtS Web Service shall use XML elements in qualified form, i.e. with an explicit namespace prefix, and XML attributes in unqualified form, i.e. without a namespace prefix.
Hvis en meddelelse vedrører mere end en vandvejs- eller farvandsstrækning, skal alle farvandsstrækninger defineres ved deres start- og slutpunkter i særskilte XML-elementer i »fairway_section«.
It is recommended to use intuitive namespace prefixes like ‘nts’ for better human readability.
For nogle lande/regioner er det nødvendigt at opbygge filterfunktionalitet.
The ISRS Location Code is explained in chapter 2 of the NtS Encoding Guide for application developers as well as the RIS Index Encoding Guide.
Hvis ISRS Location Code (1-2) er BE, anvendes ISRS Location Code (6-8) som ID for lineær referering med farvandshektometeren (ISRS Location Code 16-20).
Querying an NtS Web Service, the client can reference various objects, e.g. fairway sections, gauges or locks.
Eksempler på farvandsstrækninger (gyldige ID-elementpar i fairway_section), der omfatter de ovenfor definerede undtagelser:
If the corresponding parameters, the id elements, are used, they must contain ISRS Location Codes.
De to NL ISRS Location Codes er en gyldig definition af en vandvejstrækning (NL-undtagelse med hensyn til farvandet i km): NLSVG00130K000300191 (3,0 km, Sas van Gent på Kanaal Gent-Terneuzen) — NLWDP00130K000400200 (4,0 km, Westdorpe på Kanaal Gent-Terneuzen),
These parameters are typically given in id elements, each containing one or two ids.
De to BE ISRS Location Codes er en gyldig definition af en vandvejstrækning (BE-undtagelse med hensyn til fairway section code (»020« Albertkanaal)): BEGNK02016L010100414 (Genk-slusen i en afstand af 41,4 km på Albert Canal) — BEOSH02033L010500772 (Ham-slusen i en afstand af 77,2 km på Albert Canal).
When using these parameters, the following general conventions have to be observed:
Følgende figur viser modeksempler på anvendelsen af ISRS Location Code for de enkelte generelle konventioner (ingen undtagelser fra de generelle konventioner for vandvejsstrækninger i SK):
ISRS Location Codes have to be submitted as full-length 20-character codes, i.e. without truncating trailing zeros,
Ugyldige ISRS Location Code-søgninger
If two ids are used within an id element, both ISRS Location Codes have to refer to the same waterway.
Generel bemærkning: En tjeneste til at søge efter gældende ISRS Location Codes er ikke understøttet af NtS Web Service.
This means, that the codes include some identical digits located in the fairway_section part of the ISRS Location Code.
ISRS Location Codes er angivet i det europæiske system til forvaltning af referencedata (ERDMS).
The fairway section code together with the fairway hectometre defines a waterway stretch provided as pair of id elements.
Den korrekte anvendelse af ISRS Location Codes i søgninger og fortolkningen heraf fremgår af følgende fem eksempler.
For the provision of waterway stretches (id element pairs within the fairway_section geo_object) in NtS messages, the following has to be considered with respect to the ISRS Location Codes:
Eksempel 1: Intet ID-element i anmodning
digits 1 to 2 (Country code):
ID-elementet er en valgfri del af anmodningen, og der kan således foretages en søgning uden ID-elementer:
have to be identical within the id pair, but
Gyldig søgning uden ID-parameter
different country codes may be defined within one id pair in case neighbouring countries are using the same fairway section code for a specific waterway and the same system for defining the hectometres,
Hvis der ikke angives et ID-element, returneres alle meddelelser (naturligvis afhængigt af andre filterkriterier såsom validity_period eller date_issue).
digits 3 to 5 (UN Location code):
Eksempel 2: Et ID-element i anmodning
are not relevant, may contain different content within the id pair,
Hvert ID-element kan indeholde et enkelt eller to ID-elementer.
digits 6 to 10 (Fairway section code):
Et ID-element er vist i følgende figur:
[exception]: in case of using the Belgian ISRS codes within NtS WS, one should use only digits 6 to 8 to identify the fairway section, because NtS messages will be published across different sections within one fairway,
Gyldig søgning med en ID-parameter
digits 11 to 15 (Object Reference Code).
Ved modtagelsen af en sådan søgning returnerer serveren alle matchende meddelelser med en starthektometer ≤ den pågældende værdi (240,7 i eksemplet) og en hektometer ≥ denne værdi.
digits 16 to 20 (Fairway Hectometre):
Figuren nedenfor viser denne udvælgelse af meddelelser: Den søgte position ligger mellem start- og sluthektometerværdierne for meddelelse 1, 3 og 4, der vil blive returneret.
consist of five numerical digits defining the hectometre thus will usually contain different content within the id pair.
Meddelelse 2, 5 og 6 overlapper ikke den søgte position, og de vil derfor ikke blive returneret.
Example: ‘00235’ for fairway km 23,5; ‘00001’ for fairway km 0,1,
Hvis den pågældende ISRS Location Code betegner et særligt objekt, f.eks. en profil eller en sluse, bør webtjenesten returnere de meddelelser, som vedrører dette objekt.
[exception]: in case of the Netherlands there is not always a direct connection between the Fairway hectometre and the physical kilometre of the fairway due to the definition of the start of the fairway stretch in the network model and in the real world, in such cases the Object Reference Code for objects of the type ‘dismar’ starts with Kxxxx (xxxx includes the physical kilometre, e.g. NLSVG00130K000300191 (km 3)).
Matchende og ikkematchende meddelelser for en ID-parameter
But for other types of objects there is no direct relation to the physical fairway km in the ISRS codes, e.g. the bridge of Sas van Gent on the same fairway at km 2,5 has the ISRS code NLSVG001300521600186.
Eksempel 3: To ID-elementer i anmodning
For the Kanaal Gent-Terneuzen the physical km 0,0 starts at the border of Belgium and the Netherlands and the Fairway Hectometre 0,0 starts at the beginning of the canal in Gent.
Et eksempel med to ID-elementer er vist i følgende figur:
In case a message touches more than one waterway or fairway sections all fairway sections have to be defined by their begin- and end-point in separate ‘fairway_section’ XML elements.
Gyldig søgning med to ID-parametre
For some countries/regions it is required to build filter functionality.
Alle søgte hektometerværdier betragtes som gyldige, selv om den tilsvarende farvandsstrækning har forskellige start- eller slutpunkter.
For example if ISRS Location Code (1-2) is BE use ISRS Location Code (6-8) as the ID for linear referencing with the fairway hectometre (ISRS Location Code 16-20).
Hvis farvandsstrækningen f.eks. starter ved hektometer 100,0 og slutter ved hektometer 300,0, vil en søgning i intervallet 20,0-400,0 hektometer være gyldig.
Examples for fairway stretches (valid id element pairs within the fairway_section) that include above defined exceptions:
Internt er det naturligvis kun den »reelle« udstrækning af farvandsafsnittet, der søges.
The two NL ISRS Location Codes are a valid definition of a waterway stretch (showing NL exception with respect to the kilometre of the fairway): NLSVG00130K000300191 (km 3,0 at Sas van Gent on the Kanaal Gent-Terneuzen) — NLWDP00130K000400200 (km 4,0 at Westdorpe on the Kanaal Gent-Terneuzen),
Dette gør det også muligt at søge alle meddelelser om et farvand uden at kende den nøjagtige hektometer (ISRS Location Code fremsendes med hektometer sat til henholdsvis »00000« eller »99999«).
The two BE ISRS Location Codes are a valid definition of a waterway stretch (showing BE exception with respect to the fairway section code (‘020’ Albertkanaal)): BEGNK02016L010100414 (lock of Genk located at km 41,4 on the Albert Canal) — BEOSH02033L010500772 (lock of Ham located at km 77,2 on the Albert Canal).
Alle matchende meddelelser, der skærer det pågældende hektometerinterval, returneres.
The following figure shows counter-examples of ISRS Location Code usage for each of the general conventions (no exceptions to the general conventions apply to SK waterway stretches):
Diagrammet nedenfor illustrerer denne situation:
Invalid ISRS Location Code queries
Matchende og ikkematchende meddelelser for to ID-parametre
General remark: A service to query valid ISRS Location Codes is not supported by the NtS Web Service.
Ovenstående figur viser, hvordan »skæring« defineres.
The ISRS Location Codes are provided within the European Reference Data Management System (ERDMS).
Selv om omfanget af meddelelse 1-4 overlapper omfanget af det søgte hektometerinterval (helt eller delvist), er dette ikke tilfældet for meddelelse 5 og 6, og meddelelse 1-4 vil således blive returneret, og meddelelse 5 og 6 vil ikke blive returneret.
The correct usage of ISRS Location Codes in queries and their interpretation is given in the following five cases.
Den tekniske betingelse for, at en meddelelse skærer et interval [A og B]: Starthektometeren i meddelelsens er ≤ B og sluthektometeren er ≥ A.
Case 1: No ids element in request
Kombinering: Flere ID-elementer i anmodning
The ids element is an optional part of the request, i.e. a query without any ids elements is allowed:
Gyldig søgning med flere ID-elementer
Valid query without ids parameter
Ved at kombinere flere ID-elementer i anmodningen forenes tilsvarende meddelelser.
If no ids element is given, all messages shall be returned (depending, of course, on other filter criteria like validity_period or dates_issue).
Alle ID-elementerne behandles individuelt, og en meddelelse vil blive returneret, hvis den matcher mindst et af dem.
Case 2: One id element in request
Følgende meddelelser ville derfor blive returneret i det pågældende eksempel:
Each ids element can contain one or two id elements.
Alle meddelelser vedrørende objektet med ISRS Location Code SKXXX0000010000***** med starthektometer =0 og sluthektometer ≥ 0 (se eksempel 2)
The case of one id element is shown in the following figure:
Alle meddelelser vedrørende objektet med ISRS Location Code SKXXX0000500000*****, der skærer hektometerintervallet [220,0, 300,0] (se eksempel 3)
Valid query with one id parameter
I dette kapitel redegøres for gennemførelsesspecifikation for NtS-meddelelsestjenesten, udledt af betragtningerne og valgene i de foregående kapitler.
If such a query is received, the server shall return all matching messages with a start hectometre ≤ the given value (240,7 in the example) and an end hectometre ≥ this value.
NtS-meddelelsestjenesten tilvejebringer de fire NtS-meddelelsestyper:
The figure below depicts this selection of messages: The position queried lies between the start and end hectometre values of messages 1, 3 and 4, which would be returned.
NtS FTM (farvands- og trafikrelateret meddelelse)
Messages 2, 5 and 6 do not overlap with the query position, so they would not be returned.
NtS WRM (vandstandsrelateret meddelelse)
If the given ISRS Location Code denotes a singular object, e.g. a gauge or a lock, the web service should return the messages involving this object.
NtS ICEM (ismelding)
Matching and not matching messages for one id parameter
NtS WERM (vejrmelding)
Case 3: Two id elements in request