<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
      xmlns:sioc="http://rdfs.org/sioc/ns#"
      xmlns:sioct="http://rdfs.org/sioc/types#"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:admin="http://webns.net/mvcb/"
      xmlns:foaf="http://xmlns.com/foaf/0.1/">
<foaf:Document rdf:about=''>
  <dc:title>SIOC profile for 'sioc-project.org'</dc:title>
  <dc:description>A SIOC profile describes the structure and contents of a community site (e.g., weblog) in a machine processable form. For more information refer to the &lt;a href=&quot;http://rdfs.org/sioc&quot;&gt;SIOC project page&lt;/a&gt;</dc:description>
  <foaf:primaryTopic rdf:resource="http://sioc-project.org/node/318"/>
  <admin:generatorAgent rdf:resource="http://drupal.org/project/sioc"/>
</foaf:Document>
<sioc:Post rdf:about="http://sioc-project.org/node/318">
  <dc:title>SIOC, IRC and events</dc:title>
  <sioc:content>Hi all,
Having some thoughts this afternoon on how to represent a user
connecting / disconnecting channels on IRC, I thaught a sioc:Event
class might be useful.
More generally, it can help to represent subscription to
sioc:Containers, as IRC join / quit, RSS subscribing, starting
membership in a forum ...
This Event class could be defined in the SIOC core itself, but we may
also reuse (or subclass) existing Event classes from other ontologies
(I didn&#039;t look yet, but I think that iCal / music ontology Events may
fit there), and use
- sioc:has_creator
- sioc:has_container
- dcterms:created
- dc:description
to define event property and link it to associated Container / User
More specific event types could be then defined in SIOC core or in
external module, as, JoinEvent / QuitEvent and AwayEvent / BackEvent.
(And even some types specific to the container (as IRCJoinEvent), but
I&#039;m afraid it will lead to a lot of event types, while the 4 first
ones should be enough to describe almost everything, combined with the
sioctypes module to define container type (IRC, Forum ...))
Eg:
 a sioct:ChatChannel.
 a sioc:JoinEvent ;
  sioc:has_container  ;
  sioc:has_creator  ;
  dcterms:created &quot;2006-11-03T12:05:00Z&quot;^^xsd:dateTime .
 a sioc:QuitEvent ;
  sioc:has_container  ;
  sioc:has_creator  ;
  dc:description &quot;Leaving&quot; ;
  dcterms:created &quot;2006-11-03T12:10:00Z&quot;^^xsd:dateTime .
Any comments ?
Best,
Alex.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups &quot;SIOC-Dev&quot; group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
</sioc:content>
  <dcterms:created>2007-11-03T17:02:47+00:00</dcterms:created>
  <dcterms:modified>2007-12-12T10:57:11+00:00</dcterms:modified>
  <sioc:link rdf:resource="http://sioc-project.org/node/318" rdfs:label="SIOC, IRC and events" />
  <sioc:topic rdf:resource="http://sioc-project.org/taxonomy/term/13" rdfs:label="Developers" />
  <sioc:has_creator rdf:resource="http://sioc-project.org/sioc/user/53%2523user" rdfs:seeAlso="http://sioc-project.org/sioc/user/53" />
</sioc:Post>
</rdf:RDF>