DV_MULTIMEDIA.integrity_check should be multiple bytes
Raise
Analysis
Raise
Analysis
Description
Activity
Show:

Pieter Bos January 2, 2019 at 11:35 AM
Thanks! I'm currently doing an automated comparison of the BMM and the Archie RM implementations. Found some more errors, but they seem to be BMM mistakes. Opened them as github issues of specifications-ITS-BMM. I can open them here instead if that's better.
Thomas Beale January 2, 2019 at 11:06 AM
This was a UML publishing conversion error in fact; in the original 1.0.2 spec, it is Array<Octet>. Still needs to be fixed now though.

Pieter Bos January 2, 2019 at 11:00 AM
Should be very little impact - anyone who implemented this will already have used a byte array, as is in the BMM as well.
Thomas Beale January 2, 2019 at 10:59 AM
yep just re-read the spec, was forgetting it is a separate field. So it will be Array<Byte>.

Pieter Bos January 2, 2019 at 10:57 AM
I think it should be 0..* bytes, since the number of bytes depends on the value of integrity_check_algorithm.
Done
Details
Details
Reporter

Components
Priority
Created January 2, 2019 at 10:54 AM
Updated February 20, 2023 at 7:43 PM
Resolved January 2, 2019 at 11:13 AM
integrity check is a single byte in the specification of RM 1.0.4. It's described in the text and BMM as a multi-byte property. I think it should be more than one byte to be of any use