chat-brainstorming - Revision history

Tantek: Reverted edits by Chatroll (Talk) to last version by ChristopheDucamp

2014-03-05T20:06:34Z

Reverted edits by Chatroll (Talk) to last version by ChristopheDucamp

Show changes

Chatroll: FREE Chatting - Chatting Online, Chatting Sites

2014-03-02T22:28:45Z

FREE Chatting - Chatting Online, Chatting Sites

Show changes

Chatroll: /* Requirements */

2014-03-02T22:19:27Z

Requirements

← Older revision		Revision as of 22:19, 2 March 2014
Line 1:		Line 1:
	== ~~Requirements~~ ==		== FREE Chatting - Chatting Online, Chatting Sites ==

	~~=== Scope ===~~

	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)

	- ~~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]]~~		Join FREE Chatting - Chatting Online, Chatting Sites

	~~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)~~		ChatRoll is an [http://chatroll.org/ Free online Chatting] Video website that pairs strangers from around the world together for webcam-based conversations. Visitors to the website begin an online chat (text, audio, and video) with another visitor who is chosen at random. At any point, either user may leave the current chat by initiating another random connection.

	~~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]~~		[http://chatroll.org/ ChaTroll] offers a random chat system, which allows you to meet new people with video chat for free. The online video chat system will pair you at random with another person using the free chat video . If you don't like the people you meet, you can click on the "Next" button to match somebody new.

	~~=== Chat rooms ===~~

	~~Is it useful for this microformat to support the representation of "chat rooms", such as IRC channels? --[[User:BigSmoke\|BigSmoke]]~~

	- 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]]

	- 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)
	== Example playground ==		== Example playground ==

ChristopheDucamp: Reverted edits by I MADE THOUSANDS OF ACCOUNTS IN MICROFORMATS WIKI GO TO CHECK OUT THE USER LIST ([[User talk:I MADE THOUSANDS OF ACCOUNTS IN MICROF

2013-09-22T11:17:16Z

Reverted edits by I MADE THOUSANDS OF ACCOUNTS IN MICROFORMATS WIKI GO TO CHECK OUT THE USER LIST ([[User talk:I MADE THOUSANDS OF ACCOUNTS IN MICROF

Show changes

I MADE THOUSANDS OF ACCOUNTS IN MICROFORMATS WIKI GO TO CHECK OUT THE USER LIST at 02:43, 22 September 2013

2013-09-22T02:43:47Z

Show changes

Tantek: Reverted edits by ABIDEEN10 (Talk) to last version by Brian

2013-04-07T04:52:18Z

Reverted edits by ABIDEEN10 (Talk) to last version by Brian

Show changes

ABIDEEN10 at 03:52, 7 April 2013

2013-04-07T03:52:15Z

Show changes

Brian: Reverted edits by ElbasNonov (Talk) to last version by Colin Barrett

2008-12-20T21:57:48Z

Reverted edits by ElbasNonov (Talk) to last version by Colin Barrett

← Older revision		Revision as of 21:57, 20 December 2008
Line 1:		Line 1:
	~~laerchic~~
	== Requirements ==		== Requirements ==

Line 10:		Line 9:
	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)		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)

	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]		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]

	=== Chat rooms ===		=== Chat rooms ===
Line 117:		Line 116:
	</li></pre>		</li></pre>

	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 (<abbr class="chat-username" title="aim:BenWardcouk">~~â¦~~</abbr>) or could be a separate property altogether (chat-service).		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 (<abbr class="chat-username" title="aim:BenWardcouk">…</abbr>) or could be a separate property altogether (chat-service).

	===Example with include-pattern===		===Example with include-pattern===
Line 178:		Line 177:
	- 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]]		- 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]]

	- 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.		- 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.

	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).		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).
Line 186:		Line 185:
	--[[User:Ben Ward\|BenWard]] 12:29, 24 Sep 2006 (PDT)		--[[User:Ben Ward\|BenWard]] 12:29, 24 Sep 2006 (PDT)

	- 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].		- 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].

	--[[User:Ben Ward\|BenWard]] 03:41, 24 Oct 2006 (PDT)		--[[User:Ben Ward\|BenWard]] 03:41, 24 Oct 2006 (PDT)

ElbasNonov: geteltlac

2008-12-20T01:26:42Z

geteltlac

← Older revision		Revision as of 01:26, 20 December 2008
Line 1:		Line 1:
			laerchic
	== Requirements ==		== Requirements ==

Line 9:		Line 10:
	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)		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)

	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]		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]

	=== Chat rooms ===		=== Chat rooms ===
Line 116:		Line 117:
	</li></pre>		</li></pre>

	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 (<abbr class="chat-username" title="aim:BenWardcouk">…</abbr>) or could be a separate property altogether (chat-service).		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 (<abbr class="chat-username" title="aim:BenWardcouk">â¦</abbr>) or could be a separate property altogether (chat-service).

	===Example with include-pattern===		===Example with include-pattern===
Line 177:		Line 178:
	- 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]]		- 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]]

	- 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.		- 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.

	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).		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).
Line 185:		Line 186:
	--[[User:Ben Ward\|BenWard]] 12:29, 24 Sep 2006 (PDT)		--[[User:Ben Ward\|BenWard]] 12:29, 24 Sep 2006 (PDT)

	- 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].		- 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].

	--[[User:Ben Ward\|BenWard]] 03:41, 24 Oct 2006 (PDT)		--[[User:Ben Ward\|BenWard]] 03:41, 24 Oct 2006 (PDT)

Colin Barrett: Noting the debate about the scope of the chat uf

2006-10-30T17:01:08Z

Noting the debate about the scope of the chat uf

← Older revision		Revision as of 17:01, 30 October 2006
Line 8:		Line 8:

	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)		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)

			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]

	=== Chat rooms ===		=== Chat rooms ===