[rdfweb-dev] FOAFnet and the future of FOAF in commercial systems
jeremy at jeremygray.ca
Sun May 9 16:37:10 UTC 2004
Sorry about taking so long to respond - I too was stuck in a whole series of
> -----Original Message-----
> From: Marc Canter [mailto:marc at broadbandmechanics.com]
> Sent: Thursday, May 06, 2004 11:52 PM
> To: jeremy at jeremygray.ca; Rdfweb-Dev
> Subject: RE: [rdfweb-dev] FOAFnet and the future of FOAF in commercial
> > So, Marc, would you agree that the fundamental issue is that FOAF is
> > currently and desparately in need of being refactored into a nicely
> > locked down core specification and a range of extension modules?
> > Other readers: agree or disagree?
> > Jeremy Gray
> > ===================
> Marc's finally back from a hell of a meeting (trying to lock down a
> seriously buggy product - called 1Up.com.)
> Here's the minimum FOAF spec that the FOAFnet is proposing.......
> (kudos to Julian Bond and Paul Martino)......
I think that the list you provide might well make for a good "Core"
definition, right up until it shifts into this kind of stuff, which, if
given a choice, I'd rather see split across several non-Core modules,
especially once it gets into names, IM IDs, location-based information,
vCard, bio: stuff, etc:
> Desirable [we're debating on whether or not this is required or not
> - certainly many systems will not have all this data]
> rdf:Description //Information about this document
> foaf:weblog // or home page
> foaf:IM IDs //Any Instant Message IDs and nicks. Beware exposing email
> geo:Point geo:lat="" geo:long=""
> vCard:ADR //Address info. vCard is the best I've found.
> rdfs:seeAlso //Don't use seeAlso to point at anything but more FOAF.
> bio:keywords //I prefer this to interests. Comma Separated.
More information about the foaf-dev