Le jeudi 03 septembre 2009 à 17:45 +0200, Lucas Nussbaum a écrit :
> > > >
> > > > So if there's a table that directly maps those SHA1 of the mailto:email
> > > > of the current carnivore_email and of the current bugs:submitter, that
> > > > will be really straightforward to make the query and for
On 03/09/09 at 17:15 +0200, Olivier Berger wrote:
> Le jeudi 03 septembre 2009 à 16:33 +0200, Lucas Nussbaum a écrit :
> > On 03/09/09 at 15:25 +0200, Olivier Berger wrote:
> > > Le jeudi 03 septembre 2009 à 14:29 +0200, Lucas Nussbaum a écrit :
> > > > On 28/07/09 at 20:13 +0200, Olivier Berger wr
Le jeudi 03 septembre 2009 à 16:33 +0200, Lucas Nussbaum a écrit :
> On 03/09/09 at 15:25 +0200, Olivier Berger wrote:
> > Le jeudi 03 septembre 2009 à 14:29 +0200, Lucas Nussbaum a écrit :
> > > On 28/07/09 at 20:13 +0200, Olivier Berger wrote:
> > > > Only small minor additions to the postgres DB
On 03/09/09 at 15:25 +0200, Olivier Berger wrote:
> Le jeudi 03 septembre 2009 à 14:29 +0200, Lucas Nussbaum a écrit :
> > On 28/07/09 at 20:13 +0200, Olivier Berger wrote:
> > > Only small minor additions to the postgres DB are necessary to make
> > > triplify work : a sha1 function and a table to
Le jeudi 03 septembre 2009 à 14:29 +0200, Lucas Nussbaum a écrit :
> On 28/07/09 at 20:13 +0200, Olivier Berger wrote:
> > Only small minor additions to the postgres DB are necessary to make
> > triplify work : a sha1 function and a table to match emails to their
> > sha1 mailto: hashes.
>
> I'm n
On 28/07/09 at 20:13 +0200, Olivier Berger wrote:
> Only small minor additions to the postgres DB are necessary to make
> triplify work : a sha1 function and a table to match emails to their
> sha1 mailto: hashes.
I'm not sure I understand how you plan to use this. If we have a table
with all the
Hi.
Thanks Lucas, for the changes in the bugs table.
Now, it's more easy to convert to sioc:User and foaf:Person entities.
You can find an example of what we can achieve with triplify at
https://picoforge.int-evry.fr/cgi-bin/twiki/view/Helios_wp3/Web/TriplifyUddToRdf
(look at the attachments
Hi.
FYI, there are a few bugs whose submitters don't have a valid email
address :
SELECT id, submitter, submitter_email FROM bugs WHERE submitter_email NOT LIKE
'%...@%'
Some come from the parsing done at injection, and others from bad bug
reports, I suppose.
Maybe you'd like to check these ?
On 24/07/09 at 18:05 +0200, Olivier Berger wrote:
> The hard part is the change in the database schema to split the
> submitters email into name and email, to easily be able to match
> carnivore entries with bug submitters (for some outdated explanations of
> the views I used for doing so, see [1])
Hi.
In case some of you would be bored at the DebConf, they may try and test
using triplify [0] to produce RDF output on the contents of UDD, to
explore Semantic Web interlinking of people and bugs they have
submitted...
Here's a first working set of PHP, that requires a few custom tables /
view
10 matches
Mail list logo