ISO/IEC 15444-9:2005/Amd 5:2014

Information technology — JPEG 2000 image coding system: Interactivity tools, APIs and protocols — Part 9: — Amendment 5: UDP transport and additional enhancements to JPIP

Technologies de l'information — Système de codage d'images JPEG 2000: Outils d'interactivité, interfaces de programmes d'application et protocoles — Partie 9: — Amendement 5: Transport UDP et autres améliorations du JPIP

General Information

• Status: Withdrawn
• Publication Date: 30-Jan-2014
• ICS: 35.040 - Information coding
• ICS: 35.040.30 - Coding of graphical and photographical information
• Technical Committee: ISO/IEC JTC 1/SC 29 - Coding of audio, picture, multimedia and hypermedia information
• Drafting Committee: ISO/IEC JTC 1/SC 29/WG 1 - JPEG Coding of digital representations of images

Relations

• Amends: ISO/IEC 15444-9:2005 - Information technology — JPEG 2000 image coding system: Interactivity tools, APIs and protocols — Part 9:
• Effective Date: 13-Oct-2020
• Revised: ISO/IEC 15444-9:2023 - Information technology — JPEG 2000 image coding system — Part 9: Interactivity tools, APIs and protocols
• Effective Date: 26-Nov-2021

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 15444-9
First edition
2005-12-01
AMENDMENT 5
2014-02-01
Information technology — JPEG 2000
image coding system — Part 9:
Interactivity tools, APIs and protocols
AMENDMENT 5: UDP transport and
additional enhancements to JPIP
Technologies de l'information — Système de codage d'images
JPEG 2000 — Partie 9: Outils d'interactivité, interfaces de programmes
d'application et protocoles
AMENDEMENT 5:Transport UDP et autres améliorations du JPIP

Reference number
ISO/IEC 15444-9:2005/Amd.5:2014(E)
©
ISO/IEC 2014
ISO/IEC 15444-9:2005/Amd.5:2014(E)

©  ISO/IEC 2014
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2014 – All rights reserved

ISO/IEC 15444-9:2005/Amd.5:2014(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
Amendment 5 to ISO/IEC 15444-9:2005 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia
information, in collaboration with ITU. The identical text is published as Rec. ITU-T T.808 (2005)/
Amd.5 (03/2013).
© ISO/IEC 2014 – All rights reserved iii

ISO/IEC 15444-9:2005/Amd.5:2014 (E)
INTERNATIONAL STANDARD
RECOMMENDATION ITU-T
Information technology – JPEG 2000 image coding system:
Interactivity tools, APIs and protocols
Amendment 5
UDP transport and additional enhancements to JPIP
1) Clause 6.1
Replace the third paragraph in this clause (between Figure 3 and Figure 4) with the following text:
This protocol can be used over several different transports as shown in Figure 4. This Recommendation | International
Standard includes informative annexes on the use of the JPIP protocol over HTTP, TCP and UDP, and provides
suggestions for other example implementations. The JPIP protocol itself is neutral with respect to underlying transport
mechanisms for the client requests and server responses, except in regard to channel requests represented by the New
Channel ("cnew") request field (see C.3.3) and the New Channel ("JPIP-cnew") response header (see D.2.3), where
transport-specific details shall be communicated. This Recommendation | International Standard defines four specific
transports, which are identified by the strings "http", "https", "http-tcp" and "http-udp" in the value string associated
with New Channel requests.
2) Clause A.3.6.4
Replace clause A.3.6.4 with the following new clause A.3.6.4:
Wherever header, precinct or tile data bins exist, their codestream ID shall appear in a Placeholder box within an
appropriate metadata bin. The only exception to this requirement is for unwrapped JPEG 2000 codestreams, which are
not embedded within a JPEG 2000 family file format.
The codestream ID values that appear within the relevant Placeholder box shall conform to any requirements imposed
by the containing file format. For example, JPX files formally assign a sequence number to codestreams that are found
in Contiguous Codestream boxes or Fragment Table boxes, either at the top level of the file, or within Multiple
Codestream boxes. The first codestream in the logical target shall have a codestream ID of 0; the next shall have a
codestream ID of 1; and so forth.
Placeholders that reference multiple codestream IDs may be used only where the meaning of those codestreams is well
defined by the type of the box that is being replaced. For JPX files, Contiguous Codestream boxes, Fragment Table
boxes and Multiple Codestream boxes may be replaced by Placeholder Boxes that specify codestream IDs. Placeholders
replacing Contiguous Codestream boxes and Fragment Table boxes may specify only a single codestream ID, while a
placeholder replacing a Multiple Codestream box may specify multiple codestream IDs, corresponding to the number of
codestreams that are found within the box.
3) Clause B.1
Replace the second paragraph of B.1 with the following:
The purpose of sessions is to reduce the amount of explicit communication required between the client and server.
Within a session, the server is expected to remember client capabilities and preferences supplied in previous requests so
that this information need not be sent in every request. Even more importantly, the server may keep a log of data it
knows the client to have received so that this information need not be re-transmitted in response to future requests. This
log is subsequently referred to as the cache model. The cache model would typically be persistent for the duration of a
session. Unless explicitly instructed otherwise, the server may assume that the client caches all data it receives within a
session, and may model the client's cache, sending only those portions of the compressed image data or metadata which
the client does not already have in its cache.
Rec. ITU-T T.808 (2005)/Amd.5 (03/2013) 1

ISO/IEC 15444-9:2005/Amd.5:2014 (E)
4) Clause C.1.2
Replace the server-control-field and client-cap-pref-field lists with the following:
server-control-field = align            ; C.7.1
/ wait              ; C.7.2
/ type              ; C.7.3
/ drate             ; C.7.4
/ sendto             ; C.7.5
/ abandon            ; C.7.6
/ barrier            ; C.7.7
/ twait             ; C.7.8
client-cap-pref-field = cap             ; C.10.1
/ pref              ; C.10.2
/ csf              ; C.10.3
/ handled            ; C.10.4
5) Clause C.3.3
Replace the second and third paragraphs with the following text:
The value string identifies the names of one or more transport protocols that the client is willing to accept. This
Recommendation | International Standard defines only the transport names, "http", "https", "http-tcp", and "http-udp".
Details of the use of JPIP over the "http" transport appear in Annex F. Annex G describes the use of JPIP over the "http-
tcp" transport and Annex K describes the use of JPIP over the "http-udp" transport.
If the server is willing to open a new channel, using one of the indicated transport protocols, it shall return the new
channel identifier token using the New Channel response header (see D.2.3). In this case, the present request is the first
request within the new channel.
6) Equation C-3
Modify equation C-3 with the following augmented version of the equation and subsequent explanatory text, to take
account of the new rotation support in ISO/IEC 15444-2:2004/Amd.3. While making these editorial changes, note that
many of the symbols from the original equation are similar.
First, define the rotated frame size, offset, width and height of the composite image as follows:
2 Rec. ITU-T T.808 (2005)/Amd.5 (03/2013)

ISO/IEC 15444-9:2005/Amd.5:2014 (E)
F F
()fx - ox - sx ,(fy - oy - sy),
   
ox ,oy ,
=
   
F F
()W − XO − Wt ,(H − YO − Ht)
XO , YO
comp inst inst comp inst inst
 
 inst inst
 fx, fy, ox, oy, W , H ,
 
comp comp

if R = 0 | NoFlip
 inst
 
XO , YO , Wt , Ht
 inst inst inst inst 

F

 
fy, fx, oy, ox , H , W ,
comp comp 
if R = 90 | NoFlip
 
inst
F
YO , XO , Ht , Wt
 
 inst inst inst inst
 
 F F
 
fx, fy, ox , oy ,W , H ,

comp comp

if R = 180 | NoFlip
 
inst
F F

XO , YO , Wt , Ht


 inst inst inst inst 

F
 
fy, fx, oy , ox, H ,W ,

 comp comp
if R = 270 | NoFlip
 
inst
θ θ θ θ θ θ F

 
fx ,fy ,ox ,oy , W , H , YO , XO , Ht ,Wt
 
comp comp  inst inst inst inst 
=
 

θ θ θ θ F
 
XO , YO , Wt , Ht fx, fy, ox , oy ,W , H ,
 
inst inst inst inst  comp comp 
 
if R = 0 | Flip
 
inst
F

XO , YO ,Wt , Ht
 
 inst inst inst inst 

fy, fx, oy, ox, H , W ,
 

comp comp 
if R = 90 | Flip
  inst

YO , XO , Ht , Wt
 inst inst inst inst

F
 
 fx, fy, ox, oy ,W , H ,
comp comp 
if R = 180 | Flip
 
inst

F
XO , YO ,Wt , Ht
  (C-3a)
 inst inst inst inst 

F F

 
fy, fx, oy , ox , H , W ,
comp comp 
if R = 270 | Flip
 
inst
F F
 YO , XO , Ht , Wt
 
 inst inst inst inst 

In the above, W and H are the width and height of the composited image, specified in the composition box;
comp comp
Wt and Ht are the composited width and height as determined by the compositing instruction; XO and YO are
inst inst inst inst
the horizontal and vertical compositing offsets as determined by the compositing instruction; Ws and Hs are the
inst inst
width and height of the potentially cropped compositing layer as determined by the compositing instruction; XC and
inst
YC are the horizontal and vertical compositing layer cropping offsets as determined by the compositing instruction;
inst
and R is derived from the ROT field of the compositing instruction, if any. If the compositing instruction contains no
inst
o
ROT field or the ROT field is 0, R =0 |NoFlip. Otherwise, the rotation angle for R (expressed in degrees clockwise)
inst inst
is obtained from the least significant 3 bits of the ROT field using Table M-47 of Rec. ITU-T T.801 | ISO/IEC 15444-2,
while the Flip|NoFlip status for R is set to Flip if bit 4 of the ROT field is non-zero and NoFlip otherwise.
inst
Then, define the modified frame size fx″, fy″ as follows:
θ θ
   
XR YR
Wt W Ht H
reg reg
θ inst cod θ inst cod
fx" = fx ⋅ ⋅ ⋅ ; fy"= fy ⋅ ⋅ ⋅ (C-3b)
   
θ θ
XS Ws YS Hs
W H
   
reg inst reg inst
comp comp
   
To compute the modified region, first define the clipped region edges:
θ θ
   
fx fy
θ θ
x =XO ⋅ ; y =YO ⋅ 
min inst min inst
θ θ
W H
   
comp comp
   
(C-3c)
θ θ
   
fx fy
θ θ θ θ
x =()XO + Wt ⋅ ; y =()YO + Ht ⋅ 
lim inst inst lim inst inst
θ θ
W H
   
comp comp
   
Rec. ITU-T T.808 (2005)/Amd.5 (03/2013) 3

ISO/IEC 15444-9:2005/Amd.5:2014 (E)
The modified region size sx″ and sy″ and region offsets ox″ and oy″ are then given as:
θ θ θ
{( ) } { }
sx" = min ox + sx , x − max ox , x
lim min
θ θ θ
sy" = min{}()oy + sy , y − max{oy , y}
lim min
 θ θ 
 
 
XO
Wt fx
θ θ reg
inst (C-3d)
 
 
ox" = max{}ox , x − XO − XC − ⋅ ⋅ 
min inst inst
θ
 
 
XS Ws
W
 reg inst 
  comp
 
 
θ θ
 
 
 YO 
Ht fy
reg
θ θ
inst
 
 
{}  
oy" = max oy , y − YO − YC − ⋅ ⋅
min inst inst
θ
 
 
YS Hs
H
 
reg inst
comp
   
 
7) Clause C.4.7
Add "jpxf" context-range type; change the definition of context-range to:
context-range = jpxl-context-range / jpxf-context-range / mj2t-context / jpm-
context / reserved-context
Add the following definitions to the end of the list:
jpxf-context-range = "jpxf" "<" jpx-frame-indices ">" [ "[" jpx-thread "]" ]
jpx-frame-indices = sampled-range
jpx-thread = UINT
Replace:
"This Recommendation | International Standard defines three specific types of context-range"
with:
"This Recommendation | International Standard defines four specific types of context-range"
Append the following text at the end of the clause:
A jpxf-context-range may be used to compactly identify a range of compositing layers and coordinate
remapping transformations which could alternately be identified via a jpxl-context-range. The equivalent
jpx-layers and jpxl-geometry values may be obtained by expanding composited frames into their constituent JPX
compositing layers and compositing instructions in the manner described below.
If the logical target does not contain a JPX Composition box, the server shall ignore any jpxf-context-range.
Otherwise, the instructions found within the JPX Composition box together describe a sequence of composited frames,
as described in Annex M of Rec. ITU-T T.801 | ISO/IEC 15444-2. These composited frames may be numbered
f=0, 1, … F –1 and are considered to belong to a base presentation thread t=0. If the logical target also contains
comp
Composition layer extensions ("jplx") boxes, these boxes may contribute additional presentation threads. As explained
in Annex M of Rec. ITU-T T.801 | ISO/IEC 15444-2, a Compositing Layer Extensions box contributes Tjclx
presentation threads, each of which has the same number of composited frames, Fjclx, where the values of Tjclx and
Fjclx for each Compositing Layer Extensions box are specified by its Compositing Layer Extensions Info sub-box.
Together, the collection of all Compositing Layer Extensions boxes in the logical target defines T global presentation
threads, where T is the maximum of the associated Tjclx values. For each t in the range 1 through T, global presentation
thread t consists of the F composited frames from the Composition box, followed by the Fjclx frames defined by
comp
compositing group g = min{t, Tjclx}
...