- From: Thomas Stockhammer <stockhammer@nomor.de>
- Date: Mon, 21 Mar 2011 00:32:27 +0100
- To: Steve Lhomme <slhomme@matroska.org>
- Cc: Rob Glidden <rob.glidden@sbcglobal.net>, Mark Watson <watsonm@netflix.com>, "Ali C. Begen (abegen)" <abegen@cisco.com>, Gerard Fernando <gerardmxf@yahoo.co.uk>, "juhani.huttunen@nokia.com" <juhani.huttunen@nokia.com>, "hj08.lee@lge.com" <hj08.lee@lge.com>, "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Steve, currently the expectation is that MPEG only defines DASH profiles that restrict the usage of functionalities that are in the DASH specification. The definition of complete system specifications including codecs, DRM, etc. is expected to be done by someelse, for example 3GPP will define a systems standard that also includes codecs. You can use a URI for profile identification (typically a URN), but the exact details of that profile are defined by the one that has control of the URI,. Therefore, a DASH profile in the strict MPEG DASH sense does not include codecs or similar. Thomas On Mar 19, 2011, at 11:00 AM, Steve Lhomme wrote: > I suppose DASH profiles will specify the codecs/containers for one > particular use case ? So I assume a royalty free DASH profile should > also include codecs/containers. --- Dr. Thomas Stockhammer (CEO) || stockhammer@nomor.de || phone +49 89 978980 02 || cell +491725702667 || http://www.nomor-research.com Nomor Research GmbH - Sitz der Gesellschaft: München - Registergericht: München, HRB 165856 – Umsatzsteuer-ID: DE238047637 - Geschäftsführer: Dr. Thomas Stockhammer, Dr. Ingo Viering.
Received on Sunday, 20 March 2011 23:32:56 UTC