headers
Tom Heath | 8 Mar 2007 12:45
Picon

[foaf-dev] 2nd CFP: Scripting for the Semantic Web, Workshop and Challenge at ESWC2007

** apologies if you get multiple copies of this message **

The deadline for full paper, short paper, and Scripting Challenge
submissions  to the 3rd Workshop on Scripting for the Semantic Web is
approaching (30th March). Submissions can be made via the conference
submission system linked from <http://semanticscripting.org/SFSW2007/>

Update: Danny Ayers will give an invited talk at SFSW07 about "Two Webs!"

-------------------------------------------------------
CALL FOR PAPERS
-------------------------------------------------------

3rd Workshop on Scripting for the Semantic Web
http://www.semanticscripting.org/SFSW2007/

co-located with
4th European Semantic Web Conference
June 6 or 7 2007, Innsbruck, Austria

-------------------------------------------------------

Scripting languages such as PHP, JavaScript, Ruby, Python, Perl, JSP
and ActionScript are playing a central role in current development
towards flexible, lightweight web applications following the AJAX and
REST design paradigms. These languages are the tools of a generation
of web programmers who use them to quickly create server and
client-side web applications. Many deployed Semantic Web applications
from the FOAF, RSS/ATOM, blog and wiki communities, as well as many
innovative mashups from the Web 2.0 and Open Data movements are using
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mikael Nilsson | 9 Mar 2007 10:40
Gravatar

[foaf-dev] Advise needed for DC range definitions

Hi everyone!

As I've mentioned before, the DCMI is in the process of assigning
domains and ranges to the Dublin Core properties [1] (this is a proposal
only at this stage!). We have hit upon a fundamental issue, and I would
like to hear any advise from the RDF people on this list, as it affects
the future relationship between DC and FOAF (and the rest of the SW
community).

The issue is simple - do we want to specify ranges that are either
subclasses of owl:Thing or rdfs:Literal, but not both, or can a mixed
approach be preferable in some contexts?

Allowing ranges that can be either owl:Things or literals (such as
dcterms:description, which we are currently proposing to have an open
range of rdf:Resource) opens up for problems with OWL-DL and other
applications. However, as was recently mentioned on the SKOS list [2],
the flexibility of open ranges has advantages too.

I see that FOAF has adopted a strict separated approach, where every
range is either a subclass of owl:Thing or of rdfs:Literal but not both.
Is this correct? And does the community want DC to do the same?

Thanks in advance for any comments,

/Mikael

[1] http://dublincore.org/documents/2007/02/05/domain-range/
[2] http://lists.w3.org/Archives/Public/public-swd-wg/2007Feb/0153
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kjetil Kjernsmo | 11 Mar 2007 00:22

[foaf-dev] FOAF-based whitelisting project

Hi all!

Some of you might have noticed that I started "Community Projects" with 
the W3C semweb Education and Outreach IG, and submitted a proposal 
myself, about using FOAF-based trust networks for whitelisting email. 
And blacklisting too. 

The project overview is at 
http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/FOAFWhitelisting

Importantly, I want to build it using the most basic data, really 
identifying people, context-dependant trust, etc, will need to be added 
as we go. I just want to make this useful as quickly as possible.

If no-one objects, I intend to use foaf-dev as the project mailing list. 
After all, it should be the core topic of this list. Of course, I have 
other options as well, I even have a mailman install of my own, but I 
hope to engage people here, and besides, it isn't that much activity 
anyway. 

I've started to write some code, as plugins for Qpsmtpd and 
SpamAssassins are the main deliverables on the road-map. 

I've created some untested code, now at 
http://svn.kjernsmo.net/qpsmtpd-foafwhitelist/trunk/check-foaftrust
and
http://svn.kjernsmo.net/Mail-SpamAssassin-Plugin-FOAFTrust/trunk/lib/Mail/SpamAssassin/Plugin/FOAFTrust.pm
They should be functional, though, except for one little fact, that the 
trust metric is now just a random number... :-)
(Continue reading)

Permalink | Reply | 0 comments |
headers
B.K. DeLong | 11 Mar 2007 00:24
Picon
Favicon
Gravatar

Re: [foaf-dev] FOAF-based whitelisting project

I think this is a GREAT idea as none of the social networks seem to be
embracing anything more than the export of FOAF files.

I think the key here is that once there's stable integration of FOAF
into whitelisting/blacklisting then working with Google, Hotmail,
Yahoo! and other services that allow "contact lists" would help to
proliferate the project.

Have you approached the various antispam and SPF groups for buy-in and support?

On 3/10/07, Kjetil Kjernsmo <kjetil@...> wrote:
> Hi all!
>
> Some of you might have noticed that I started "Community Projects" with
> the W3C semweb Education and Outreach IG, and submitted a proposal
> myself, about using FOAF-based trust networks for whitelisting email.
> And blacklisting too.
>
> The project overview is at
> http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/FOAFWhitelisting
>
> Importantly, I want to build it using the most basic data, really
> identifying people, context-dependant trust, etc, will need to be added
> as we go. I just want to make this useful as quickly as possible.
>
> If no-one objects, I intend to use foaf-dev as the project mailing list.
> After all, it should be the core topic of this list. Of course, I have
> other options as well, I even have a mailman install of my own, but I
> hope to engage people here, and besides, it isn't that much activity
> anyway.
(Continue reading)

Permalink | Reply | 1 comment |
headers
R. Steven Rainwater | 11 Mar 2007 01:50
Favicon

Re: [foaf-dev] FOAF-based whitelisting project

On Sun, 2007-03-11 at 00:22 +0100, Kjetil Kjernsmo wrote:
> using FOAF-based trust networks for whitelisting email. 
> <...>
> Importantly, I want to build it using the most basic data,
> really identifying people, context-dependant trust

You might want to take a look at mod_virgule, the software used to
implement www.advogato.org and robots.net, and a few other community
sites. It includes a trust metric system and trusted members of the
community now have FOAF files as part of their profile.

If nothing else, I'd be happy to modify mod_virgule to submit trusted
user's FOAF data to whatever sort of repository your anti-spam system
will use. Or is it more of a distributed system where you'll just direct
spamassassin to the source of the FOAF file? 

-Steve
Permalink | Reply | 29 comments |
headers
Dan Brickley | 11 Mar 2007 01:58

Re: [foaf-dev] FOAF-based whitelisting project

R. Steven Rainwater wrote:
> On Sun, 2007-03-11 at 00:22 +0100, Kjetil Kjernsmo wrote:
>> using FOAF-based trust networks for whitelisting email. 
>> <...>
>> Importantly, I want to build it using the most basic data,
>> really identifying people, context-dependant trust
> 
> You might want to take a look at mod_virgule, the software used to
> implement www.advogato.org and robots.net, and a few other community
> sites. It includes a trust metric system and trusted members of the
> community now have FOAF files as part of their profile.
> 
> If nothing else, I'd be happy to modify mod_virgule to submit trusted
> user's FOAF data to whatever sort of repository your anti-spam system
> will use. Or is it more of a distributed system where you'll just direct
> spamassassin to the source of the FOAF file? 

Would definitely be cool to see more of the trust-metric info within 
advogato flow out in machine-readable form.

I did some prototyping in this area a few years ago (urk, many years 
ago!), http://www.w3.org/2001/12/rubyrdf/util/foafwhite/intro.html -- 
not so much the trust metrics side, ... just basic info about who you 
deem a non-spammer.

Kjetil, did you see 
http://www.w3.org/2001/12/rubyrdf/util/foafwhite/intro.html ?

Re mod_virgule, ... I guess a lot can be done simply with existing info, 
since we don't need to know how *great*, *wise* etc someone is, ...
(Continue reading)

Permalink | Reply | 25 comments |
headers
R. Steven Rainwater | 11 Mar 2007 02:16
Favicon

Re: [foaf-dev] FOAF-based whitelisting project

On Sun, 2007-03-11 at 00:58 +0000, Dan Brickley wrote:
> Would definitely be cool to see more of the trust-metric info
> within advogato flow out in machine-readable form.
> 
> I did some prototyping in this area a few years ago (urk, many
> years ago!), 
> http://www.w3.org/2001/12/rubyrdf/util/foafwhite/intro.html

Cool, I wasn't aware of the foafwhite.xml format at all. It looks very
easy to implement. If anyone could use this, I'll add it to the ToDo
list and see if I can get something done next week.

-Steve
Permalink | Reply | 2 comments |
headers
Dave Brondsema | 11 Mar 2007 06:07
Gravatar

Re: [foaf-dev] FOAF-based whitelisting project

Kjetil Kjernsmo wrote:
> Hi all!
> 
> Some of you might have noticed that I started "Community Projects" with 
> the W3C semweb Education and Outreach IG, and submitted a proposal 
> myself, about using FOAF-based trust networks for whitelisting email. 
> And blacklisting too. 
> 
> The project overview is at 
> http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/FOAFWhitelisting
> 
> Importantly, I want to build it using the most basic data, really 
> identifying people, context-dependant trust, etc, will need to be added 
> as we go. I just want to make this useful as quickly as possible.

Hi Kjetil, others.  Its great to see this project as sponsored by the
SWEO group.  There's a LOT of potential here.

While making practical incremental progress is important, I think we
should discuss for a little while our plans for this project so that we
can work in the best direction.  Do you have any particular plans or
ideas that you'd like to share, Kjetil or Chris?

I've spent quite a while thinking and working on the Konfidi project
which has similar goals.  I'll share some of my long-term vision soon.
In the meantime, I invite folks to check out http://konfidi.org, and
http://konfidi.org/wiki/Application_Ideas.

--

-- 
Dave Brondsema : dave@...
(Continue reading)

Permalink | Reply | 9 comments |
headers
Dan Brickley | 11 Mar 2007 11:56

Re: [foaf-dev] FOAF-based whitelisting project

R. Steven Rainwater wrote:
> On Sun, 2007-03-11 at 00:58 +0000, Dan Brickley wrote:
>> Would definitely be cool to see more of the trust-metric info
>> within advogato flow out in machine-readable form.
>>
>> I did some prototyping in this area a few years ago (urk, many
>> years ago!), 
>> http://www.w3.org/2001/12/rubyrdf/util/foafwhite/intro.html
> 
> Cool, I wasn't aware of the foafwhite.xml format at all. It looks very
> easy to implement. If anyone could use this, I'll add it to the ToDo
> list and see if I can get something done next week.

I'm not sure it's quite the best thing to do. I think it may have been 
invented before I put foaf:mbox:sha1_sum into the spec. Perhaps now, 
we'd use something based on that instead. But as you say, it's not a 
huge implementation effort to play around with, ... Kjetil,  what do you 
reckon?

Dan
Permalink | Reply | 1 comment |
headers
Lukas Rosenstock | 11 Mar 2007 15:42
Picon

Re: [foaf-dev] FOAF-based whitelisting project

Hi!
The OpenID community also had discussions about "social whitelisting".  
Maybe we could work together and define a standard for whitelisting that  
can be used for both e-mails (for which the FOAFWhitelist is) and OpenID.
I gathered some of the suggestions in this blog post:  
http://blog.identity20.eu/5.e
Regards,
  Lukas
Permalink | Reply | 0 comments |

Gmane