This is a public chat log generated from the #semsol IRC channel.
08:45:43
moin :)
08:46:08
have you planned to pimp the profile page with some microformts?
08:46:17
bengee?
08:46:57
it's poshrdf-based
08:47:19
microformats are a bit tricky to autogenerate when you don't know which data is available
08:47:46
hatom for the activities would be easy, though
08:48:32
but xfn (rel=contact) and hCard for the profile infos should also be possible, or?
08:48:40
it's possible, though. the rdf profile generator supports attribute plugins
08:49:07
you'd just have to define a small template for each microformat attribute
08:49:21
well, "just" might not be the right word here
08:49:27
:)
08:50:35
it's because noserub uses microformats to get some informations from linked sources, so it would be more interoperable
08:54:39
rel-contact would be hard, the sub-templates in the contact list don't know that they are a list of relations, they just render info about "some person"
08:56:11
even though the profile page might look like a custom view, it's really just a set of generic rdf views with different SPARQL filters
08:58:32
hcard could work as I could add the vcard container to the outer html section, and then specify micro-temlates for foaf:name (fn), foaf:homepage (url), foaf:img (photo) etc
08:59:36
an alternative for noserub could be an opensocial service
09:00:13
it should be easy to generate osoc results from sparql queries
09:13:52
and I could similarily add a "contacts as rel-contact" to the Export/subscribe links
09:14:18
or does noserub need the MFs to be on the main profile page?
09:17:58
i think the hcard should be on the main profile page
09:18:31
i don't know if dirk supports <link rel="me" />
09:19:04
but why is the rel=contact difficult?
09:19:34
because the list of people doesn't know its context
09:20:03
i thout all linked people in the sidebar are my contacts!?!
09:20:35
don't you use the social-graph api?
09:20:56
yes, but the the list is generated by a generic SPARQL query fed into an RDF viewer
09:21:47
ok, the problem is not the contact, its the relation.
09:22:12
it's a single line of php: $html = $viewer->getPredicateHTML($this->user_uri, 'knowee:knowee');
09:22:29
right
09:23:17
ok, but do you think it would be very hacky to use rel=contact for any relation?
09:23:30
better than nothing :)
09:24:23
oh, wait
09:24:50
the viewer supports predicate-level templates
09:25:42
wow, Im starting to lose track of my own code
09:26:20
I already have a template for knowee:knowee (the super-prop for all contacts relations)
09:26:46
it has image, homepage, and name
09:27:00
I can just add rel-contact and a small hcard
09:28:34
awesome
09:31:02
ok, vcard+fn+photo+url and rel-contact are active now
09:31:42
I should add rel-me to all next/prev links
09:38:54
jep
09:38:55
:)
09:47:58
ok, I added rel-mes and hatom
10:10:34
.. and now a vcard + at least fn and photo to the main profile section
11:38:44
could you add rel-me also to the "profile" links?
11:58:06
ah, right
12:01:08
:)
12:01:10
ok, done
12:09:01
cool, i tried it with noserub and it works perfect!
12:09:11
yay!
12:09:48
:)
12:10:15
do you provide an rss/atom-feed?
12:10:27
not yet, but that's coming
12:11:32
knowee: a semantic firework :)
12:14:20
heh :)
12:20:45
i mean the german "feuerwerk"