Serveur d'exploration sur la TEI

Attention, ce site est en cours de développement !
Attention, site généré par des moyens informatiques à partir de corpus bruts.
Les informations ne sont donc pas validées.

What Characterizes Pictures and Text?

Identifieur interne : 000119 ( Istex/Corpus ); précédent : 000118; suivant : 000120

What Characterizes Pictures and Text?

Auteurs : Michael A. R. Biggs

Source :

RBID : ISTEX:F56628CF941546965DB7275DE4F437DFC38C5283

Abstract

This paper addresses an apparently trivial question: what is the difference between graphics and text? It appears to be trivial because there would seem to be several alternative and simple ways of answering it. For example, ‘text is made up of letters whereas graphics are not’, ‘one can create text using a keyboard’, ‘one can read text aloud’, etc. However, none of these provides robust conditions to differentiate graphics from text, e.g. cases such as typewriter art and gobbledygook can be identified. The paper approaches the problem of identifying content conditions by analysing boundary cases which lie on the margins and are difficult to classify. It considers examples that arise in the production of materials, including bitmapped text, graphics consisting of letters and words, text used as patterns or in tables, etc. It also considers examples that arise from the consumption of materials, including a comparison of the methods used for reading and interpreting text and graphics. This paper concludes that current XML specifications, e.g. TEI guidelines, for the integration of graphics into text are primarily made on the basis of form rather than content. This is incompatible with a content-based or descriptive markup scheme. Before such guidelines can be modified we must be clearer about what differentiates graphics from text in terms of content conditions rather than technological or formal conditions.

Url:
DOI: 10.1093/llc/19.3.265

Links to Exploration step

ISTEX:F56628CF941546965DB7275DE4F437DFC38C5283

Le document en format XML

<record>
<TEI wicri:istexFullTextTei="biblStruct">
<teiHeader>
<fileDesc>
<titleStmt>
<title xml:lang="en">What Characterizes Pictures and Text?</title>
<author wicri:is="90%">
<name sortKey="Biggs, Michael A R" sort="Biggs, Michael A R" uniqKey="Biggs M" first="Michael A. R." last="Biggs">Michael A. R. Biggs</name>
<affiliation>
<mods:affiliation>University of Hertfordshire, UK</mods:affiliation>
</affiliation>
</author>
</titleStmt>
<publicationStmt>
<idno type="wicri:source">ISTEX</idno>
<idno type="RBID">ISTEX:F56628CF941546965DB7275DE4F437DFC38C5283</idno>
<date when="2004" year="2004">2004</date>
<idno type="doi">10.1093/llc/19.3.265</idno>
<idno type="url">https://api.istex.fr/document/F56628CF941546965DB7275DE4F437DFC38C5283/fulltext/pdf</idno>
<idno type="wicri:Area/Istex/Corpus">000119</idno>
</publicationStmt>
<sourceDesc>
<biblStruct>
<analytic>
<title level="a" type="main" xml:lang="en">What Characterizes Pictures and Text?</title>
<author wicri:is="90%">
<name sortKey="Biggs, Michael A R" sort="Biggs, Michael A R" uniqKey="Biggs M" first="Michael A. R." last="Biggs">Michael A. R. Biggs</name>
<affiliation>
<mods:affiliation>University of Hertfordshire, UK</mods:affiliation>
</affiliation>
</author>
</analytic>
<monogr></monogr>
<series>
<title level="j">Literary and Linguistic Computing</title>
<title level="j" type="abbrev">Lit Linguist Computing</title>
<idno type="ISSN">0268-1145</idno>
<idno type="eISSN">1477-4615</idno>
<imprint>
<publisher>Oxford University Press</publisher>
<date type="published" when="2004-09">2004-09</date>
<biblScope unit="volume">19</biblScope>
<biblScope unit="issue">3</biblScope>
<biblScope unit="page" from="265">265</biblScope>
<biblScope unit="page" to="272">272</biblScope>
</imprint>
<idno type="ISSN">0268-1145</idno>
</series>
<idno type="istex">F56628CF941546965DB7275DE4F437DFC38C5283</idno>
<idno type="DOI">10.1093/llc/19.3.265</idno>
<idno type="local">190265</idno>
</biblStruct>
</sourceDesc>
<seriesStmt>
<idno type="ISSN">0268-1145</idno>
</seriesStmt>
</fileDesc>
<profileDesc>
<textClass></textClass>
<langUsage>
<language ident="en">en</language>
</langUsage>
</profileDesc>
</teiHeader>
<front>
<div type="abstract" xml:lang="en">This paper addresses an apparently trivial question: what is the difference between graphics and text? It appears to be trivial because there would seem to be several alternative and simple ways of answering it. For example, ‘text is made up of letters whereas graphics are not’, ‘one can create text using a keyboard’, ‘one can read text aloud’, etc. However, none of these provides robust conditions to differentiate graphics from text, e.g. cases such as typewriter art and gobbledygook can be identified. The paper approaches the problem of identifying content conditions by analysing boundary cases which lie on the margins and are difficult to classify. It considers examples that arise in the production of materials, including bitmapped text, graphics consisting of letters and words, text used as patterns or in tables, etc. It also considers examples that arise from the consumption of materials, including a comparison of the methods used for reading and interpreting text and graphics. This paper concludes that current XML specifications, e.g. TEI guidelines, for the integration of graphics into text are primarily made on the basis of form rather than content. This is incompatible with a content-based or descriptive markup scheme. Before such guidelines can be modified we must be clearer about what differentiates graphics from text in terms of content conditions rather than technological or formal conditions.</div>
</front>
</TEI>
<istex>
<corpusName>oup</corpusName>
<author>
<json:item>
<name>Michael A. R. Biggs</name>
<affiliations>
<json:string>University of Hertfordshire, UK</json:string>
</affiliations>
</json:item>
</author>
<language>
<json:string>eng</json:string>
</language>
<originalGenre>
<json:string>research-article</json:string>
</originalGenre>
<abstract>This paper addresses an apparently trivial question: what is the difference between graphics and text? It appears to be trivial because there would seem to be several alternative and simple ways of answering it. For example, ‘text is made up of letters whereas graphics are not’, ‘one can create text using a keyboard’, ‘one can read text aloud’, etc. However, none of these provides robust conditions to differentiate graphics from text, e.g. cases such as typewriter art and gobbledygook can be identified. The paper approaches the problem of identifying content conditions by analysing boundary cases which lie on the margins and are difficult to classify. It considers examples that arise in the production of materials, including bitmapped text, graphics consisting of letters and words, text used as patterns or in tables, etc. It also considers examples that arise from the consumption of materials, including a comparison of the methods used for reading and interpreting text and graphics. This paper concludes that current XML specifications, e.g. TEI guidelines, for the integration of graphics into text are primarily made on the basis of form rather than content. This is incompatible with a content-based or descriptive markup scheme. Before such guidelines can be modified we must be clearer about what differentiates graphics from text in terms of content conditions rather than technological or formal conditions.</abstract>
<qualityIndicators>
<score>6.34</score>
<pdfVersion>1.3</pdfVersion>
<pdfPageSize>538.307 x 697.433 pts</pdfPageSize>
<refBibsNative>false</refBibsNative>
<keywordCount>0</keywordCount>
<abstractCharCount>1429</abstractCharCount>
<pdfWordCount>3676</pdfWordCount>
<pdfCharCount>22116</pdfCharCount>
<pdfPageCount>8</pdfPageCount>
<abstractWordCount>222</abstractWordCount>
</qualityIndicators>
<title>What Characterizes Pictures and Text?</title>
<genre>
<json:string>research-article</json:string>
</genre>
<host>
<volume>19</volume>
<publisherId>
<json:string>litlin</json:string>
</publisherId>
<pages>
<last>272</last>
<first>265</first>
</pages>
<issn>
<json:string>0268-1145</json:string>
</issn>
<issue>3</issue>
<genre>
<json:string>journal</json:string>
</genre>
<language>
<json:string>unknown</json:string>
</language>
<eissn>
<json:string>1477-4615</json:string>
</eissn>
<title>Literary and Linguistic Computing</title>
</host>
<categories>
<wos>
<json:string>LINGUISTICS</json:string>
<json:string>LITERATURE</json:string>
</wos>
</categories>
<publicationDate>2004</publicationDate>
<copyrightDate>2004</copyrightDate>
<doi>
<json:string>10.1093/llc/19.3.265</json:string>
</doi>
<id>F56628CF941546965DB7275DE4F437DFC38C5283</id>
<score>0.28746122</score>
<fulltext>
<json:item>
<original>true</original>
<mimetype>application/pdf</mimetype>
<extension>pdf</extension>
<uri>https://api.istex.fr/document/F56628CF941546965DB7275DE4F437DFC38C5283/fulltext/pdf</uri>
</json:item>
<json:item>
<original>false</original>
<mimetype>application/zip</mimetype>
<extension>zip</extension>
<uri>https://api.istex.fr/document/F56628CF941546965DB7275DE4F437DFC38C5283/fulltext/zip</uri>
</json:item>
<istex:fulltextTEI uri="https://api.istex.fr/document/F56628CF941546965DB7275DE4F437DFC38C5283/fulltext/tei">
<teiHeader>
<fileDesc>
<titleStmt>
<title level="a" type="main" xml:lang="en">What Characterizes Pictures and Text?</title>
<respStmt xml:id="ISTEX-API" resp="Références bibliographiques récupérées via GROBID" name="ISTEX-API (INIST-CNRS)"></respStmt>
<respStmt xml:id="ISTEX-API" resp="Références bibliographiques récupérées via GROBID" name="ISTEX-API (INIST-CNRS)"></respStmt>
<respStmt>
<resp>Références bibliographiques récupérées via GROBID</resp>
<name resp="ISTEX-API">ISTEX-API (INIST-CNRS)</name>
</respStmt>
</titleStmt>
<publicationStmt>
<authority>ISTEX</authority>
<publisher>Oxford University Press</publisher>
<availability>
<p>OUP</p>
</availability>
<date>2004</date>
</publicationStmt>
<sourceDesc>
<biblStruct type="inbook">
<analytic>
<title level="a" type="main" xml:lang="en">What Characterizes Pictures and Text?</title>
<author>
<persName>
<forename type="first">Michael A. R.</forename>
<surname>Biggs</surname>
</persName>
<affiliation>University of Hertfordshire, UK</affiliation>
</author>
</analytic>
<monogr>
<title level="j">Literary and Linguistic Computing</title>
<title level="j" type="abbrev">Lit Linguist Computing</title>
<idno type="pISSN">0268-1145</idno>
<idno type="eISSN">1477-4615</idno>
<imprint>
<publisher>Oxford University Press</publisher>
<date type="published" when="2004-09"></date>
<biblScope unit="volume">19</biblScope>
<biblScope unit="issue">3</biblScope>
<biblScope unit="page" from="265">265</biblScope>
<biblScope unit="page" to="272">272</biblScope>
</imprint>
</monogr>
<idno type="istex">F56628CF941546965DB7275DE4F437DFC38C5283</idno>
<idno type="DOI">10.1093/llc/19.3.265</idno>
<idno type="local">190265</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc>
<creation>
<date>2004</date>
</creation>
<langUsage>
<language ident="en">en</language>
</langUsage>
<abstract xml:lang="en">
<p>This paper addresses an apparently trivial question: what is the difference between graphics and text? It appears to be trivial because there would seem to be several alternative and simple ways of answering it. For example, ‘text is made up of letters whereas graphics are not’, ‘one can create text using a keyboard’, ‘one can read text aloud’, etc. However, none of these provides robust conditions to differentiate graphics from text, e.g. cases such as typewriter art and gobbledygook can be identified. The paper approaches the problem of identifying content conditions by analysing boundary cases which lie on the margins and are difficult to classify. It considers examples that arise in the production of materials, including bitmapped text, graphics consisting of letters and words, text used as patterns or in tables, etc. It also considers examples that arise from the consumption of materials, including a comparison of the methods used for reading and interpreting text and graphics. This paper concludes that current XML specifications, e.g. TEI guidelines, for the integration of graphics into text are primarily made on the basis of form rather than content. This is incompatible with a content-based or descriptive markup scheme. Before such guidelines can be modified we must be clearer about what differentiates graphics from text in terms of content conditions rather than technological or formal conditions.</p>
</abstract>
</profileDesc>
<revisionDesc>
<change when="2004-09">Published</change>
<change xml:id="refBibs-istex" who="#ISTEX-API" when="2016-3-15">References added</change>
<change xml:id="refBibs-istex" who="#ISTEX-API" when="2016-3-21">References added</change>
<change xml:id="refBibs-istex" who="#ISTEX-API" when="2016-07-27">References added</change>
</revisionDesc>
</teiHeader>
</istex:fulltextTEI>
<json:item>
<original>false</original>
<mimetype>text/plain</mimetype>
<extension>txt</extension>
<uri>https://api.istex.fr/document/F56628CF941546965DB7275DE4F437DFC38C5283/fulltext/txt</uri>
</json:item>
</fulltext>
<metadata>
<istex:metadataXml wicri:clean="corpus oup" wicri:toSee="no header">
<istex:xmlDeclaration>version="1.0" encoding="US-ASCII"</istex:xmlDeclaration>
<istex:docType PUBLIC="-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" URI="journalpublishing.dtd" name="istex:docType"></istex:docType>
<istex:document>
<article xml:lang="en" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">litlin</journal-id>
<journal-id journal-id-type="hwp">litlin</journal-id>
<journal-title>Literary and Linguistic Computing</journal-title>
<abbrev-journal-title abbrev-type="publisher">Lit Linguist Computing</abbrev-journal-title>
<issn pub-type="ppub">0268-1145</issn>
<issn pub-type="epub">1477-4615</issn>
<publisher>
<publisher-name>Oxford University Press</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="other">190265</article-id>
<article-id pub-id-type="doi">10.1093/llc/19.3.265</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>What Characterizes Pictures and Text?</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Biggs</surname>
<given-names>Michael A. R.</given-names>
</name>
<xref rid="AFF1">1</xref>
</contrib>
<aff>
<target target-type="aff" id="AFF1"></target>
<label>1</label>
University of Hertfordshire, UK</aff>
</contrib-group>
<pub-date pub-type="ppub">
<month>09</month>
<year>2004</year>
</pub-date>
<volume>19</volume>
<issue>3</issue>
<fpage>265</fpage>
<lpage>272</lpage>
<permissions>
<copyright-statement>Copyright Association for Literary & Linguistic Computing 2004</copyright-statement>
<copyright-year>2004</copyright-year>
</permissions>
<abstract xml:lang="en">
<p>This paper addresses an apparently trivial question: what is the difference between graphics and text? It appears to be trivial because there would seem to be several alternative and simple ways of answering it. For example, ‘text is made up of letters whereas graphics are not’, ‘one can create text using a keyboard’, ‘one can read text aloud’, etc. However, none of these provides robust conditions to differentiate graphics from text, e.g. cases such as typewriter art and gobbledygook can be identified. The paper approaches the problem of identifying content conditions by analysing boundary cases which lie on the margins and are difficult to classify. It considers examples that arise in the production of materials, including bitmapped text, graphics consisting of letters and words, text used as patterns or in tables, etc. It also considers examples that arise from the consumption of materials, including a comparison of the methods used for reading and interpreting text and graphics. This paper concludes that current XML specifications, e.g. TEI guidelines, for the integration of graphics into text are primarily made on the basis of form rather than content. This is incompatible with a content-based or descriptive markup scheme. Before such guidelines can be modified we must be clearer about what differentiates graphics from text in terms of content conditions rather than technological or formal conditions.</p>
</abstract>
<custom-meta-wrap>
<custom-meta>
<meta-name>hwp-legacy-fpage</meta-name>
<meta-value>265</meta-value>
</custom-meta>
<custom-meta>
<meta-name>hwp-legacy-dochead</meta-name>
<meta-value>Article</meta-value>
</custom-meta>
</custom-meta-wrap>
</article-meta>
</front>
</article>
</istex:document>
</istex:metadataXml>
<mods version="3.6">
<titleInfo lang="en">
<title>What Characterizes Pictures and Text?</title>
</titleInfo>
<titleInfo type="alternative" lang="en" contentType="CDATA">
<title>What Characterizes Pictures and Text?</title>
</titleInfo>
<name type="personal">
<namePart type="given">Michael A. R.</namePart>
<namePart type="family">Biggs</namePart>
<affiliation>University of Hertfordshire, UK</affiliation>
</name>
<typeOfResource>text</typeOfResource>
<genre type="research-article" displayLabel="research-article"></genre>
<originInfo>
<publisher>Oxford University Press</publisher>
<dateIssued encoding="w3cdtf">2004-09</dateIssued>
<copyrightDate encoding="w3cdtf">2004</copyrightDate>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
<languageTerm type="code" authority="rfc3066">en</languageTerm>
</language>
<physicalDescription>
<internetMediaType>text/html</internetMediaType>
</physicalDescription>
<abstract lang="en">This paper addresses an apparently trivial question: what is the difference between graphics and text? It appears to be trivial because there would seem to be several alternative and simple ways of answering it. For example, ‘text is made up of letters whereas graphics are not’, ‘one can create text using a keyboard’, ‘one can read text aloud’, etc. However, none of these provides robust conditions to differentiate graphics from text, e.g. cases such as typewriter art and gobbledygook can be identified. The paper approaches the problem of identifying content conditions by analysing boundary cases which lie on the margins and are difficult to classify. It considers examples that arise in the production of materials, including bitmapped text, graphics consisting of letters and words, text used as patterns or in tables, etc. It also considers examples that arise from the consumption of materials, including a comparison of the methods used for reading and interpreting text and graphics. This paper concludes that current XML specifications, e.g. TEI guidelines, for the integration of graphics into text are primarily made on the basis of form rather than content. This is incompatible with a content-based or descriptive markup scheme. Before such guidelines can be modified we must be clearer about what differentiates graphics from text in terms of content conditions rather than technological or formal conditions.</abstract>
<relatedItem type="host">
<titleInfo>
<title>Literary and Linguistic Computing</title>
</titleInfo>
<titleInfo type="abbreviated">
<title>Lit Linguist Computing</title>
</titleInfo>
<genre type="journal">journal</genre>
<identifier type="ISSN">0268-1145</identifier>
<identifier type="eISSN">1477-4615</identifier>
<identifier type="PublisherID">litlin</identifier>
<identifier type="PublisherID-hwp">litlin</identifier>
<part>
<date>2004</date>
<detail type="volume">
<caption>vol.</caption>
<number>19</number>
</detail>
<detail type="issue">
<caption>no.</caption>
<number>3</number>
</detail>
<extent unit="pages">
<start>265</start>
<end>272</end>
</extent>
</part>
</relatedItem>
<identifier type="istex">F56628CF941546965DB7275DE4F437DFC38C5283</identifier>
<identifier type="DOI">10.1093/llc/19.3.265</identifier>
<identifier type="local">190265</identifier>
<accessCondition type="use and reproduction" contentType="copyright">Copyright Association for Literary & Linguistic Computing 2004</accessCondition>
<recordInfo>
<recordContentSource>OUP</recordContentSource>
</recordInfo>
</mods>
</metadata>
<enrichments>
<istex:catWosTEI uri="https://api.istex.fr/document/F56628CF941546965DB7275DE4F437DFC38C5283/enrichments/catWos">
<teiHeader>
<profileDesc>
<textClass>
<classCode scheme="WOS">LINGUISTICS</classCode>
<classCode scheme="WOS">LITERATURE</classCode>
</textClass>
</profileDesc>
</teiHeader>
</istex:catWosTEI>
<json:item>
<type>refBibs</type>
<uri>https://api.istex.fr/document/F56628CF941546965DB7275DE4F437DFC38C5283/enrichments/refBibs</uri>
</json:item>
</enrichments>
<serie></serie>
</istex>
</record>

Pour manipuler ce document sous Unix (Dilib)

EXPLOR_STEP=$WICRI_ROOT/Wicri/Ticri/explor/TeiVM2/Data/Istex/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000119 | SxmlIndent | more

Ou

HfdSelect -h $EXPLOR_AREA/Data/Istex/Corpus/biblio.hfd -nk 000119 | SxmlIndent | more

Pour mettre un lien sur cette page dans le réseau Wicri

{{Explor lien
   |wiki=    Wicri/Ticri
   |area=    TeiVM2
   |flux=    Istex
   |étape=   Corpus
   |type=    RBID
   |clé=     ISTEX:F56628CF941546965DB7275DE4F437DFC38C5283
   |texte=   What Characterizes Pictures and Text?
}}

Wicri

This area was generated with Dilib version V0.6.31.
Data generation: Mon Oct 30 21:59:18 2017. Site generation: Sun Feb 11 23:16:06 2024