search

Dash-Industry-Forum / DRM

Collect DRM related comments
2 stars 0 forks source link

box hierarchy #3

Closed haudiobe closed 10 years ago

haudiobe commented 10 years ago

Minor comment on the box hierarchy, should it not be traf/saiz and traf/saio (i.e. both these present at traf level)?

andrejp commented 10 years ago

Should both be traf/saiz and traf/saio

nthorwir commented 10 years ago

yes, thanks. I agree with comment and Andrew: It should be • moof/traf/saiz (one, if encrypted) • moof/traf/saio (one, if encrypted) not • moof/traf/saiz/saiz (one, if encrypted) • moof/traf/saiz/saio (one, if encrypted)

andrejp commented 10 years ago

Ok need to re-check a diagram and probably fix it. Thank you for pointing out.

A.

ghost commented 10 years ago

Maybe those path errors (‘saiz’/’saiz’) were based on trying to represent sample groups and sample group description ‘seig’ as a path hierarchy at the F2F. It was confusing because it isn’t a box, so our rough edit might have been misinterpreted later. Need to check if we are missing something now.

Kilroy Hughes | Senior Digital Media Architect |Windows Azure Media Services | Microsoft Corporation [cid:image001.png@01CDABBA.71FD8800]http://www.windowsazure.com/media

From: Andrew Popov [mailto:notifications@github.com] Sent: Friday, March 21, 2014 5:20 AM To: Dash-Industry-Forum/DRM Subject: Re: [DRM] box hierarchy (#3)

Ok need to re-check a diagram and probably fix it. Thank you for pointing out.

A.

— Reply to this email directly or view it on GitHubhttps://github.com/Dash-Industry-Forum/DRM/issues/3#issuecomment-38270827.

haudiobe commented 10 years ago

There seems to be agreement on the box location. I don’t have any more questions here.

haudiobe commented 10 years ago

Agree. Typo will be fixed by Niels