W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > January 2002

Re: TAG issues during technical plenary

From: Patrick Stickler <patrick.stickler@nokia.com>
Date: Tue, 22 Jan 2002 09:46:58 +0200
To: ext Brian McBride <bwm@hplb.hpl.hp.com>, RDF Core <w3c-rdfcore-wg@w3.org>
Message-ID: <B872E592.C060%patrick.stickler@nokia.com>

Very good questions, and all very much needing answers ASAP.

I would include in your list some questions regarding distinctions
between digital (web) resources and non-digital (including abstract)

C.f. my thoughts on this in



  o Should there be a formal distinction between digital (web-accessible)
    and non-digital (non-web-accessible) resources?

  o What does a URI Reference denote (if anything) for a non-digital

And then regarding namespaces (presuming you mean XML Namespaces):

  o What is the relation between a namespace, a vocabulary, and a
    content model?

This question is based on the assertion that a namespace does
not equate to either a vocabulary or content model (contrary to
popular use and common misconception) and it would be very good
for the W3C to state this explicitly. A namespace is just
punctuation; a prefix to achieve globally distinct partitions
of name spaces. The affiliation of specific namespace URIs
with specific vocabularies, ontologies, schemas, and content
models leads to alot of confusion and "hacks" wihch are not
grounded on the actual specifications.

Also, is it necessary to specifically mention or include the
HTTP protocol? Do we not wish the foundational model for resources
and URIs to be independent of protocol? Or are your questions
only concerned with 'http:' URIs?



On 2002-01-21 21:48, "ext Brian McBride" <bwm@hplb.hpl.hp.com> wrote:

> I received the message below from a member of the new Technical
> Architecture Group.
> I'm thinking of sending a response along the lines of:
> I would like the TAG to define the foundations of the architecture of the
> web.  The concept of a resource is fundamental to web architecture, yet it
> is very hard to pin down exactly what it means and how it relates to the
> concepts of URI, URI reference and namespace.  I suggest the TAG publish a
> W3C recommendation containing a description and a formal model explaining:
>  o what is a resource
>  o How URI's relate to resources (e.g. can the same resource
>    be named by more than one URI)
>  o what is named by a URI reference and how does this relate to resources
>  o what is a namespace and how do the names within it relate to URI's and URI
>    references
>  o the operation of the http protocol within the context of this model.
> I would welcome comments on the above and other suggestions in response to
> the TAG's request.  I can respond with either a suggestion from the WG as a
> whole, or with a collection of suggestions from individual members of the WG.
> Brian
>> Dear chairs,
>> The TAG requests your assistance in two matters.  Firstly, the TAG solicits
>> your input on topics that the TAG should address.  The TAG has the charter
>> to publish recommendations on issues.  We believe in surveying a wide
>> spectrum of parties for issues to address, and your help would be
>> appreciated.  Secondly, some members of the TAG also believe that the TAG
>> should provide artifacts/documents that provide context for Recommendations.
>> One example of the context is an architecture document with various text and
>> diagrams.  The TAG solicits your input on what forms of context would be
>> useful to you.
>> The technical plenary agenda [1] has a portion of time for the TAG.  We
>> would like to present information on our documentation deliverables and
>> issues list during the session, so your feedback sufficiently before then
>> would be much appreciated.
>> Cheers,
>> Dave Orchard
>> [1] http://www.w3.org/2001/07/Plenary/Agenda.html

Patrick Stickler              Phone: +358 50 483 9453
Senior Research Scientist     Fax:   +358 7180 35409
Nokia Research Center         Email: patrick.stickler@nokia.com
Received on Tuesday, 22 January 2002 04:40:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:24:08 UTC