W3C home > Mailing lists > Public > www-rdf-comments@w3.org > July to September 2001

Re: some questions on RefactoringRDF draft

From: Dave Beckett <dave.beckett@bristol.ac.uk>
Date: Thu, 13 Sep 2001 12:28:06 +0100
To: Roland Schwaenzl <Roland.Schwaenzl@mathematik.Uni-Osnabrueck.DE>
cc: bwm@hplb.hpl.hp.com, www-rdf-comments@w3.org
Message-ID: <31829.1000380486@tatooine.ilrt.bris.ac.uk>
>>>Roland Schwaenzl said:
> Brian McBride said:
> > Where did you see a suggestion that typed nodes needed to be prefixed?
> > Maybe we can make this more clear there.
> 
> This seems to be implied by the revised EBNF table 3.1 rule 6.19 

That is why we are not going to continue to use that exact format in
the EBNF to be the definitive syntax.  That format cannot capture
that there is an assocation between an XML element and a namespace
which is EITHER by a default in-scope XML namespace OR an explict
namespace on the XML element.  It is too specific on the mechanism.

In other words, ignore the earlier sections which are for recording
the process of modifying and consider section 4 as an indication of
what will be the kind of thing we will be using.  The XML Infoset
allows the association above to be defined but without specifying the
particular mechanism as to how that is provided by XML, which is the
business of the XML specifications and interfaces (e.g DOM, SAX), not
RDF.

<snip/>

> How an RDF processor is supposed to handle 4.18 ?? ...again a
> question about processing, sorry.

This work-in-progress clearly states that what happens after the
syntax matches, and and what statements should be emitted is the next
step in the process of evolving this document. From the Introduction:

  This process is not yet complete, in that the final step is
  defining for each syntax production which RDF statements are added
  to the resulting model (if any).
  -- http://www.w3.org/TR/2001/WD-rdf-syntax-grammar-20010906/#section-Introduction

However, I suspect that what happens to processing other parseTypes
is going to be entirely application dependent.  In this case, all we
can do is encourge APIs and applications to provide a suitable
interface to the content of the element.

Dave
Received on Thursday, 13 September 2001 07:31:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 21 September 2012 14:16:28 GMT