[rdfweb-dev] Re: Atom-FOAF
henry.story at bblfish.net
Wed Aug 18 09:44:19 UTC 2004
Here are some of my own thoughts concerning this  work:
- How is this an improvement over RSS1.0. I am very new to RDF, RSS
and have not yet had much time to look at what the RSS1.0 community
has come up
with. Perhaps I am just (badly) re-inventing the wheel. I would love
from that area on how they think one could improve on their work, and
the pitfalls one should avoid. Perhaps there is an RSS1.0 meeting
point I should send this to.
- clearly there is a lot of overlap with Dublin Core. It would be
make these obvious by stating the equality relations between the
I have defined and the Dublin Core ones in the Atom.owl file.
- Should the foaf:Agent class be accessed directly, as it is in the
should one interpose an interface class, say atom:Agent, as Danny
Ayers does in
his Atom-OWL work from which mine is derived. An interface class
be one that specifies the minimal requirements. If one were to do
this, then presumably somebody could still end up with something
foaf:Agent, but I suppose they would have to import some ontology
the equality explicit. What is the best way to deal with importing
Anyway as a side comment I have to say that this RDF thing is really
easy to get a grip on. With tools such as Protege , from Stanford
University, writing object oriented RDF is a breeze. Languages such as
N3 make reading RDF as easy as reading the
morning newspaper. And it really feels good to have something that is
based not only on such widely adopted standards as XML, but also
supported by the full mathematical infrastructure of set theory and
logic . I love power tools, and we have not found anything much
better than mathematics yet. It is only by building on the shoulder of
giants that we can hope to go any further. I think that the view from
up on Tim Berner's Lee's shoulder is going to be pretty awesome.
On 15 Aug 2004, at 16:55, Henry Story wrote:
> I have written out a full description with a lot of illustrations on
> how to FOAFify Atom . The description is written out as a blog
> which is using the format it is advocating to back it up. So it is
> both a description and a proof of concept.
> I see this being useful to the foaf, atom, and bloged communities for
> different reasons:
> - for the atom community it could bring bring some ontological
> insight, and lead to clarifications - mapping always do that.
> - for the foaf community, I suggest this as an opening into the
> blogging space
> - for bloged, the blog editor I am working on, this will be useful
> at the very
> least to help nail down the needed data structures, though I hope to
> use it both as
> an internal and external data-structure.
> I look very much forward to any criticism. This document is the result
> of many such criticisms, for which I am very thankful.
> Henry Story
More information about the foaf-dev