remove audioTrackNumber and change to nonNegativeInteger for numberOf…

[MarcAntoine-Arnaud]

…*Tracks

issue #342

[JuergenGrupp]

Thank you, @MarcAntoine-Arnaud !
No need for duplicate property. No negative number of tracks possible.
@alexander-schulze : Any objections?

[JuergenGrupp]

EBU EditorialCommittee:
Please re-analyse: audioTrackNumber (in the sense of "index") is NOT the same as hasNumberOfAudioTracks (in the sense of "count").

[alexander-schulze]

Hey @MarcAntoine-Arnaud, @JuergenGrupp
Currently, both audioTrackNumber and numberOfVideoTracks have similar comments in the ontology, but their actual meanings are different:

• audioTrackNumber refers to a specific audio track in a media file (e.g., track 1 for English audio in a multi-language video).
• numberOfVideoTracks represents the total number of video tracks available (e.g., two video streams for different camera angles).

If we use these properties for their distinct meanings, we should keep both and update the comments in the ontology to reflect their unique purposes.

However, if the goal is to represent only the total number of tracks, not individual audio tracks, we can remove audioTrackNumber and keep numberOfVideoTracks, which would then represent the total count of both audio and video tracks.

[JuergenGrupp]

Comment by the Editorial Committee:

• we need a field for the index of the audio track
• we need a field for the total count of the audio tracks
• we should rename those two to the intended meaning

Conclusion: we will decline the pull request, but improve the naming of the properties

[JuergenGrupp]

This pull request is also related to the issue "Index of track in a MediaResource"
#344
Its resolution should fix #344 also.

[JuergenGrupp]

This pull request is declined in favor of #369.