http://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=Colin+BarrettMicroformats Wiki - User contributions [en]2026-04-23T09:59:45ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=mailing-lists-proposals&diff=12948mailing-lists-proposals2007-01-27T06:14:03Z<p>Colin Barrett: /* Mailing Lists Proposals */</p>
<hr />
<div>=Mailing Lists Proposals=<br />
<br />
There is a proposal for creating a new [[mailing-lists|mailing list]] for discussing the research and creation of new microformats so that those discussions do not overwhelm microformats-discuss.<br />
<br />
Some candidates for names with the thinking behind them. Feel free to add your name and opinion (+/- 1 or 0).<br />
<br />
==microformats-new==<br />
Focusing on discussing "new" microformats<br />
* +1 Tantek - this name has the advantage of attracting the newbie that wants to do a "new" microformat.<br />
* +1 ScottReynen<br />
* -1 Lachlan Hunt<br />
* +1 Joe Andrieu<br />
* -1 Andy Mabbett<br />
* +1 Bob Jonkman<br />
* +1 Ben Ward<br />
* +1 Ben O'Neill<br />
* +1 Robert Bachmann<br />
* +1 Colin Barrett - "new" is a shiny word, and will hopefully folks interested in shiny things off uf-discuss.<br />
<br />
==microformats-research==<br />
Focusing on the essential, and often overlooked by first-time proposers "research" phase(s) in the process<br />
* -1 Tantek - agreed with Bob Jonkman's comment, research is only part of the process.<br />
* +1 ScottReynen<br />
* +1 cgriego<br />
* +1 Phae<br />
* +1 JustinThorp<br />
* -1 Andy Mabbett<br />
* -1 Joe Andrieu<br />
* -1 Bob Jonkman (research is part of process, best documented on the Wiki)<br />
* -1 Ben Ward (strikes me as dilution too far of µf-discuss and µf-new)<br />
* 0 Lachlan Hunt<br />
<br />
==microformats-process==<br />
That's really what we're talking about with research of new microformats, isn't it?<br />
* +1 ScottReynen<br />
* +1 Lachlan Hunt<br />
* +1 [[User:Singpolyma|singpolyma]]<br />
* -1 Andy Mabbett<br />
* -1 Joe Andrieu<br />
* -1 cgriego (reminds me of parsing--processing--more so than even microformats-dev)<br />
* -1 Bob Jonkman (Is this the process of creating a new microformat, or the some other process? Document it on the Wiki, I say)<br />
* +0 Tantek - I think this is too vague and won't automatically attract the newbie that wants to propose new microformats. Still the semantic is roughly correct.<br />
* -1 [[User:WizardIsHungry|Jon Williams]] 11:10, 26 Jan 2007 (PST)<br />
* -1 Colin Barrett - A bit ambiguous, might be mistaken for a meta discuss list.<br />
<br />
==microformats-propose==<br />
* -1 Tantek - It misses the point of the process, and implies that there is a desire for microformats proposals - there isn't.<br />
* -1 ScottReynen<br />
* 0 Andy Mabbett<br />
* -1 Bob Jonkman<br />
* -1 Ben Ward<br />
<br />
==microformats-suggest==<br />
Similar to propose but milder ;)<br />
* +1 ChrisMessina<br />
* -1 Tantek - same comment as on microformats-propose<br />
* -1 ScottReynen<br />
* -1 Phae (I feel this is just -propose in disguise)<br />
* -1 BenWest<br />
* -1 Andy Mabbett<br />
* -1 Bob Jonkman<br />
* -1 Ben Ward (If µf-new or similar is created for active spec'ing and format development, uf-discuss would comfortably accomodate this as part of the course of discussion)<br />
<br />
==microformats-work==<br />
For working on microformats, new and old. <br />
* +1 BenWest: I thought we are interested in a list that provides a venue for iterating through the process, and revising and refining microformats in general. discuss is for newbies, and dev is for implementing them.<br />
* -1 Tantek: work could mean anything though, not just work on creating new microformats.<br />
<br />
==microformats-wg==<br />
WG is an abbreviation of Working Group<br />
* +1 Lachlan Hunt<br />
* -1 Tantek: "working group" means something quite specific in W3C terminology. Very little of that applies to the set of people that work on creating new microformats.<br />
* -1 BenWard: As Tantek says, ‘working group’ means something that Microformats doesn't have and doesn't want. What's more, to an observer ‘Working Group’ implies exclusivity which isn't what µf development is about.<br />
<br />
==microformats-tf==<br />
TF is an abbreviation of Task Force<br />
* 0 Lachlan Hunt<br />
* -1 Tantek: Though less overloaded with specific meaning than "working group", "task force" still means something quite specific in W3C terminology as well as other standards organizations. Very little of that applies to the set of people that work on creating new microformats.<br />
* -1 BenWard<br />
<br />
==microformats-meta==<br />
General-purpose "meta-discussion" about microformats.org process and policies<br />
* +1 Ernest Prabhakar: captures all the things normal people don't want on uf-discuss. :-)<br />
* -1 Tantek - this is outside the scope of the proposal for a list for new microformats.<br />
<br />
==Change nothing==<br />
e.g fix uf-dev (we have done that), do nothing else (for now)<br />
* +1 RyanKing<br />
* +1 Tim White<br />
* +1 Andy Mabbett<br />
* 0 Bob Jonkman<br />
* 0 Ben Ward<br />
* -1 BenWest<br />
* -1 Tantek - we have opened uf-dev and I still strongly believe we need a new list for the discussion of new microformats, separate from microformats-discuss in order to avoid overwhelming new folks with details and minutiae of new and in development formats.<br />
* -1 Robert Bachmann<br />
* -1 Ernest Prabhakar: there's way too much "useful" noise that confuses new entrants (and me, sometimes)<br />
* 0 Colin Barrett - I'm not convinced that doing nothing isn't an option, but momentum seems to be in the other direction, so I've registered my vote for uf-new<br />
<br />
= General Comments=<br />
<br />
==Andy Mabbett==<br />
Why not create a new mailing list for each proposal, once it's reached a certain stage? Then , if the uF is created, or the proposal abandoned, the specific list would be closed, and the archive retained as a link from the "brainstorming" page, as a permanent, and discrete record of discussion on that topic. <br />
<br />
Alternatively, the list could be retained for discussion of the implementation and development of that specific uF.<br />
<br />
For example, several academic and professional taxonomists have told me in e-mail that they would be interested in the [[species]] proposal, (and one astronomer, likewise, for [[mars]]/ [[luna]]), but do not have the time to follow a general mailing list; indeed, a couple asked me specifically if I would set up a separate mailing list for the subject.<br />
<br />
[[User:AndyMabbett|Andy Mabbett]] 04:44, 24 Oct 2006 (PDT)<br />
<br />
*The biggest challenge with creating new microformats (especially for new comers) is with following the process. The same discussions are often had over and over for different formats, thus it makes sense for people developing different formats to at least see the discussions around the creation of other formats and hopefully learn from them and avoid repeating the same questions or mistakes. [[User:Tantek|Tantek]] 00:10, 25 Oct 2006 (PDT)<br />
**Someone new to the mailing list won't see past discussion there anyway; they need to be referred to the archive. If busy people, whose expertise we need, choose not to see discussion of other, unrelated microformats, we can't force it on them - we either provide a more specifically-focussed forum, or they don't participate at all - which is best? [[User:AndyMabbett|Andy Mabbett]] 03:06, 25 Oct 2006 (PDT)<br />
***Getting the *process/format/interop/reuse* aspects correct are more important than specific expertise in any vertical field. The point of the process is that we don't actually need the expertise of field experts - anyone can do research on the open web and find examples. In some ways, field experts may be a negative on the process in that they usually want to represent 100% of the possibilities for a format, rather than 80/20 of the *real world* use cases that are already in use on the Web. [[User:Tantek|Tantek]] 10:53, 26 Jan 2007 (PST)<br />
<br />
*In addition, part of the [[microformats]] methodology/philosophy/principles is simplicity and minimalism - the fewer the better. This applies not only to microformats, microformats properties, and microformats values, but to microformats mailing lists as well. Thus since the beginning we have only created lists when absolutely necessary (i.e. when the traffic/topics crowded out one of the other lists), and then only one at a time. [[User:Tantek|Tantek]] 00:10, 25 Oct 2006 (PDT)<br />
**I can see what has happened previously; I'm suggesting - with a stated justification - a variation on that. There is more than one opinion, as to what is "necessary". [[User:AndyMabbett|Andy Mabbett]] 03:06, 25 Oct 2006 (PDT)<br />
***You don't know that more than one list will be necessary until you create the first one and use it. Let's base our actions here on real world experience with the creation of *a* new list, not the theoretical expectations of needing more than one list. In addition, the previous discussion shows why it would be a *negative* to have more than one list that created microformats.[[User:Tantek|Tantek]] 10:53, 26 Jan 2007 (PST)</div>Colin Barretthttp://microformats.org/wiki/index.php?title=chat-formats&diff=31703chat-formats2006-10-30T17:20:31Z<p>Colin Barrett: Trying to get this not to be broken, again.</p>
<hr />
<div><h1> chat formats </h1><br />
<br />
Various formats that are used to represent chat conversations, typically internally. With the use cases from the [[chat-examples]], and the vocabularies used here, the next steps are to start [[chat-brainstorming]] on proposals for a chat microformat.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* ChristopherStJohn<br />
* Tantek Çelik<br />
* Jude Robinson<br />
* Chris Messina<br />
* Colin Barrett<br />
<br />
==ChatZilla Internal Format==<br />
Note that there is no proof that this format is being used "in the wild" for publishing. ChatZilla uses HTML as its presentation layer. This heavily elided excerpt shows two lines from a chat. It gives the flavor (a very big table with each row a chat message divided up into three columns: timestamp, user name and the message itself) but there are many more classes in use in a full log.<br />
<br />
<pre><br />
<div id="messages-outer"><br />
...<br />
<div id="output"><br />
...<br />
<table view-type="IRCChannel" class="msg-table"><br />
<tbody><br />
<tr mark="even" msg-user="cks_ ME!"<br />
statusText="01/31/2006 01:39 PM, cks_!n=chatzill@ppp-70-248-121-149.dsl.rcsntx.swbell.net"<br />
view-type="IRCChannel" dest-type="IRCChannel" msg-dest="#microformats"<br />
msg-type="PRIVMSG" class="msg"><br />
<td time-s="57" time-n="39" time-h="13" time-d="31" time-m="01" time-y="2006" class="msg-timestamp"><br />
</td><br />
<td class="msg-user"><br />
<span>cks_</span><br />
</td><br />
<td class="msg-data"><br />
<span>so, using chatzilla for just a minute so i can extract the logs.</span><br />
</td><br />
</tr><br />
<tr mark="odd" msg-user="Atamido" statusText="01/31/2006 01:43 PM, Atamido!n=atamido@cpe-67-9-173-252.austin.res.rr.com"<br />
view-type="IRCChannel" dest-type="IRCChannel" msg-dest="#microformats"<br />
msg-type="PRIVMSG" class="msg"><br />
<td time-s="25" time-n="43" time-h="13" time-d="31" time-m="01" time-y="2006" class="msg-timestamp"><br />
</td><br />
<td class="msg-user"><br />
<a href="irc://irc.freenode.net/Atamido,isnick" class="chatzilla-link"><br />
<span>Atamido</span><br />
</a><br />
</td><br />
<td class="msg-data"><br />
<span><br />
Here are some examples.<br />
<a target="_content" class="chatzilla-link" href="http://www.hacksrus.com/%7Eginda/chatzilla/motifs.html"><br />
http://www.hacksrus.<wbr><br />
com/~ginda/chatzilla/<wbr><br />
motifs.html<wbr><br />
</a><br />
</span><br />
</td><br />
</tr><br />
</tbody><br />
</table><br />
</div><br />
</div><br />
</pre><br />
<br />
==Google Talk Format Logs==<br />
Again, user1 is local.<br />
<br />
<pre><br />
3<br />
17b5df8a<br />
01c61af0<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v66EC7D7137%22+to%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Esome+but+not+much%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+to%3D%22user1%40gmail.com%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI'm+ready+to+crawl+in+bed+and+read.++Do+well+on+your+paper.++Love++Mom%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v66EC7D7137%22+to%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ethanks%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Emom%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EHi%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ei+totally+forgot+about+the+awning%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Edo+you+want+me+to+come+over%3F%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI+have+tomorrow+off.++Is+the+wind+supposed+to+get+bad+before+then%3F%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Enot+sure.+its+stormy+now%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI'm+ready+if+yo+are.++I+thought+you+would+be+here+anyway+about+the+boat+or+I+would+have+called.%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI+think+we+decided+to+do+the+boat+on+a+dry+night%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ei'll+come+over+now%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
</pre><br />
<br />
==Unified Logging Format==<br />
[http://adiumx.com Adium], [http://gaim.sf.net Gaim], and [http://kopete.kde.org Kopete] are currently developing an XML-based log format.<br />
This is a small sample of version 0.4-01:<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" ?><br />
<chat xmlns="http://purl.org/net/ulf/ns/0.4-01" account="mactigerz" service="AIM"><br />
<event type="windowOpened" time="2006-07-14T12:42:01-05:00"/><br />
<message sender="chz16" time="2006-07-14T12:42:01-05:00">'sup?</message><br />
<message sender="mactigerz" time="2006-07-14T12:43:15-05:00">trying to get to work on the the new XML log format</message><br />
<message sender="chz16" time="2006-07-14T12:43:55-05:00">Doesn't sound bad.</message><br />
<message sender="chz16" time="2006-07-14T12:44:10-05:00">Providing you have the log specs, of course.</message><br />
<message sender="mactigerz" time="2006-07-14T12:45:15-05:00">that's what I'm creating.</message><br />
<status type="offline" sender="chz16" time="2006-07-14T12:46:23-05:00"/><br />
<status type="online" sender="chz16" time="2006-07-14T12:46:43-05:00"/><br />
<status type="away" sender="mactigerz" time="2006-07-14T12:47:10-05:00">brb, working on the XML log format</status><br />
<event type="windowClosed" time="2006-07-14T12:47:20-05:00"/><br />
</chat><br />
</pre><br />
The current version of the spec can be found [http://purl.org/NET/ULF/SPEC here].<br />
<br />
==ILRT Logger Bot Format==<br />
Found at: http://chatlogs.planetrdf.com/swig/, generated by: http://cvs.ilrt.org/cvsweb/redland/logger/, there are three formats: HTML, plain text, and RDF. The entry discussed the RDF format, as it's presumably directed at machines and not people.<br />
<br />
Taking RDF first just because that's kind of fun and is presumably 100% semantics. Pretty straightforward RDF Sequence with date/description/creator, except for the line with a Dublin Core relation stuck in there. As is normal with RDF, semantics are reused, so to fully grok it there's some followon work to do, see: http://www.w3.org/2004/Talks/0522-rrs/ The foaf group got involved with IRC chat since IRC names are one of the ways to identify people, looks like it snowballed, not sure if the ChatChannel stuff is official or not. The Dublin Core and WordNet stuff is mentioned in the FOAF spec index, but seems to be missing from the actual text, I might have been looking at an old version.<br />
<br />
<pre><br />
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"<br />
xmlns:dc="http://purl.org/dc/elements/1.1/"<br />
xmlns:wn="http://xmlns.com/wordnet/1.6/"<br />
xmlns:foaf="http://xmlns.com/foaf/0.1/"><br />
<foaf:ChatChannel rdf:about="irc://irc.freenode.net/swig"><br />
<foaf:chatEventList><br />
<rdf:Seq><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T00-01-19"><br />
<dc:date>2006-02-01T00:01:19Z</dc:date><br />
<dc:description>keithalexander has quit</dc:description><br />
<dc:creator><wn:Person foaf:nick="keithalexander"/></dc:creator><br />
</foaf:chatEvent><br />
</rdf:li><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T00-27-42"><br />
<dc:date>2006-02-01T00:27:42Z</dc:date><br />
<dc:description>Gromgull: nice quote re. x years later</dc:description><br />
<dc:creator><wn:Person foaf:nick="CaptSolo"/></dc:creator><br />
</foaf:chatEvent><br />
</rdf:li><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T01-38-49"><br />
<dc:date>2006-02-01T01:38:49Z</dc:date><br />
<dc:description>A: http://aaronland.info/python/pyupcoming/ from karlUshi</dc:description><br />
<dc:creator><wn:Person foaf:nick="dc_swig"/></dc:creator><br />
<dc:relation rdf:resource="http://aaronland.info/python/pyupcoming/"/><br />
</foaf:chatEvent><br />
</rdf:li><br />
</rdf:Seq><br />
</foaf:chatEventList><br />
</foaf:ChatChannel><br />
</rdf:RDF><br />
</pre><br />
<br />
==Trillian Internal Format==<br />
This is for an AIM chat, but one for a Yahoo! chat looks the same. It is saved as plaintext as well as XML. (user1 is local). This is a description of the XML format, as it is presumably intended for machines and not humans.<br />
<br />
The same in XML:<br />
<pre><br />
<session type="start" time="1112395386" medium="AIM" to="user2" from="user1"/><br />
<message type="incoming_privateMessage" time="1112395386" medium="AIM" to="user1" from="user2" from_display="user2" text="ping"/><br />
<message type="information_standard" time="1112395387" medium="AIM" text="Auto%2Dresponse%20sent%20to%20user2%3A%20My%20hovercraft%20is%20full%20of%20eels%2E"/><br />
<message type="outgoing_privateMessage" time="1112395573" medium="AIM" to="user2" from="user1" from_display="user1" text="hey"/><br />
<session type="stop" time="1112395619" medium="AIM" to="user2" from="user1"/><br />
</pre><br />
<br />
There is also a "user2-assets.xml" file for stuff like Buddy icons & file transers:<br />
<br />
<pre><br />
<asset medium="AIM" name="user2" link="C%3A%5CProgram%20Files%5CTrillian%5Cusers%5Cdefault%5Cbuddyicons%5Cassets%5CAIM%2Duser2%2D1118046544%2Ejpg"/><br />
<asset medium="AIM" name="user2" link="D%3A%5CPIX%5CY2005%5C0619%5CMOV02050%2EMPG"/><br />
<asset medium="AIM" name="user2" link="C%3A%5CDocuments%20and%20Settings%5Cant%5CDesktop%5CDSCN0372_resize%2EJPG"/><br />
<asset medium="AIM" name="user2" link="C%3A%5CProgram%20Files%5CTrillian%5Cusers%5Cdefault%5Cbuddyicons%5Cassets%5CAIM%2Duser2%2D1133932754%2Ejpg"/><br />
</pre><br />
<br />
<br />
== Nature podcast format ==<br />
<br />
Snippets of XML from [http://www.nature.com/nature/podcast/v440/n7085/nature-2006-04-06.html Nature journal's podcast of 6 April 2006]. Differences from chat formats above include the (current) lack of any timestamps, and defined "roles", ie: presenter/interviewer/interviewee.<br />
<br />
<pre><?xml version="1.0" encoding="utf-8"?><br />
<podcast id="nature-2006-04-06"<br />
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<br />
xsi:noNamespaceSchemaLocation="NPG_podcast_transcript.xsd"><br />
<source><br />
<jtl>Nature</jtl><br />
<vol>440</vol><br />
<iss>7085</iss><br />
<idt>20060406</idt><br />
<issn type="print">0028-0836</issn><br />
<issn type="electronic">1476-4679</issn><br />
<cpg><br />
<cpy>2006</cpy><br />
<cpn>Nature Publishing Group</cpn><br />
</cpg><br />
</source><br />
<fm><br />
<doi>10.1038/pod-nature-2006-04-06</doi><br />
<title>Nature Podcast</title><br />
<presenter><br />
<name><br />
<fname>Chris</fname><br />
<sname>Smith</sname><br />
</name><br />
</presenter><br />
<intro><br />
<p><br />
This is a transcript of the 6 April edition of the weekly podcast.<br />
Audio files for the current show and archive episodes can be accessed<br />
from the podcast index page (<weblink url="http://www.nature.com/nature/podcast"/>)...<br />
</p><br />
<p>Sponsor: The podcast from...</p><br />
<p>This week Tiktaalik and what it can tell us about how early life invaded the land..</p><br />
</intro><br />
</fm><br />
<body><br />
<interview><br />
<interviewer><br />
<name><br />
<fname>Chris</fname><br />
<sname>Smith</sname><br />
</name><br />
<p>Hello, I'm Chris Smith. Welcome to the 6th April edition of Nature's podcast.<br />
First this week we're winding our watches back about 380 million years to the time when<br />
the first animals substituted feet for fins and began to heave themselves out of the<br />
sea and onto land... (<cite><br />
<jtl>Nature</jtl><br />
<vid>440</vid>, <ppf>747</ppf>&#45;<ppl>749</ppl>; <cd>2006</cd><br />
<refdoi>10.1038/440747a</refdoi><br />
</cite>).</p><br />
</interviewer><br />
<interviewee><br />
<name><br />
<fname>Neil</fname><br />
<sname>Shubin</sname><br />
</name><br />
<p>The transition from a fish that lives in water to an animal that's able to live on land<br />
is one of the great transitions in the history of life. We know from a variety of...</p><br />
</interviewee><br />
...<br />
</interview><br />
<filler><br />
<p>Well that's it for this week, and thanks for listening. Remember that...</p><br />
<p>Next week we are fighting malaria and finding out how parasites can...</p><br />
<p>Production on this week's podcast was by Anna Lacey in the Department of Pathology<br />
at Cambridge University, and I'm Chris Smith.</p><br />
<p>Sponsor: The podcast is sponsored by Bio-Rad at the centre of scientific discovery<br />
for over 50 years, and on the web at <weblink url="http://www.discover.biorad.com"/>.</p><br />
</filler><br />
</body><br />
</podcast><br />
<br />
<br />
</pre><br />
<br />
==Adium Message Style==<br />
<br />
This is a presentation format, which has really no fixed style imposed. The only rules are the use of replacement strings (e.g. %displayname%), and the use of magic file names to identify which HTML snippet is which template. More information can be found in [http://naib.dnsalias.org:8000/~markfickett/adium/tutorial/AdiumMessageStylemirrored.html this tutorial]. <br />
<br />
There is evidence of [http://adiumx.com Adium], [http://kopete.kde.org Kopete], [http://chucker.mystfans.com/2006/02/27/adium-message-styles-and-skype.entry Skype for Mac] and [http://itorrey.com/index.php?itemid=56 Gizmo for Mac] all using this format, or derivatives thereof.</div>Colin Barretthttp://microformats.org/wiki/index.php?title=chat-formats&diff=9907chat-formats2006-10-30T17:19:41Z<p>Colin Barrett: </p>
<hr />
<div><h1> chat formats </h1><br />
<br />
Various formats that are used to represent chat conversations, typically internally. With the use cases from the [[chat-examples]], and the vocabularies used here, the next steps are to start [[chat-brainstorming]] on proposals for a chat microformat.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* ChristopherStJohn<br />
* Tantek Çelik<br />
* Jude Robinson<br />
* Chris Messina<br />
* Colin Barrett<br />
<br />
==ChatZilla Internal Format==<br />
Note that there is no proof that this format is being used "in the wild" for publishing. ChatZilla uses HTML as its presentation layer. This heavily elided excerpt shows two lines from a chat. It gives the flavor (a very big table with each row a chat message divided up into three columns: timestamp, user name and the message itself) but there are many more classes in use in a full log.<br />
<br />
<pre><br />
<div id="messages-outer"><br />
...<br />
<div id="output"><br />
...<br />
<table view-type="IRCChannel" class="msg-table"><br />
<tbody><br />
<tr mark="even" msg-user="cks_ ME!"<br />
statusText="01/31/2006 01:39 PM, cks_!n=chatzill@ppp-70-248-121-149.dsl.rcsntx.swbell.net"<br />
view-type="IRCChannel" dest-type="IRCChannel" msg-dest="#microformats"<br />
msg-type="PRIVMSG" class="msg"><br />
<td time-s="57" time-n="39" time-h="13" time-d="31" time-m="01" time-y="2006" class="msg-timestamp"><br />
</td><br />
<td class="msg-user"><br />
<span>cks_</span><br />
</td><br />
<td class="msg-data"><br />
<span>so, using chatzilla for just a minute so i can extract the logs.</span><br />
</td><br />
</tr><br />
<tr mark="odd" msg-user="Atamido" statusText="01/31/2006 01:43 PM, Atamido!n=atamido@cpe-67-9-173-252.austin.res.rr.com"<br />
view-type="IRCChannel" dest-type="IRCChannel" msg-dest="#microformats"<br />
msg-type="PRIVMSG" class="msg"><br />
<td time-s="25" time-n="43" time-h="13" time-d="31" time-m="01" time-y="2006" class="msg-timestamp"><br />
</td><br />
<td class="msg-user"><br />
<a href="irc://irc.freenode.net/Atamido,isnick" class="chatzilla-link"><br />
<span>Atamido</span><br />
</a><br />
</td><br />
<td class="msg-data"><br />
<span><br />
Here are some examples.<br />
<a target="_content" class="chatzilla-link" href="http://www.hacksrus.com/%7Eginda/chatzilla/motifs.html"><br />
http://www.hacksrus.<wbr><br />
com/~ginda/chatzilla/<wbr><br />
motifs.html<wbr><br />
</a><br />
</span><br />
</td><br />
</tr><br />
</tbody><br />
</table><br />
</div><br />
</div><br />
</pre><br />
<br />
==Google Talk Format Logs==<br />
Again, user1 is local.<br />
<br />
<pre><br />
3<br />
17b5df8a<br />
01c61af0<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v66EC7D7137%22+to%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Esome+but+not+much%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+to%3D%22user1%40gmail.com%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI'm+ready+to+crawl+in+bed+and+read.++Do+well+on+your+paper.++Love++Mom%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v66EC7D7137%22+to%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ethanks%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Emom%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EHi%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ei+totally+forgot+about+the+awning%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Edo+you+want+me+to+come+over%3F%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI+have+tomorrow+off.++Is+the+wind+supposed+to+get+bad+before+then%3F%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Enot+sure.+its+stormy+now%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI'm+ready+if+yo+are.++I+thought+you+would+be+here+anyway+about+the+boat+or+I+would+have+called.%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI+think+we+decided+to+do+the+boat+on+a+dry+night%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ei'll+come+over+now%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
</pre><br />
<br />
==Unified Logging Format==<br />
[http://adiumx.com Adium], [http://gaim.sf.net Gaim], and [http://kopete.kde.org Kopete] are currently developing an XML-based log format.<br />
This is a small sample of version 0.4-01:<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" ?><br />
<chat xmlns="http://purl.org/net/ulf/ns/0.4-01" account="mactigerz" service="AIM"><br />
<event type="windowOpened" time="2006-07-14T12:42:01-05:00"/><br />
<message sender="chz16" time="2006-07-14T12:42:01-05:00">'sup?</message><br />
<message sender="mactigerz" time="2006-07-14T12:43:15-05:00">trying to get to work on the the new XML log format</message><br />
<message sender="chz16" time="2006-07-14T12:43:55-05:00">Doesn't sound bad.</message><br />
<message sender="chz16" time="2006-07-14T12:44:10-05:00">Providing you have the log specs, of course.</message><br />
<message sender="mactigerz" time="2006-07-14T12:45:15-05:00">that's what I'm creating.</message><br />
<status type="offline" sender="chz16" time="2006-07-14T12:46:23-05:00"/><br />
<status type="online" sender="chz16" time="2006-07-14T12:46:43-05:00"/><br />
<status type="away" sender="mactigerz" time="2006-07-14T12:47:10-05:00">brb, working on the XML log format</status><br />
<event type="windowClosed" time="2006-07-14T12:47:20-05:00"/><br />
</chat><br />
</pre><br />
The current version of the spec can be found [http://purl.org/NET/ULF/SPEC here].<br />
<br />
==ILRT Logger Bot Format==<br />
Found at: http://chatlogs.planetrdf.com/swig/, generated by: http://cvs.ilrt.org/cvsweb/redland/logger/, there are three formats: HTML, plain text, and RDF. The entry discussed the RDF format, as it's presumably directed at machines and not people.<br />
<br />
Taking RDF first just because that's kind of fun and is presumably 100% semantics. Pretty straightforward RDF Sequence with date/description/creator, except for the line with a Dublin Core relation stuck in there. As is normal with RDF, semantics are reused, so to fully grok it there's some followon work to do, see: http://www.w3.org/2004/Talks/0522-rrs/ The foaf group got involved with IRC chat since IRC names are one of the ways to identify people, looks like it snowballed, not sure if the ChatChannel stuff is official or not. The Dublin Core and WordNet stuff is mentioned in the FOAF spec index, but seems to be missing from the actual text, I might have been looking at an old version.<br />
<br />
<pre><br />
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"<br />
xmlns:dc="http://purl.org/dc/elements/1.1/"<br />
xmlns:wn="http://xmlns.com/wordnet/1.6/"<br />
xmlns:foaf="http://xmlns.com/foaf/0.1/"><br />
<foaf:ChatChannel rdf:about="irc://irc.freenode.net/swig"><br />
<foaf:chatEventList><br />
<rdf:Seq><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T00-01-19"><br />
<dc:date>2006-02-01T00:01:19Z</dc:date><br />
<dc:description>keithalexander has quit</dc:description><br />
<dc:creator><wn:Person foaf:nick="keithalexander"/></dc:creator><br />
</foaf:chatEvent><br />
</rdf:li><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T00-27-42"><br />
<dc:date>2006-02-01T00:27:42Z</dc:date><br />
<dc:description>Gromgull: nice quote re. x years later</dc:description><br />
<dc:creator><wn:Person foaf:nick="CaptSolo"/></dc:creator><br />
</foaf:chatEvent><br />
</rdf:li><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T01-38-49"><br />
<dc:date>2006-02-01T01:38:49Z</dc:date><br />
<dc:description>A: http://aaronland.info/python/pyupcoming/ from karlUshi</dc:description><br />
<dc:creator><wn:Person foaf:nick="dc_swig"/></dc:creator><br />
<dc:relation rdf:resource="http://aaronland.info/python/pyupcoming/"/><br />
</foaf:chatEvent><br />
</rdf:li><br />
</rdf:Seq><br />
</foaf:chatEventList><br />
</foaf:ChatChannel><br />
</rdf:RDF><br />
</pre><br />
<br />
==Trillian Internal Format==<br />
This is for an AIM chat, but one for a Yahoo! chat looks the same. It is saved as plaintext as well as XML. (user1 is local). This is a description of the XML format, as it is presumably intended for machines and not humans.<br />
<br />
The same in XML:<br />
<pre><br />
<session type="start" time="1112395386" medium="AIM" to="user2" from="user1"/><br />
<message type="incoming_privateMessage" time="1112395386" medium="AIM" to="user1" from="user2" from_display="user2" text="ping"/><br />
<message type="information_standard" time="1112395387" medium="AIM" text="Auto%2Dresponse%20sent%20to%20user2%3A%20My%20hovercraft%20is%20full%20of%20eels%2E"/><br />
<message type="outgoing_privateMessage" time="1112395573" medium="AIM" to="user2" from="user1" from_display="user1" text="hey"/><br />
<session type="stop" time="1112395619" medium="AIM" to="user2" from="user1"/><br />
</pre><br />
<br />
There is also a "user2-assets.xml" file for stuff like Buddy icons & file transers:<br />
<br />
<pre><br />
<asset medium="AIM" name="user2" link="C%3A%5CProgram%20Files%5CTrillian%5Cusers%5Cdefault%5Cbuddyicons%5Cassets%5CAIM%2Duser2%2D1118046544%2Ejpg"/><br />
<asset medium="AIM" name="user2" link="D%3A%5CPIX%5CY2005%5C0619%5CMOV02050%2EMPG"/><br />
<asset medium="AIM" name="user2" link="C%3A%5CDocuments%20and%20Settings%5Cant%5CDesktop%5CDSCN0372_resize%2EJPG"/><br />
<asset medium="AIM" name="user2" link="C%3A%5CProgram%20Files%5CTrillian%5Cusers%5Cdefault%5Cbuddyicons%5Cassets%5CAIM%2Duser2%2D1133932754%2Ejpg"/><br />
</pre><br />
<br />
<br />
== Nature podcast format ==<br />
<br />
Snippets of XML from [http://www.nature.com/nature/podcast/v440/n7085/nature-2006-04-06.html Nature journal's podcast of 6 April 2006]. Differences from chat formats above include the (current) lack of any timestamps, and defined "roles", ie: presenter/interviewer/interviewee.<br />
<br />
<pre><?xml version="1.0" encoding="utf-8"?><br />
<podcast id="nature-2006-04-06"<br />
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<br />
xsi:noNamespaceSchemaLocation="NPG_podcast_transcript.xsd"><br />
<source><br />
<jtl>Nature</jtl><br />
<vol>440</vol><br />
<iss>7085</iss><br />
<idt>20060406</idt><br />
<issn type="print">0028-0836</issn><br />
<issn type="electronic">1476-4679</issn><br />
<cpg><br />
<cpy>2006</cpy><br />
<cpn>Nature Publishing Group</cpn><br />
</cpg><br />
</source><br />
<fm><br />
<doi>10.1038/pod-nature-2006-04-06</doi><br />
<title>Nature Podcast</title><br />
<presenter><br />
<name><br />
<fname>Chris</fname><br />
<sname>Smith</sname><br />
</name><br />
</presenter><br />
<intro><br />
<p><br />
This is a transcript of the 6 April edition of the weekly podcast.<br />
Audio files for the current show and archive episodes can be accessed<br />
from the podcast index page (<weblink url="http://www.nature.com/nature/podcast"/>)...<br />
</p><br />
<p>Sponsor: The podcast from...</p><br />
<p>This week Tiktaalik and what it can tell us about how early life invaded the land..</p><br />
</intro><br />
</fm><br />
<body><br />
<interview><br />
<interviewer><br />
<name><br />
<fname>Chris</fname><br />
<sname>Smith</sname><br />
</name><br />
<p>Hello, I'm Chris Smith. Welcome to the 6th April edition of Nature's podcast.<br />
First this week we're winding our watches back about 380 million years to the time when<br />
the first animals substituted feet for fins and began to heave themselves out of the<br />
sea and onto land... (<cite><br />
<jtl>Nature</jtl><br />
<vid>440</vid>, <ppf>747</ppf>&#45;<ppl>749</ppl>; <cd>2006</cd><br />
<refdoi>10.1038/440747a</refdoi><br />
</cite>).</p><br />
</interviewer><br />
<interviewee><br />
<name><br />
<fname>Neil</fname><br />
<sname>Shubin</sname><br />
</name><br />
<p>The transition from a fish that lives in water to an animal that's able to live on land<br />
is one of the great transitions in the history of life. We know from a variety of...</p><br />
</interviewee><br />
...<br />
</interview><br />
<filler><br />
<p>Well that's it for this week, and thanks for listening. Remember that...</p><br />
<p>Next week we are fighting malaria and finding out how parasites can...</p><br />
<p>Production on this week's podcast was by Anna Lacey in the Department of Pathology<br />
at Cambridge University, and I'm Chris Smith.</p><br />
<p>Sponsor: The podcast is sponsored by Bio-Rad at the centre of scientific discovery<br />
for over 50 years, and on the web at <weblink url="http://www.discover.biorad.com"/>.</p><br />
</filler><br />
</body><br />
</podcast><br />
<br />
<br />
</pre><br />
<br />
==Adium/Kopete Message Style==<br />
This is a presentation format, which has really no fixed style imposed. The only rules are the use of replacement strings (e.g. %displayname%), and the use of magic file names to identify which HTML snippet is which template. More information can be found in [http://naib.dnsalias.org:8000/~markfickett/adium/tutorial/AdiumMessageStylemirrored.html this tutorial]. <br />
<br />
There is evidence of [http://adiumx.com Adium], [http://kopete.kde.org Kopete], [http://chucker.mystfans.com/2006/02/27/adium-message-styles-and-skype.entry Skype for Mac] and [http://itorrey.com/index.php?itemid=56 Gizmo for Mac] all using this format, or derivatives thereof.</div>Colin Barretthttp://microformats.org/wiki/index.php?title=chat-formats&diff=9906chat-formats2006-10-30T17:09:10Z<p>Colin Barrett: Adding the adium message style information</p>
<hr />
<div><h1> chat formats </h1><br />
<br />
Various formats that are used to represent chat conversations, typically internally. With the use cases from the [[chat-examples]], and the vocabularies used here, the next steps are to start [[chat-brainstorming]] on proposals for a chat microformat.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* ChristopherStJohn<br />
* Tantek Çelik<br />
* Jude Robinson<br />
* Chris Messina<br />
* Colin Barrett<br />
<br />
==ChatZilla Internal Format==<br />
Note that there is no proof that this format is being used "in the wild" for publishing. ChatZilla uses HTML as its presentation layer. This heavily elided excerpt shows two lines from a chat. It gives the flavor (a very big table with each row a chat message divided up into three columns: timestamp, user name and the message itself) but there are many more classes in use in a full log.<br />
<br />
<pre><br />
<div id="messages-outer"><br />
...<br />
<div id="output"><br />
...<br />
<table view-type="IRCChannel" class="msg-table"><br />
<tbody><br />
<tr mark="even" msg-user="cks_ ME!"<br />
statusText="01/31/2006 01:39 PM, cks_!n=chatzill@ppp-70-248-121-149.dsl.rcsntx.swbell.net"<br />
view-type="IRCChannel" dest-type="IRCChannel" msg-dest="#microformats"<br />
msg-type="PRIVMSG" class="msg"><br />
<td time-s="57" time-n="39" time-h="13" time-d="31" time-m="01" time-y="2006" class="msg-timestamp"><br />
</td><br />
<td class="msg-user"><br />
<span>cks_</span><br />
</td><br />
<td class="msg-data"><br />
<span>so, using chatzilla for just a minute so i can extract the logs.</span><br />
</td><br />
</tr><br />
<tr mark="odd" msg-user="Atamido" statusText="01/31/2006 01:43 PM, Atamido!n=atamido@cpe-67-9-173-252.austin.res.rr.com"<br />
view-type="IRCChannel" dest-type="IRCChannel" msg-dest="#microformats"<br />
msg-type="PRIVMSG" class="msg"><br />
<td time-s="25" time-n="43" time-h="13" time-d="31" time-m="01" time-y="2006" class="msg-timestamp"><br />
</td><br />
<td class="msg-user"><br />
<a href="irc://irc.freenode.net/Atamido,isnick" class="chatzilla-link"><br />
<span>Atamido</span><br />
</a><br />
</td><br />
<td class="msg-data"><br />
<span><br />
Here are some examples.<br />
<a target="_content" class="chatzilla-link" href="http://www.hacksrus.com/%7Eginda/chatzilla/motifs.html"><br />
http://www.hacksrus.<wbr><br />
com/~ginda/chatzilla/<wbr><br />
motifs.html<wbr><br />
</a><br />
</span><br />
</td><br />
</tr><br />
</tbody><br />
</table><br />
</div><br />
</div><br />
</pre><br />
<br />
==Google Talk Format Logs==<br />
Again, user1 is local.<br />
<br />
<pre><br />
3<br />
17b5df8a<br />
01c61af0<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v66EC7D7137%22+to%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Esome+but+not+much%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+to%3D%22user1%40gmail.com%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI'm+ready+to+crawl+in+bed+and+read.++Do+well+on+your+paper.++Love++Mom%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v66EC7D7137%22+to%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ethanks%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Emom%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EHi%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ei+totally+forgot+about+the+awning%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Edo+you+want+me+to+come+over%3F%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI+have+tomorrow+off.++Is+the+wind+supposed+to+get+bad+before+then%3F%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Enot+sure.+its+stormy+now%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI'm+ready+if+yo+are.++I+thought+you+would+be+here+anyway+about+the+boat+or+I+would+have+called.%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI+think+we+decided+to+do+the+boat+on+a+dry+night%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ei'll+come+over+now%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
</pre><br />
<br />
==Unified Logging Format==<br />
[http://adiumx.com Adium], [http://gaim.sf.net Gaim], and [http://kopete.kde.org Kopete] are currently developing an XML-based log format.<br />
This is a small sample of version 0.4-01:<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" ?><br />
<chat xmlns="http://purl.org/net/ulf/ns/0.4-01" account="mactigerz" service="AIM"><br />
<event type="windowOpened" time="2006-07-14T12:42:01-05:00"/><br />
<message sender="chz16" time="2006-07-14T12:42:01-05:00">'sup?</message><br />
<message sender="mactigerz" time="2006-07-14T12:43:15-05:00">trying to get to work on the the new XML log format</message><br />
<message sender="chz16" time="2006-07-14T12:43:55-05:00">Doesn't sound bad.</message><br />
<message sender="chz16" time="2006-07-14T12:44:10-05:00">Providing you have the log specs, of course.</message><br />
<message sender="mactigerz" time="2006-07-14T12:45:15-05:00">that's what I'm creating.</message><br />
<status type="offline" sender="chz16" time="2006-07-14T12:46:23-05:00"/><br />
<status type="online" sender="chz16" time="2006-07-14T12:46:43-05:00"/><br />
<status type="away" sender="mactigerz" time="2006-07-14T12:47:10-05:00">brb, working on the XML log format</status><br />
<event type="windowClosed" time="2006-07-14T12:47:20-05:00"/><br />
</chat><br />
</pre><br />
The current version of the spec can be found [http://purl.org/NET/ULF/SPEC here].<br />
<br />
==ILRT Logger Bot Format==<br />
Found at: http://chatlogs.planetrdf.com/swig/, generated by: http://cvs.ilrt.org/cvsweb/redland/logger/, there are three formats: HTML, plain text, and RDF. The entry discussed the RDF format, as it's presumably directed at machines and not people.<br />
<br />
Taking RDF first just because that's kind of fun and is presumably 100% semantics. Pretty straightforward RDF Sequence with date/description/creator, except for the line with a Dublin Core relation stuck in there. As is normal with RDF, semantics are reused, so to fully grok it there's some followon work to do, see: http://www.w3.org/2004/Talks/0522-rrs/ The foaf group got involved with IRC chat since IRC names are one of the ways to identify people, looks like it snowballed, not sure if the ChatChannel stuff is official or not. The Dublin Core and WordNet stuff is mentioned in the FOAF spec index, but seems to be missing from the actual text, I might have been looking at an old version.<br />
<br />
<pre><br />
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"<br />
xmlns:dc="http://purl.org/dc/elements/1.1/"<br />
xmlns:wn="http://xmlns.com/wordnet/1.6/"<br />
xmlns:foaf="http://xmlns.com/foaf/0.1/"><br />
<foaf:ChatChannel rdf:about="irc://irc.freenode.net/swig"><br />
<foaf:chatEventList><br />
<rdf:Seq><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T00-01-19"><br />
<dc:date>2006-02-01T00:01:19Z</dc:date><br />
<dc:description>keithalexander has quit</dc:description><br />
<dc:creator><wn:Person foaf:nick="keithalexander"/></dc:creator><br />
</foaf:chatEvent><br />
</rdf:li><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T00-27-42"><br />
<dc:date>2006-02-01T00:27:42Z</dc:date><br />
<dc:description>Gromgull: nice quote re. x years later</dc:description><br />
<dc:creator><wn:Person foaf:nick="CaptSolo"/></dc:creator><br />
</foaf:chatEvent><br />
</rdf:li><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T01-38-49"><br />
<dc:date>2006-02-01T01:38:49Z</dc:date><br />
<dc:description>A: http://aaronland.info/python/pyupcoming/ from karlUshi</dc:description><br />
<dc:creator><wn:Person foaf:nick="dc_swig"/></dc:creator><br />
<dc:relation rdf:resource="http://aaronland.info/python/pyupcoming/"/><br />
</foaf:chatEvent><br />
</rdf:li><br />
</rdf:Seq><br />
</foaf:chatEventList><br />
</foaf:ChatChannel><br />
</rdf:RDF><br />
</pre><br />
<br />
==Trillian Internal Format==<br />
This is for an AIM chat, but one for a Yahoo! chat looks the same. It is saved as plaintext as well as XML. (user1 is local). This is a description of the XML format, as it is presumably intended for machines and not humans.<br />
<br />
The same in XML:<br />
<pre><br />
<session type="start" time="1112395386" medium="AIM" to="user2" from="user1"/><br />
<message type="incoming_privateMessage" time="1112395386" medium="AIM" to="user1" from="user2" from_display="user2" text="ping"/><br />
<message type="information_standard" time="1112395387" medium="AIM" text="Auto%2Dresponse%20sent%20to%20user2%3A%20My%20hovercraft%20is%20full%20of%20eels%2E"/><br />
<message type="outgoing_privateMessage" time="1112395573" medium="AIM" to="user2" from="user1" from_display="user1" text="hey"/><br />
<session type="stop" time="1112395619" medium="AIM" to="user2" from="user1"/><br />
</pre><br />
<br />
There is also a "user2-assets.xml" file for stuff like Buddy icons & file transers:<br />
<br />
<pre><br />
<asset medium="AIM" name="user2" link="C%3A%5CProgram%20Files%5CTrillian%5Cusers%5Cdefault%5Cbuddyicons%5Cassets%5CAIM%2Duser2%2D1118046544%2Ejpg"/><br />
<asset medium="AIM" name="user2" link="D%3A%5CPIX%5CY2005%5C0619%5CMOV02050%2EMPG"/><br />
<asset medium="AIM" name="user2" link="C%3A%5CDocuments%20and%20Settings%5Cant%5CDesktop%5CDSCN0372_resize%2EJPG"/><br />
<asset medium="AIM" name="user2" link="C%3A%5CProgram%20Files%5CTrillian%5Cusers%5Cdefault%5Cbuddyicons%5Cassets%5CAIM%2Duser2%2D1133932754%2Ejpg"/><br />
</pre><br />
<br />
<br />
== Nature podcast format ==<br />
<br />
Snippets of XML from [http://www.nature.com/nature/podcast/v440/n7085/nature-2006-04-06.html Nature journal's podcast of 6 April 2006]. Differences from chat formats above include the (current) lack of any timestamps, and defined "roles", ie: presenter/interviewer/interviewee.<br />
<br />
<pre><?xml version="1.0" encoding="utf-8"?><br />
<podcast id="nature-2006-04-06"<br />
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<br />
xsi:noNamespaceSchemaLocation="NPG_podcast_transcript.xsd"><br />
<source><br />
<jtl>Nature</jtl><br />
<vol>440</vol><br />
<iss>7085</iss><br />
<idt>20060406</idt><br />
<issn type="print">0028-0836</issn><br />
<issn type="electronic">1476-4679</issn><br />
<cpg><br />
<cpy>2006</cpy><br />
<cpn>Nature Publishing Group</cpn><br />
</cpg><br />
</source><br />
<fm><br />
<doi>10.1038/pod-nature-2006-04-06</doi><br />
<title>Nature Podcast</title><br />
<presenter><br />
<name><br />
<fname>Chris</fname><br />
<sname>Smith</sname><br />
</name><br />
</presenter><br />
<intro><br />
<p><br />
This is a transcript of the 6 April edition of the weekly podcast.<br />
Audio files for the current show and archive episodes can be accessed<br />
from the podcast index page (<weblink url="http://www.nature.com/nature/podcast"/>)...<br />
</p><br />
<p>Sponsor: The podcast from...</p><br />
<p>This week Tiktaalik and what it can tell us about how early life invaded the land..</p><br />
</intro><br />
</fm><br />
<body><br />
<interview><br />
<interviewer><br />
<name><br />
<fname>Chris</fname><br />
<sname>Smith</sname><br />
</name><br />
<p>Hello, I'm Chris Smith. Welcome to the 6th April edition of Nature's podcast.<br />
First this week we're winding our watches back about 380 million years to the time when<br />
the first animals substituted feet for fins and began to heave themselves out of the<br />
sea and onto land... (<cite><br />
<jtl>Nature</jtl><br />
<vid>440</vid>, <ppf>747</ppf>&#45;<ppl>749</ppl>; <cd>2006</cd><br />
<refdoi>10.1038/440747a</refdoi><br />
</cite>).</p><br />
</interviewer><br />
<interviewee><br />
<name><br />
<fname>Neil</fname><br />
<sname>Shubin</sname><br />
</name><br />
<p>The transition from a fish that lives in water to an animal that's able to live on land<br />
is one of the great transitions in the history of life. We know from a variety of...</p><br />
</interviewee><br />
...<br />
</interview><br />
<filler><br />
<p>Well that's it for this week, and thanks for listening. Remember that...</p><br />
<p>Next week we are fighting malaria and finding out how parasites can...</p><br />
<p>Production on this week's podcast was by Anna Lacey in the Department of Pathology<br />
at Cambridge University, and I'm Chris Smith.</p><br />
<p>Sponsor: The podcast is sponsored by Bio-Rad at the centre of scientific discovery<br />
for over 50 years, and on the web at <weblink url="http://www.discover.biorad.com"/>.</p><br />
</filler><br />
</body><br />
</podcast><br />
<br />
<br />
</pre><br />
<br />
==Adium/Kopete Message Style==<br />
This is a presentation format, which has really no fixed style imposed. The only rules are the use of replacement strings (e.g. %displayname%), and the use of magic file names to identify which HTML snippet is which template. More information can be found in [http://naib.dnsalias.org:8000/~markfickett/adium/tutorial/AdiumMessageStylemirrored.html this tutorial]. There is evidence of [http://adiumx.com Adium], [http://kopete.kde.org] Kopete, [http://chucker.mystfans.com/2006/02/27/adium-message-styles-and-skype.entry Skype for Mac] and [http://itorrey.com/index.php?itemid=56 Gizmo] for Mac all using this format, or derivatives thereof.</div>Colin Barretthttp://microformats.org/wiki/index.php?title=chat-brainstorming&diff=31905chat-brainstorming2006-10-30T17:01:08Z<p>Colin Barrett: Noting the debate about the scope of the chat uf</p>
<hr />
<div>== Requirements ==<br />
<br />
=== Scope ===<br />
<br />
Should a microformat matching these requirements be capable of representing only transcripts of existing IM protocols or should it also be able to serve as an exchange format itself. This '''might''' be useful for simple AJAX IM platforms, although I doubt if [http://www.xmpp.org/ XMPP] is not per definition a better choise for such purposes. --[[User:BigSmoke|BigSmoke]] 13:09, 21 Jun 2006 (PDT)<br />
<br />
- Anything that can be parsed can be used in AJAX, so we don't need to consider this in developing a microformat. --[[User:ScottReynen|Scott Reynen]]<br />
<br />
How much, and what kind of data is going to be in the file? The work done by the [http://purl.org/NET/ULF/SPEC Unified Logging Format WG] has a pretty good overview of the various types of things that an IM client would want to log. Don't make too much of a bikeshed about it -- I'm mostly linking it beacuse it's a good overview of the sorts of general element types (message, event, status) we probably want to use. --[[User:Colin Barrett|Colin Barrett]] 05:33, 22 Aug 2006 (PDT)<br />
<br />
There has been debate on the mailing list recently as to wether on-disk data storage or presentation should be the focus of this microformat. [http://microformats.org/discuss/mail/microformats-discuss/2006-October/006869.html here is one thread]. pipermail is a bit braindead so it may be useful to look at the whole [http://microformats.org/discuss/mail/microformats-discuss/2006-October/thread.html#6869 october page]<br />
<br />
=== Chat rooms ===<br />
<br />
Is it useful for this microformat to support the representation of "chat rooms", such as IRC channels? --[[User:BigSmoke|BigSmoke]]<br />
<br />
- Location is a problem that can be clearly separated from chats. We should stick to solving the smallest problem possible, so we can more easily combine microformats later to solve larger problems. --[[User:ScottReynen|Scott Reynen]]<br />
<br />
- On chat-formats and chat-examples, IRC logs are used. I would say we should include IRC logs in our spec -- it just makes sense to design for mult-user chat, because one-to-one messaging is just a special case of that. --[[User:Colin Barrett|Colin Barrett]] 05:33, 22 Aug 2006 (PDT)<br />
== Example playground ==<br />
<br />
<pre><br />
<div class="hchat-log"><br />
<p class="hchat-msg"><br />
<abbr class="time" title="YYYY-MM-DDTHH:MM:SS">HH:MM:SS</abbr><br />
<!-- Please, fill me in --><br />
</p><br />
</div><br />
</pre><br />
<br />
== hChatLog Strawman Proposal==<br />
<br />
Initially compiled by [[User:Ben Ward|BenWard]].<br />
<br />
Following [http://microformats.org/discuss/mail/microformats-discuss/2006-October/006719.html a post] to uf-discuss, Colin Barrett requested I write up my hChatLog example in more detail, so I present it here as a straw man proposal to see if chat can gain any traction. <br />
<br />
It's based around the initial brainstorming, but was initially led by my own preferences for mark-up. The class names introduced are reused or derived from other existing microformats, and new class names are based on the Unified Logging Format, as the element names in ULF are already human-friendly.<br />
<br />
===hChatLog Structure===<br />
<br />
* hChatLog<br />
** message<br />
*** dt (or time)<br />
*** sender (which MUST be an hCard and SHOULD be a CITE element)<br />
*** 'quoted message content' (which MUST be a Q or BLOCKQUOTE element)<br />
** status<br />
*** dt (or time)<br />
*** sender (which MUST be an hCard and SHOULD be a CITE element)<br />
*** type (from a predefined list of values)<br />
*** message (optional, the custom message the user assigns to a status, e.g. an 'away message')<br />
<br />
====Notes about the above structure====<br />
<br />
* message, sender, status and type are all taken from ULF. Note that 'type' also corresponds with tel > type and adr > type in hCard.<br />
* 'dt' is proposed as a derivative of 'dtstart' and 'dtend' as used in hCalendar, however 'time' (again from ULF) may be preferable<br />
* The message text does not have a class name, and is instead identified as from quoted text within a message, marked up with Q (for common single line messages) or BLOCKQUOTE (for multiline or otherwise complex messages).<br />
<br />
====List of status 'type' values====<br />
<br />
This should be a single-word list of the common status types from current IM implementations, namely:<br />
<br />
* Online<br />
* Offline<br />
* Away<br />
* Busy<br />
* BRB (Be Right Back)<br />
* Lunch (Out To Lunch)<br />
* Phone (On The Phone)<br />
<br />
===Example===<br />
<br />
Note that this example uses an OL as the container, with LI elements for each message/status. This mark-up scheme for dialogue is subject to opinions of how strictly an Ordered List should be specified. For this reason OL/LI mark-up as is not specified as 'SHOULD' or 'MUST' in the structure above. The WHATWG list was recently included a discussion about tightening of the definition of OL for HTML5 (no definitive resolution was made though).<br />
<br />
<pre>&lt;!-- &lsquo;hChatLog&rsquo;&nbsp;straw man by Ben Ward --&gt;<br />
&lt;ol class=&quot;hChatLog&quot;&gt;<br />
&lt;li class=&quot;message&quot;&gt;<br />
&lt;abbr class=&quot;dt&quot; title=&quot;2006-10-26T01:22:00+0100&quot;&gt;1:22am&lt;/abbr&gt;: <br />
&lt;cite class=&quot;sender vcard&quot;&gt;&lt;a class=&quot;fn nickname url&quot; href=&quot;aim:goim?screenname=HanniUsername&quot;&gt;Hanni&lt;/a&gt;&lt;/cite&gt;<br />
&lt;q&gt;Hello Ben&lt;/q&gt;<br />
&lt;/li&gt;<br />
&lt;li class=&quot;message&quot;&gt;<br />
&lt;abbr class=&quot;dt&quot; title=&quot;2006-10-26T01:25:00+0100&quot;&gt;1:25am&lt;/abbr&gt;: <br />
&lt;cite class=&quot;sender vcard&quot;&gt;&lt;a class=&quot;fn nickname url&quot; href=&quot;aim:goim?screenname=BenWardcouk&quot;&gt;Ben&lt;/a&gt;&lt;/cite&gt;<br />
&lt;blockquote&gt;<br />
&lt;p&gt;Hello Hanni&lt;/p&gt;<br />
&lt;p&gt;How&apos;re you today?&lt;/p&gt;<br />
&lt;/blockquote&gt;<br />
&lt;/li&gt;<br />
&lt;li class=&quot;status&quot;&gt; &lt;!-- not &apos;event&apos; --&gt;<br />
&lt;abbr class=&quot;dt&quot; title=&quot;2006-08-08T01:27:00+0100&quot;&gt;1:27am&lt;/abbr&gt;: <br />
&lt;span class=&quot;sender vcard&quot;&gt;&lt;a class=&quot;fn nickname url&quot; href=&quot;aim:goim?screenname=HanniUsername&quot;&gt;Hanni&lt;/a&gt; went &lt;span class=&quot;type&quot;&gt;away&lt;/span&gt;&lt;/span&gt;<br />
&lt;/li&gt;<br />
&lt;li class=&quot;status&quot;&gt;<br />
&lt;abbr class=&quot;dt&quot; title=&quot;2006-08-08T01:28:00+0100&quot;&gt;1:28am&lt;/abbr&gt;: <br />
&lt;span class=&quot;sender vcard&quot;&gt;&lt;a class=&quot;fn nickname url&quot; href=&quot;aim:goim?screenname=HanniUsername&quot;&gt;Hanni&lt;/a&gt;<br />
&lt;abbr class=&quot;type&quot; title=&quot;online&quot;&gt;came back&lt;/abbr&gt;&lt;/span&gt;<br />
&lt;/li&gt;<br />
&lt;/ol&gt;</pre><br />
<br />
In this example, two messages are exchanged followed by two status changes. Each message contains an hCard, identifying the user's nickname (which should map to the user's 'display name' or 'screen name') and uses the form proposed in [[hcard-examples]] for New Types of Contact Info to identify the AIM usernames.<br />
<br />
Messages are quoted. Single line messages in Q elements and multiline messages in BLOCKQUOTE. There's no reason to limit each message to contain only one Q or BLOCKQUOTE, as depending on the precision of the timestamps being used, it may be appropriate to allow messages from the same individual to be placed together.<br />
<br />
Status messages contain the DT, SENDER and then a TYPE. Since we're presenting humans-first information here, note that the first status change ('Hanni went away') uses the exact status type, the second ('Hanni came back') uses the abbr-pattern to embed the 'online' status type name.<br />
<br />
It may be necessary to integrate the IM service URL patterns into the 'hChatLog' microformat itself, depending on whether they are treated as a formal part of hCard yet, but a means to identify service usernames with less reliance on implications is needed (for example, MSN accounts are identified by @hotmail, @msn or @passport domains, which is not inclusive of MSN Messenger users with their own domains, while other IM services may not have a URI scheme at all).<br />
<br />
===Example of 'chat-username' class, extending hCard===<br />
<br />
Whilst fitting this into the process needs to be clarified, it would be clearest to introduce a 'chat-username' class within hCards in hChatLog, to identify usernames.<br />
<br />
<pre>&lt;li class=&quot;message&quot;&gt;<br />
&lt;abbr class=&quot;dt&quot; title=&quot;2006-10-26T01:25:00+0100&quot;&gt;1:25am&lt;/abbr&gt;: <br />
&lt;cite class=&quot;sender vcard&quot;&gt;&lt;a class=&quot;url&quot; href=&quot;aim:goim?screenname=BenWardcouk&quot;&gt;&lt;abbr class=&quot;chat-username&quot; title=&quot;BenWardcouk&quot;&gt;&lt;span class=&quot;fn nickname&quot;&gt;Ben&lt;/span&gt;&lt;/abbr&gt;&lt;/a&gt;&lt;/cite&gt;<br />
&lt;q&gt;Hello&lt;/q&gt;<br />
&lt;/li&gt;</pre><br />
<br />
This fits into existing patterns OK, but loses one very important piece of information, the service provider. This could be spec'd as a prefix (&lt;abbr class="chat-username" title="aim:BenWardcouk">…&lt;/abbr>) or could be a separate property altogether (chat-service).<br />
<br />
===Example with include-pattern===<br />
<br />
Introducing two new properties to each message hCard would create much clutter in the mark-up, and the repeition of hCards is already sub-optimal. The include-pattern in hCard can be used to keep the format cleaner, as demonstrated below.<br />
<br />
Note: In this example, I'm still using the aim: URL form of representing usernames.<br />
<br />
<pre>&lt;html&gt; &lt;!-- &hellip; --&gt;<br />
&lt;body&gt;<br />
&lt;h1&gt;Chat between Ben and Hanni &ndash;&nbsp;Friday October 26th&lt;/h1&gt;<br />
<br />
&lt;h2&gt;Participants&lt;/h2&gt;<br />
&lt;ul&gt;<br />
&lt;li id=&quot;benwardcouk&quot;&gt;<br />
&lt;h3&gt;&lt;a class=&quot;fn url nickname&quot; href=&quot;aim:goaim?benwardcouk&quot;&gt;Ben&lt;/a&gt;&lt;/h3&gt;<br />
&lt;p&gt;&lt;a class=&quot;url&quot; href=&quot;http://ben-ward.co.uk&quot;&gt;Homepage&lt;/a&gt;&lt;/p&gt;<br />
&lt;p class=&quot;description&quot;&gt;Ben is a 22 year old web application developer in Birmingham, England&lt;/p&gt; <br />
&lt;/li&gt;<br />
&lt;li id=&quot;hanni&quot;&gt;<br />
&lt;h3&gt;&lt;a class=&quot;fn url nickname&quot; href=&quot;aim:goaim?hanniusername&quot;&gt;Hanni&lt;/a&gt;&lt;/h3&gt;<br />
&lt;p&gt;&lt;a class=&quot;url&quot; href=&quot;http://hanniross.com&quot;&gt;Homepage&lt;/a&gt;&lt;/p&gt;<br />
&lt;/li&gt;<br />
&lt;/ul&gt;<br />
<br />
&lt;ol class=&quot;hChatLog&quot;&gt;<br />
&lt;li class=&quot;message&quot;&gt;<br />
&lt;abbr class=&quot;dtstart&quot; title=&quot;2006-08-08T01:22:00+0100&quot;&gt;1:22am&lt;/abbr&gt;: <br />
&lt;cite class=&quot;sender vcard&quot;&gt;&lt;a class=&quot;include&quot; href=&quot;#hanni&quot;&gt;Hanni&lt;/a&gt;&lt;/cite&gt;<br />
&lt;q&gt;Hello Ben&lt;/q&gt;<br />
&lt;/li&gt;<br />
&lt;li class=&quot;message&quot;&gt;<br />
&lt;abbr class=&quot;dtstart&quot; title=&quot;2006-08-08T01:25:00+0100&quot;&gt;1:25am&lt;/abbr&gt;: <br />
&lt;cite class=&quot;sender vcard&quot;&gt;&lt;a class=&quot;include&quot; href=&quot;#benward&quot;&gt;Ben&lt;/a&gt;&lt;/cite&gt;<br />
&lt;blockquote&gt;&lt;p&gt;Hello Hanni&lt;/p&gt;<br />
&lt;p&gt;How&apos;re you today?&lt;/p&gt;&lt;/blockquote&gt;<br />
&lt;/li&gt;<br />
&lt;li class=&quot;status&quot;&gt;<br />
&lt;abbr class=&quot;dtstart&quot; title=&quot;2006-08-08T01:27:00+0100&quot;&gt;1:27am&lt;/abbr&gt;: <br />
&lt;span class=&quot;sender vcard&quot;&gt;&lt;a class=&quot;include&quot; href=&quot;#hanni&quot;&gt;Hanni&lt;/a&gt; went &lt;span class=&quot;type&quot;&gt;away&lt;/span&gt;&lt;/span&gt;<br />
&lt;/li&gt;<br />
&lt;li class=&quot;status&quot;&gt;<br />
&lt;abbr class=&quot;dtstart&quot; title=&quot;2006-08-08T01:28:00+0100&quot;&gt;1:28am&lt;/abbr&gt;: <br />
&lt;span class=&quot;sender vcard&quot;&gt;&lt;a class=&quot;include&quot; href=&quot;#hanni&quot;&gt;Hanni&lt;/a&gt; <br />
&lt;abbr class=&quot;type&quot; title=&quot;online&quot;&gt;came back&lt;/abbr&gt;&lt;/span&gt;<br />
&lt;/li&gt;<br />
&lt;/ol&gt;<br />
</pre><br />
<br />
In this last example, the repeated hCards are declared once at the top of the document, with additional detail, and then can be parsed into the log itself using the include-pattern. The A/@class=include pattern is used, rather than OBJECT, as it allows the user display name to be repeated in each message as text, but will be replaced when parsed.<br />
<br />
Note: The VCARD class name is on the CITE elements in each message/status, rather than on the LIs where the hCards are declared in full. This is because the include-pattern currently only to works <em>inside</em> an hCard. It would be tidier to have the VCARD class on the LIs in the participants list, but unless the include-pattern can be extended to apply natively inside hChatLog, the hCards must be arranged like this.<br />
<br />
== Ideas ==<br />
<br />
=== Using paragraphs to represent chat messages ===<br />
<br />
I think that individual messages in a chat log should be formatted as XHTML paragraphs (<code>&lt;p&gt;</code>), because this is how conversations are commonly formatted. From the [[chat-examples|examples]] I gather that this is also what the [[chat-examples#ILRT_Logger_Bot_Format|ILRT Logger Bot]] currently does. --[[User:BigSmoke|BigSmoke]] 13:09, 21 Jun 2006 (PDT)<br />
<br />
- We can't assume all paragraphs are chat messages, so we'll need a class name to identify a chat message. Once a class name is identifying something as a message, what is the advantage of applying the additional stipulation of a specific HTML tag? It doesn't appear to aid parsing, and it only constrains publishers. --[[User:ScottReynen|Scott Reynen]]<br />
<br />
- I'm not convinced that ‘messages are paragraphs’ is an overly fair assumption: Lots of chat is extremely fragmented into sentences (or even partial sentences). I'd be nervous about generalising the P element any further than it all ready.<br />
<br />
I have a lot of love for [http://microformats.org/wiki/chat-examples#MSN_Messenger_Marked_Up_By_Anne_van_Kesteren Anne van Kesteren's chat mark-up] (using Q elements for single line text, and BLOCKQUOTE > P for multiline messages, where the presence of newlines seems a more concrete basis on which to describe paragraph).<br />
<br />
As far as block level element construction goes, AvK's mark-up again highlights the capability of raw HTML: OL is certainly correct, as is CITE and Q/BLOCKQUOTE. Paragraphs might not always be correct.<br />
<br />
--[[User:Ben Ward|BenWard]] 12:29, 24 Sep 2006 (PDT)<br />
<br />
- No sooner do I say ‘OL is certainly correct’ but something comes up to question it. Those interested in developing hChat might also like to keep an eye on the WHATWG list where there's been [http://www.mail-archive.com/whatwg@lists.whatwg.org/msg02526.html some questioning of using OL for dialogue]. Additionally, there's a fresh [http://meyerweb.com/eric/thoughts/2006/10/23/broken-rights/ discussion on dialogue mark-up at Eric Meyer's blog].<br />
<br />
--[[User:Ben Ward|BenWard]] 03:41, 24 Oct 2006 (PDT)</div>Colin Barretthttp://microformats.org/wiki/index.php?title=irc-people&diff=9908irc-people2006-10-25T10:10:57Z<p>Colin Barrett: </p>
<hr />
<div>A list of [[irc|IRC]] regulars and their normal timezones. (winter/summer)<br />
<br />
* [[User:BenWest|bewest]] (-0800/-0700)<br />
* [[User:Adam Craven|AdamCraven]] (+0000)<br />
* [[User:Amette|amette]] (+1000)<br />
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)<br />
* [[User:Ben Ward|BenWard]] (+0000)<br />
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)<br />
* [[User:Boneill|boneill]] (+0000)<br />
* [[User:Brian|briansuda]] (+0000)<br />
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)<br />
* [[User:Cgriego|cgriego]] (-0600/-0500)<br />
* [[User:CharlesRoper|charles_r]] (0000/+0100)<br />
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)<br />
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)<br />
* [[User:ChristopherStJohn|cks]] (-0600/-0500)<br />
* [[User:Cloud|Cloud]] (+0000)<br />
* [[User:DanC|DanC]] (-0600/-0500)<br />
** office hours: Wednesday afternoons, America/Chicago time<br />
* [[User:Dave Cardwell|davecardwell]] (+0000)<br />
* [[User:DeanEro|deanero]] (-0800/-0700)<br />
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)<br />
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)<br />
* [[User:EdwardOConnor|hober]] (-0800/-0700)<br />
* [[User:Enric|enric]] (-0800/-0700)<br />
* [[User:Evan|evanpro]] (-0500)<br />
* [[User:Fil|Fil]] (+0200)<br />
* [[User:Grantbow|Grantbow]] (-0800/-0700)<br />
* [[User:Hlb|hlb]] (+0800-0700)<br />
* [[User:IanHickson|Hixie]] (-0800/-0700)<br />
* [[User:Izo|IZO]]<br />
* [[User:JoeGregorio|jcgregorio]]<br />
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)<br />
* [[User:JasonK|jkridner]]] (-0600/-0500)<br />
* [[User:Kapowaz|kapowaz]] (+0000/+0100)<br />
* [[User:Keri Henare|kerihenare]] (+1200)<br />
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)<br />
* [[User:Mark Mansour|Mark Mansour]] (+1100)<br />
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)<br />
* [[User:CiaranMc|McNulty]] (+0000/+0100)<br />
* [[User:neuro|neuro`]]<br />
* [[User:Phae|Phae]] (+0000/+0100)<br />
* [[User:PriitLaes|plaes]] (+0200/+0300)<br />
* [[User:DavidOsolkowski|qid]] (-0500)<br />
* [[User:Remi|Remi]] (-0500/-0400)<br />
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)<br />
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)<br />
* [[User:Ronnos|Ron Kok]] (+0000)<br />
* [[User:RyanKing|kingryan]] (-0800/-0700)<br />
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC<br />
* [[User:Csarven|csarven]] (-0500/-0400)<br />
* [[User:Dana Benson|Snowden]] (-0800/-0700)<br />
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)<br />
* [[User:Tantek|Tantek]] (-0800/-0700)<br />
* [[User:Trovster|trovster]] (-0800/-0700)<br />
* [[User:Dan Kubb|dkubb]] (-0800/-0700)<br />
* [[User:Ed Summers|edsu]] (-0500/-0400)<br />
* [[User:Smackman|Steve Farrell]] (-0800/-0700)<br />
* [[User:Enric|Enric]] (-0800/-0700)<br />
* [[User:Charlvn|Charl]] (+0200/+0200)<br />
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)<br />
* [[User:Vant|vant]] (+0900)<br />
* [[User:KrissWatt|VoodooChild]] (+0000/+0100)<br />
* [[User:IwaiMasaharu|iwaim]] (+0900)<br />
* [[User:Richard Conyard|WhiskeyM]] (+0000)<br />
* [[User:Veeliam|William Lawrence]] (-0800/-0700)<br />
* [[User:Ianloic|yakk]] (-0800/-0700)<br />
* [[User:Ashley|Ashley]] (+1000)<br />
* [[User:SuperPhly|SuperPhly]] (-600/-500)<br />
* [[User:Colin_Barrett|cbarrett]] (-1000)</div>Colin Barretthttp://microformats.org/wiki/index.php?title=irc-people&diff=9835irc-people2006-10-25T10:10:38Z<p>Colin Barrett: </p>
<hr />
<div>A list of [[irc|IRC]] regulars and their normal timezones. (winter/summer)<br />
<br />
* [[User:BenWest|bewest]] (-0800/-0700)<br />
* [[User:Adam Craven|AdamCraven]] (+0000)<br />
* [[User:Amette|amette]] (+1000)<br />
* [[User:B.K._DeLong|bkdelong]] (-0500/-0400)<br />
* [[User:Ben Ward|BenWard]] (+0000)<br />
* [[User:BenjaminCarlyle|BenjaminCarlyle]] (+1000)<br />
* [[User:Boneill|boneill]] (+0000)<br />
* [[User:Brian|briansuda]] (+0000)<br />
* [[User:ColinDDevroe|cdevroe]] (-0500/-0600)<br />
* [[User:Cgriego|cgriego]] (-0600/-0500)<br />
* [[User:CharlesRoper|charles_r]] (0000/+0100)<br />
* [[User:ChrisCasciano|pnhChris]] (-0500/-0400)<br />
* [[User:ChrisMessina|factoryjoe]] (-0800/-0700)<br />
* [[User:ChristopherStJohn|cks]] (-0600/-0500)<br />
* [[User:Cloud|Cloud]] (+0000)<br />
* [[User:DanC|DanC]] (-0600/-0500)<br />
** office hours: Wednesday afternoons, America/Chicago time<br />
* [[User:Dave Cardwell|davecardwell]] (+0000)<br />
* [[User:DeanEro|deanero]] (-0800/-0700)<br />
* [[User:DimitriGlazkov|dglazkov]] (-0600/-0500)<br />
* [[User:DrewMcLellan|drewinthehead]] (+0000/+0100)<br />
* [[User:EdwardOConnor|hober]] (-0800/-0700)<br />
* [[User:Enric|enric]] (-0800/-0700)<br />
* [[User:Evan|evanpro]] (-0500)<br />
* [[User:Fil|Fil]] (+0200)<br />
* [[User:Grantbow|Grantbow]] (-0800/-0700)<br />
* [[User:Hlb|hlb]] (+0800-0700)<br />
* [[User:IanHickson|Hixie]] (-0800/-0700)<br />
* [[User:Izo|IZO]]<br />
* [[User:JoeGregorio|jcgregorio]]<br />
* [[User:Jonathan_Arkell|jonnay]] (-0700/0600)<br />
* [[User:JasonK|jkridner]]] (-0600/-0500)<br />
* [[User:Kapowaz|kapowaz]] (+0000/+0100)<br />
* [[User:Keri Henare|kerihenare]] (+1200)<br />
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)<br />
* [[User:Mark Mansour|Mark Mansour]] (+1100)<br />
* [[User:MarkNormanFrancis|Mark Norman Francis]] (+0000/+0100)<br />
* [[User:CiaranMc|McNulty]] (+0000/+0100)<br />
* [[User:neuro|neuro`]]<br />
* [[User:Phae|Phae]] (+0000/+0100)<br />
* [[User:PriitLaes|plaes]] (+0200/+0300)<br />
* [[User:DavidOsolkowski|qid]] (-0500)<br />
* [[User:Remi|Remi]] (-0500/-0400)<br />
* [[User:RobertBachmann|RobertBachmann]] (+0100/+0200)<br />
** Office hours: <del>Wednesday, 18:00-20:00 UTC</del> (Currently no office hours)<br />
* [[User:Ronnos|Ron Kok]] (+0000)<br />
* [[User:RyanKing|kingryan]] (-0800/-0700)<br />
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC<br />
* [[User:Csarven|csarven]] (-0500/-0400)<br />
* [[User:Dana Benson|Snowden]] (-0800/-0700)<br />
* [[User:Steve Ganz|SteveGanz]] (-0800/-0700)<br />
* [[User:Tantek|Tantek]] (-0800/-0700)<br />
* [[User:Trovster|trovster]] (-0800/-0700)<br />
* [[User:Dan Kubb|dkubb]] (-0800/-0700)<br />
* [[User:Ed Summers|edsu]] (-0500/-0400)<br />
* [[User:Smackman|Steve Farrell]] (-0800/-0700)<br />
* [[User:Enric|Enric]] (-0800/-0700)<br />
* [[User:Charlvn|Charl]] (+0200/+0200)<br />
* [[User:MarkoMrdjenovic|friedcell]] (+0100/+0200)<br />
* [[User:Vant|vant]] (+0900)<br />
* [[User:KrissWatt|VoodooChild]] (+0000/+0100)<br />
* [[User:IwaiMasaharu|iwaim]] (+0900)<br />
* [[User:Richard Conyard|WhiskeyM]] (+0000)<br />
* [[User:Veeliam|William Lawrence]] (-0800/-0700)<br />
* [[User:Ianloic|yakk]] (-0800/-0700)<br />
* [[User:Ashley|Ashley]] (+1000)<br />
* [[User:SuperPhly|SuperPhly]] (-600/-500)<br />
* [[User:Colin_Barrett|cbarrett]] (-1000/-1000)</div>Colin Barretthttp://microformats.org/wiki/index.php?title=WikiWord&diff=32286WikiWord2006-10-03T10:17:03Z<p>Colin Barrett: Page created.</p>
<hr />
<div>A WikiWord is any word which contains at least two upper case letters, separated by at least one lower case letter. For example, ThisIsAnExample.<br />
<br />
Many pages on this particular wiki use dashes or underscores to separate words as well.</div>Colin Barretthttp://microformats.org/wiki/index.php?title=User:Colin_Barrett&diff=19810User:Colin Barrett2006-08-25T07:17:59Z<p>Colin Barrett: </p>
<hr />
<div>[http://adiumx.com Adium] developer. Original author of the [http://purl.org/NET/ULF/SPEC ULF] format. Author of the reference implementation for it.<br />
<br />
Personal website forthcoming.</div>Colin Barretthttp://microformats.org/wiki/index.php?title=chat-brainstorming&diff=8896chat-brainstorming2006-08-22T12:33:00Z<p>Colin Barrett: Adding a question about how much information we want stored in hChat</p>
<hr />
<div>== Requirements ==<br />
<br />
=== Scope ===<br />
<br />
Should a microformat matching these requirements be capable of representing only transcripts of existing IM protocols or should it also be able to serve as an exchange format itself. This '''might''' be useful for simple AJAX IM platforms, although I doubt if [http://www.xmpp.org/ XMPP] is not per definition a better choise for such purposes. --[[User:BigSmoke|BigSmoke]] 13:09, 21 Jun 2006 (PDT)<br />
<br />
- Anything that can be parsed can be used in AJAX, so we don't need to consider this in developing a microformat. --[[User:ScottReynen|Scott Reynen]]<br />
<br />
How much, and what kind of data is going to be in the file? The work done by the [http://purl.org/NET/ULF/SPEC Unified Logging Format WG] has a pretty good overview of the various types of things that an IM client would want to log. Don't make too much of a bikeshed about it -- I'm mostly linking it beacuse it's a good overview of the sorts of general element types (message, event, status) we probably want to use. --[[User:Colin Barrett|Colin Barrett]] 05:33, 22 Aug 2006 (PDT)<br />
=== Chat rooms ===<br />
<br />
Is it useful for this microformat to support the representation of "chat rooms", such as IRC channels? --[[User:BigSmoke|BigSmoke]]<br />
<br />
- Location is a problem that can be clearly separated from chats. We should stick to solving the smallest problem possible, so we can more easily combine microformats later to solve larger problems. --[[User:ScottReynen|Scott Reynen]]<br />
<br />
- On chat-formats and chat-examples, IRC logs are used. I would say we should include IRC logs in our spec -- it just makes sense to design for mult-user chat, because one-to-one messaging is just a special case of that. --[[User:Colin Barrett|Colin Barrett]] 05:33, 22 Aug 2006 (PDT)<br />
== Example playground ==<br />
<br />
<pre><br />
<div class="hchat-log"><br />
<p class="hchat-msg"><br />
<abbr class="time" title="YYYY-MM-DDTHH:MM:SS">HH:MM:SS</abbr><br />
<!-- Please, fill me in --><br />
</p><br />
</div><br />
</pre><br />
<br />
== Ideas ==<br />
<br />
=== Using paragraphs to represent chat messages ===<br />
<br />
I think that individual messages in a chat log should be formatted as XHTML paragraphs (<code>&lt;p&gt;</code>), because this is how conversations are commonly formatted. From the [[chat-examples|examples]] I gather that this is also what the [[chat-examples#ILRT_Logger_Bot_Format|ILRT Logger Bot]] currently does. --[[User:BigSmoke|BigSmoke]] 13:09, 21 Jun 2006 (PDT)<br />
<br />
- We can't assume all paragraphs are chat messages, so we'll need a class name to identify a chat message. Once a class name is identifying something as a message, what is the advantage of applying the additional stipulation of a specific HTML tag? It doesn't appear to aid parsing, and it only constrains publishers. --[[User:ScottReynen|Scott Reynen]]</div>Colin Barretthttp://microformats.org/wiki/index.php?title=chat-formats&diff=9905chat-formats2006-08-22T12:08:31Z<p>Colin Barrett: Revamping the ULF section</p>
<hr />
<div><h1> chat formats </h1><br />
<br />
Various formats that are used to represent chat conversations, typically internally. With the use cases from the [[chat-examples]], and the vocabularies used here, the next steps are to start [[chat-brainstorming]] on proposals for a chat microformat.<br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* ChristopherStJohn<br />
* Tantek Çelik<br />
* Jude Robinson<br />
* Chris Messina<br />
* Colin Barrett<br />
<br />
==ChatZilla Internal Format==<br />
Note that there is no proof that this format is being used "in the wild" for publishing. ChatZilla uses HTML as its presentation layer. This heavily elided excerpt shows two lines from a chat. It gives the flavor (a very big table with each row a chat message divided up into three columns: timestamp, user name and the message itself) but there are many more classes in use in a full log.<br />
<br />
<pre><br />
<div id="messages-outer"><br />
...<br />
<div id="output"><br />
...<br />
<table view-type="IRCChannel" class="msg-table"><br />
<tbody><br />
<tr mark="even" msg-user="cks_ ME!"<br />
statusText="01/31/2006 01:39 PM, cks_!n=chatzill@ppp-70-248-121-149.dsl.rcsntx.swbell.net"<br />
view-type="IRCChannel" dest-type="IRCChannel" msg-dest="#microformats"<br />
msg-type="PRIVMSG" class="msg"><br />
<td time-s="57" time-n="39" time-h="13" time-d="31" time-m="01" time-y="2006" class="msg-timestamp"><br />
</td><br />
<td class="msg-user"><br />
<span>cks_</span><br />
</td><br />
<td class="msg-data"><br />
<span>so, using chatzilla for just a minute so i can extract the logs.</span><br />
</td><br />
</tr><br />
<tr mark="odd" msg-user="Atamido" statusText="01/31/2006 01:43 PM, Atamido!n=atamido@cpe-67-9-173-252.austin.res.rr.com"<br />
view-type="IRCChannel" dest-type="IRCChannel" msg-dest="#microformats"<br />
msg-type="PRIVMSG" class="msg"><br />
<td time-s="25" time-n="43" time-h="13" time-d="31" time-m="01" time-y="2006" class="msg-timestamp"><br />
</td><br />
<td class="msg-user"><br />
<a href="irc://irc.freenode.net/Atamido,isnick" class="chatzilla-link"><br />
<span>Atamido</span><br />
</a><br />
</td><br />
<td class="msg-data"><br />
<span><br />
Here are some examples.<br />
<a target="_content" class="chatzilla-link" href="http://www.hacksrus.com/%7Eginda/chatzilla/motifs.html"><br />
http://www.hacksrus.<wbr><br />
com/~ginda/chatzilla/<wbr><br />
motifs.html<wbr><br />
</a><br />
</span><br />
</td><br />
</tr><br />
</tbody><br />
</table><br />
</div><br />
</div><br />
</pre><br />
<br />
==Google Talk Format Logs==<br />
Again, user1 is local.<br />
<br />
<pre><br />
3<br />
17b5df8a<br />
01c61af0<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v66EC7D7137%22+to%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Esome+but+not+much%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+to%3D%22user1%40gmail.com%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI'm+ready+to+crawl+in+bed+and+read.++Do+well+on+your+paper.++Love++Mom%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v66EC7D7137%22+to%3D%22user2%40gmail.com%2FTalk.v66EC841CB6%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ethanks%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Emom%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EHi%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ei+totally+forgot+about+the+awning%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Edo+you+want+me+to+come+over%3F%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI+have+tomorrow+off.++Is+the+wind+supposed+to+get+bad+before+then%3F%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Enot+sure.+its+stormy+now%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
incoming<br />
%3Ccli%3Amessage+from%3D%22user2%40gmail.com%2FTalk.v687050428D%22+to%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI'm+ready+if+yo+are.++I+thought+you+would+be+here+anyway+about+the+boat+or+I+would+have+called.%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3EI+think+we+decided+to+do+the+boat+on+a+dry+night%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
outgoing<br />
%3Ccli%3Amessage+from%3D%22user1%40gmail.com%2FTalk.v68701EBF07%22+to%3D%22user2%40gmail.com%2FTalk.v687050428D%22+type%3D%22chat%22+xmlns%3Acli%3D%22jabber%3Aclient%22%3E%3Ccli%3Abody%3Ei'll+come+over+now%3C%2Fcli%3Abody%3E%3Cactive+xmlns%3D%22http%3A%2F%2Fjabber.org%2Fprotocol%2Fchatstates%22%2F%3E%3C%2Fcli%3Amessage%3E<br />
</pre><br />
<br />
==Unified Logging Format==<br />
[http://adiumx.com Adium], [http://gaim.sf.net Gaim], and [http://kopete.kde.org Kopete] are currently developing an XML-based log format.<br />
This is a small sample of version 0.4-01:<br />
<pre><br />
<?xml version="1.0" encoding="UTF-8" ?><br />
<chat xmlns="http://purl.org/net/ulf/ns/0.4-01" account="mactigerz" service="AIM"><br />
<event type="windowOpened" time="2006-07-14T12:42:01-05:00"/><br />
<message sender="chz16" time="2006-07-14T12:42:01-05:00">'sup?</message><br />
<message sender="mactigerz" time="2006-07-14T12:43:15-05:00">trying to get to work on the the new XML log format</message><br />
<message sender="chz16" time="2006-07-14T12:43:55-05:00">Doesn't sound bad.</message><br />
<message sender="chz16" time="2006-07-14T12:44:10-05:00">Providing you have the log specs, of course.</message><br />
<message sender="mactigerz" time="2006-07-14T12:45:15-05:00">that's what I'm creating.</message><br />
<status type="offline" sender="chz16" time="2006-07-14T12:46:23-05:00"/><br />
<status type="online" sender="chz16" time="2006-07-14T12:46:43-05:00"/><br />
<status type="away" sender="mactigerz" time="2006-07-14T12:47:10-05:00">brb, working on the XML log format</status><br />
<event type="windowClosed" time="2006-07-14T12:47:20-05:00"/><br />
</chat><br />
</pre><br />
The current version of the spec can be found [http://purl.org/NET/ULF/SPEC here].<br />
<br />
==ILRT Logger Bot Format==<br />
Found at: http://chatlogs.planetrdf.com/swig/, generated by: http://cvs.ilrt.org/cvsweb/redland/logger/, there are three formats: HTML, plain text, and RDF. The entry discussed the RDF format, as it's presumably directed at machines and not people.<br />
<br />
Taking RDF first just because that's kind of fun and is presumably 100% semantics. Pretty straightforward RDF Sequence with date/description/creator, except for the line with a Dublin Core relation stuck in there. As is normal with RDF, semantics are reused, so to fully grok it there's some followon work to do, see: http://www.w3.org/2004/Talks/0522-rrs/ The foaf group got involved with IRC chat since IRC names are one of the ways to identify people, looks like it snowballed, not sure if the ChatChannel stuff is official or not. The Dublin Core and WordNet stuff is mentioned in the FOAF spec index, but seems to be missing from the actual text, I might have been looking at an old version.<br />
<br />
<pre><br />
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"<br />
xmlns:dc="http://purl.org/dc/elements/1.1/"<br />
xmlns:wn="http://xmlns.com/wordnet/1.6/"<br />
xmlns:foaf="http://xmlns.com/foaf/0.1/"><br />
<foaf:ChatChannel rdf:about="irc://irc.freenode.net/swig"><br />
<foaf:chatEventList><br />
<rdf:Seq><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T00-01-19"><br />
<dc:date>2006-02-01T00:01:19Z</dc:date><br />
<dc:description>keithalexander has quit</dc:description><br />
<dc:creator><wn:Person foaf:nick="keithalexander"/></dc:creator><br />
</foaf:chatEvent><br />
</rdf:li><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T00-27-42"><br />
<dc:date>2006-02-01T00:27:42Z</dc:date><br />
<dc:description>Gromgull: nice quote re. x years later</dc:description><br />
<dc:creator><wn:Person foaf:nick="CaptSolo"/></dc:creator><br />
</foaf:chatEvent><br />
</rdf:li><br />
<rdf:li><br />
<foaf:chatEvent rdf:ID="T01-38-49"><br />
<dc:date>2006-02-01T01:38:49Z</dc:date><br />
<dc:description>A: http://aaronland.info/python/pyupcoming/ from karlUshi</dc:description><br />
<dc:creator><wn:Person foaf:nick="dc_swig"/></dc:creator><br />
<dc:relation rdf:resource="http://aaronland.info/python/pyupcoming/"/><br />
</foaf:chatEvent><br />
</rdf:li><br />
</rdf:Seq><br />
</foaf:chatEventList><br />
</foaf:ChatChannel><br />
</rdf:RDF><br />
</pre><br />
<br />
==Trillian Internal Format==<br />
This is for an AIM chat, but one for a Yahoo! chat looks the same. It is saved as plaintext as well as XML. (user1 is local). This is a description of the XML format, as it is presumably intended for machines and not humans.<br />
<br />
The same in XML:<br />
<pre><br />
<session type="start" time="1112395386" medium="AIM" to="user2" from="user1"/><br />
<message type="incoming_privateMessage" time="1112395386" medium="AIM" to="user1" from="user2" from_display="user2" text="ping"/><br />
<message type="information_standard" time="1112395387" medium="AIM" text="Auto%2Dresponse%20sent%20to%20user2%3A%20My%20hovercraft%20is%20full%20of%20eels%2E"/><br />
<message type="outgoing_privateMessage" time="1112395573" medium="AIM" to="user2" from="user1" from_display="user1" text="hey"/><br />
<session type="stop" time="1112395619" medium="AIM" to="user2" from="user1"/><br />
</pre><br />
<br />
There is also a "user2-assets.xml" file for stuff like Buddy icons & file transers:<br />
<br />
<pre><br />
<asset medium="AIM" name="user2" link="C%3A%5CProgram%20Files%5CTrillian%5Cusers%5Cdefault%5Cbuddyicons%5Cassets%5CAIM%2Duser2%2D1118046544%2Ejpg"/><br />
<asset medium="AIM" name="user2" link="D%3A%5CPIX%5CY2005%5C0619%5CMOV02050%2EMPG"/><br />
<asset medium="AIM" name="user2" link="C%3A%5CDocuments%20and%20Settings%5Cant%5CDesktop%5CDSCN0372_resize%2EJPG"/><br />
<asset medium="AIM" name="user2" link="C%3A%5CProgram%20Files%5CTrillian%5Cusers%5Cdefault%5Cbuddyicons%5Cassets%5CAIM%2Duser2%2D1133932754%2Ejpg"/><br />
</pre><br />
<br />
<br />
== Nature podcast format ==<br />
<br />
Snippets of XML from [http://www.nature.com/nature/podcast/v440/n7085/nature-2006-04-06.html Nature journal's podcast of 6 April 2006]. Differences from chat formats above include the (current) lack of any timestamps, and defined "roles", ie: presenter/interviewer/interviewee.<br />
<br />
<pre><?xml version="1.0" encoding="utf-8"?><br />
<podcast id="nature-2006-04-06"<br />
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<br />
xsi:noNamespaceSchemaLocation="NPG_podcast_transcript.xsd"><br />
<source><br />
<jtl>Nature</jtl><br />
<vol>440</vol><br />
<iss>7085</iss><br />
<idt>20060406</idt><br />
<issn type="print">0028-0836</issn><br />
<issn type="electronic">1476-4679</issn><br />
<cpg><br />
<cpy>2006</cpy><br />
<cpn>Nature Publishing Group</cpn><br />
</cpg><br />
</source><br />
<fm><br />
<doi>10.1038/pod-nature-2006-04-06</doi><br />
<title>Nature Podcast</title><br />
<presenter><br />
<name><br />
<fname>Chris</fname><br />
<sname>Smith</sname><br />
</name><br />
</presenter><br />
<intro><br />
<p><br />
This is a transcript of the 6 April edition of the weekly podcast.<br />
Audio files for the current show and archive episodes can be accessed<br />
from the podcast index page (<weblink url="http://www.nature.com/nature/podcast"/>)...<br />
</p><br />
<p>Sponsor: The podcast from...</p><br />
<p>This week Tiktaalik and what it can tell us about how early life invaded the land..</p><br />
</intro><br />
</fm><br />
<body><br />
<interview><br />
<interviewer><br />
<name><br />
<fname>Chris</fname><br />
<sname>Smith</sname><br />
</name><br />
<p>Hello, I'm Chris Smith. Welcome to the 6th April edition of Nature's podcast.<br />
First this week we're winding our watches back about 380 million years to the time when<br />
the first animals substituted feet for fins and began to heave themselves out of the<br />
sea and onto land... (<cite><br />
<jtl>Nature</jtl><br />
<vid>440</vid>, <ppf>747</ppf>&#45;<ppl>749</ppl>; <cd>2006</cd><br />
<refdoi>10.1038/440747a</refdoi><br />
</cite>).</p><br />
</interviewer><br />
<interviewee><br />
<name><br />
<fname>Neil</fname><br />
<sname>Shubin</sname><br />
</name><br />
<p>The transition from a fish that lives in water to an animal that's able to live on land<br />
is one of the great transitions in the history of life. We know from a variety of...</p><br />
</interviewee><br />
...<br />
</interview><br />
<filler><br />
<p>Well that's it for this week, and thanks for listening. Remember that...</p><br />
<p>Next week we are fighting malaria and finding out how parasites can...</p><br />
<p>Production on this week's podcast was by Anna Lacey in the Department of Pathology<br />
at Cambridge University, and I'm Chris Smith.</p><br />
<p>Sponsor: The podcast is sponsored by Bio-Rad at the centre of scientific discovery<br />
for over 50 years, and on the web at <weblink url="http://www.discover.biorad.com"/>.</p><br />
</filler><br />
</body><br />
</podcast><br />
<br />
<br />
</pre></div>Colin Barrett