W3C home > Mailing lists > Public > public-tt@w3.org > February 2015

Re: TTML2 FPWD Publication

From: Thierry MICHEL <tmichel@w3.org>
Date: Fri, 06 Feb 2015 10:47:14 +0100
Message-ID: <54D48DA2.1020902@w3.org>
To: Nigel Megitt <nigel.megitt@bbc.co.uk>, Glenn Adams <glenn@skynav.com>, "public-tt@w3.org >> W3C Public TTWG" <public-tt@w3.org>


On 06/02/2015 10:35, Nigel Megitt wrote:
>
>
> On 06/02/2015 08:50, "Thierry MICHEL" <tmichel@w3.org> wrote:
>
>> Glenn,
>>
>> If have uploaded a placeholder for the new TTML2 namespaces, to allow
>> dereferencing.
>> http://www.w3.org/ns/ttml/profile/ttml2-full
>> http://www.w3.org/ns/ttml/profile/ttml2-presentation
>> http://www.w3.org/ns/ttml/profile/ttml2-transformation
>>
>> for the following URI, coukld you please fix it, as it is a 404.
>> http://www.smpte-ra.org/schemas/2052-1/2013/smpte-tt#cea608 (1 occurrence)
>
> That's a SMPTE "problem" (if you think that non-resolvable namespace URIs
> is a problem):

It could have been a URL typo, like a wrong copy/paste.

But in fact, it is not:  I see it is mention here by SMPTE:
https://www.smpte.org/sites/default/files/RP2052-10-2013.pdf

So youa re right, we have no control on this SMPTE resource, and it 
seems SMPTE does dereference their namespace URI.

I will inform the webmaster about this issue.

Thierry
>
> 	
> 		
> 		
> 	
> 	
> 		
> 			
> 				
> 					
> 						http://www.smpte-ra.org/schemas/2052-1/2010/smpte-tt
>
> 					
> 				
> 			
> 		
> 	
> is referenced from
> https://www.smpte.org/sites/default/files/st2052-1-2010.pdf but gives a
> 404. I'm not sure what's to be done about that.
>
>
> Similarly
>
> 	
> 		
> 		
> 	
> 	
> 		
> 			
> 				
> 					
> 						http://www.smpte-ra.org/schemas/2052-1/2010/smpte-tt#cea608
>
> 					
> 				
> 			
> 		
> 	
> is referenced from SMPTE RP 2052-10:2012 but gives a 404.
>
>
> By the way, the reference in the FPWD for conversion from CEA708 is to
> SMPTE 2052-11, whose namespace is listed on page 6 as
>
> http://www.smpte-ra.org/schemas/2052-1/2013/smpte-tt#cea708
>
> i.e. a different fragment identifier - it still isn't resolvable.
> 					
> 				
> 			
> 		
> 	
>
>
>
> Can we proceed with a non-resolvable namespace URI?
>
>
>
>>
>> Once I get your updated ttml2 draft, I will request publication for the
>> 10th.
>>
>>
>> Thanks,
>>
>> Thierry.
>>
>>
>> 2- The Namespaces Checker reports broken namespace URIs.
>> Note: If they are not namespace URIs, we should just let the Webmaster
>> know in our publication request.
>> Let me know if you want me to put some kind of wording as a place holder
>> in these URLs:
>>
>> http://www.w3.org/ns/ttml/profile/ttml2-full (1 occurrence)
>>      -> 404 (Not Found)
>> http://www.w3.org/ns/ttml/profile/ttml2-presentation (4 occurrences)
>>      -> 404 (Not Found)
>> http://www.w3.org/ns/ttml/profile/ttml2-transformation (3 occurrences)
>>      -> 404 (Not Found)
>> http://www.smpte-ra.org/schemas/2052-1/2013/smpte-tt#cea608 (1 occurrence)
>>      -> 404 (Not Found)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On 05/02/2015 09:44, Thierry MICHEL wrote:
>>> Glenn,
>>>
>>> Thank you for the TTML2 Zip package.
>>>
>>> I have now uploaded the files to final destination at
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/
>>>
>>> In order to have a document that fullfils Pubrules, I have done the
>>> following changes to the document:
>>> - Changed date to "10 February 2015"
>>> - Changed "this version" URL to
>>>       http://www.w3.org/TR/2015/WD-ttml2-20150210/
>>> - Changed the "previous version" to "none"
>>> - Added "Latest TTML1 Recommendation version" and URL
>>> - Added boilerplate text in the status section to identify the governing
>>> process:
>>> <p>This document is governed by the <a id="w3c_process_revision"
>>> href="http://www.w3.org/2014/Process-20140801/">1 August 2014 W3C
>>> Process Document</a>.</p>
>>>
>>>
>>> The document conforms to
>>> - HTML validator
>>> - CSS validator
>>>
>>>
>>> There are issues whith broken links and  namespace URIs which must be
>>> fixed before publication.
>>> Please update these (just send me an update Overview.html file) and then
>>> I will send the Publication request to the webmaster.
>>>
>>> 1-Broken links are listed at the end of this email and available with
>>> the linkchecker
>>>
>>> http://validator.w3.org/checklink?url=http://www.w3.org/TR/2015/WD-ttml2-
>>> 20150210/
>>>
>>>
>>> 2- The Namespaces Checker reports broken namespace URIs.
>>> Note: If they are not namespace URIs, we should just let the Webmaster
>>> know in our publication request.
>>> Let me know if you want me to put some kind of wording as a place holder
>>> in these URLs:
>>>
>>> http://www.w3.org/ns/ttml/profile/ttml2-full (1 occurrence)
>>>       -> 404 (Not Found)
>>> http://www.w3.org/ns/ttml/profile/ttml2-presentation (4 occurrences)
>>>       -> 404 (Not Found)
>>> http://www.w3.org/ns/ttml/profile/ttml2-transformation (3 occurrences)
>>>       -> 404 (Not Found)
>>> http://www.smpte-ra.org/schemas/2052-1/2013/smpte-tt#cea608 (1
>>> occurrence)
>>>       -> 404 (Not Found)
>>>
>>>
>>> Best,
>>>
>>> Thierry.
>>>
>>> --------------------------------------------------------
>>> Following are broken links repported by the linkchecker:
>>> --------------------------------------------------------
>>>
>>>    Line: 6893
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/procedure-associate-region
>>>       Status: 404 Not Found
>>>
>>> The link is broken. Double-check that you have not made any typo, or
>>> mistake in copy-pasting. If the link points to a resource that no longer
>>> exists, you may want to remove or fix the link.
>>> error Line: 90 http://www.w3.org/TR/ttml2/
>>>       Status: 404 Not Found
>>>
>>>       The link is broken. Double-check that you have not made any typo,
>>> or mistake in copy-pasting. If the link points to a resource that no
>>> longer exists, you may want to remove or fix the link.
>>> error Lines: 89, 785, 805, 874, 936, 937, 996, 1233, 1238, 1244, 1388,
>>> 1391, 1394, 1400, 1401, 1402, 1405, 1406, 1409, 1411, 1413, 1414, 1417,
>>> 1418, 1421, 1423, 1426, 1446, 1458, 1459, 1460, 1461, 1469, 1477, 1523,
>>> 1527, 1528, 1532, 2251, 2258, 2260, 2262, 2269, 2277, 2278, 2279, 2312,
>>> 3111, 3305, 3312, 3386, 3398, 3559, 3567, 3574, 3576, 3695, 3721, 3765,
>>> 4041, 4042, 6381, 6705, 6822, 8167, 8168, 9037, 9040, 9837, 9840, 10263
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/
>>>       Status: 200 OK
>>>
>>>       Some of the links to this resource point to broken URI fragments
>>> (such as index.html#fragment).
>>>       Broken fragments:
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#data-vocabulary-source
>>> (line 1461)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#terms-data-definition-contex
>>> t
>>> (line 805)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#document-structure-vocabular
>>> y-resources
>>> (line 3721)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#contentt-vocabulary-p (line
>>> 3576)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#parameter-attribute-contentP
>>> rofiles
>>> (line 1233)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#data-vocabulary-font (lines
>>> 1469, 1532)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#data-vocabulary-audio
>>> (lines 1446, 1527)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#data-vocabulary-data (lines
>>> 1458, 1459, 1523)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#parameter-attribute-processo
>>> rProfiles
>>> (lines 1238, 1244)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#terms-inferred-processor-pro
>>> file
>>> (lines 1388, 1391, 1394)
>>>           http://www.w3.org/TR/2015/WD-ttml2-20150210/#viewport (line
>>> 996)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#layout-vocabular-region
>>> (line 6381)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#data-vocabulary-resources
>>> (line 1460)
>>>           http://www.w3.org/TR/2015/WD-ttml2-20150210/#non-content-image
>>> (line 4041)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#data-vocabulary-image
>>> (lines 1477, 1528)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#bound-parameter-steroLeft
>>> (line 8167)
>>>           http://www.w3.org/TR/2015/WD-ttml2-20150210/#content-image
>>> (line 4042)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#terms-default-processor-prof
>>> ile
>>> (lines 1400, 1402, 1406, 1409, 1414, 1418, 1421, 1426, 2312)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#terms-validating-content-pro
>>> cessor
>>> (lines 2251, 2258, 2260, 2262, 2269, 2277, 2278, 2279)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#bound-parameter-steroRight
>>> (line 8168)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#terms-image-definition-conte
>>> xt
>>> (line 874)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#terms-conditionalized-elemen
>>> t
>>> (line 3111)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#terms-intermediate-synchroni
>>> c-document-syntax
>>> (line 9837)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#animation-vocabulary-styling
>>> (line
>>> 6822)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#contentt-vocabulary-div
>>> (line 3574)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#terms-intermediate-synchroni
>>> c-document-sequence-syntax
>>> (line 9840)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#contentt-vocabulary-span
>>> (line 3576)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#terms-embedded-content-resou
>>> rce
>>> (line 3695)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#terms-embedded-data-element
>>> (line 3765)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#terms-audio-definition-conte
>>> xt
>>> (line 785)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#presentation-viewport (line
>>> 936)
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#parameter-attribute-version
>>> (lines 1401, 1405, 1411, 1413, 1417, 1423, 6705, 9037, 9040, 10263)
>>>           http://www.w3.org/TR/2015/WD-ttml2-20150210/#authoring-viewport
>>> (line 937)
>>>
>>>
>>> http://www.w3.org/TR/2015/WD-ttml2-20150210/#embedded-content-vocabulary-
>>> resource
>>> (lines 3305, 3312, 3386, 3398, 3559, 3567)
>>>
>>> info Line: 122 mailto:public-tt-request@w3.org?subject=subscribe
>>>       Status: (N/A) Access to 'mailto' URIs has been disabled
>>>
>>>       Accessing links with this URI scheme has been disabled in link
>>> checker.
>>> info Line: 121 mailto:public-tt@w3.org
>>>       Status: (N/A) Access to 'mailto' URIs has been disabled
>>>
>>>       Accessing links with this URI scheme has been disabled in link
>>> checker.
>>> error Lines: 10105, 10107 http://dev.w3.org/csswg/css-ruby-1/
>>>       Status: 500 read timeout
>>>
>>>       This is a server side problem. Check the URI.
>>> error Lines: 3540, 10099, 10100 http://dev.w3.org/csswg/css-fonts/
>>>       Status: 500 read timeout
>>>
>>>       This is a server side problem. Check the URI.
>>>       Broken fragments:
>>>
>>>           http://dev.w3.org/csswg/css-fonts/#font-face-loading (line
>>> 3540)
>>>
>>> error Lines: 10096, 10097 http://dev.w3.org/csswg/css-box-3/
>>>       Status: 500 read timeout
>>>
>>>       This is a server side problem. Check the URI.
>>> error Lines: 10115, 10116 http://dev.w3.org/csswg/css-writing-modes-3/
>>>       Status: 500 read timeout
>>>
>>>       This is a server side problem. Check the URI.
>>>
>>> ------------------------------------------
>>
>
Received on Friday, 6 February 2015 09:47:22 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:20 UTC