Re: Publication problem with RDF 1.1 semantics document?

That request's result depends on the Referer header. If the Referer is a PR/CR/WD, the service returns a small JSON response with a URL to the new location. The fixup.js script then displays a popup with that link. Otherwise, the service returns 404, and fixup.js doesn’t display a popup. AFAICT that all works as designed.

Richard



> On 28 May 2018, at 13:16, Stefan Schumacher <stefan@duckflight.de> wrote:
> 
> Hello,
> 
> I see request.open in that page that returns an 404 error.
> www.w3.org/scripts/TR/fixup.js
> request.open('GET', '//www.w3.org/TR/tr-outdated-spec');
> 
> Maybe that script does not get the right path.
> 
> Sorry for keeping the buzz alive ;-)
> Stefan
> 
> Am 28.05.2018 um 16:43 schrieb Richard Cyganiak:
>> There is a bit of JS in all documents that asks a service whether the document is outdated. If the service answers yes, then the big red popup message appears. This is supposed to happen for all the WDs, CRs, PRs, but not for the rdf-mt REC which already has the yellow warning in the document itself.
>> 
>> The service seems to be working fine, but maybe a response from the service got stuck in a cache somewhere, so that an inappropriate response got used on some requests.
>> 
>> One of those mysteries.
>> 
>> Richard
>> 
>> 
>> 
>>> On 28 May 2018, at 11:59, Graham Klyne <gk@ninebynine.org> wrote:
>>> 
>>> Maybe my local browser cache, or something, is screwed up.  It happens sometimes.
>>> 
>>> I just tried a different browser following the errata page link, and it was fine.
>>> 
>>> So, too, is the original browser now.
>>> 
>>> Also strange is that if I now go to the old 1.0 semantics page, I get a document with a warning about being superseded, but completely differently formatted - I was previously getting a big red flash message, with the page content was greyed out.  All very puzzling.
>>> 
>>> Sorry for the noise.
>>> 
>>> #g
>>> --
>>> 
>>> 
>>> On 28/05/2018 11:46, Richard Cyganiak wrote:
>>>> 
>>>> 
>>>>> On 28 May 2018, at 10:52, Ivan Herman <ivan@w3.org> wrote:
>>>>> 
>>>>> I am not what is happening: I have looked at the file from two different browser on my machine, made a forced reload (and I have just changed my primary browser, ie, I do not think I have used this browser before to look at this file) and everything seems to be fine…
>>>>> 
>>>>> Anybody else experiences this?
>>>> 
>>>> Works fine for me too. I had a look at the JS code and HTTP interaction that generate this warning, and they seem to work fine. I have no explanation for the phenomenon that Graham sees.
>>>> 
>>>> Richard
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>> Ivan
>>>>> 
>>>>>> On 28 May 2018, at 05:45, Graham Klyne <gk@ninebynine.org <mailto:gk@ninebynine.org>> wrote:
>>>>>> 
>>>>>> I think there's a problem with the web publication of
>>>>>> 
>>>>>> http://www.w3.org/TR/2014/REC-rdf11-mt-20140225/ <http://www.w3.org/TR/2014/REC-rdf11-mt-20140225/>
>>>>>> 
>>>>>> I get an overlkay message "This version is outdated!
>>>>>> For the latest version, please look at http://www.w3.org/TR/rdf-mt/ <http://www.w3.org/TR/rdf-mt/>."
>>>>>> 
>>>>>> (Which, ironically, is pointing to the older version)
>>>>>> 
>>>>>> 
>>>>>> I get this even when I follow the link from:
>>>>>> 
>>>>>> https://www.w3.org/2001/sw/wiki/RDF1.1_Errata <https://www.w3.org/2001/sw/wiki/RDF1.1_Errata>
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> It's OK if I go to this link:
>>>>>> 
>>>>>> http://www.w3.org/TR/rdf11-mt/ <http://www.w3.org/TR/rdf11-mt/>
>>>>>> 
>>>>>> #g
>>>>>> 
>>>>> 
>>>>> 
>>>>> ----
>>>>> Ivan Herman, W3C
>>>>> Publishing@W3C Technical Lead
>>>>> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
>>>>> mobile: +31-641044153
>>>>> ORCID ID: https://orcid.org/0000-0003-0782-2704 <https://orcid.org/0000-0003-0782-2704>
>>>>> 
>>>> 
>>>> 
>>> 
>> 
>> 
>> 
>

Received on Monday, 28 May 2018 12:58:04 UTC