W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > September 2001

2001-09-21#11 parseType qnames

From: Bill de hOra <bdehora@interx.com>
Date: Tue, 25 Sep 2001 15:55:38 +0100
To: <w3c-rdfcore-wg@w3.org>
Message-ID: <000001c145d2$23e82670$1c010a0a@MITCHUM>

action: "2001-09-21#11: Bill DeHora / Take proposal to the list next
week on parseType Qnames"

The text below is a revision from
(action 2001-09-07#5). The goals are to legitimise the use of namespaced
parseType extensions and clarify text surrounding XML literals,
particularly M&S p203 in a backward compatible fashion. The text doesn't
saying anything about XML literal encoding, that's being dealt with
, simply that rdf xml literals must be wf xml.


Bill de hÓra
bdehora at interx.com 
dehora at acm.org 

proposed text:

(p1) The parseType attribute changes the interpretation of its element

(p2) The parseType attributes values defined are 'Literal' and
'Resource'. These values are case-sensitive. The value 'Literal'
specifies that the element content SHALL be treated as an RDF XML
literal. The element content is considered opaque: that is, it MUST not
be interpreted or passed on as RDF by the RDF processor in question. The
value 'Resource' specifies that the element content SHALL be treated as
if it were the content of a Description element. Further, content of an
element having a parseType="Resource" attribute MUST match the
production for Description. In all cases, the content of an element
having a parseType attribute MUST be well-formed XML in accordance with
the XML Recommendation [see 1 section 2].

(p3) It is recognized that parseType is useful as an extensibility
mechanism. The preferred technique to extend parseType is through the
use of namespace qualified names, as defined in the Namespaces In XML
Recommendation [2]. The purpose of using namespaces to denote parseType
values is to allow extensions to be associated with a vocabulary or
schema, and to avoid naming collisions between extensions. Note:
irregardless of the intended interpretation of any such extended
parseType, the element content itself MUST be at minimum well-formed

(p4) In the same sense that the XML Namespaces notion of the default
namespace does not apply to XML attributes [see 2, section 5.2], the
default namespace is not applicable to RDF parseType values. Unqualified
values of parseType MUST NOT considered to be in any namespace.

(p5) Namespace unqualified values of parseType are reserved for use by

(p6) How XML attributes which affect the interpretation of RDF XML
Literals are passed along by RDF processors is not specified: this
includes extended values of parseType. Processors which encounter
extended parseType values MAY pass on the found parseType value, where
they are capable of doing so. An RDF-XML processor encountering an
unrecognised extension of parseType value MUST default to treat that
parseType value as 'Literal'. 

[1] <http://www.w3.org/TR/2000/REC-xml-20001006>
[2] <http://www.w3.org/TR/1999/REC-xml-names-19990114>

Received on Tuesday, 25 September 2001 10:57:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:51 UTC