headers
Bob Ferris | 6 Feb 2011 12:07
Gravatar

[foaf-dev] FOAF-RDF-2-(X)HTML+RDFa-izer?

Hi,

I searched recently for FOAF-RDF-2-(X)HTML+RDFa-izers. I found FOAFr[1] 
from Michael Hausenblas. Unfortunately, it can't parse my FOAF profile 
for some reason. The result was (X)HTML+RDFa that still have the 
variables unresolved.
The RDF2RDFa converter[2] provided by the GoodRelations team is more or 
less only a nice frontend of Rhizomik[3]. It produce nicely invisible RDFa.
However, I searched for a nice generator that converts my FOAF-RDF into 
a standard (X)HTML-RDFa view of it.

Are you aware of any other tools in that direction. I think such a tool 
might be quite interesting today, or?

Cheers,

Bob

[1] http://sw.joanneum.at:8080/foafr/
[2] http://www.ebusiness-unibw.org/tools/rdf2rdfa/
[3] http://rhizomik.net/redefer/
Permalink | Reply | 8 comments |
headers
Jonas Smedegaard | 6 Feb 2011 13:14
X-Face
Face
Picon
Gravatar

Re: [foaf-dev] FOAF-RDF-2-(X)HTML+RDFa-izer?

On Sun, Feb 06, 2011 at 12:07:24PM +0100, Bob Ferris wrote:
>I searched recently for FOAF-RDF-2-(X)HTML+RDFa-izers. I found FOAFr[1] 
>from Michael Hausenblas. Unfortunately, it can't parse my FOAF profile 
>for some reason. The result was (X)HTML+RDFa that still have the 
>variables unresolved.
>The RDF2RDFa converter[2] provided by the GoodRelations team is more or
>less only a nice frontend of Rhizomik[3]. It produce nicely invisible RDFa.
>However, I searched for a nice generator that converts my FOAF-RDF into
>a standard (X)HTML-RDFa view of it.
>
>Are you aware of any other tools in that direction. I think such a tool
>might be quite interesting today, or?

I am interested in this as well.  I know of [FOAFer], [FOAF-explorer] 
and [FOAF Visualizer].

Some of those are mentioned at the FOAF wiki [Tools] page.  I maintain 
a few notes at [my own wiki page] as well.

The style of implementation are very different, as is the features they 
include and how they present them.  Note also how only some of them 
properly handle content-negotiation (resolve to the RDF resource when 
given a dir offering multiple variants).

  - Jonas

[FOAFer]:
  http://www.foafer.org/?file=http://dr.jones.dk/me/index.rdf 
[FOAF-explorer]:
  http://xml.mfd-consult.dk/foaf/explorer/?foaf=http://dr.jones.dk/me/
(Continue reading)

Permalink | Reply | 7 comments |
headers
Bob Ferris | 6 Feb 2011 14:47
Gravatar

Re: [foaf-dev] FOAF-RDF-2-(X)HTML+RDFa-izer?

Hi Jones,

Thanks a lot for your references, but I was really interested into a 
FOAF-profile-RDFa-izer. So the RDFa in the (X)HTML is the interesting 
part for me here ;)

Am 06.02.2011 13:14, schrieb Jonas Smedegaard:
> [FOAFer]:
> http://www.foafer.org/?file=http://dr.jones.dk/me/index.rdf

This doesn't include any RDFa, or?

> [FOAF-explorer]:
> http://xml.mfd-consult.dk/foaf/explorer/?foaf=http://dr.jones.dk/me/

This doesn't include any RDFa, or?

> [FOAF Visualizer]:
> http://foaf-visualizer.org/?uri=http://dr.jones.dk/me/

This doesn't include any RDFa, or?

All in all, these visualizers are note bad. However, they don't include 
RDFa at all.
My intention behind this need is that I would like to deliver i.e. XML, 
Turtle and RDFa serializations of my FOAF (RDF) profile. So that one can 
get a preferred representation when resolving my FOAF profile address.
An example of how such an intended (X)HTML+RDFa could look like is 
mhausenblas profile[1]. I guess, he used FOAFr to transform it ;)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bob Ferris | 6 Feb 2011 16:19
Gravatar

Re: [foaf-dev] FOAF-RDF-2-(X)HTML+RDFa-izer?

Hello again,

due a nice hint from Melvin Carvalho, who made me aware of the RDFa 
serializer plugin for ARC[1], I could easily set up a small web 
interface. I wasn't aware of the easy deployment of ARC. That's pretty nice.

So here we go: http://zazi.smiy.org/rdfaparser.html

Cheers,

Bob

[1] http://arc.semsol.org/download/plugins

PS: This does no further processing at the moment, so it's only a simple 
frontend of the ARC RDFa serializer plugin
Permalink | Reply | 0 comments |
headers
Michael Haschke | 6 Feb 2011 18:44

Re: [foaf-dev] FOAF-RDF-2-(X)HTML+RDFa-izer?

Hello Bob and Jones,

2011/2/6 Jonas Smedegaard <dr <at> jones.dk>:
>> Are you aware of any other tools in that direction. I think such a tool
>> might be quite interesting today, or?
> I am interested in this as well.  I know of [FOAFer], [FOAF-explorer] and
> [FOAF Visualizer].

I've started to develop Foafpress, what is probably not exactly what
you are searching for, but maybe you want to give it a try. It takes a
FOAF file (or other RDF data stored in a file) and renders a nice HTML
page, providing RDF as XML, Turtle and NT via content negotiation.
Same formats are possible for import (Foafpress is currently using
Arc2). It is using linked data technics to get more information about
the resource URIs what are used in the FOAF profile (e.g. to link
interests via DBpedia). It also can render an activity stream.
Currently the the template lacks RDFa support b/c I thought content
negotiation is enough to deliver RDF to RDF consuming clients.

Foafpress is written in PHP, the repository is public [1], code is
under GPL2, but as this is only a personal project the development is
not that fast I wished it would be :), if you want to see a live
example, of cause I use it for my own FOAF profile [2].

regards,
Haschek

[1] http://bit.ly/gQtnc8
[2] http://michael.haschke.biz/
_______________________________________________
(Continue reading)

Permalink | Reply | 4 comments |
headers
Bob Ferris | 6 Feb 2011 21:13
Gravatar

Re: [foaf-dev] FOAF-RDF-2-(X)HTML+RDFa-izer?

Hi Michael,

Your project idea sounds interesting and the example page looks really 
good. However, I can't find any hypertext link that references your FOAF 
profile in a RDF serialization format. With RDFa the content negotiation 
step is primarily not necessary. This enables an easier deployment. No 
configuration for content negotiation is necessary. Although, it could 
still be deployed and the (X)HTML+RDFa lives side by side with the other 
RDF serialization formats. Whereby, the (X)HTML+RDFa document has the 
advantage that it is out-of-the-box usable by human and machine agents. 
It enables me to serve processable views for both humans and machines in 
one document.
I think (X)HTML+RDFa deployment is crucial for FOAF profiles and for 
Linked Data deployment in general (see for example GoodRelations).

Cheers,

Bob
Permalink | Reply | 3 comments |
headers
Bob Ferris | 6 Feb 2011 21:26
Gravatar

Re: [foaf-dev] FOAF-RDF-2-(X)HTML+RDFa-izer?

Am 06.02.2011 21:13, schrieb Bob Ferris:
> Hi Michael,
>
> Your project idea sounds interesting and the example page looks really
> good. However, I can't find any hypertext link that references your FOAF
> profile in a RDF serialization format. With RDFa the content negotiation
> step is primarily not necessary. This enables an easier deployment. No
> configuration for content negotiation is necessary. Although, it could
> still be deployed and the (X)HTML+RDFa lives side by side with the other
> RDF serialization formats. Whereby, the (X)HTML+RDFa document has the
> advantage that it is out-of-the-box usable by human and machine agents.
> It enables me to serve processable views for both humans and machines in
> one document.
> I think (X)HTML+RDFa deployment is crucial for FOAF profiles and for
> Linked Data deployment in general (see for example GoodRelations).

Btw, I saw your weighted skills in the profile. I co-developed recently 
the Cognitive Characteristics Ontology[1] which should exactly address 
such a modelling. That means, it enables you to describe cognitive 
pattern e.g., skills, expertises or interests, simply in form of a 
triple or extended. An extended version can include for instance a 
weighting of the cognitive pattern (by utilizing the Weighting 
Ontology[2]). Please have a look at the examples in the Cognitive 
Characteristics Ontology specification documentation e.g., this one [3].
When applying a weighting it is especially important that the scale 
should be no out-of-band knowledge. It should rather be possible to 
discover that knowledge as needed. Hence, it is useful to also provide 
scales in machine processable form.

Cheers,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Leif Warner | 6 Feb 2011 22:16
Picon
Gravatar

Re: [foaf-dev] FOAF-RDF-2-(X)HTML+RDFa-izer?

If you want manual control over that sort of thing, there's XSPARQL that allows you to write SPARQL queries that return XHTML.


Also, more simply, I've been working on using RDFa as a templating / data-binding language for a sort of web framework. [1]
The basic idea is that this:
<p xmlns:foaf="http://xmlns.com/foaf/0.1/">
   <span property="foaf:name"/>
   <a href="" rel="foaf:knows"><span property="foaf:name"/></a>
</p>

gets filled out to this:

<p xmlns:foaf="http://xmlns.com/foaf/0.1/">
 <span property="foaf:name">Leif</span>
 <a href="http://john.com" rel="foaf:knows"><span property="foaf:name">John</span></a>
 <a href="http://bill.com" rel="foaf:knows"><span property="foaf:name">Bill</span></a>
</p>

The idea is just that "property" lists properties of the current subject, and "rel" traverses to a new subject, filling out an "href" or "resource" or whatever along the way.  Runs against Jena right now, but that could easily be changed.

It's quite similar to what's used in Callimachus, a well-developed project, it turns out. [2]

-Leif Warner


On Sun, Feb 6, 2011 at 12:26 PM, Bob Ferris <zazi-o0kiOr3Ba/rk1uMJSBkQmQ@public.gmane.org> wrote:
Am 06.02.2011 21:13, schrieb Bob Ferris:
> Hi Michael,
>
> Your project idea sounds interesting and the example page looks really
> good. However, I can't find any hypertext link that references your FOAF
> profile in a RDF serialization format. With RDFa the content negotiation
> step is primarily not necessary. This enables an easier deployment. No
> configuration for content negotiation is necessary. Although, it could
> still be deployed and the (X)HTML+RDFa lives side by side with the other
> RDF serialization formats. Whereby, the (X)HTML+RDFa document has the
> advantage that it is out-of-the-box usable by human and machine agents.
> It enables me to serve processable views for both humans and machines in
> one document.
> I think (X)HTML+RDFa deployment is crucial for FOAF profiles and for
> Linked Data deployment in general (see for example GoodRelations).

Btw, I saw your weighted skills in the profile. I co-developed recently
the Cognitive Characteristics Ontology[1] which should exactly address
such a modelling. That means, it enables you to describe cognitive
pattern e.g., skills, expertises or interests, simply in form of a
triple or extended. An extended version can include for instance a
weighting of the cognitive pattern (by utilizing the Weighting
Ontology[2]). Please have a look at the examples in the Cognitive
Characteristics Ontology specification documentation e.g., this one [3].
When applying a weighting it is especially important that the scale
should be no out-of-band knowledge. It should rather be possible to
discover that knowledge as needed. Hence, it is useful to also provide
scales in machine processable form.

Cheers,


Bob


PS: If have further questions re. the Cognitive Characteristics
Ontology, don't hesitate to ask me ;)


[1] http://purl.org/ontology/cco/core#
[2] http://purl.org/ontology/wo/core#
[3]
http://purl.org/ontology/cco/cognitivecharacteristics.html#sec-cognitive-patterns-example

_______________________________________________
foaf-dev mailing list
foaf-dev@...
http://lists.foaf-project.org/mailman/listinfo/foaf-dev
Permalink | Reply | 0 comments |
headers
Bob Ferris | 6 Feb 2011 23:11
Gravatar

[foaf-dev] RECommendations Ontology - a vocabulary to formalize preferences in the Semantic Web

Hi,

I discovered per accident the RECommendations Ontology (not to be 
confused with the Recommendation Ontology[2] ;) ). A vocabulary for 
expressing preferences and further concepts to enable personalized 
recommmendations.
On a first view, this ontology looks quite interesting. I'm just 
wondering myself why I didn't get aware of this vocabulary earlier, when 
I searched for an ontology for proper modelling user profiles (and 
laterely pushed forward the Cognitive Charactertics Ontology[3] :\ ).
It would be quite interesting to see this ontology in action. I didn't 
find any good reference for that.
The only misconception I noticed so far, is the usage of rdf:type for 
addressing the subject of a preference. The preference is quite seldom 
also its subject e.g., the preference is not a film, however, I can have 
certain preferences in specific films.

Is anyone of this list aware of this project and/or could provide 
further information about it?

Cheers,

Bob

[1] http://ontologies.ezweb.morfeo-project.org/reco/spec
[2] http://purl.org/ontology/rec/core#
[3] http://purl.org/ontology/cco/core#
Permalink | Reply | 0 comments |
headers
Peter Williams | 7 Feb 2011 21:41
Favicon

Re: [foaf-dev] FOAF-RDF-2-(X)HTML+RDFa-izer?

I know I want the same thing. I just want to fill in a contact form, in a browser plugin, and it writes a file of
XHTML with the RDFa of the FOAF facts. Then the browser shows it. Optionally, the user then adds that static
material to his/her home page.

End of (this) story.

The next story can read my home page and its hcard at site X, and write a new home page at site Y, rewritten into
RDFa with FOAF terms.

Folks are VERY resisting to the notion of static sources of triples, for some reason. I've yet to find out
why. For some reason, folks won't take the space that micro-format hcards and the like occupy, doing the
same thing (less logically).

I think I understand that they want the active agent to be there (so more can build on the URI). But, step by
step... if one wants viral adoption. First do something ANYONE can complete, all billion of us.

-----Original Message-----
From: foaf-dev-bounces@...
[mailto:foaf-dev-bounces@...] On Behalf Of Bob Ferris
Sent: Sunday, February 06, 2011 12:14 PM
To: foaf-dev@...
Subject: Re: [foaf-dev] FOAF-RDF-2-(X)HTML+RDFa-izer?

Hi Michael,

Your project idea sounds interesting and the example page looks really good. However, I can't find any
hypertext link that references your FOAF profile in a RDF serialization format. With RDFa the content
negotiation step is primarily not necessary. This enables an easier deployment. No configuration for
content negotiation is necessary. Although, it could still be deployed and the (X)HTML+RDFa lives side
by side with the other RDF serialization formats. Whereby, the (X)HTML+RDFa document has the advantage
that it is out-of-the-box usable by human and machine agents. 
It enables me to serve processable views for both humans and machines in one document.
I think (X)HTML+RDFa deployment is crucial for FOAF profiles and for Linked Data deployment in general
(see for example GoodRelations).

Cheers,

Bob
_______________________________________________
foaf-dev mailing list
foaf-dev@...
http://lists.foaf-project.org/mailman/listinfo/foaf-dev
Permalink | Reply | 0 comments |

Gmane