Topics ISO/IEC 14496-18:2004/ AMD 1 Updated semantics of decoderSpecificInfo and font data description for ISOBMFF
This amendment clarifies usage of font data streams decoder specific information, and provide tools to carry font data streams in ISO/IEC 14496-12
-
.
Number
|
Session
|
Title
|
Source
|
Dispositions
|
|
|
|
|
|
Summary of discussions
Action Points / Ballots
ISO/IEC 14496-18:2004/DAM 1
(SC 29 N 13698)
|
Part 18: Font compression and streaming
AMENDMENT 1: Updated semantics of decoderSpecificInfo and font data description for ISOBMFF
|
DAM
(2014-01-16)
|
Open Font Format (14496-22) Topics -
Contributions
.
Number
|
Session
|
Title
|
Source
|
Dispositions
|
m32405
|
Font
|
Microsoft Response to the CFP for color font and math layout technology
|
Michelle Perham, Greg Hitchcock, Simon Daniels
|
Accepted
N14124
|
m32406
|
Font
|
W3C Response to the CFP on color font and math layout technology
|
Sairus Patel, Chris Lilley,
|
Accepted
N14124
|
m32441
|
Font
|
Google Response to the CFP on color font and math layout technology
|
Stuart Gill, Behdad Esfahbod,
|
Accepted
N14124
|
|
|
|
|
|
Summary of discussions
-
Composite Font Representation (14496-28) Topics ISO/IEC 14496-28 COR 1 Contributions
.
Number
|
Session
|
Title
|
Source
|
Dispositions
|
|
|
|
|
|
Summary of discussions
Action Points
ISO/IEC 14496-28:2012/DCOR 2
(SC 29 N 13885)
|
Part 28: Composite font representation
TECHNICAL CORRIGENDUM 2: Changes and clarifications of CFR element descriptions
|
DCOR
(2014-02-20)
|
Reference Software (21000-8) Topics ISO/IEC 21000-8 AMD 3 Contract Expression Language (CEL) and Media Contract Ontology (MCO) Reference Software
Contributions
Number
|
Session
|
Title
|
Source
|
Dispositions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Summary of discussions
Action Points / Ballots
ISO/IEC 21000-8:2008/DAM 3
(SC 29 N 13641)
|
Part 8: Reference Software
AMENDMENT 3: Contract Expression Language (CEL) and Media Contract Ontology (MCO) Reference Software
|
DAM
(2014-01-16)
|
Surveillance AF (23000-10) Topics ISO/IEC 23000-10 2nd edition
A packaging format designed for the storage of video and audio content originating from surveillance cameras and microphones. It packages the media content together with associated metadata by using the appropriate file format definitions e.g. AVC file format.
Contributions
Number
|
Session
|
Title
|
Source
|
Disposition
|
m31786
|
AF
|
Summary of Voting on ISO/IEC 23000-10:2012/DCOR 1
|
SC 29 Secretariat
|
Refer N14125
|
|
|
|
|
|
|
|
|
|
|
Summary of discussions
Action Points / Ballots
ISO/IEC 23000-10:2012/DCOR 1
(SC 29 N 13642)
|
Part 10: Surveillance application format
TECHNICAL CORRIGENDUM 1
|
DCOR
(2013-11-04)
|
Stereoscopic Video AF (23000-11) Topics ISO/IEC 23000-11:2009/AMD 3
Stereoscopic Video AF (SVAF) provides information about composition type and transition between 2D and 3D view. This amendment is to provide a further investigation of said information in terms of movie fragment structure in order to enable delivery of SVAF content that is incrementally encapsulated.
Contributions
Number
|
Session
|
Title
|
Source
|
Disposition
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Summary of discussions
Action Points
ISO/IEC 23000-11:2009/DAM 3
(SC 29 N 13472)
|
Part 11: Stereoscopic video application format
AMENDMENT 3: Support movie fragment for Stereoscopic Video AF
|
DAM
(2013-10-12)
|
MP-AF (23000-15) Topics Multimedia Preservation Application Format
The objective of the Multimedia Preservation Description Information (MPDI) framework is to provide a standardized description to multimedia content to enable users to plan, execute, and evaluate preservation operations to achieve the objectives of digital preservation.
Contributions
Number
|
Session
|
Title
|
Source
|
Dispositions
|
m32235
|
AF
|
Study of 3rd WD of ISO/IEC 23000-15 Multimedia Preservation Application Format (N13970)
|
Walter Allasia, Werner Bailer, Laurent Boch, Wo Chang, Jean-Pierre Evain, Sergiu Gordea, Kenneth Tibodeau
|
Deferred
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Summary of discussions
Action Points
Common encryption format for ISO BMFF (23001-7) Topics ISO/IEC 23001-7 2nd Edition
This format defines a way to encrypt media (audio, video, etc.) in files of the ISO base media file format family. By using a common encryption format, a single media asset can be used by several services and devices using different digital rights management systems, and the implementation complexity that would be consequent on having duplicate files and formats for the same content can be reduced or eliminated.
Contributions
Number
|
Session
|
Title
|
Source
|
Disposition
|
m32467
|
File Format
|
Support of partial encryption of high bitrate content in 23001-7
|
Mark Watson
|
Accepted
N14127
|
m32126
|
File Format
|
Partial encryption proposal for AEC-CBC 128-bit in CENC
|
David Singer, Zubair Visharam
|
Accepted
N14128
|
|
|
|
|
|
Summary of discussions m32467 Support of partial encryption of high bitrate content in 23001-7
We agree in principle, but the text proposed had a contradiction. We will try to phrase as a functional rule (that NAL headers have to remain clear) and allow writers to lay out subsamples over the NAL units as they wish while respecting this rule. Into the study text. We will also make sure we are consistent with the requirements/recommendations on encrypting video and non-video NAL units.
m32126 Partial encryption proposal for AEC-CBC 128-bit in CENC
Lots of detailed questions. We note that in the case that a tile size is less than the clear portion (e.g. 144 bytes) if it didn’t cross an encrypted 16-byte block, it would be in the clear. Is this a worry (it is presumably unlikely, and once tiles exceed the size of the unencrypted portion, cannot happen)? Some discussion of the goal: make the video unwatchable (but occasional parts may decode) or make it ensure a ‘blank screen’? Perhaps the rules should permit encryption of non-video NALs (e.g. captions, to prevent derivation of a transcription)?
Accepted as an optional mode in common encryption; proponents to draft an amendment text based on the latest base (study of 2nd edition) and modeled on the previous amendment.
In further discussion in systems plenary questions were raised on whether this was really ‘common encryption’. We already have two modes (cenc and cbc1) and this adds a third (cbc2), but both cbc1 and cbc2 require support for cenc.
We need to make sure that the technology uses as much in common as possible, so that the schemes ‘hang together’ and make it easy to implement in the same software.
Dostları ilə paylaş: |