[mpeg-OTspec] RE: Proposed Script tag additions

[Leonardo Chiariglione]

Vladimir,

There is a specific process to set up an RA. Nothing terrible (we've done
several times now), but the process goes up to JTC1

Leonardo

 

 

From: mpeg-OTspec at yahoogroups.com [mailto:mpeg-OTspec at yahoogroups.com] On
Behalf Of Levantovsky, Vladimir
Sent: Monday, 22 November, 2010 22:31
To: Peter Constable; John Hudson
Cc: Michelle Perham; mpeg-OTspec at yahoogroups.com
Subject: RE: [mpeg-OTspec] RE: Proposed Script tag additions

 

  

John, Peter, all,

 

I researched the process for establishing a Registration Authority and I
doubt that it can be simply done by amendment. We will most likely need an
amendment once RA is established but first we need to get there.

 

According to ISO/IEC Directives [1] and JTC1 Directives [2], the
registration authorities are established during the development of a
standard that requires maintaining a registry. Usually, the process of doing
this includes issuing a Call for Registration Authority, which establishes a
period when interested parties can respond by declaring their interest and
intention to serve as RA. The candidates for RA will have to provide certain
assurances to ISO in order to qualify - these assurances will essentially be
seen as a commitment to provide the needed resources and facilities to
support the functions of RA without requiring any financial contribution
from ISO/IEC Secretariats or their members.

 

I do agree that establishing a registry for OT/OFF feature tags would be a
good thing, but the process of doing this has to be followed, and we
definitely will need to have National Body support for this.

 

Best regards,

Vlad

 

[1]
http://www.iso.org/sites/ConsumersStandards/en/pdf/ISO%20IEC%20Directives%20
Part%201%20-Procedures%20for%20the%20technical%20work.pdf

[2]
http://isotc.iso.org/livelink/livelink/fetch/2000/2489/186491/186605/Jtc1_Di
rectives.pdf?nodeid=3959538
<http://isotc.iso.org/livelink/livelink/fetch/2000/2489/186491/186605/Jtc1_D
irectives.pdf?nodeid=3959538&vernum=-2> &vernum=-2

 

 

From: Peter Constable [mailto:petercon at microsoft.com] 
Sent: Thursday, November 18, 2010 3:29 AM
To: John Hudson; Levantovsky, Vladimir
Cc: Michelle Perham; mpeg-OTspec at yahoogroups.com
Subject: RE: [mpeg-OTspec] RE: Proposed Script tag additions

 

I second this. Several ISO standards allow for registries that allow for
data elements to be added to collections without requiring the formal
process of an amendment or new addition to the standard. There is no reason
why the addition of OT layout tags should require an amendment to ISO/IEC
14496-22. 

 

(Re a specific point in John's question: a registry can formally be part of
an ISO standard without requiring a new or amended standard to add to the
registry.)

 

I would suggest that, if there is to be an amendment, that one of the
revisions should be to clarify that the OT Layout tag registry is exactly
that, a registry, and to identify Microsoft as the ISO-sanctioned
Registration Authority for this registry, bringing the standard into
alignment with industry practice as it has been since the format was first
created.

 

 

 

Peter Constable

 

From: mpeg-OTspec at yahoogroups.com [mailto:mpeg-OTspec at yahoogroups.com] On
Behalf Of John Hudson
Sent: Wednesday, November 10, 2010 12:30 AM
To: Levantovsky, Vladimir
Cc: Michelle Perham; mpeg-OTspec at yahoogroups.com
Subject: Re: [mpeg-OTspec] RE: Proposed Script tag additions

 

  

Vladimir wrote:

> Also, if we decide to recommend a new amendment for 14496-22, are there 
> any other proposed changes or new items that we should discuss and/or 
> consider for inclusion in this future amendment? I would like to ask all 
> AHG members to please bring your ideas and proposals for the AHG 
> discussion as part of this new work item.

This seems a good opportunity to enquire, again, whether the OTL feature 
tag registry is considered a formal part of the specification, and what 
the process for proposing and registering new OTL features should be.

JH



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20101122/a982a089/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/x-ygp-stripped
Size: 126 bytes
Desc: not available
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20101122/a982a089/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/x-ygp-stripped
Size: 126 bytes
Desc: not available
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20101122/a982a089/attachment-0001.bin>