Sequential components of a MediaResource

[RendersKoen]

Hi (happy holidays!),

In our MAM system for music a mediaobject is an aligned set of mediasources that have exactly the same length. A low-res and a hi-res source.

The hi-res mediasource can exist of one or more files (linked through mediasourcefilelink table, which has order numbers).
The lo-res source on the contrary is an mp3 file created from one or more hi-res files, made for prelistening.

But since the mediasources have the same total length, you can decide by inspecting the lo-res from which timecode to which you can for example order media. In that way it can create an export file spanning over more than one hi-res file and attach them (handy when other segmentation is needed than delivered in tracks belinging to a fileset of an album...

Apparently not impossible to do, but to define the order of files i needed to use ec:audioTrackNumber, which I'm not sure is the right thing to do. It would be very welcome if one of the EC+ specialists might have a look at this use case :-)

# Editorial work (track)
vrtdata:ZAPPA_ITEM_6613548 ec:hasObjectType vrtskoseo:track ;
    ec:isExtractOf vrtdata:ZAPPA_ITEM_6613544 ;
    ec:isInstantiatedBy <https://www.vrt.be/ontologies/vrt-ontology#ZAPPA_MEDIAOBJECT_1136646#t=204.16381,361.569796> ;
    ec:position "01.002" ;
    ec:title "Back To The Sea" ;
    rdf:type ec:EditorialWork .

# Mediafragment that instantiates the track
<https://www.vrt.be/ontologies/vrt-ontology#ZAPPA_MEDIAOBJECT_1136646#t=204.16381,361.569796> rdf:type ec:MediaFragment .

# MediaObject (aligned set of MediaSources)
vrtdata:ZAPPA_MEDIAOBJECT_1136646 rdf:type ec:MediaResource ;
    ec:hasRelatedEssence vrtdata:ZAPPA_MEDIASOURCE_2167082 ;  # Hi-res
    ec:hasRelatedEssence vrtdata:ZAPPA_MEDIASOURCE_2167083 .  # Lo-res preview

# Hi-res MediaSource (archive quality)
vrtdata:ZAPPA_MEDIASOURCE_2167082 rdf:type ec:Essence ;
    ec:hasObjectType vrtskosrt:Zappa_Archive .

# Lo-res MediaSource (preview)
vrtdata:ZAPPA_MEDIASOURCE_2167083 rdf:type ec:Essence ;
    ec:hasObjectType vrtskosrt:Zappa_Preview .

# File component (one of potentially multiple files in hi-res source)
vrtdata:ZAPPA_FILE_3232831 ec:audioTrackNumber "2"^^xsd:nonNegativeInteger ;
    ec:filename "9D\\9D42\\9D4280\\9D4280A614C3666F.wav" ;
    ec:hasLocator vrtdata:ZAPPA_PATHID_72811 ;
    ec:hasParentMediaResource vrtdata:ZAPPA_MEDIASOURCE_2167082 ;
    rdf:type ec:Component .

# File path
vrtdata:ZAPPA_PATHID_72811 ec:name "\\\\servername\\Archive\\HiRes\\" ;
		rdf:type ec:Locator .

[tormodv]

Hi
Nice solution, but as you also think using ec:audioTrackNumber for this is to streetch the consept a little to far. But there is a solution: each mediaresource may have an editorialObject associated with it.
:EditorialObject SubClassOf :hasManifestation only :Resource
So with the subclasses this will be equal to:
AudioContent SubClassOf :hasManifestation only :MediaFragment

I.e each mediafragment has (very often an omitted) EditorialObject describing the content, and the EditorialObject, and thus, the AudioContent have a :segmentNumber max 1 xsd:integer that I think can be used here. The rest of the AudioContent can, of course, stay empty, but start and end as sample counts from the original file.

/Vær