{"id":864,"date":"2009-10-27T19:01:48","date_gmt":"2009-10-27T19:01:48","guid":{"rendered":"http:\/\/jodischneider.com\/blog\/?p=864"},"modified":"2009-10-27T19:01:48","modified_gmt":"2009-10-27T19:01:48","slug":"when-an-abstract-is-not-a-summary-check-the-audience","status":"publish","type":"post","link":"https:\/\/jodischneider.com\/blog\/2009\/10\/27\/when-an-abstract-is-not-a-summary-check-the-audience\/","title":{"rendered":"When an abstract is not a summary: check the audience"},"content":{"rendered":"<p>I&#8217;ve been arguing with <a href=\"http:\/\/www.stat.berkeley.edu\/users\/pitman\/\">Jim Pitman<\/a> about how abstracts are different from summaries. The <strong>audience<\/strong>, I think, determines whether a text is suitable to be used as a summary.<\/p>\n<p>This seems like a good example:<\/p>\n<p>Lumley, J., Gimson, R., &amp; Rees, O. (2007). Endless documents: a publication as a continual function. In <span>Proceedings of the 2007 ACM symposium on Document engineering<\/span> (pp. 174-176). Winnipeg, Manitoba, Canada: ACM. doi: <a href=\"http:\/\/dx.doi.org\/10.1145\/1284420.1284463\">10.1145\/1284420.1284463<\/a><\/p>\n<blockquote><p>Variable data can be considered as functions of their bindings to values. The Document Description Framework (DDF) treats documents in this manner, using XSLT semantics to describe document functionality and a variety of related mechanisms to support layout, reference and so forth. But the result of evaluation of a function could itself be a function: can variable data documents behave likewise? We show that documents can be treated as simple continuations within that framework with minor modifications. We demonstrate this on a perpetual diary.<\/p><\/blockquote>\n<p>This is a really interesting article from a <a href=\"http:\/\/www.hpl.hp.com\/research\/web_services\/\">team<\/a> at <a href=\"http:\/\/www.hpl.hp.com\/bristol\/index.html\">HP Bristol (UK)<\/a>. They seem to be talking about the benefit of publishing as you go along (i.e. blogs or medical records). They call these &#8220;continual documents&#8221;.<\/p>\n<p>I picked it up ((I came across a <a href=\"http:\/\/portal.acm.org\/toc.cfm?id=1284420\">conference on &#8216;document engineering&#8217;<\/a> [ACM digital library, may have a paywall] while sifting through articles for my literature review. &#8216;Document engineering&#8217; includes lots of stuff that&#8217;s out of scope. Some material, on structural markup,may be relevant to online argumentation.)) because the abstract seemed bizarre, but the topic seemed interesting. &#8220;Continual documents&#8221; struck me as &#8220;continual functions&#8221;. And the mention of XSLT hinted at transforming a document using its underlying structure.<\/p>\n<p>Surely, I thought, this abstract couldn&#8217;t describe its contents. After glancing through it, I&#8217;m not sure: This abstract may well summarize the contents of the article. But for me, the abstract really didn&#8217;t serve as a summary: I don&#8217;t know the field, so the terminology (e.g. document engineering, Document <span>Description<\/span> <span>Framework ((<\/span>One interesting line stands out: &#8220;In DDF documents most program elements are &lt;xslt:template\/&gt; trees.&#8221;))<span>) didn&#8217;t clue me in. <\/span><\/p>\n<p><span>This difference gets at what <a href=\"http:\/\/acawiki.org\/\">AcaWiki <\/a>is trying to do: provide a place for people to discuss\/summarize research articles, in the way that Wikipedia is a place to discuss\/summarize topics. Neither is a place for research but both are places for experts to share knowledge, for would-be-experts to describe what they know, and for non-experts to glean a deeper sense of the world than they might have had otherwise.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve been arguing with Jim Pitman about how abstracts are different from summaries. The audience, I think, determines whether a text is suitable to be used as a summary. This seems like a good example: Lumley, J., Gimson, R., &amp; Rees, O. (2007). Endless documents: a publication as a continual function. In Proceedings of the [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[175,174,96],"tags":[160],"class_list":["post-864","post","type-post","status-publish","format-standard","hentry","category-argumentative-discussions","category-phd-diary","category-random-thoughts","tag-acawiki"],"_links":{"self":[{"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/posts\/864","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/comments?post=864"}],"version-history":[{"count":17,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/posts\/864\/revisions"}],"predecessor-version":[{"id":882,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/posts\/864\/revisions\/882"}],"wp:attachment":[{"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/media?parent=864"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/categories?post=864"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/tags?post=864"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}