| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 06:00:30 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 18:29:24 GMT
cache-control: max-age=2592000, public
expires: Sat, 08 Nov 2025 06:00:30 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98bba87739d9cb77
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: EXPIRED
set-cookie: __cf_bm=8nD8ns5UDpS3.GFyS1ACud7huU1Fq4e6yxvhptM975E-1759989630-1.0.1.1-c2g_FagCWr5JmATtdw0qd.gkP1a7qn8SYOTO_UrqXCDiNyEZuQNeeUQ092FIic.4iJY896mpW6AvFWiZavW9Df19BEUeKcN83g7EvDnc.V4; path=/; expires=Thu, 09-Oct-25 06:30:30 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bba87739d9cb77-BLR
alt-svc: h3=":443"; ma=86400
Re: Undeclared prefix in @datatype -- what happens? from Damian Steer on 2009-08-26 (public-rdf-in-xhtml-tf@w3.org from August 2009)
Re: Undeclared prefix in @datatype -- what happens?
- From: Damian Steer <pldms@mac.com>
- Date: Wed, 26 Aug 2009 20:17:51 +0100
- To: Richard Cyganiak <richard@cyganiak.de>
- Cc: RDFa <public-rdf-in-xhtml-tf@w3.org>
- Message-id: <989721D9-17B0-422C-90C2-A58BCDC703B4@mac.com>
On 26 Aug 2009, at 19:12, Richard Cyganiak wrote: > All, > > One of the more iconic RDFa-enabled pages on the Web is this one: > https://www.myspace.com/parishilton > > As has been pointed out before, it's slightly broken, because the > xsd: namespace is used in @datatype, but undeclared in the document. > > Now I wonder what a conformant RDFa parser should do when confronted > with an undeclared namespace in @datatype? Ignore the triple? Ignore > the @datatype? Assume the empty string as prefix URI? Halt and catch > fire? fwiw, my vote is for ignoring the triple. Producing a wonky literal is simply annoying. Halting doesn't seem to be in the spirit of RDFa. However in practice I'd assume the xml schema namespace and repair it. Damian
Received on Wednesday, 26 August 2009 19:18:40 UTC