Re: Small @profile question

On that note, might I suggest adding the following text (or similar) to 
rule 2 of the profile URI processing rules.

<ins>If the complete document cannot be successfully parsed as an RDFa 
document then continue with the next URI in the value.</ins>

Regards,

Nathan

Ivan Herman wrote:
> Hm. I have difficulties to go down that route. I wonder whether we should really care about such a situation.
> 
> That being said, one outcome of this thread is the possibility to expand Jeni's law to any possible error situation that would happen in a profile file and not only for the case when the file is not reachable. Any thoughts on that? 
> 
> Ivan
> 
> On Sep 14, 2010, at 15:57 , Toby Inkster wrote:
> 
>> On Tue, 14 Sep 2010 09:27:26 +0200
>> Ivan Herman <ivan@w3.org> wrote:
>>
>>> On Sep 14, 2010, at 09:15 , Toby Inkster wrote:
>>>
>>>> This situation could occur if the server hosting the profile serves,
>>>> say, an error response (e.g. Not Found) with an incorrect HTTP
>>>> status code.  
>>> Hm. I do not think I agree with your last statement, though I agree
>>> with the rest. An HTTP not found should mean the file is not loadable
>>> so the 'no triple generated' feature should kick in.
>> I agree that an HTTP not found *should* do that, but the situation I
>> outlined is where a "Not Found" or similar error page has been served
>> with an incorrect HTTP status code - such as 200 OK. One does see such
>> things from time to time - mainly on sites with poorly written content
>> management systems.
>>
>> -- 
>> Toby A Inkster
>> <mailto:mail@tobyinkster.co.uk>
>> <http://tobyinkster.co.uk>
>>
> 
> 
> ----
> Ivan Herman, W3C Semantic Web Activity Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> PGP Key: http://www.ivan-herman.net/pgpkey.html
> FOAF: http://www.ivan-herman.net/foaf.rdf
> 
> 
> 
> 
> 

Received on Wednesday, 15 September 2010 21:54:16 UTC