[Nepomuk] [RFC] Nepomuk Resource naming convention

Vishesh Handa me at vhanda.in
Wed Feb 13 14:48:05 UTC 2013


On Wed, Feb 13, 2013 at 7:53 PM, Jörg Ehrichs <Joerg.Ehrichs at gmx.de> wrote:

> >
> > [...] I would like to move
> > to a much simpler naming scheme - nepomuk:/TYPE/number. The number will
> be
> > an increasing integer which will start from 0.
> >
> > This way, we will not need to rely on uuid generation and won't have to
> > query the database during each creation.
> >
>
> What happens when a resource is deleted or the some id is unused again
> after merging some resources?
> Do we keep a list of unused ids before we start to increase the counter
> again?
> Or do we ignore it and hope to never reach max integer created
> resources in a lifetime?
>

Ignore the deleted one.

We can't really reach the max integer limit. It is stored as a string.
Example - "nepomuk:/res/535345345"


>
> What is the worst that can happen if we have for some reason two
> different resources with the same id?
>

Well, you would have 2 resources which would be acting as the same. Not a
that big deal.

>
> Other than that, I'm fine with it.
> The nepomuk resource is just an internal detail no developer ever
> needs to see, so how it looks like doesn't really matter.
>



-- 
Vishesh Handa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20130213/bee35bb9/attachment-0001.html>


More information about the Nepomuk mailing list