W3C home > Mailing lists > Public > www-tag@w3.org > September 2003

RE: Arch Doc: 26 September 2003 Editor's Draft

From: David Orchard <dorchard@bea.com>
Date: Mon, 29 Sep 2003 16:59:49 -0700
To: "'Roy T. Fielding'" <fielding@apache.org>, "'Tim Bray'" <tbray@textuality.com>
Cc: "'Ian B. Jacobs'" <ij@w3.org>, <www-tag@w3.org>
Message-ID: <02aa01c386e5$c53fa060$470ba8c0@beasys.com>


Why did you change from descriptive links to descriptive metadata?  My poor
brain starts to hurt when a link is either a link or metadata.  Why not keep
as hypertext links and descriptive links?

While you answered a number of my earlier questions in various emails to
other people, you didn't answer the question about whether web service
references, such as <callback location="mycallbackserviceuri"/> is a
hypertext link or a different kind of link.


> -----Original Message-----
> From: www-tag-request@w3.org
> [mailto:www-tag-request@w3.org]On Behalf Of
> Roy T. Fielding
> Sent: Monday, September 29, 2003 4:26 PM
> To: Tim Bray
> Cc: Ian B. Jacobs; www-tag@w3.org
> Subject: Re: Arch Doc: 26 September 2003 Editor's Draft
> > Huh?  Resources are indeed connected by hypertext links,
> but *also*,
> > you are saying, by "descriptive metadata"?  I may not
> understand what
> > you mean but I think I disagree with what this actually says.  We
> > could either (a) try to find something else to say about
> metadata or
> > (b) just stop after the word "links", losing "and descriptive
> > metadata".
> For example, <foo xmlns="http://www.tbray.org/"> is
> descriptive metadata, not a hypertext link.  The reason I didn't
> say just "links" instead of "hypertext links and descriptive metadata"
> is because the latter makes people think a little harder rather than
> assuming all links are hyperlinks.
> ....Roy
Received on Monday, 29 September 2003 20:06:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:32:39 UTC