ADS as functional substitute for driver requirement RC-002 | UNECE / 1968 Vienna Convention | System | System-dependent | Self-monitoring | Possible interface | Possible interface | No human remote dr… | No | No | Technical compliance | No | No |
ADS as functional substitute for driver requirementDDTSystemFallback / MRMSystem-dependentMonitoring / supervisionSelf-monitoringRemote assistancePossible interfaceRemote interventionPossible interfaceRemote drivingNo human remote drivingDispatch / trip strategyNoService operationNoADS lifecycle complianceTechnical complianceTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleCritical ontology distinction: a technical system may perform the driving task without becoming the person legally responsible for service operation, compliance or supervision.Verification statusPrimary-source checkedTermAutomated driving system satisfying Article 34 bis conditionsFrameworkUNECE / 1968 Vienna ConventionActor typeTechnical systemCore functionPerforms dynamic driving in a manner that can satisfy the Convention's driver requirement when conforming to applicable technical rules or domestic legislation.Primary legal / technical source1968 Convention on Road Traffic, Article 34 bisSlovak current-law equivalentNo general autonomous legal person; ADS is treated as vehicle/system functionalitySlovak draft 1329 equivalentADS remains distinct from operator and supervision rolesFunctional equivalenceConceptual only; do not equate system with legal operatorSlovak drafting implicationADS can perform DDT without becoming the legal operator. |
Remote assistance / remote interaction RC-003 | UNECE ADS work / technical interpretation | No | Support only | Yes | Yes | Limited | No | Possible | No | No | No | No |
Remote assistance / remote interactionDDTNoFallback / MRMSupport onlyMonitoring / supervisionYesRemote assistanceYesRemote interventionLimitedRemote drivingNoDispatch / trip strategyPossibleService operationNoADS lifecycle complianceNoTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleMust remain distinct from remote driving. Advice/assistance does not automatically mean takeover of lateral and longitudinal control.Verification statusROAT verified sourceTermRemote assistance / remote interactionFrameworkUNECE ADS work / technical interpretationActor typeHuman-supported functionCore functionProvides information or support to the ADS without necessarily assuming continuous DDT control.Primary legal / technical sourceUNECE ADS Guidance and Interpretation work on remote intervention / interactionSlovak current-law equivalentNo settled general statutory category in current Slovak lawSlovak draft 1329 equivalentClosest candidates: control-centre and supervision functions; exact mapping unresolvedFunctional equivalencePartialSlovak drafting implicationKeep remote assistance distinct from remote driving. |
Transport / service operator RC-004 | European Union – Regulation (EU) 2022/1426 | No | Organisational | Entity-level | Arranged | Arranged | No | Yes | Yes | Possible | No | No |
Transport / service operatorDDTNoFallback / MRMOrganisationalMonitoring / supervisionEntity-levelRemote assistanceArrangedRemote interventionArrangedRemote drivingNoDispatch / trip strategyYesService operationYesADS lifecycle compliancePossibleTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleDo not conflate with vehicle owner, ADS manufacturer/provider or remote human supervisor.Verification statusPrimary-source checked via ROATTermTransport service operatorFrameworkEuropean Union – Regulation (EU) 2022/1426Actor typeLegal or organisational entityCore functionOrganises or operates the transport service in which fully automated vehicles are deployed.Primary legal / technical sourceCommission Implementing Regulation (EU) 2022/1426, as amendedSlovak current-law equivalentNo complete general current-law equivalent for commercial FAV operationSlovak draft 1329 equivalentClosest: prevádzkovateľ plne automatizovaného vozidla / licence-holder architectureFunctional equivalencePartial to strong at service-operator level, subject to exact statutory textSlovak drafting implicationPotential comparator for Slovak licensed FAV operator. |
Remote management function RC-005 | European Union – Regulation (EU) 2022/1426 / JRC interpretation | No | Support | Yes | Yes | Yes | Not necessarily | Yes | Supports | Possible | No | No |
Remote management functionDDTNoFallback / MRMSupportMonitoring / supervisionYesRemote assistanceYesRemote interventionYesRemote drivingNot necessarilyDispatch / trip strategyYesService operationSupportsADS lifecycle compliancePossibleTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleOntology should model this primarily as a function or organisational capability, not automatically as one named natural person.Verification statusPrimary / official interpretation checkedTermRemote managementFrameworkEuropean Union – Regulation (EU) 2022/1426 / JRC interpretationActor typeOrganisational / technical functionCore functionSupports fleet/vehicle operation remotely within the approved system architecture, including defined interaction with vehicles and operational management.Primary legal / technical sourceRegulation (EU) 2022/1426 and JRC interpretation addendum on Safety Management System and Remote ManagementSlovak current-law equivalentNo general fully developed current-law equivalentSlovak draft 1329 equivalentClosest: riadiace centrum / control-centre functionsFunctional equivalencePartialSlovak drafting implicationModel as function/capability, not automatically as a person. |
Authorised self-driving entity / ADS legal-responsibility entity RC-006 | Great Britain – Automated Vehicles Act 2024 | No | No direct | Entity-level | Possible | Possible | No | No | No / distinct | Yes | No | No |
Authorised self-driving entity / ADS legal-responsibility entityDDTNoFallback / MRMNo directMonitoring / supervisionEntity-levelRemote assistancePossibleRemote interventionPossibleRemote drivingNoDispatch / trip strategyNoService operationNo / distinctADS lifecycle complianceYesTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleHigh-value comparison for Slovak drafting: UK separates the entity responsible for the authorised self-driving feature from individual users and service-operation roles.Verification statusPrimary-source checkedTermAuthorised self-driving entity (ASDE)FrameworkGreat Britain – Automated Vehicles Act 2024Actor typeLegal person / entityCore functionLegally responsible for ensuring an authorised automated vehicle continues to meet self-driving requirements and other statutory obligations.Primary legal / technical sourceAutomated Vehicles Act 2024Slovak current-law equivalentNo direct current-law equivalentSlovak draft 1329 equivalentClosest: licensed FAV operator, but functions are not necessarily identicalFunctional equivalencePartialSlovak drafting implicationSeparate ADS safety-responsibility entity from service operator. |
User with limited in-vehicle legal duties during self-driving RC-007 | Great Britain – Automated Vehicles Act 2024 | No while engaged | Transition | Readiness duties | No | No | No | Limited | No | No | No | No |
User with limited in-vehicle legal duties during self-drivingDDTNo while engagedFallback / MRMTransitionMonitoring / supervisionReadiness dutiesRemote assistanceNoRemote interventionNoRemote drivingNoDispatch / trip strategyLimitedService operationNoADS lifecycle complianceNoTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleUseful to prevent collapsing 'driver', 'user' and 'operator' into one category.Verification statusPrimary-source checkedTermUser-in-chargeFrameworkGreat Britain – Automated Vehicles Act 2024Actor typeNatural personCore functionOccupies the vehicle and retains specified non-driving legal duties while not responsible for the manner of driving during authorised self-driving.Primary legal / technical sourceAutomated Vehicles Act 2024Slovak current-law equivalentPartly comparable to driver / person required to take over under selected automated-driving rulesSlovak draft 1329 equivalentDraft role allocation should be checked; not equivalent to supervision operatorFunctional equivalencePartialSlovak drafting implicationDo not conflate in-vehicle user with supervision operator. |
No-user-in-charge operational entity RC-008 | Great Britain – Automated Vehicles Act 2024 | No | Organisational | Entity-level | Arranged | Arranged | No | Yes | Yes | Possible | No | No |
No-user-in-charge operational entityDDTNoFallback / MRMOrganisationalMonitoring / supervisionEntity-levelRemote assistanceArrangedRemote interventionArrangedRemote drivingNoDispatch / trip strategyYesService operationYesADS lifecycle compliancePossibleTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationalePotential model for commercial driverless operation in Slovakia where no human user-in-charge is present.Verification statusPrimary-source checkedTermNo-user-in-charge operator (NUIC operator)FrameworkGreat Britain – Automated Vehicles Act 2024Actor typeLicensed legal entityCore functionUndertakes responsibilities that cannot be allocated to an in-vehicle user where the vehicle operates without a user-in-charge.Primary legal / technical sourceAutomated Vehicles Act 2024Slovak current-law equivalentNo current-law equivalentSlovak draft 1329 equivalentClosest: licensed operator of fully automated vehicle/serviceFunctional equivalenceModerate to strong at organisational levelSlovak drafting implicationStrong model for driverless commercial operation entity. |
Technical remote supervisor RC-009 | Germany – StVG / AFGBV | No continuous | Support | Yes | Yes | Legally constrained | No | No | No | No | No | No |
Technical remote supervisorDDTNo continuousFallback / MRMSupportMonitoring / supervisionYesRemote assistanceYesRemote interventionLegally constrainedRemote drivingNoDispatch / trip strategyNoService operationNoADS lifecycle complianceNoTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleA key warning against translating Technische Aufsicht simply as remote driver: German law deliberately separates supervision/authorisation from continuous vehicle control.Verification statusPrimary-source checkedTermTechnische AufsichtFrameworkGermany – StVG / AFGBVActor typeNatural personCore functionPerforms legally defined remote technical-supervision functions, including assessment and enabling/authorising specified manoeuvres or measures when the automated vehicle requests support.Primary legal / technical sourceGerman Road Traffic Act (StVG), §§ 1d–1f; Autonomous Vehicles Approval and Operation Ordinance (AFGBV)Slovak current-law equivalentNo settled current-law general equivalentSlovak draft 1329 equivalentClosest: operátor dohľadu / technický dohľad, but scope must be compared provision-by-provisionFunctional equivalencePartialSlovak drafting implicationClosest supervision comparator; not remote driver. |
Automated road transport system operator RC-010 | France – STRA framework | No | Organisational | Entity-level | Arranged | Arranged | No | Yes | Yes | Possible | No | No |
Automated road transport system operatorDDTNoFallback / MRMOrganisationalMonitoring / supervisionEntity-levelRemote assistanceArrangedRemote interventionArrangedRemote drivingNoDispatch / trip strategyYesService operationYesADS lifecycle compliancePossibleTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleFrance structures responsibility around the transport system/service, not only around the individual vehicle.Verification statusPrimary-source checked via ROATTermExploitant du système de transport routier automatiséFrameworkFrance – STRA frameworkActor typeLegal / organisational entityCore functionOperates the automated road transport system under the French service-level safety and commissioning framework.Primary legal / technical sourceOrdonnance n° 2021-443 and Décret n° 2021-873Slovak current-law equivalentNo complete current-law equivalentSlovak draft 1329 equivalentClosest: licensed operator / service operator architectureFunctional equivalencePartial to strong at service-system levelSlovak drafting implicationService/system operator model; distinct from remote human role. |
Authorised remote intervention person RC-011 | France – STRA / automated-driving framework | Limited intervention | Support | Yes | Yes | Yes | Not ordinary | No | No | No | No | No |
Authorised remote intervention personDDTLimited interventionFallback / MRMSupportMonitoring / supervisionYesRemote assistanceYesRemote interventionYesRemote drivingNot ordinaryDispatch / trip strategyNoService operationNoADS lifecycle complianceNoTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleFrench law is useful because it expressly links remote intervention to personal legal responsibility; this is a distinct design choice from pure technical supervision.Verification statusPrimary-source checked via ROATTermPersonne habilitée à intervenir à distanceFrameworkFrance – STRA / automated-driving frameworkActor typeNatural personCore functionPerforms legally authorised remote intervention within the conditions laid down for the automated road transport system.Primary legal / technical sourceOrdonnance n° 2021-443; Code des transports / implementing decreeSlovak current-law equivalentNo explicit general current-law equivalentSlovak draft 1329 equivalentClosest: operátor dohľadu or a future remote-intervention role, depending on draft wordingFunctional equivalencePartialSlovak drafting implicationGood comparator for explicit remote-intervention powers. |
In-vehicle operator during automated operation RC-012 | Croatia – Road Traffic Safety Act | No | MRM request | Yes | No remote | In-vehicle commands | No | Route / stops | No | No | No | No |
In-vehicle operator during automated operationDDTNoFallback / MRMMRM requestMonitoring / supervisionYesRemote assistanceNo remoteRemote interventionIn-vehicle commandsRemote drivingNoDispatch / trip strategyRoute / stopsService operationNoADS lifecycle complianceNoTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleUseful counter-example: Croatia explicitly names an in-vehicle operator separately from a remote intervention operator.Verification statusPrimary-source checked via ROATTermOperator u voziluFrameworkCroatia – Road Traffic Safety ActActor typeNatural personCore functionHuman role located in the vehicle under the Croatian statutory architecture for automated vehicle operation.Primary legal / technical sourceCroatia Road Traffic Safety Act amendments, NN 145/2024Slovak current-law equivalentNo dedicated equivalent in current Slovak general frameworkSlovak draft 1329 equivalentCould overlap with a readiness/supervision person depending on final draft designFunctional equivalenceWeak to partialSlovak drafting implicationUseful in-vehicle operator comparator; ADS retains DDT. |
Remote intervention operator RC-013 | Croatia – Road Traffic Safety Act | No | MRM support | Yes | Yes | Yes | No | Possible | No | No | No | No |
Remote intervention operatorDDTNoFallback / MRMMRM supportMonitoring / supervisionYesRemote assistanceYesRemote interventionYesRemote drivingNoDispatch / trip strategyPossibleService operationNoADS lifecycle complianceNoTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleStrong comparative candidate for Slovak legislative drafting because Croatia separates remote intervention from in-vehicle operation.Verification statusPrimary-source checked via ROATTermOperator intervencije na daljinuFrameworkCroatia – Road Traffic Safety ActActor typeNatural personCore functionPerforms remote intervention functions for a fully automated vehicle under Croatian law.Primary legal / technical sourceCroatia Road Traffic Safety Act amendments, NN 145/2024Slovak current-law equivalentNo explicit general current-law equivalentSlovak draft 1329 equivalentClosest: operátor dohľadu, but remote-intervention powers need separate analysisFunctional equivalencePartialSlovak drafting implicationStrong comparator if Slovak role intervenes but ADS remains DDT performer. |
Licensed fully automated vehicle operator RC-014 | Slovakia – parliamentary print 1329 (draft) | No | Organisational | Entity-level | Arranged | Arranged | No | Yes | Yes | Possible | No | No |
Licensed fully automated vehicle operatorDDTNoFallback / MRMOrganisationalMonitoring / supervisionEntity-levelRemote assistanceArrangedRemote interventionArrangedRemote drivingNoDispatch / trip strategyYesService operationYesADS lifecycle compliancePossibleTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleStatus flag is essential: as of 26 August 2026 this is not effective law and should never be returned as a current Slovak legal role without qualification.Verification statusDraft text checked; not in forceTermPrevádzkovateľ plne automatizovaného vozidla – proposed licence-holder roleFrameworkSlovakia – parliamentary print 1329 (draft)Actor typeLicensed operator / legal subjectCore functionWould hold the licence and carry central organisational and operational obligations for fully automated vehicle operation.Primary legal / technical sourceGovernment bill, parliamentary print 1329Slovak current-law equivalentNo general current-law commercial-operation equivalent; §49 Act 106/2018 is test-operation permit architectureSlovak draft 1329 equivalentExact draft roleFunctional equivalenceN/A – Slovak reference pointSlovak drafting implicationDraft reference point for commercial-operation responsibility. |
Supervision operator RC-015 | Slovakia – parliamentary print 1329 (draft) | No continuous | Support | Yes | Possible | Possible | Potential boundary | No | No | No | No | No |
Supervision operatorDDTNo continuousFallback / MRMSupportMonitoring / supervisionYesRemote assistancePossibleRemote interventionPossibleRemote drivingPotential boundaryDispatch / trip strategyNoService operationNoADS lifecycle complianceNoTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleKey research issue: determine whether the draft function is closer to German Technische Aufsicht, French authorised remote intervener, Croatian remote intervention operator, or an EU remote-management function. It may improperly combine several models.Verification statusDraft text checked; not in forceTermOperátor dohľaduFrameworkSlovakia – parliamentary print 1329 (draft)Actor typeNatural person / operational roleCore functionWould perform supervision functions assigned by the proposed Slovak framework within the control-centre/operator structure.Primary legal / technical sourceGovernment bill, parliamentary print 1329Slovak current-law equivalentNo settled general equivalent in current lawSlovak draft 1329 equivalentExact draft roleFunctional equivalenceN/A – Slovak reference pointSlovak drafting implicationCore Slovak issue: define boundary between supervision, intervention and remote driving. |
Level 3 fallback-ready user RC-016 | SAE J3016 | After takeover | Yes | Readiness | No | No | No | No | No | No | No | No |
Level 3 fallback-ready userDDTAfter takeoverFallback / MRMYesMonitoring / supervisionReadinessRemote assistanceNoRemote interventionNoRemote drivingNoDispatch / trip strategyNoService operationNoADS lifecycle complianceNoTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleCritical distinction for Level 3: fallback-ready user is not a remote supervisor and is not the service operator.Verification statusPrimary technical standard checked via ROATTermDDT fallback-ready userFrameworkSAE J3016Actor typeNatural person / userCore functionRemains receptive to a request to intervene and performs the DDT fallback when the Level 3 ADS can no longer continue.Primary legal / technical sourceSAE J3016_202104 – Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor VehiclesSlovak current-law equivalentClosest to a driver/person subject to takeover duties in automated-driving rules; no general standalone statutory categorySlovak draft 1329 equivalentShould remain distinct from operátor dohľadu; check whether draft allocates any takeover role to an in-vehicle userFunctional equivalencePartialSlovak drafting implicationKeep Level 3 fallback user outside remote-supervision category. |
Remote human driver RC-017 | SAE J3016 | Yes | Possible | Yes | No | Yes – direct | Yes | No | No | No | No | No |
Remote human driverDDTYesFallback / MRMPossibleMonitoring / supervisionYesRemote assistanceNoRemote interventionYes – directRemote drivingYesDispatch / trip strategyNoService operationNoADS lifecycle complianceNoTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleThis is the cleanest comparator for testing whether Slovak supervision powers cross the line into actual remote driving.Verification statusPrimary technical standard checked via ROATTermRemote driverFrameworkSAE J3016Actor typeNatural personCore functionPerforms part or all of the dynamic driving task from outside the conventional in-vehicle driving position.Primary legal / technical sourceSAE J3016_202104Slovak current-law equivalentNo explicit general remote-driver category in current Slovak road-traffic frameworkSlovak draft 1329 equivalentNo clearly separate remote-driver role; must not be presumed identical to operátor dohľaduFunctional equivalenceWeak / no direct equivalentSlovak drafting implicationExplicit separate remote-driver role is needed if direct DDT is ever intended. |
Trip-dispatch / strategic user RC-018 | SAE J3016 | No | No | No | Possible | No | No | Yes | Support | No | No | No |
Trip-dispatch / strategic userDDTNoFallback / MRMNoMonitoring / supervisionNoRemote assistancePossibleRemote interventionNoRemote drivingNoDispatch / trip strategyYesService operationSupportADS lifecycle complianceNoTesting permit / trial responsibilityNoOwnership / keeper responsibilityNoPrimary current-law rationaleUseful reminder that strategic trip management, DDT performance and remote supervision are separate functions.Verification statusPrimary technical standard checked via ROATTermDispatcherFrameworkSAE J3016Actor typeNatural person / userCore functionDispatches an ADS-operated vehicle and performs strategic trip functions without performing the DDT.Primary legal / technical sourceSAE J3016_202104Slovak current-law equivalentNo standalone statutory equivalentSlovak draft 1329 equivalentPossible control-centre dispatch function, but not necessarily a named legal roleFunctional equivalenceFunctional onlySlovak drafting implicationSeparate dispatch/strategic functions from safety supervision. |
Safety driver in public-road AV testing RC-022 | California – DMV testing regime | Conditional | Yes | Yes | No | In-vehicle takeover | No | No | No | No | Testing driver role | No |
Safety driver in public-road AV testingDDTConditionalFallback / MRMYesMonitoring / supervisionYesRemote assistanceNoRemote interventionIn-vehicle takeoverRemote drivingNoDispatch / trip strategyNoService operationNoADS lifecycle complianceNoTesting permit / trial responsibilityTesting driver roleOwnership / keeper responsibilityNoPrimary current-law rationaleCalifornia 2026 rules retain a distinct permitting pathway for testing with a safety driver, separate from driverless testing and deployment.Verification statusOfficial California current regulations checkedTermAutonomous vehicle test driver / safety driverFrameworkCalifornia – DMV testing regimeActor typeNatural person / licensed test driverCore functionProvides the human driving and safety fallback required for AV testing under the drivered-testing permit category.Primary legal / technical sourceCalifornia Code of Regulations, title 13, AV testing regulations; DMV 2026 frameworkSlovak current-law equivalentFunctional analogue of the human safety driver used under a Slovak test-operation permitSlovak draft 1329 equivalentNot a necessary deployment role for fully driverless operationFunctional equivalenceStrong in testing contextSlovak drafting implicationTesting-only human safeguard. |
AV testing permit holder RC-023 | California – DMV AV program | No | Organisational | Entity-level | Arranged | Arranged | No | Yes | Testing programme | Possible | Yes | No |
AV testing permit holderDDTNoFallback / MRMOrganisationalMonitoring / supervisionEntity-levelRemote assistanceArrangedRemote interventionArrangedRemote drivingNoDispatch / trip strategyYesService operationTesting programmeADS lifecycle compliancePossibleTesting permit / trial responsibilityYesOwnership / keeper responsibilityNoPrimary current-law rationaleUseful for separating testing authorisation from commercial/deployment operator licensing in Slovak law.Verification statusOfficial California permit framework checkedTermManufacturer / autonomous vehicle testing permit holderFrameworkCalifornia – DMV AV programActor typeLegal entity / manufacturerCore functionHolds DMV authority to test or deploy AVs subject to the applicable permit category, ODD, reporting and compliance conditions.Primary legal / technical sourceCalifornia DMV Autonomous Vehicle Regulations and Permit ProgramSlovak current-law equivalentClosest current comparator: holder/applicant of a §49 Act No. 106/2018 test-operation permitSlovak draft 1329 equivalentDraft licensed FAV operator is closer for deployment, but not identical to California testing permit holderFunctional equivalenceStrong for testing permit; partial for deploymentSlovak drafting implicationSeparate Slovak §49 permit holder from eventual deployment licence holder. |
Vehicle owner as statutory responsibility holder RC-030 | Croatia – Road Traffic Safety Act | No | No | No | No | No | No | No | Distinct | No | No | Yes |
Vehicle owner as statutory responsibility holderDDTNoFallback / MRMNoMonitoring / supervisionNoRemote assistanceNoRemote interventionNoRemote drivingNoDispatch / trip strategyNoService operationDistinctADS lifecycle complianceNoTesting permit / trial responsibilityNoOwnership / keeper responsibilityYesPrimary current-law rationaleCroatia is a useful warning against conflating owner, service operator and remote human roles: the owner carries specific offence and data duties even though intervention roles are separately defined.Verification statusPrimary-source checked via ROATTermVlasnik potpuno automatiziranog vozilaFrameworkCroatia – Road Traffic Safety ActActor typeNatural or legal person / ownerCore functionBears statutory responsibility for traffic offences committed by the fully automated vehicle subject to exceptions, and has data-preservation/disclosure duties.Primary legal / technical sourceCroatia Road Traffic Safety Act amendments, NN 145/2024, Articles 281.d–281.eSlovak current-law equivalentVehicle owner/holder concepts exist, but Slovak AV law does not currently use ownership as a complete substitute for driver/operator responsibilitySlovak draft 1329 equivalentDraft operator/licence-holder should remain distinct from vehicle owner unless the law expressly combines themFunctional equivalencePartial – ownership is a separate legal axisSlovak drafting implicationKeep owner/holder liability axis separate from operator and supervisor roles. |