Library not recognizing headers for newer Autosar Versions even thought they are mentioned as supported in the Crate

[jjvilches]

Hello,
I have arxmls using r24.11. The python library is not recognizing them and rejects the file when reading the header and throws "Failed to parse file.arxml:2: Invalid arxml file: bad file header". Here is a header example:
xmlns="http://autosar.org/schema/r24.11".

I checked the rust crate, and the library should handle up to r25.11. So expected behavior should be that namespace URI http://autosar.org/schema/r24.11 is accepted (same as how http://autosar.org/schema/r4.0 is), since AUTOSAR_00053 schema is already supported.

Temporary workaround:

• modify the header so that an older Autosar schema is declared and used. The library runs smoothly then.

It seems the namespace URI validation in the header parser wasn't updated when the R24-11 schema was added — only the element/attribute definitions were updated. The r24.11 / r25.11 URI patterns need to be added to the accepted namespace list alongside r4.0.
This is not an big issue so far since I dont see any schema changes between the versions delivered by Autosar, but this might become a blocking one in the future.

[DanielT]

As far as I know, the file version is determined by the schema URL in the file header, not the namespace.
I checked the relevant sections in the standard (in particular AUTOSAR_FO_TPS_ARXMLSerializationRules.pdf, section 2.2.4) and the wording hasn't changed in any substantial way between e.g. 21-11 and 25-11.

As far as I can tell, a correct file header for an arxml file using R24-11 should be:

<?xml version="1.0" encoding="UTF-8"?>
<AUTOSAR xsi:schemaLocation="http://autosar.org/schema/r4.0 AUTOSAR_00053.xsd" xmlns="http://autosar.org/schema/r4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>

I'm using Autosar less these days than I used to, so maybe I've missed some relevant info in a different place. If so, let me know where I should look.