| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 00:22:44 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 18:20:37 GMT
cache-control: max-age=2592000, public
expires: Sun, 09 Nov 2025 20:52:59 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98c9012e78708626
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
set-cookie: __cf_bm=9UMPxj4h1dQw_XqbhHV_CWepIjvrH0nf58j.LtjZVbw-1760142164-1.0.1.1-DaumAwiMse9sLyjysjF_tIrkpwykOMFnTn_NmuksJjMmDtmkqjJmP.3ti..QR0PcMGIRBO2YS__eNYFuxAkDt4.H1vyxdT1.vrAQREYEmnI; path=/; expires=Sat, 11-Oct-25 00:52:44 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98ca346b0a3d1f95-BLR
alt-svc: h3=":443"; ma=86400
Formal Objection: overly-complex datatypes solution from Aaron Swartz on 2003-01-17 (w3c-rdfcore-wg@w3.org from January 2003)
Formal Objection: overly-complex datatypes solution
- From: Aaron Swartz <me@aaronsw.com>
- Date: Fri, 17 Jan 2003 08:48:15 -0600
- To: RDF Core <w3c-rdfcore-wg@w3.org>
- Message-Id: <B5A42A55-2A2A-11D7-8E57-0003936780B2@aaronsw.com>
I object to the proposed datatypes solution. It is overly-complex, requiring RDF processors to understand a large system of datatypes and their relations. (It also has many edge-cases that are likely to cause more of the problems and incompatibilities this WG was chartered to fix.) It is backwards-incompatible, requiring all software with RDF data structures to be changed. I support the rdfs:format datatypes proposal of Dan Connolly: https://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2002Oct/0031.html It is simple, elegant, and fully backwards-compatible. I also support the null datatypes proposal. -- Aaron Swartz [https://www.aaronsw.com/]
Received on Friday, 17 January 2003 09:48:24 UTC