Questions XML

We are several tyre manufacturers in ETRMA having problems with the current XSD scheme 2.1 and the resulting XML files used in the VECTO Trailer tool. As you see below in the answer from Harald Martini, it is proposed to switch back to version 2.0. This could be done, theoretically, but in this case the VECTO truck tool also would need to be able to read and to accept the 2.0 files. Could you confirm that this is the case ? Or do you know when the trailer tool will accept the 2.1 namespace ?

assigned to @n003bqet

added 45m of time spent at 2023-09-16

I think there is some misunderstanding/confusion on the XML versions. I'm not sure if I can explain this via e-mail, but let's try.

One needs to differentiate several namespaces. Let me copy my answer to a support ticket here:

To clarify all the version numbers: we distinguish basically 3 different kinds of schemas:

1. schemas: VectoDeclarationDefinitions

This schema files contain definitions of XML types that can be used somewhere else.

• VectoDeclarationDefinitions-1.0 - contains both, component types (engine, gearbox, axlegear, ...) and the vehicle types (VehicleDeclarationType)
• VectoDeclarationDefinitions-2.0 - also contains both, component types where the structure and type names are the same as in 1.0, it just uses a different namespace; and the vehicle type (VehicleDeclarationType) in the first version (i.e., without SleeperCab, Vocational, ZeroEmission, ADAS, ...). It is not allowed/supported to create vehicles in this schema version.
• VectoDeclarationDefinitions-2.1 - contains the XML type for vehicles as in version 1.0 with all the changes after the 1st amendment (SleeperCab, ADAS, Vocational, ...) and an XML type for the combustion engine with a corrected list of fuel types. This schema version can be used for vehicles right now, it is equivalent to vehicles in schema version 1.0
• VectoDeclarationDefinitions-2.2 - contains an updated type for tyres, due to new tyre dimensions
• VectoDeclarationDefinitions-2.2.1 - contains an updated type for exempted vehicles (equivalent to exempted vehicles in version 1.0 after some updates in the schema)
• VectoDeclarationDefinitions-2.3 - contains XML type definitions for all electric components (EM, battery, supercap, IEPC, IHPC, ...), a new XML type for the ICE in case of a dual fuel engine or an engine equipped with a WHR system, and an updated XML type for tyres (new dimensions)
• VectoDeclarationDefinitions-2.4 - contains XML type definitions for vehicles according to the 2nd amendment for all architectures: conventional, hybrid electric, pure electric, exempted / lorries, primary bus, complete(d) bus.
• VectoDeclarationDefinitions-2.5 - contains XML type definitions for tyres. This schema no longer enforces the tyre dimension via the schema but the hashing tool (which is mandatory to be used) checks whether the tyre dimension is known to VECTO.

2. schemas: VectoComponent

This schema files contain the definitions for a component file, i.e. the XML element VectoInputDeclaration.

• VectoComponent-1.0 - allows only XML components defined in VectoDeclarationDefinitions-1.0
• VectoComponent-2.0 - allows to use XML components defined in VectoDeclarationDefinitions-1.0, 2.0 and 2.1 as it refers to the abstract base types. It only supports components defined in the first version of 2017/2400
• VectoComponent-2.1 - allows to use XML components defined in VectoDeclarationDefinitions-1.0, 2.0, 2.1 and 2.3, i.e. it extends VectoComponent-2.0 with the electric components defined in the 2nd amendment.

3. schemas: VectoInput

This schema files contain the definitions for a VECTO job, i.e. a vehicle. These schemas define the XML element VectoInputDeclaration.

• VectoInput-1.0 - allows to specify a vehicle defined in VectoDeclarationDefinitions-1.0 -- so only vehicle and components in schema version 1.0.
• VectoInput-2.0 - allows to specify a vehicle defined in one of the schemas VectoDeclarationDefinitions-2.0, 2.1 and 2.4.

Unfortunately VectoComponent and VectoInput both define the XML element VectoInputDeclaration. But one is in the namespace urn:tugraz:ivt:VectoAPI:DeclarationInput:... and the other in urn:tugraz:ivt:VectoAPI:DeclarationComponent:.... I understand that this is difficult to understand at first. But this was demanded/proposted by OEMs. Back then I did not thinkt that it will get this complicated.

So as far as I know (that's the status when we finished the development), the trailer tool supports tires up to version 2.3 (VectoDeclarationDefinitions Namespace). The most recent version 2.5 (which is not mandatory, it only removes the constraint on the dimension string as it is now checked in the hashing tool whether the dimension is known to VECTO) is not supported by the trailer tool. But again (AFAIK) there is an open ticket for the trailer tool on this.

The other namespace involved if you create a component file is the VectoComponent. And this is what Harald suggested to change in his e-mail. VectoComponent is 'only' the wrapping container for single component data. VectoComponent-2.0 supports all components required for a conventional heavy lorry (Engine, Gearbox, Axlegear, ... and Tyre). VectoComponent-2.1 was necessary to provide a container for the new electric components (EM, IEPC, Batteries, ...) but this container also supports the other components.

For tyre manufacturers it is perfectly fine to provide the component data in the format/namespace VectoComponent v2.0. It is not necessary to use VectoComponent v2.1. Unfortunately, the Trailer Tool does not know about the new VectoComponent v2.1 - this is caused by diverging developments.

The component data for the tyre itself, however, can (and has to be for newly certified components) in VectoDeclarationDefinitons v2.3. And this is supported by the trailer tool.

So to wrap this up:

• the 'container' for newly certified component data shall be VectoComponent v2.0
• the component data for newly certified tires shall be VectoDeclarationDefinitions v2.3 (already certified component data can still be used both in VECTO and in the Trailer Tool)

I hope this clarifies things. If you think you need more in-depth knowledge on XML and the Namespaces involved in VECTO we can offer a dedicated workshop on this topic for ETRMA members (unfortunately, the costs of such a workshop are currently not covered by any contract we are holding with COM, so we would need to charge for such a workshop)

closed

added typebug label

changed milestone to %Unscheduled

changed milestone to %v1.0.1

added statusin progress label

added resolutionincomplete label

mentioned in issue #36 (closed)

added hashing schema labels