| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 20:42:34 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 18:28:49 GMT
cache-control: max-age=2592000, public
expires: Sun, 09 Nov 2025 09:38:15 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98c524d0c8ea352d
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=8sY0gvuV2CpY3Lk_WwiBNTBjlg.YC.yt_VCG6AICV7I-1760128954-1.0.1.1-RFlbzpGDTalVtBWhQT1HP5WxULWwyq7_lJLxLCoVzmW9Ed_P9SiySQVjhaDZbfLBtXEMw2ic9AzpsTBGaFc98czG8wAooKdQLX4nbAdCptA; path=/; expires=Fri, 10-Oct-25 21:12:34 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c8f1e7cbd175e9-BLR
alt-svc: h3=":443"; ma=86400
Proposal for clarification of RDF from Rick Jelliffe on 2001-06-20 (www-rdf-comments@w3.org from April to June 2001)
Proposal for clarification of RDF
- From: Rick Jelliffe <ricko@allette.com.au>
- Date: Wed, 20 Jun 2001 22:22:42 +0800
- To: <www-rdf-comments@w3.org>
- Message-ID: <00aa01c0f994$7839bde0$d2c8a8c0@allette.com.au>
See attached a proposal for clarifying the syntax of RDF. I have found it extremely difficult to pin down RDF's syntax from its specs. The reasons are well-known: the treatment of namespace, etc. To overcome these, here is a concrete and straight-forward proposal which brings RDF back into mainstream XML usage, and yet retains compatability (as far as I am aware) with existing specifications. The proposal is in the form of a DTD and certain conventions. Cheers Rick Jelliffe C.T.O. Topologi Pty. Ltd. https://www.topologi.com Invited Expert, W3C I18n IG Invited Expert (former WG member), W3C XML Schemas IG Former member, XML Schemas Group.
Attachments
- text/html attachment: rdf-clear.xhtml
Received on Wednesday, 20 June 2001 08:26:43 UTC