[sc34wg3] Questions on N0396: (1) external information resources

[Lars Marius Garshol]

* Jan Algermissen
| 
| To be sure: can a topic map refer to the content of a <resourceData>
| element (that is part of an XTM document) as an information
| resource?

I'm not sure what you mean. Obviously it can: give it an ID, create a
URI that points to it, and then stick that in one of the locator
properties. I think you knew that already, but then I don't really
know what your question is.
 
| You also write "A locator is a string that references one or more
| information resources."
| 
| Why do you write 'one or more'?

It's possible to have locators that reference more than one resource.
HyTime definitely allows this, and for all I know URIs may, too.
 
| Is this addressing the issue of the HTTP indirection between a
| resource and its (possibly many) representations?

No, we've stayed clear of that. The SAM says that the interpretation
of locators is defined by the specifications that define the locator
notations.  

| Regarding the above: On the Web it is impossible to address an
| information resource, all you can address is a resource. The
| representations (= the information resources) that are the results
| of performing a GET/POST/HEAD on a resource may vary and statements
| made about them might become invalid (e.g. language of a document).
| 
| Is N0396 simply ignoring this issue (as most/all? of us silently do)?
 
It does, yes.
 
| Should we bother at all?

I can't think of any reason to try and solve the web's philosophical
problems in topic maps. Only the web can really do that.

-- 
Lars Marius Garshol, Ontopian         <URL: http://www.ontopia.net >
GSM: +47 98 21 55 50                  <URL: http://www.garshol.priv.no >