5.4 Examples of server organisation and file naming convention (informative)
The example below shows a delivery of two releases both with two resource files associated with them. The first release has already been acknowledged by the DSP, the second has not. The example does not use the ResourceType component of the file name. The delivery of both releases is a "normal" delivery (as opposed to a priority one).
N_A10301A0001887532A_20100517154800000/
A10301A0001887532A.xml
resources/
A10301A0001887532A_T1.mp3
A10301A0001887532A_T2.jpg
acknowledgements/
ACK_A10301A0001887532A_20100517154800000.xml
N_A10301A00017EG98F_20100517155422000/
A10301A00017EG98F.xml
resources/
A10301A00017EG98F_T1_001.mp4
A10301A00017EG98F_T2_2.jpg
|
The example below shows one delivery where one of the three resources has been taken from a different release.
N_A10301A0001887532A_20100517154800000/ A10301A0001887532A.xml resources/ A10301A0001887532A_T1.mp3 A21412B1112998643B_T2.mp3 A10301A0001887532A_T3.jpg |
The example below shows a delivery where three separate files of one resource is provided. The three files are a video file, an audio file and a colour space information file.
A_A10301A0001887532A_20100517154800000/ A10301A0001887532A.xml resources/ A10301A0001887532A_T2_video_.bit A10301A0001887532A_T2_audio.bit A10301A0001887532A_T2_color.bit |