W3C home > Mailing lists > Public > www-rdf-interest@w3.org > October 2003

AW: Attaching (embedding?) RDF

From: Bodo Hüsemann <huesemann@wi.uni-muenster.de>
Date: Tue, 28 Oct 2003 18:11:49 +0100
Message-ID: <D55E4D0E96DDF64E810B2845DD5573D11869C5@wi-mail1.wi1.uni-muenster.de>
To: "Martin May" <maym@foobar.lu>
Cc: <www-rdf-interest@w3.org>, "Damian Steer" <pldms@mac.com>

I think in this direction it is also worth to mention WebDAV, which is platform-independent, web-based and can also save user-defined metadata with files. I think you essentially save attribute value pairs within webdav, but it could be useful nevertheless. Either you try a mapping or just try to use it as a container...

Regards,
Bodo



-----Ursprüngliche Nachricht-----
Von: Martin May [mailto:maym@foobar.lu] 
Gesendet: Dienstag, 28. Oktober 2003 13:27
An: Damian Steer
Cc: www-rdf-interest@w3.org
Betreff: Re: Attaching (embedding?) RDF



You're right, that's a very viable option that I forgot to mention. I've looked 
into this a bit, and indeed HFS (and HFS+) support metadata, although I am not 
sure whether it can be arbitrary.

NTFS must support it somehow, since that's what Microsoft will build WinFS on 
(a metadata-enable file store).

I think that using a technique like this would have the great benefit of being 
completely transparent, which is always nice. However, what happens when the 
file is moved outside of the filesystem (i.e. via FTP)?

Regards,

Martin

Quoting Damian Steer <pldms@mac.com>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Martin May <maym@foobar.lu> writes:
> 
> > I would like to attach RDF metadata to files. So far I have identified
> > the following options for doing so, all of which have drawbacks:
> >
> 
> > 4. create an archive file which groups the file and its metadata
> > (e.g. jar)
> >
> 
> One option you didn't mention, related to 4, is to put the rdf
> together with the data in the file, which some filesytems support. HFS
> and HFS+ on the Mac have two parts to a file - the data fork (what one
> normally thinks of as the content) and the resource fork (arbtrary
> collection of things like icons, etc). Similarly NTFS has streams,
> although only viruses seem to use them IME, and Reiser 4 has something
> like this, IIRC. No doubt there are other examples.
> 
> These features were implemented to facilitate exactly the behaviour
> you want, associating metadata with inodes, but I appreciate that it
> might not be a practical solution for you. Just thought it was worth
> mentioning.
> 
> Damian
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (Darwin)
> Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
> 
> iD8DBQE/nl7NAyLCB+mTtykRAm1DAKDDDUAVlsLa3EKVdRBlC/6B2RSedQCgsK6w
> MNLIP3KElrMSrA0Rfyd1wX8=
> =xaGK
> -----END PGP SIGNATURE-----
> 
> 




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
Received on Tuesday, 28 October 2003 12:13:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:52:02 GMT