CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 07:28:47 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 18:28:48 GMT
cache-control: max-age=2592000, public
expires: Sat, 08 Nov 2025 06:05:12 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98bbaf596b41eb53
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=tO7S_vXT9BcsCz0_g9ljmMq5PFUqeL_m6m0eoFj9B.A-1759994927-1.0.1.1-ta5k8jKXZ.4NCY9_ynycjfVwlYRoW2tKtJBzPt68O8ypHZ.uJOhRh.tij42Dsy4m7wg6.T.mhg0k5sVz27B7nI8dZMc7IYWWSn56pSKA9UA; path=/; expires=Thu, 09-Oct-25 07:58:47 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bc29c63d7ec469-BLR
alt-svc: h3=":443"; ma=86400
rdf:resource="..." vs. resource="..." from Dan Connolly on 2000-04-26 (www-rdf-comments@w3.org from April to June 2000)
rdf:resource="..." vs. resource="..."
- From: Dan Connolly <connolly@w3.org>
- Date: Wed, 26 Apr 2000 05:12:05 -0500
- To: www-rdf-comments@w3.org
- Message-ID: <3906C0F5.B563EBC6@w3.org>
I'm working on an XSLT-base RDF parser[1]. I got thru 2.2.1. Basic Serialization Syntax just fine, including: [9] resourceAttr ::= 'resource="' URI-reference '"' -- https://www.w3.org/TR/1999/REC-rdf-syntax-19990222 but then in 2.2.2. Basic Abbreviated Syntax I see this example using rdf:resource=, rather than resource=: <rdf:RDF> <rdf:Description about="https://www.w3.org/Home/Lassila"> <s:Creator rdf:resource="https://www.w3.org/staffId/85740"/> </rdf:Description> <rdf:Description about="https://www.w3.org/staffId/85740"> <v:Name>Ora Lassila</v:Name> <v:Email>lassila@w3.org</v:Email> </rdf:Description> </rdf:RDF> Is this supposed to give the same model as: <rdf:RDF> <rdf:Description about="https://www.w3.org/Home/Lassila"> <s:Creator resource="https://www.w3.org/staffId/85740"/> </rdf:Description> <rdf:Description about="https://www.w3.org/staffId/85740"> <v:Name>Ora Lassila</v:Name> <v:Email>lassila@w3.org</v:Email> </rdf:Description> </rdf:RDF> or as: <rdf:RDF> <rdf:Description about="https://www.w3.org/Home/Lassila"> <s:Creator> <rdf:Description resource="https://www.w3.org/staffId/85740"/> </s:Creator> </rdf:Description> <rdf:Description about="https://www.w3.org/staffId/85740"> <v:Name>Ora Lassila</v:Name> <v:Email>lassila@w3.org</v:Email> </rdf:Description> </rdf:RDF> If so, where is this specified? I looked hard, and I can't find it. If this idiom is intended to be a consequence of using XML namespaces, https://www.w3.org/TR/1999/REC-xml-names-19990114 it's not. See the last example under 5.3 Uniqueness of Attributes in particular. See also: Myth #4: Unprefixed attribute names are in XML namespaces https://www.xml.com/pub/2000/03/08/namespaces/myth1.html The same comment applies to about, ID, bagID, aboutEach, aboutEachPrefix, type, and perhaps the _1, _2, ... attributes. I suggest you define the general case to be the rdf:resource case, and specify that for rdf:Description, an unprefixed attribute called resource should be treated as rdf:resource. [1] https://www.w3.org/XML/2000/04rdf-parse/rdfp.xsl -- Dan Connolly, W3C https://www.w3.org/People/Connolly/
Received on Wednesday, 26 April 2000 06:13:43 UTC