<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.9.2 (http://www.squarespace.com/) on Wed, 10 Mar 2010 00:31:53 GMT--><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><title>Microsyntax.org</title><link>http://www.microsyntax.org/microsyntax/</link><description></description><lastBuildDate>Mon, 01 Feb 2010 14:49:40 +0000</lastBuildDate><copyright></copyright><language>en-US</language><generator>Squarespace Site Server v5.9.2 (http://www.squarespace.com/)</generator><item><title>The Slashtag: Let's Be Global, People</title><dc:creator>Stowe Boyd</dc:creator><pubDate>Mon, 01 Feb 2010 14:46:35 +0000</pubDate><link>http://www.microsyntax.org/microsyntax/2010/2/1/the-slashtag-lets-be-global-people.html</link><guid isPermaLink="false">493701:5622766:6517271</guid><description><![CDATA[<p>[cross posted from <a href="http://www.stoweboyd.com/message/the-slashtag-lets-be-global-people.html?SSScrollPosition=0">/Message</a>]</p>
<p>A new trend in microsyntax is spreading across the tech-end of the Twitter community. This is the use of so-called 'slashtags' to set off certain syntax elements of natural language for presumed easier understanding.</p>
<p>﻿[...]</p>
<p>Slashtags, at least for the examples where they are generally used, are simply preceding parts of speech, words, or acronyms that are understandable based on natural language and written conventions. For example</p>
<p style="padding-left: 30px;">This is history. via @barackobama cc @gregarious @themaria #election2008</p>
<p>isn't significantly less understandable than the slashtagged alternative</p>
<p style="padding-left: 30px;">This is history. /via @barackobama /cc @gregarious @themaria #election2008</p>
<p>In fact, this example also increases the number of characters in the tweet, which isn't horrible, but isn't good either.</p>
<p>I also feel that the use of '/' puts too much stress on these little propositions, and detracts from the other aspects of the tweet.</p>
<p>More importantly, the notion than '/via', '/by', and '/cc' are some sort of microsyntax keywords that hypothetical applications could use to mine interesting information patterns from the twitter stream leads to a basic problem: it's English, folks. These are English words and conventions.</p>
<p>We should certainly lean toward potentially internationalized microsyntax when we can. That's one reason that '@username' is good microsyntax, because we used '@username' and not '/to username'. Likewise, that's why '#foodpron' is good, and '/keyword foodpron' isn't. '@' and "#' meet the test of short and global.</p>
<p>[read the <a href="http://www.stoweboyd.com/message/the-slashtag-lets-be-global-people.html?SSScrollPosition=0">entire piece</a>.]</p>]]></description><wfw:commentRss>http://www.microsyntax.org/microsyntax/rss-comments-entry-6517271.xml</wfw:commentRss></item><item><title>Open Mobile Health Exchange</title><category>OMHE</category><dc:creator>Stowe Boyd</dc:creator><pubDate>Fri, 15 Jan 2010 18:31:35 +0000</pubDate><link>http://www.microsyntax.org/microsyntax/2010/1/15/open-mobile-health-exchange.html</link><guid isPermaLink="false">493701:5622766:6335617</guid><description><![CDATA[In November we announced Open Mobile Health Exchange as a Microsyntax.org project. During the next few weeks, OMHE will be rehosting some of their activities to this new website. More to follow.]]></description><wfw:commentRss>http://www.microsyntax.org/microsyntax/rss-comments-entry-6335617.xml</wfw:commentRss></item><item><title>Messifesto 2010: Microsyntax.org</title><dc:creator>Stowe Boyd</dc:creator><pubDate>Fri, 15 Jan 2010 15:40:24 +0000</pubDate><link>http://www.microsyntax.org/microsyntax/2010/1/15/messifesto-2010-microsyntaxorg.html</link><guid isPermaLink="false">493701:5622766:6334429</guid><description><![CDATA[<p>[Coming soon]</p>]]></description><wfw:commentRss>http://www.microsyntax.org/microsyntax/rss-comments-entry-6334429.xml</wfw:commentRss></item><item><title>Relaunching Microsyntax.org</title><dc:creator>Stowe Boyd</dc:creator><pubDate>Fri, 15 Jan 2010 15:39:53 +0000</pubDate><link>http://www.microsyntax.org/microsyntax/2010/1/15/relaunching-microsyntaxorg.html</link><guid isPermaLink="false">493701:5622766:6334426</guid><description><![CDATA[<p>I am moving the Microsytax.org blog onto this new blogging platform (Squarespace) to take advantage of a higher degree of potential social interaction that it offers, and to consolidate the blog and wiki that were set up in 2009. I found the two part arrangement to be more confusing that helpful.</p>
<p>As a result I have done the following:</p>
<ol>
<li>The 2009 Microsyntax.org blog has been moved to the a sidebar item, here, called '2009 Microsyntax.org Blog'. The old comments -- they were implemented on Disqus -- have been shut down, but the native Squaresoft comments will be active.</li>
<li>The 2009 Microsyntax Wiki contributions has been repartitioned into various sections of the new Contributions section (in the sidebar). [In process.]</li>
<li>I have added a forum, so that anyone can join threads on different topics, or start new ones.</li>
<li>Lastly, the Squaresoft technology makes it easy for me to grant limited editing capabilities to others. So if you would like to submit a contribution to one of the blogs please register <a href="http://www.microsyntax.org/join-microsyntax/">here</a>.</li>
</ol>]]></description><wfw:commentRss>http://www.microsyntax.org/microsyntax/rss-comments-entry-6334426.xml</wfw:commentRss></item></channel></rss>