<?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: Reflection and Description Of Meaning</title>
	<atom:link href="http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Sep 2010 10:58:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Aristotle Pagaltzis</title>
		<link>http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/comment-page-1/#comment-246</link>
		<dc:creator>Aristotle Pagaltzis</dc:creator>
		<pubDate>Mon, 20 Aug 2007 17:33:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/#comment-246</guid>
		<description>[Jim](#comment-179):

&gt; When I read or write something, I don’t think about bold or italics. I think about the tone of voice and which words are stressed – as if I were speaking or listening to somebody speak.

Exactly.</description>
		<content:encoded><![CDATA[<p><a href="#comment-179">Jim</a>:</p>

<p>&gt; When I read or write something, I don’t think about bold or italics. I think about the tone of voice and which words are stressed – as if I were speaking or listening to somebody speak.</p>

<p>Exactly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/comment-page-1/#comment-179</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Thu, 16 Aug 2007 15:19:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/#comment-179</guid>
		<description>&gt; And so as both a reader and a writer, I think in terms of italic and bold.

It&#039;s hard for me to believe this, as I also read and write a lot, and I&#039;ve never thought this way at all.  Not even close.  When I read or write something, I don&#039;t think about bold or italics.  I think about the tone of voice and which words are stressed - as if I were speaking or listening to somebody speak.

Of course, nobody would advocate that I use &lt;toneofvoice&gt; and &lt;stressed&gt; would they?  No, because my intention - even if I don&#039;t specifically think of it that way - is to *emphasise* particular parts of what I am writing.  I don&#039;t think in the abstract way because when somebody communicates with me, it&#039;s always fixed in a specific medium.  And even if you *do* think in terms of bold and italics, the same applies to you.  The bold and italics are merely a surface representation, not the underlying meaning, despite the fact that up until the past few decades of human history, the two have been inseparable.

PS: I used to participate on Usenet quite a bit, where markup wasn&#039;t available.  People used \*asterisks\* as a substitute; which is the precursor to Markdown.  Do you think people participating in Usenet think in terms of asterisks or in terms of emphasis?</description>
		<content:encoded><![CDATA[<p>&gt; And so as both a reader and a writer, I think in terms of italic and bold.</p>

<p>It&#8217;s hard for me to believe this, as I also read and write a lot, and I&#8217;ve never thought this way at all.  Not even close.  When I read or write something, I don&#8217;t think about bold or italics.  I think about the tone of voice and which words are stressed &#8211; as if I were speaking or listening to somebody speak.</p>

<p>Of course, nobody would advocate that I use &lt;toneofvoice&gt; and &lt;stressed&gt; would they?  No, because my intention &#8211; even if I don&#8217;t specifically think of it that way &#8211; is to <em>emphasise</em> particular parts of what I am writing.  I don&#8217;t think in the abstract way because when somebody communicates with me, it&#8217;s always fixed in a specific medium.  And even if you <em>do</em> think in terms of bold and italics, the same applies to you.  The bold and italics are merely a surface representation, not the underlying meaning, despite the fact that up until the past few decades of human history, the two have been inseparable.</p>

<p>PS: I used to participate on Usenet quite a bit, where markup wasn&#8217;t available.  People used &#42;asterisks&#42; as a substitute; which is the precursor to Markdown.  Do you think people participating in Usenet think in terms of asterisks or in terms of emphasis?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Montgomery</title>
		<link>http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/comment-page-1/#comment-160</link>
		<dc:creator>David Montgomery</dc:creator>
		<pubDate>Wed, 15 Aug 2007 01:10:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/#comment-160</guid>
		<description>I understand what you mean about inventing concepts and explanations after-the-fact (as with explaining our motivations), but I don&#039;t think it applies here.

When I write something using italics, I intuitively mean the same thing as when I say something with emphasis.  *Like this.*  Which is spoken differently than &quot;like this.&quot;

And read italics mean the same thing to me.

Now when I say something with emphasis, I don&#039;t think at all about italics or bold or emphasis ... or even pitch or volume or stress.  I just *say it*.

Because the emphasis in speech and the italics in text *mean* something, it&#039;s clear they carry semantic content.

Because they mean the *same* thing, it&#039;s clear to me that that meaning is not about italics.  

I think emphasis is a good word for what that meaning is about.</description>
		<content:encoded><![CDATA[<p>I understand what you mean about inventing concepts and explanations after-the-fact (as with explaining our motivations), but I don&#8217;t think it applies here.</p>

<p>When I write something using italics, I intuitively mean the same thing as when I say something with emphasis.  <em>Like this.</em>  Which is spoken differently than &#8220;like this.&#8221;</p>

<p>And read italics mean the same thing to me.</p>

<p>Now when I say something with emphasis, I don&#8217;t think at all about italics or bold or emphasis &#8230; or even pitch or volume or stress.  I just <em>say it</em>.</p>

<p>Because the emphasis in speech and the italics in text <em>mean</em> something, it&#8217;s clear they carry semantic content.</p>

<p>Because they mean the <em>same</em> thing, it&#8217;s clear to me that that meaning is not about italics.  </p>

<p>I think emphasis is a good word for what that meaning is about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Finney</title>
		<link>http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/comment-page-1/#comment-157</link>
		<dc:creator>Ben Finney</dc:creator>
		<pubDate>Tue, 14 Aug 2007 22:13:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/#comment-157</guid>
		<description>&gt; Wait, bold isn’t emphasis, it’s strong!

The EM and STRONG elements are both emphasis.

EM:
    Indicates emphasis.
STRONG:
    Indicates stronger emphasis.

http://www.w3.org/TR/html4/struct/text.html#h-9.2.1</description>
		<content:encoded><![CDATA[<p>&gt; Wait, bold isn’t emphasis, it’s strong!</p>

<p>The EM and STRONG elements are both emphasis.</p>

<p>EM:
    Indicates emphasis.
STRONG:
    Indicates stronger emphasis.</p>

<p><a href="http://www.w3.org/TR/html4/struct/text.html#h-9.2.1" rel="nofollow">http://www.w3.org/TR/html4/struct/text.html#h-9.2.1</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Bicking</title>
		<link>http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/comment-page-1/#comment-154</link>
		<dc:creator>Ian Bicking</dc:creator>
		<pubDate>Tue, 14 Aug 2007 21:37:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/#comment-154</guid>
		<description>Yeah, I think my point isn&#039;t just that there aren&#039;t enough semantic tokens to describe stuff, or that people wouldn&#039;t know how or be bothered to distinguish the semantic meaning of what they are saying; I&#039;m saying that the semantic meaning *isn&#039;t there* -- we mean what we write, or what we say, and in most cases the writer hasn&#039;t even manufactured deeper meaning than that.  You could challenge the writer to say *more*, but it&#039;s not that they left stuff out -- the extra meaning literally won&#039;t be there until it&#039;s asked for.  

And given a finite amount of resources, I don&#039;t know if we&#039;ll have any *more* total meaning with full semantic markup, than we would have with partial semantic markup and more information (possible because of the smaller burden placed on the writer).</description>
		<content:encoded><![CDATA[<p>Yeah, I think my point isn&#8217;t just that there aren&#8217;t enough semantic tokens to describe stuff, or that people wouldn&#8217;t know how or be bothered to distinguish the semantic meaning of what they are saying; I&#8217;m saying that the semantic meaning <em>isn&#8217;t there</em> &#8212; we mean what we write, or what we say, and in most cases the writer hasn&#8217;t even manufactured deeper meaning than that.  You could challenge the writer to say <em>more</em>, but it&#8217;s not that they left stuff out &#8212; the extra meaning literally won&#8217;t be there until it&#8217;s asked for.  </p>

<p>And given a finite amount of resources, I don&#8217;t know if we&#8217;ll have any <em>more</em> total meaning with full semantic markup, than we would have with partial semantic markup and more information (possible because of the smaller burden placed on the writer).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cliff Wells</title>
		<link>http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/comment-page-1/#comment-152</link>
		<dc:creator>Cliff Wells</dc:creator>
		<pubDate>Tue, 14 Aug 2007 21:31:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/#comment-152</guid>
		<description>Heh, and reading my own comment after markdown/CSS has been applied demonstrates how a stylesheet can subtly change the meaning of a document, something that would be more easily avoided by using purely visual descriptions (I used asterisks to denote emphasis in several places which markdown converted to strong which then got changed to italic with a slightly smallish font by the stylesheet.  Subtle, but it now reads slightly differently to me than it did when I wrote it - maybe it&#039;s adopted Ian&#039;s tone of voice because it&#039;s his stylesheet?).  Meaning destroyed by semantics - sounds familiar.</description>
		<content:encoded><![CDATA[<p>Heh, and reading my own comment after markdown/CSS has been applied demonstrates how a stylesheet can subtly change the meaning of a document, something that would be more easily avoided by using purely visual descriptions (I used asterisks to denote emphasis in several places which markdown converted to strong which then got changed to italic with a slightly smallish font by the stylesheet.  Subtle, but it now reads slightly differently to me than it did when I wrote it &#8211; maybe it&#8217;s adopted Ian&#8217;s tone of voice because it&#8217;s his stylesheet?).  Meaning destroyed by semantics &#8211; sounds familiar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cliff Wells</title>
		<link>http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/comment-page-1/#comment-151</link>
		<dc:creator>Cliff Wells</dc:creator>
		<pubDate>Tue, 14 Aug 2007 21:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ianbicking.org/2007/08/14/reflection-and-description-of-meaning/#comment-151</guid>
		<description>Part of the problem is that descriptions like &quot;strong&quot; don&#039;t really map to what we&#039;re thinking when we write.  If descriptions like &quot;emphasize&quot; and &quot;shout&quot; were used, then I think the argument would end there.  No one &quot;strongs&quot; a word.  They *emphasize* it.  I think that &quot;bold&quot; is also wrong, but it&#039;s become a synonym for something meaning &quot;emphasize that I&#039;m using this word in a very exact way&quot; amongst computer-oriented people.  Of course, extrapolating from &quot;computer-oriented&quot; to &quot;average joe&quot; probably fails a lot.

Also, certain conventions also come into play, such as &quot;underline&quot; which can be used both to emphasize as well as to follow a convention (such as when underlining the title of a publication).  Should there be a separate semantic markup symbol to distinguish these two uses?  Maybe, but in practice we think &quot;underline&quot; out of habit and conciseness.  The context defines its meaning and this is commonly recognized enough to be acceptable.

The &quot;semantic web&quot; people seem to disregard the fact that there simply aren&#039;t enough semantically distinguishable tokens in HTML and CSS to describe the vagaries of language (nor should there be, lest we end up with hundreds of tokens with subtle distinctions that would probably be lost or misinterpreted by 90% of readers anyway really. it. isn&#039;t. needed.).  Semantics is heavily dependent on context and interpretation.  Tokens like &quot;bold&quot;, &quot;italic&quot; and &quot;underline&quot; describe the *visual* appearance of the written word and that&#039;s really what&#039;s needed.  The visual appearance is a substitute for other cues normally gathered from a speaker&#039;s tone, not a meaning in and of itself.   Context provides the meaning.  We should simply accept that the written word will never carry the subtleties of spoken word and agree that a visual description (i.e. bold, italic) is as adequate as any other subset and actually provides a much more flexible system precisely *because* it doesn&#039;t try to convey meaning outside of a particular context.</description>
		<content:encoded><![CDATA[<p>Part of the problem is that descriptions like &#8220;strong&#8221; don&#8217;t really map to what we&#8217;re thinking when we write.  If descriptions like &#8220;emphasize&#8221; and &#8220;shout&#8221; were used, then I think the argument would end there.  No one &#8220;strongs&#8221; a word.  They <em>emphasize</em> it.  I think that &#8220;bold&#8221; is also wrong, but it&#8217;s become a synonym for something meaning &#8220;emphasize that I&#8217;m using this word in a very exact way&#8221; amongst computer-oriented people.  Of course, extrapolating from &#8220;computer-oriented&#8221; to &#8220;average joe&#8221; probably fails a lot.</p>

<p>Also, certain conventions also come into play, such as &#8220;underline&#8221; which can be used both to emphasize as well as to follow a convention (such as when underlining the title of a publication).  Should there be a separate semantic markup symbol to distinguish these two uses?  Maybe, but in practice we think &#8220;underline&#8221; out of habit and conciseness.  The context defines its meaning and this is commonly recognized enough to be acceptable.</p>

<p>The &#8220;semantic web&#8221; people seem to disregard the fact that there simply aren&#8217;t enough semantically distinguishable tokens in HTML and CSS to describe the vagaries of language (nor should there be, lest we end up with hundreds of tokens with subtle distinctions that would probably be lost or misinterpreted by 90% of readers anyway really. it. isn&#8217;t. needed.).  Semantics is heavily dependent on context and interpretation.  Tokens like &#8220;bold&#8221;, &#8220;italic&#8221; and &#8220;underline&#8221; describe the <em>visual</em> appearance of the written word and that&#8217;s really what&#8217;s needed.  The visual appearance is a substitute for other cues normally gathered from a speaker&#8217;s tone, not a meaning in and of itself.   Context provides the meaning.  We should simply accept that the written word will never carry the subtleties of spoken word and agree that a visual description (i.e. bold, italic) is as adequate as any other subset and actually provides a much more flexible system precisely <em>because</em> it doesn&#8217;t try to convey meaning outside of a particular context.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.810 seconds -->
