<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Micro-semantics for fun and profit</title>
	<atom:link href="http://www.zeldman.com/2009/04/06/micro-semantics-for-fun-and-profit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zeldman.com/2009/04/06/micro-semantics-for-fun-and-profit/</link>
	<description>Web design news and insights since 1995</description>
	<lastBuildDate>Thu, 02 Feb 2012 19:54:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Micro-Semantisches Trendsetting? &#171; Reinseite</title>
		<link>http://www.zeldman.com/2009/04/06/micro-semantics-for-fun-and-profit/#comment-41292</link>
		<dc:creator>Micro-Semantisches Trendsetting? &#171; Reinseite</dc:creator>
		<pubDate>Tue, 14 Apr 2009 10:07:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=829#comment-41292</guid>
		<description>[...] / * Zeldman [...]</description>
		<content:encoded><![CDATA[<p>[...] / * Zeldman [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antoine E Butler Sr</title>
		<link>http://www.zeldman.com/2009/04/06/micro-semantics-for-fun-and-profit/#comment-41259</link>
		<dc:creator>Antoine E Butler Sr</dc:creator>
		<pubDate>Wed, 08 Apr 2009 19:40:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=829#comment-41259</guid>
		<description>In regards to special characters in IM&#039;s, Tweets, and even in Emails I think the use of each is either based on:

1. An assumed standard. ie # via twitter
2. or personal interpretation

The latter would prove most difficult for the average user to adopt. It&#039;s one thing from a development point of view to say, this the standard, moving forward xyz should be accented with such and such character. But end users still use IE6 even though it&#039;s not standards compliant, most people don&#039;t write according to AP or any other guidelines. The examples are plentiful, in my opinion.

I&#039;ve seen people use = for a correction but I&#039;ve seen used more often in my circle the use of * to denote a correction. The latter seems more intuitive to &lt;em&gt;me&lt;/em&gt;. I find interesting though that emphasizing the copy immediately following the asterisks reads as a &lt;em&gt;source&lt;/em&gt;. Again, to me.

That alone would be the most difficult thing to overcome. Although we could justify the *,@, and perhaps even # in regards to semantic meaning I think $ would be more problematic. As what does the sign actually signify. Currency. That&#039;s it. Used in stocks, it&#039;s a reference to the said stocks &quot;value&quot;, but the stock name itself is not the value, it&#039;s an entity &lt;em&gt;with&lt;/em&gt; a value.

Then again, I&#039;m no semantics expert.</description>
		<content:encoded><![CDATA[<p>In regards to special characters in IM&#8217;s, Tweets, and even in Emails I think the use of each is either based on:</p>
<p>1. An assumed standard. ie # via twitter<br />
2. or personal interpretation</p>
<p>The latter would prove most difficult for the average user to adopt. It&#8217;s one thing from a development point of view to say, this the standard, moving forward xyz should be accented with such and such character. But end users still use IE6 even though it&#8217;s not standards compliant, most people don&#8217;t write according to AP or any other guidelines. The examples are plentiful, in my opinion.</p>
<p>I&#8217;ve seen people use = for a correction but I&#8217;ve seen used more often in my circle the use of * to denote a correction. The latter seems more intuitive to <em>me</em>. I find interesting though that emphasizing the copy immediately following the asterisks reads as a <em>source</em>. Again, to me.</p>
<p>That alone would be the most difficult thing to overcome. Although we could justify the *,@, and perhaps even # in regards to semantic meaning I think $ would be more problematic. As what does the sign actually signify. Currency. That&#8217;s it. Used in stocks, it&#8217;s a reference to the said stocks &#8220;value&#8221;, but the stock name itself is not the value, it&#8217;s an entity <em>with</em> a value.</p>
<p>Then again, I&#8217;m no semantics expert.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.zeldman.com/2009/04/06/micro-semantics-for-fun-and-profit/#comment-41251</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Wed, 08 Apr 2009 12:06:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=829#comment-41251</guid>
		<description>= for correction. I like that.

Asterisk is still overloaded, it can mean &lt;i&gt;multiplication&lt;/i&gt; and is a common wildcard character. But I think those uses are not likely to be confused with *&lt;i&gt;source&lt;/i&gt; so, yeah,  that could work :)</description>
		<content:encoded><![CDATA[<p>= for correction. I like that.</p>
<p>Asterisk is still overloaded, it can mean <i>multiplication</i> and is a common wildcard character. But I think those uses are not likely to be confused with *<i>source</i> so, yeah,  that could work :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Magellan</title>
		<link>http://www.zeldman.com/2009/04/06/micro-semantics-for-fun-and-profit/#comment-41250</link>
		<dc:creator>Peter Magellan</dc:creator>
		<pubDate>Wed, 08 Apr 2009 10:32:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=829#comment-41250</guid>
		<description>@Andrew: I&#039;ve never seen the asterisk used for IM corrections, afair. Everybody I know either just sends the correct version, or uses the equals sign: 

wiikpeida=wikipedia

or just

=wikipedia

Depending how obvious the error is/how much in a hurry they are to avoid ridicule. ;-)

Not saying your way is incorrect - we&#039;re talking customs rather than rules, after all - but the equals sign does seem to me to be more appropriate for corrections. Asterisks are commonly used in ordinary text to refer to footnotes, so their use to indicate a net source or reference would make sense. 

My 2p...</description>
		<content:encoded><![CDATA[<p>@Andrew: I&#8217;ve never seen the asterisk used for IM corrections, afair. Everybody I know either just sends the correct version, or uses the equals sign: </p>
<p>wiikpeida=wikipedia</p>
<p>or just</p>
<p>=wikipedia</p>
<p>Depending how obvious the error is/how much in a hurry they are to avoid ridicule. ;-)</p>
<p>Not saying your way is incorrect &#8211; we&#8217;re talking customs rather than rules, after all &#8211; but the equals sign does seem to me to be more appropriate for corrections. Asterisks are commonly used in ordinary text to refer to footnotes, so their use to indicate a net source or reference would make sense. </p>
<p>My 2p&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.zeldman.com/2009/04/06/micro-semantics-for-fun-and-profit/#comment-41247</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 07 Apr 2009 23:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=829#comment-41247</guid>
		<description>Using asterisk to indicate &lt;i&gt;source&lt;/i&gt; would overload the symbol. In particular, I&#039;m used to seeing an asterisk used in this way during IM conversations to indicate a correction. For example:

&gt; yeah, I read that on wiikpeida
&gt; *wikipedia

That said, it might be difficult to find an alternative character that does not already have a defined or conventional meaning elsewhere.</description>
		<content:encoded><![CDATA[<p>Using asterisk to indicate <i>source</i> would overload the symbol. In particular, I&#8217;m used to seeing an asterisk used in this way during IM conversations to indicate a correction. For example:</p>
<p>&gt; yeah, I read that on wiikpeida<br />
&gt; *wikipedia</p>
<p>That said, it might be difficult to find an alternative character that does not already have a defined or conventional meaning elsewhere.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Brummels</title>
		<link>http://www.zeldman.com/2009/04/06/micro-semantics-for-fun-and-profit/#comment-41242</link>
		<dc:creator>Jason Brummels</dc:creator>
		<pubDate>Tue, 07 Apr 2009 14:16:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=829#comment-41242</guid>
		<description>I have been using @name for a long time! I think makes perfect sense. #Tag and *source would make good additions for me, and a practical way to become semantic.

I also like Michael&#039;s idea of $APPL.

However, if only developer adopt this across the web, and not normal folk, does it really work?</description>
		<content:encoded><![CDATA[<p>I have been using @name for a long time! I think makes perfect sense. #Tag and *source would make good additions for me, and a practical way to become semantic.</p>
<p>I also like Michael&#8217;s idea of $APPL.</p>
<p>However, if only developer adopt this across the web, and not normal folk, does it really work?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.zeldman.com/2009/04/06/micro-semantics-for-fun-and-profit/#comment-41239</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Tue, 07 Apr 2009 10:24:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=829#comment-41239</guid>
		<description>There&#039;s also the pattern for stock companies: i.e. $APPL</description>
		<content:encoded><![CDATA[<p>There&#8217;s also the pattern for stock companies: i.e. $APPL</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Confused</title>
		<link>http://www.zeldman.com/2009/04/06/micro-semantics-for-fun-and-profit/#comment-41226</link>
		<dc:creator>Confused</dc:creator>
		<pubDate>Mon, 06 Apr 2009 18:57:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.zeldman.com/?p=829#comment-41226</guid>
		<description>I thought the at-sign was a reference for a &lt;em&gt;recipient&lt;/em&gt;, not a sender.

Note to those who use twitter: there are more of us that don&#039;t use twitter than you think.  Actually, that probably goes for any value of &quot;twitter&quot;.</description>
		<content:encoded><![CDATA[<p>I thought the at-sign was a reference for a <em>recipient</em>, not a sender.</p>
<p>Note to those who use twitter: there are more of us that don&#8217;t use twitter than you think.  Actually, that probably goes for any value of &#8220;twitter&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

