On Tuesday 20 February 2007 23:25:54 Mikkel Kamstrup Erlandsen wrote:
2007/2/20, Jos van den Oever [EMAIL PROTECTED]:
2007/2/20, Joe Shaw [EMAIL PROTECTED]:
Hi,
On Tue, 2007-02-20 at 20:52 +0100, Jos van den Oever wrote:
But reading, writing and searching metadata fields is
Sorry for the radio silence about Xesam, but I was on a 100% off line
vacation to Cyprus.
Anyway, I put up a brainstorming wiki page at:
http://wiki.freedesktop.org/wiki/XesamMetadataBrainstorm
I've already put some of my thoughts on it, so go go read it - or even
better put your own thoughts
On Thursday 08 March 2007 12:40:54 Mikkel Kamstrup Erlandsen wrote:
2007/3/8, Sebastian Trüg [EMAIL PROTECTED]:
On Wednesday 07 March 2007 21:13:19 Mikkel Kamstrup Erlandsen wrote:
From a technical standpoint I think rdf and ontologies are great, but
from
an application developers
Hi guys,
let me finally comment on this.
In the Nepomuk project we are defining metadata ontologies. This means that
each resource (a file is also a resource but Nepomuk does not only handle
files but all kinds of information entities on the desktop such as persons,
i.e. contacts, emails,
On Wednesday 07 March 2007 21:13:19 Mikkel Kamstrup Erlandsen wrote:
From a technical standpoint I think rdf and ontologies are great, but from
an application developers viewpoint they seem overly complex for most tasks
I could think of. Most things can be done if you just know a list of
Le mardi 20 février 2007, à 23:08, Mikkel Kamstrup Erlandsen a écrit :
2007/2/20, Vincent Untz [EMAIL PROTECTED]:
Le lundi 19 février 2007, à 23:35, Mikkel Kamstrup Erlandsen a écrit :
Let's get the ball rolling on the metadata spec. This first period
will
Hi,
[trimmed CC line]
Mikkel Kamstrup Erlandsen wrote:
How would you manage locks on the db?
Assuming sqlite, you just let it handle them. You have to be
intelligent in your use of transactions, but I don't see how a daemon
inherently improves lock contention.
Was synchronization issues
Hi,
jamie wrote:
(3) is the safest and best way - you get a richer service that allows
all apps to share metadata and stay up to date.
(2) is great in theory but falls over in practice for loads of reasons
(mainly need for fallbacks). XMP sidecar is better and really just needs
GVFS and KIO
On Wed, 2007-02-21 at 08:54 -0500, Joe Shaw wrote:
Hi,
jamie wrote:
(3) is the safest and best way - you get a richer service that allows
all apps to share metadata and stay up to date.
(2) is great in theory but falls over in practice for loads of reasons
(mainly need for
With approaches (1) and (2), notification is trivial. You get
WRITE_CLOSE event and ATTR_CHANGED events on the files themselves. For
(3), you can watch the database file for changes. (This means you have
to timestamp rows, but once that's done you can trivially SELECT for
Hi,
On Wed, 2007-02-21 at 14:26 +, jamie wrote:
Sorry, I must not have been clear in my previous email. The entire
point is to have fallbacks, because it gives you the richest experience.
You try (1) [inline metdata] and if it fails or doesn't make sense,
you try (2) [extended
2007/2/21, Fabrice Colin [EMAIL PROTECTED]:
On 2/21/07, Jos van den Oever [EMAIL PROTECTED] wrote:
2007/2/20, Joe Shaw [EMAIL PROTECTED]:
Heh. Fair enough. Should we keep it simply to the search-side of
things, then?
The intention is to define a way to define metadata fields. This is
2007/2/19, Mikkel Kamstrup Erlandsen [EMAIL PROTECTED]:
Let's get the ball rolling on the metadata spec. This first period will just
be *brainstorming*, so let's try and avoid the nitty gritty details for now.
** What we need:
Fields) Metadata field names and descriptions for *desktop*
2007/2/20, Jos van den Oever [EMAIL PROTECTED]:
2007/2/19, Mikkel Kamstrup Erlandsen [EMAIL PROTECTED]:
Let's get the ball rolling on the metadata spec. This first period will
just
be *brainstorming*, so let's try and avoid the nitty gritty details for
now.
** What we need:
Fields)
2007/2/20, Mikkel Kamstrup Erlandsen [EMAIL PROTECTED]:
2007/2/20, Jos van den Oever [EMAIL PROTECTED]:
2007/2/19, Mikkel Kamstrup Erlandsen [EMAIL PROTECTED]:
Let's get the ball rolling on the metadata spec. This first period will
just
be *brainstorming*, so let's try and avoid the nitty
Le lundi 19 février 2007, à 23:35, Mikkel Kamstrup Erlandsen a écrit :
Let's get the ball rolling on the metadata spec. This first period will
just be *brainstorming*, so let's try and avoid the nitty gritty details
for now.
Hi Mikkel,
Just wondering: would it make sense to move the
2007/2/20, Joe Shaw [EMAIL PROTECTED]:
On Mon, 2007-02-19 at 23:35 +0100, Mikkel Kamstrup Erlandsen wrote:
** What we need:
Fields) Metadata field names and descriptions for *desktop*
objects
Types) A type grouping of metadata fields to be used in user search
language. Example types
Hi,
On Tue, 2007-02-20 at 21:23 +0100, Jos van den Oever wrote:
Hehe, now _you_ are taking this spec further then intended. ;-)
I'll not get into this. On the KDE side this is something for
Sebastian Trueg (Nepomuk) to consider.
Heh. Fair enough. Should we keep it simply to the search-side
2007/2/20, Joe Shaw [EMAIL PROTECTED]:
Hi,
On Tue, 2007-02-20 at 21:23 +0100, Jos van den Oever wrote:
Hehe, now _you_ are taking this spec further then intended. ;-)
I'll not get into this. On the KDE side this is something for
Sebastian Trueg (Nepomuk) to consider.
Heh. Fair enough.
2007/2/20, Jon Phillips [EMAIL PROTECTED]:
On Tue, 2007-02-20 at 15:10 +0100, Jos van den Oever wrote:
2007/2/20, Mikkel Kamstrup Erlandsen [EMAIL PROTECTED]:
2007/2/20, Jos van den Oever [EMAIL PROTECTED]:
2007/2/19, Mikkel Kamstrup Erlandsen [EMAIL PROTECTED]:
Let's get the ball
2007/2/20, Vincent Untz [EMAIL PROTECTED]:
Le lundi 19 février 2007, à 23:35, Mikkel Kamstrup Erlandsen a écrit :
Let's get the ball rolling on the metadata spec. This first period
will
just be *brainstorming*, so let's try and avoid the nitty gritty
details
for now.
Hi Mikkel,
2007/2/20, Jos van den Oever [EMAIL PROTECTED]:
2007/2/20, Joe Shaw [EMAIL PROTECTED]:
Hi,
On Tue, 2007-02-20 at 21:23 +0100, Jos van den Oever wrote:
Hehe, now _you_ are taking this spec further then intended. ;-)
I'll not get into this. On the KDE side this is something for
Sebastian
2007/2/20, Jos van den Oever [EMAIL PROTECTED]:
2007/2/20, Joe Shaw [EMAIL PROTECTED]:
Hi,
On Tue, 2007-02-20 at 20:52 +0100, Jos van den Oever wrote:
But reading, writing and searching metadata fields is something that
desktop applications will want to do more and more. Since there is,
On Tue, 2007-02-20 at 23:31 +0100, Mikkel Kamstrup Erlandsen wrote:
2007/2/20, Joe Shaw [EMAIL PROTECTED]:
Indeed, and we should also use the same storage for it
whenever
possible. I envision a three-tiered system for actually
setting
Let's get the ball rolling on the metadata spec. This first period will just
be *brainstorming*, so let's try and avoid the nitty gritty details for now.
** What we need:
Fields) Metadata field names and descriptions for *desktop* objects
Types) A type grouping of metadata fields to be used
25 matches
Mail list logo
