Re: RDF-In-XHTML; A "New" Approach

The scraper looks for a profile to know how to deal with a page. If it can't
find one in the page, then it could look for metadata taht has been provided
(we don't have a standard mechanism for that yet, and if we did it would
likely be by dereferencing the supplied profile URI). After that it is stuck.

What I am suggesting is that as we are  starting to develop multile tools for
scraping differnt information from one page, we should think about how to use
the profile so it works to support this. I am not convinced that a
space-seperated list of URIs is a good solution, although it has the benefiot
of not requiring out of line information.

CHaals

On Fri, 31 Aug 2001, Seth Russell wrote:

  From: "Charles McCathieNevile" <charles@w3.org>

  > There is also the question of how to use multiple profiles, which we are
  > getting into needing a solution for.

  I'm probably not understand the details of this but that shouldnt stop me
  from blue skying anyway ....

  Doesn't the profile basically specify how the page is to be scraped ?  So
  doesn't it flow through a decision sive like:

  1) is profile provided by author on page? ... use that one
  2) is profile provided by surfer? ... use that one
  3) is profile provided by groupOf(surfer)? ... use that one
  3) is profile specified for profileFn(document type)? ... use that one
  4) otherwise default to the most general profile

  Based on (3) this we wouldnt need to limit ourselves to Xhtml ... of course
  then we probably couldnt use XSLT .. but shucks we could just use a script.

  ?
  Seth



-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)

Received on Saturday, 1 September 2001 23:18:28 UTC