Re: [foaf-dev] FOAF-RDF-
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.
[mailto:foaf-dev-bounces@...] On Behalf Of Bob Ferris
Sent: Sunday, February 06, 2011 12:14 PM
Subject: Re: [foaf-dev] FOAF-RDF-
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).
foaf-dev mailing list