Peter Williams | 2 Mar 2008 23:09
Favicon

RE: [foaf-dev] generating FOAF - dumb or smart?

Concerning Twinkle and access controls:
 
Setting the JRE/JDK system proxy allows control to be stripped from the application. In my case, my (scriptable) client-side proxy now responds to the SPARQL server's authentication challenge.
 
For fun, I went beyond having the proxy respond to the 401 basic authentication Challenge. I had the server issue an openid2 challenge. The (scriptable, extensible) proxy provides the responding openid2 assertion back - to authenticate and authorize the already delivered SPARQL request. (*)
 
Its probably important that the security model for SPARQL is standard and based on the communication layer rather than the information layer, ontlogies or data model . It obviously should not be based on any proprietary (security) features specific to the SPARQL client, the RDF library, or the  VM (.NET, JRE, etc)
 
 
(*) To be truthful it redirects to the openid assertion agent, which itself redirects through a chain of SAML agents which do std authentication and athorization processing. But, noone know this - it "looks like" openid.
 
If I summarize
 
1. I can generate FOAF files by template
2. I can generate FOAF streams by SPARQL CONSTRUCT
3. I can generate FOAF individuals from rdfs:subproperty, rdfs:subclass inferences (using OWL Full)
4. I can impose an agent-centric websso security model, with comsec semantics
 
With this, I think I have most of the infrastructure in place to now focus on Henry's problem: impose access controls on properties.
 
For that, I assume ill need a "community-endorsed" ontology for expressing an overlay of access control "security" facets on top of the object/data types associated with particular RDFS properties.
 
Peter.
 
 
===============================================================================
.
  JAVA: java
.
  JAVA_OPTS: -Dprogram.name=run.bat -DproxySet=true -DproxyHost=localhost -DproxyPort=8888 -Xms128m -Xmx512m
.
  CLASSPATH:
.
===============================================================================
From: Leigh Dodds
Sent: Sat 2/23/2008 10:53 AM
To: Peter Williams
Cc: foaf-dev <at> lists.foaf-project.org
Subject: Re: [foaf-dev] generating FOAF - dumb or smart?

> Meantime, I got tired of using http basic auth to the SPARQL server. (Never did get > Twinkle2.0 to talk to my http endpoint accepting SPARQL protocol, which required at least > basic auth - as there is no obvious way to configure the twinkle client agent for security). Thats because the 2.0 version doesn't support access control on SPARQL endpoints. I've been waiting for the recent ARQ release, which includes some changes I requested to the API. One of those was having a bit more control over the construction of the endpoint URL parameters than was previously available. I need that particular change to support endpoints with access tokens. So the 2.1 release which I'll hopefully have time for next week should include the feature you need. L.
_______________________________________________
foaf-dev mailing list
foaf-dev@...
http://lists.foaf-project.org/mailman/listinfo/foaf-dev
paola.dimaio | 4 Mar 2008 11:29
Picon
Gravatar

[foaf-dev] help with testing debuggin


Greets all

Our first version of the foafX is up, it needs some testing and debuggin (while we are still tweaking)

whatever we can fix quick it can be done within this release, long term improvements can be scheduled for later
so all feedback welcome (asap!) thanks

If you are interested in developing this demo further please download the code and kindly link back to us
thanks


--
Paola Di Maio
School of IT
www.mfu.ac.th
*********************************************
_______________________________________________
foaf-dev mailing list
foaf-dev@...
http://lists.foaf-project.org/mailman/listinfo/foaf-dev
paola.dimaio | 4 Mar 2008 11:34
Picon
Gravatar

[foaf-dev] Re: help with testing debuggin

ooppss

sorrry forgot URL

http://www.foafx.punfai.com/

On Tue, Mar 4, 2008 at 5:29 PM, <paola.dimaio-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

Greets all

Our first version of the foafX is up, it needs some testing and debuggin (while we are still tweaking)

whatever we can fix quick it can be done within this release, long term improvements can be scheduled for later
so all feedback welcome (asap!) thanks

If you are interested in developing this demo further please download the code and kindly link back to us
thanks


--
Paola Di Maio
School of IT
www.mfu.ac.th
*********************************************



--
Paola Di Maio
School of IT
www.mfu.ac.th
*********************************************
_______________________________________________
foaf-dev mailing list
foaf-dev@...
http://lists.foaf-project.org/mailman/listinfo/foaf-dev
Norman Gray | 4 Mar 2008 21:03
Picon
Picon
Gravatar

[foaf-dev] OpenID logins to the wiki


Greetings.

When I try to log in to the wiki using OpenID, I get an error saying  
that ``Safari [for Safari it turns out to be] can’t open the page
“http://wiki.foaf-project.org/Special:OpenIDLogin 
” because it couldn’t establish a secure connection to the server  
“wiki.foaf-project.org”.'', and true enough, I can't seem to connect  
to <https://wiki.foaf-project.org/>.

Is this a known issue?  The OpenID provider is <http://certifi.ca>, by  
the way.

All the best,

Norman

--

-- 
Norman Gray  :  http://nxg.me.uk
eurovotech.org  :  University of Leicester
Tom Heath | 6 Mar 2008 11:34
Picon

[foaf-dev] Deadline Extended, Scripting for the Semantic Web (SFSW) at ESWC 2008

[apologies if you see this message more than once]

Hi all,

Due to numerous requests the deadline for submissions to the Scripting
for the Semantic Web workshop at ESWC2008 has been extended by one
week, to Friday 14th March 2008 (11:59pm Hawaii time). This deadline
extension applies to full papers, short papers and Scripting Challenge
entries. The Scripting Challenge is sponsored this year by Talis, and
carries a prize of an iPod Touch or 250 euros cash.

 More details are available at the workshop web site:
 http://www.semanticscripting.org/SFSW2008/

 Cheers,

 Tom.

 > -----Original Message-----
 > From: semantic-web-request@...
 > [mailto:semantic-web-request@...] On Behalf Of Chris Bizer
 > Sent: 25 February 2008 12:40
 > To: semantic-web@...; Linking Open Data
 > Subject: 2nd CfP: Scripting for the Semantic Web (SFSW) at ESWC 2008
 >
 >
 > Hi all,
 >
 > just a quick reminder that the submission deadline for the
 > ESWC 2008 Scripting for the Semantic Web (SFSW) workshop is
 > approaching quickly, but there is still enough time to
 > prepare submissions.
 >
 > SFSW submission deadline: March 7, 2008
 >
 > The workshop seeks high-quality submissions on all aspects of
 > using scripting languages within Semantic Web applications
 > ranging from populating the Semantic Web with data from
 > existing systems to applications that do surprising things
 > with data from the Semantic Web.
 >
 > The special focus of this years workshop is the creation of
 > Semantic Web data through social interactions, as well as
 > applications that integrate socially-created data across
 > communities. Therefore, we especially encourage work on
 > providing Semantic Web access to socially-created content
 > bases, as well as approaches that facilitate data integration
 > across different content bases using Semantic Web technologies.
 >
 > I'm sure will have a great workshop and I'm looking forward
 > to meeting the whole scripting community in person at ESWC
 > 2008 again :-)
 >
 > Cheers,
 >
 > Chris
 >
 >
 > -------------------------------------------------------
 > CALL FOR PAPERS
 > -------------------------------------------------------
 >
 > 4th Workshop on Scripting for the Semantic Web
 > http://www.semanticscripting.org/SFSW2008/
 >
 > co-located with
 > 5th European Semantic Web Conference (ESWC2008) June 1, 2008,
 > Tenerife, Spain
 >
 > -------------------------------------------------------
 >
 > OBJECTIVES
 > ----------
 >
 > The workshop aims to bring together developers who are
 > building applications and infrastructure for the Semantic Web
 > using scripting languages such as PHP, JavaScript, Ruby,
 > Python, Perl, JSP and ActionScript. 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 scripting
 > languages, and it is likely that the process of RDF-izing
 > existing Web applications and database-backed Web sites will
 > continue to rely heavily on scripting languages.
 >
 > This year's fourth workshop on Scripting for the Semantic Web
 > aims to continue the tradition of successful ESWC scripting
 > workshops. Last years Scripting for the Semantic Web workshop
 > in Innsbruck, Austria
 > (http://www.semanticscripting.org/SFSW2007/) focused on the
 > role of scripting languages in populating the Web with Linked
 > Data, as well as showcasing innovative scripting applications
 > that consume Linked Data from the Web.
 >
 > The special focus of this years workshop is the creation of
 > Semantic Web data through social interactions, as well as
 > applications that integrate socially-created data across
 > communities. Therefore, we especially encourage work on
 > providing Semantic Web access to socially-created content
 > bases, as well as approaches that facilitate data integration
 > across different content bases using Semantic Web technologies.
 >
 > The workshop will include a scripting challenge which will
 > award an industry sponsored prize to the most innovative
 > scripting application.
 >
 >
 > TOPICS OF INTEREST
 > ------------------
 >
 > Topics of interest include, but are not limited to:
 >
 > Infrastructure
 > - Semantic Web frameworks and APIs for scripting languages
 > - RDF repositories and query languages implemented using scripting
 > languages
 > - Reasoning engines implemented using scripting languages
 > - Semantic Web publishing and data syndication frameworks
 > - Approaches to providing Linked Data views on socially-created
 > content bases
 > - Approaches to crawling Web data and querying distributed
 > data on the
 > Web
 >
 > Applications
 > - Semantic Web applications using scripting languages
 > - Approaches to using Semantic Web technologies for integrating data
 > across socially-created content bases and user communities
 > - Mashups that combine Linked Data from the Web with data
 > from Web 2.0
 > data sources such as Google, Yahoo, flickr, Amazon or eBay
 > - Wikis, weblogs, data syndication and content management
 > applications
 > using RDF
 > - Scripting applications for visualizing Web data
 > - Semantic Web Mining and Social Network Analysis
 > - Approaches to RDF-izing existing web-content, such as RDFa,
 > microformats, GRDDL
 > - Mashups that demonstrate the novel capabilities of Semantic Web
 > technologies
 >
 > Conceptual
 > - Rapid development techniques for the Semantic Web
 > - Employment of scripting language characteristics for Semantic Web
 > development
 > - Scalability and benchmarks of Semantic Web scripting applications
 >
 >
 > SCRIPTING CHALLENGE
 > -------------------
 >
 > The workshop includes a scripting challenge which will award an
 > industry sponsored prize to the most innovative small scripting
 > application or mashup. The application must be implemented using a
 > scripting language and Semantic Web technologies. It should access,
 > visualize or combine data from heterogeneous sources in a novel way.
 > Authors of Scripting Challenge submissions are not required to attend
 > the workshop personally. Please contact Gunnar Grimnes
 > (gunnar.grimnes
 > {at} dfki.de) for further information about the Scripting Challenge.
 >
 >
 > IMPORTANT DATES
 > ---------------
 >
 > Submission deadline: March 7, 2008
 > Notication of acceptance: April 4, 2008
 > Camera-ready paper submission: April 18, 2008
 > Workshop date: June 1, 2008
 >
 >
 > WORKSHOP CHAIRS
 > ---------------
 >
 > * Chris Bizer, Freie Universität Berlin, Germany
 > * Sören Auer, Universität Leipzig, Germany and University of
 > Pennsylvania, USA
 > * Gunnar Aastrand Grimnes, DFKI Knowledge Management Lab, Germany
 > * Tom Heath, Talis Information Ltd, United Kingdom
 >
 >
 > SUBMISSIONS
 > -----------
 >
 > We seek three kinds of submissions:
 > * Full papers - up to 12 pages in length.
 > * Short papers - up to 6 pages in length.
 > * Scripting Challenge Submissions - 2 page description of the
 > application, ideally accompanied with the source code and a
 > link to an
 > online demo.
 >
 >
 > FURTHER INFORMATION
 > -------------------
 >
 > Updated information about the workshop is found on the workshop
 > website
 > http://www.semanticscripting.org/SFSW2008/
 >
 > For further information, please send email to sfsw2008 {at}
 > semanticscripting.org
 >
 > --
 > Chris Bizer
 > Freie Universität Berlin
 > Phone: +49 30 838 54057
 > Mail: chris@...
 > Web: www.bizer.de
 >
 >
 >
Axel Polleres | 8 Mar 2008 23:04

[foaf-dev] dc:creator vs foaf:maker

Hi all,

What I read about foaf:maker vs. dc:creator at [1,2] seems to be 
outdated by the latest DCMI recommendations [3].

Also if you look at http://dblp.l3s.de/d2r/page/authors/Axel_Polleres, 
it seems that the D2R guys - somewhat ahead of their time ;-) -
already seem to use dc:creator like that, i.e. referring to URI 
identified resources directly.

for me personally it seems that one should deprecate foaf:maker and make 
it a subproperty of dc:creator.

Opinions?

Axel

1. http://xmlns.com/foaf/spec/#term_maker
2. http://wiki.foaf-project.org/UsingDublinCoreCreator
3. http://dublincore.org/documents/dc-rdf/

--

-- 
Dr. Axel Polleres
email: axel@...  url: http://www.polleres.net/

rdfs:Resource owl:differentFrom xsd:anyURI .
Peter Williams | 9 Mar 2008 01:35
Favicon

RE: [foaf-dev] dc:creator vs foaf:maker

As a non expert, mere "user", it comes across as a "my name is more viable than your name" playground statement, age 7.
 
Either the semweb is about everyone being peers in how they name things (with cited equivalencies, possibly )  or its not.
 
If the community in the core schema world is undermining the notion that all names are equally valid (and certain naming schemas are not in fact more "valid" than others), we cannot expect folks to let semweb take off. SemWeb has not broken out of the notion that there evn exists a "dominant" naming doctrine - for any layer.
 
Speaking as a peon.
From: Axel Polleres
Sent: Sat 3/8/2008 2:04 PM
To: foaf-dev
Subject: [foaf-dev] dc:creator vs foaf:maker

Hi all, What I read about foaf:maker vs. dc:creator at [1,2] seems to be outdated by the latest DCMI recommendations [3]. Also if you look at http://dblp.l3s.de/d2r/page/authors/Axel_Polleres, it seems that the D2R guys - somewhat ahead of their time ;-) - already seem to use dc:creator like that, i.e. referring to URI identified resources directly. for me personally it seems that one should deprecate foaf:maker and make it a subproperty of dc:creator. Opinions? Axel 1. http://xmlns.com/foaf/spec/#term_maker 2. http://wiki.foaf-project.org/UsingDublinCoreCreator 3. http://dublincore.org/documents/dc-rdf/ -- -- Dr. Axel Polleres email: axel-TbQWwXTvOqfk1uMJSBkQmQ@public.gmane.org url: http://www.polleres.net/ rdfs:Resource owl:differentFrom xsd:anyURI . _______________________________________________ foaf-dev mailing list foaf-dev-RyYwo1q5J+qsOXdr9/+iASST3g8Odh+X@public.gmane.org http://lists.foaf-project.org/mailman/listinfo/foaf-dev
_______________________________________________
foaf-dev mailing list
foaf-dev@...
http://lists.foaf-project.org/mailman/listinfo/foaf-dev
Axel Polleres | 9 Mar 2008 02:02

Re: [foaf-dev] dc:creator vs foaf:maker

Peter Williams wrote:
> As a non expert, mere "user", it comes across as a "my name is more 
> viable than your name" playground statement, age 7.

not sure what you are rferring to, I am not referring to identifiers on 
the web, this is a different issue and of course I am aware of that ;-)
  I was referring to basically whether dc:creator should be used as an 
objectproperty or as a mere datatypeproperty.

the current foaf spec gives a clear recommendation in that (see [1,2])
whereas the new DMCI spec seems to treat this issue differently in a way 
that does seem to make a separate foaf:maker property no longer necessary.

Axel

> Either the semweb is about everyone being peers in how they name things 
> (with cited equivalencies, possibly )  or its not.
>  
> If the community in the core schema world is undermining the notion that 
> all names are equally valid (and certain naming schemas are not in fact 
> more "valid" than others), we cannot expect folks to let semweb take 
> off. SemWeb has not broken out of the notion that there evn exists a 
> "dominant" naming doctrine - for any layer.
>  
> Speaking as a peon.
> ------------------------------------------------------------------------
> *From:* Axel Polleres
> *Sent:* Sat 3/8/2008 2:04 PM
> *To:* foaf-dev
> *Subject:* [foaf-dev] dc:creator vs foaf:maker
> 
> Hi all,
> 
> What I read about foaf:maker vs. dc:creator at [1,2] seems to be 
> outdated by the latest DCMI recommendations [3].
> 
> Also if you look at http://dblp.l3s.de/d2r/page/authors/Axel_Polleres, 
> it seems that the D2R guys - somewhat ahead of their time ;-) -
> already seem to use dc:creator like that, i.e. referring to URI 
> identified resources directly.
> 
> for me personally it seems that one should deprecate foaf:maker and make 
> it a subproperty of dc:creator.
> 
> Opinions?
> 
> Axel
> 
> 1. http://xmlns.com/foaf/spec/#term_maker
> 2. http://wiki.foaf-project.org/UsingDublinCoreCreator
> 3. http://dublincore.org/documents/dc-rdf/
> 
> -- 
> Dr. Axel Polleres
> email: axel@...  url: http://www.polleres.net/
> 
> rdfs:Resource owl:differentFrom xsd:anyURI .
> _______________________________________________
> foaf-dev mailing list
> foaf-dev@...
> http://lists.foaf-project.org/mailman/listinfo/foaf-dev

--

-- 
Dr. Axel Polleres
email: axel@...  url: http://www.polleres.net/

rdfs:Resource owl:differentFrom xsd:anyURI .
Peter Williams | 9 Mar 2008 20:41
Favicon

RE: [foaf-dev] dc:creator vs foaf:maker

Axel:
 
I got frustrated with the topic you introduced, as I went to some trouble to try and understand the issue you raised : starting with FOAF as-is. I never really got far enough into the topic to really understanding your suggestion, given your hint about updates in Dublin Core.  I cannot (practically) understand the FOAF document as it is currently stands (which is my lack of basic expertise in core techniques, clearly).
1. I captured Henry Story's foaf file, as rdf/xml. I cleaned it up to remove the non American characters from his friends names. This allowed to me view his published resources, with the tool's owl reasoning engine turned on.
 
2. Reading your email's citations properly took me to the FOAF spec - and to its textual description of the concepts of agents, persons, and makers.
maker - An agent that made this thing.
Status: Domain: Range:
stable
http://www.w3.org/2002/07/owl#Thing
foaf:Agent

The foaf:maker property relates something to a foaf:Agent that foaf:made it. As such it is an inverse of the foaf:made property.

The foaf:name (or other rdfs:label) of the foaf:maker of something can be described as the dc:creator of that thing.

For example, if the thing named by the URI http://rdfweb.org/people/danbri/ has a foaf:maker that is a foaf:Person whose foaf:name is 'Dan Brickley', we can conclude that http://rdfweb.org/people/danbri/ has a dc:creator of 'Dan Brickley'.

 
3. Aha! we have a nice example of owl being (simplistically) useful, I said to myself, noting the domain of the property is owl:Thing and a defined agent notion is properly and intuitively responsible for making this particular type of "document". This will allow me to conclude (from last quoted paragraph) dc:creator from foaf:maker is some "creating" individual in practice, distinguished from the declared agent that "makes it".
 
4 So, I imported the foaf ontology into the dataset to start reasoning with foaf rules. Lots of additional inferences duly occurred. However, inferences about foaf:maker and dc:creator were not among them, in the individual foaf:PersonalProfileDocument.
 
5. On the foaf:maker property decryption itself, only rdfs:sameAs <uri> was usefully inferred
OK. We are back to 'Peter is just too dumb' for the SemWeb. The fact that conclusion are dc:creator are discussed in the foaf standard , does NOT mean that a tool using the rules in the foaf ontology's rdf file will ACTUALLY cause a machine to make the discussed inference/conclusion. Sigh.
 
Perhaps after all I'm really not that dumb. A more valid conclusion could be : its really hard to tell what is settled in FOAF - vs. what is ongoing basic research.
 
 
At that point, I decided I'd really had enough of the topic of maker and creator.
 
Peter.
 
From: Axel Polleres
Sent: Sat 3/8/2008 5:02 PM
To: Peter Williams
Cc: foaf-dev
Subject: Re: [foaf-dev] dc:creator vs foaf:maker

Peter Williams wrote: > As a non expert, mere "user", it comes across as a "my name is more > viable than your name" playground statement, age 7. not sure what you are rferring to, I am not referring to identifiers on the web, this is a different issue and of course I am aware of that ;-) I was referring to basically whether dc:creator should be used as an objectproperty or as a mere datatypeproperty. the current foaf spec gives a clear recommendation in that (see [1,2]) whereas the new DMCI spec seems to treat this issue differently in a way that does seem to make a separate foaf:maker property no longer necessary. Axel > Either the semweb is about everyone being peers in how they name things > (with cited equivalencies, possibly ) or its not. > > If the community in the core schema world is undermining the notion that > all names are equally valid (and certain naming schemas are not in fact > more "valid" than others), we cannot expect folks to let semweb take > off. SemWeb has not broken out of the notion that there evn exists a > "dominant" naming doctrine - for any layer. > > Speaking as a peon. > ------------------------------------------------------------------------ > *From:* Axel Polleres > *Sent:* Sat 3/8/2008 2:04 PM > *To:* foaf-dev > *Subject:* [foaf-dev] dc:creator vs foaf:maker > > Hi all, > > What I read about foaf:maker vs. dc:creator at [1,2] seems to be > outdated by the latest DCMI recommendations [3]. > > Also if you look at http://dblp.l3s.de/d2r/page/authors/Axel_Polleres, > it seems that the D2R guys - somewhat ahead of their time ;-) - > already seem to use dc:creator like that, i.e. referring to URI > identified resources directly. > > for me personally it seems that one should deprecate foaf:maker and make > it a subproperty of dc:creator. > > Opinions? > > Axel > > 1. http://xmlns.com/foaf/spec/#term_maker > 2. http://wiki.foaf-project.org/UsingDublinCoreCreator > 3. http://dublincore.org/documents/dc-rdf/ > > -- > Dr. Axel Polleres > email: axel-TbQWwXTvOqfk1uMJSBkQmQ@public.gmane.org url: http://www.polleres.net/ > > rdfs:Resource owl:differentFrom xsd:anyURI . > _______________________________________________ > foaf-dev mailing list > foaf-dev-RyYwo1q5J+qsOXdr9/+iASST3g8Odh+X@public.gmane.org > http://lists.foaf-project.org/mailman/listinfo/foaf-dev -- -- Dr. Axel Polleres email: axel-TbQWwXTvOqfk1uMJSBkQmQ@public.gmane.org url: http://www.polleres.net/ rdfs:Resource owl:differentFrom xsd:anyURI .
_______________________________________________
foaf-dev mailing list
foaf-dev@...
http://lists.foaf-project.org/mailman/listinfo/foaf-dev
Peter Williams | 10 Mar 2008 02:11
Favicon

[foaf-dev] Indian personal names, in local scripts. Also Thai.

One of our very short terms goals is to deliver a so called "multiple listing system" for use by the average Indian Internet user seeking homes and property via the web - for that part of the land and housing in parts of India that uses investment criteria, ratings, credit, valuation notions of property and property ownership.
 
If anyone one has a foaf file with their names or home address/directions in their local language and its local script, please let me know.
 
The goal is to allow me to locally render your foaf file using the following tool:
 
 
That is: the property names would be shown to (ignorant-old) me in English and Romanized characters (Gujǎrātī), but your names and address are shown as you would personally say them in Gujurati ...and then write them down... in Gujurati script (ગુજરાતી)
 
(The same request also goes to folk using Thai.)
_______________________________________________
foaf-dev mailing list
foaf-dev@...
http://lists.foaf-project.org/mailman/listinfo/foaf-dev

Gmane