Adopting foaf:Agent, also foaf:tipjar proposal
Mike Linksvayer
ml at creativecommons.org
Mon Feb 16 22:27:12 EST 2004
As I've mentioned
<http://lists.ibiblio.org/pipermail/cc-metadata/2004-January/000269.html>
I'd like to adopt foaf:Agent in place of cc:Agent. See example current
vis foafified use at
<http://lists.ibiblio.org/pipermail/cc-metadata/2004-January/000273.html>.
Most response I've gotten to this is positive, so I'm planning to
move ahead shortly.
I think it makes sense to make cc:Agent a subclass of foaf:Agent, though
I wouldn't recommend using the former going forward (are there any
conventions for deprecating RDF Schema classes short of using OWL
<http://www.w3.org/TR/2004/REC-owl-semantics-20040210/#owl_DeprecatedClass>,
and is there any reason not to add OWL to the CC schema?>
Also, see <http://rdfweb.org/mt/foaflog/archives/2004/02/12/20.07.32/>
for a foaf:tipjar proposal. Lots of people are building on FOAF, but a
tipjar property could be particularly interesting for CC users --
soliciting donations flows naturally from free content offerings, and
lots of people seem to expect CC to do something in this area. Adding
support for a generic pointer to a tipjar seems like a very
low-cost/risk way to get started.
I have a lame imagination, but how about a metadata-aware media player
that makes a "$", or "donate", or "patron" button active when playing
media that is associated with metadata that specifies a tipjar URI as a
0th-generation app?
--
Mike Linksvayer
http://creativecommons.org/learn/aboutus/people#21
More information about the cc-metadata
mailing list