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 is text, really?

Identifieur interne : 000199 ( Istex/Corpus ); précédent : 000198; suivant : 000200

What is text, really?

Auteurs : J. Derose ; G. Durand ; Elli Mylonas ; H. Renear

Source :

RBID : ISTEX:0261DF9B24207ABDE17B70D0C15901A0384F243B

Abstract

Abstract: THE WAY IN WHICH TEXT IS represented on a computer affects the kinds of uses to which it can be put by its creator and by subsequent users. The electronic document model currently in use is impoverished and restrictive. The authors argue that text is best represented as an ordered hierarchy of content object (OHCO), because that is what text really is. This model conforms with emerging standards such as SGML and contains within it advantages for the writer, publisher, and researcher. The authors then describe how the hierarchical model can allow future use and reuse of the document as a database, hypertext, or network.

Url:
DOI: 10.1007/BF02941632

Links to Exploration step

ISTEX:0261DF9B24207ABDE17B70D0C15901A0384F243B

Le document en format XML

<record>
<TEI wicri:istexFullTextTei="biblStruct">
<teiHeader>
<fileDesc>
<titleStmt>
<title xml:lang="en">What is text, really?</title>
<author>
<name sortKey="Derose, J" sort="Derose, J" uniqKey="Derose J" first="J." last="Derose">J. Derose</name>
<affiliation>
<mods:affiliation>praXis, USA</mods:affiliation>
</affiliation>
</author>
<author>
<name sortKey="Durand, G" sort="Durand, G" uniqKey="Durand G" first="G." last="Durand">G. Durand</name>
<affiliation>
<mods:affiliation>Brandeis University, USA</mods:affiliation>
</affiliation>
</author>
<author>
<name sortKey="Mylonas, Elli" sort="Mylonas, Elli" uniqKey="Mylonas E" first="Elli" last="Mylonas">Elli Mylonas</name>
<affiliation>
<mods:affiliation>Harvard University, USA</mods:affiliation>
</affiliation>
</author>
<author>
<name sortKey="Renear, H" sort="Renear, H" uniqKey="Renear H" first="H." last="Renear">H. Renear</name>
<affiliation>
<mods:affiliation>Brown University, USA</mods:affiliation>
</affiliation>
</author>
</titleStmt>
<publicationStmt>
<idno type="wicri:source">ISTEX</idno>
<idno type="RBID">ISTEX:0261DF9B24207ABDE17B70D0C15901A0384F243B</idno>
<date when="1990" year="1990">1990</date>
<idno type="doi">10.1007/BF02941632</idno>
<idno type="url">https://api.istex.fr/document/0261DF9B24207ABDE17B70D0C15901A0384F243B/fulltext/pdf</idno>
<idno type="wicri:Area/Istex/Corpus">000199</idno>
</publicationStmt>
<sourceDesc>
<biblStruct>
<analytic>
<title level="a" type="main" xml:lang="en">What is text, really?</title>
<author>
<name sortKey="Derose, J" sort="Derose, J" uniqKey="Derose J" first="J." last="Derose">J. Derose</name>
<affiliation>
<mods:affiliation>praXis, USA</mods:affiliation>
</affiliation>
</author>
<author>
<name sortKey="Durand, G" sort="Durand, G" uniqKey="Durand G" first="G." last="Durand">G. Durand</name>
<affiliation>
<mods:affiliation>Brandeis University, USA</mods:affiliation>
</affiliation>
</author>
<author>
<name sortKey="Mylonas, Elli" sort="Mylonas, Elli" uniqKey="Mylonas E" first="Elli" last="Mylonas">Elli Mylonas</name>
<affiliation>
<mods:affiliation>Harvard University, USA</mods:affiliation>
</affiliation>
</author>
<author>
<name sortKey="Renear, H" sort="Renear, H" uniqKey="Renear H" first="H." last="Renear">H. Renear</name>
<affiliation>
<mods:affiliation>Brown University, USA</mods:affiliation>
</affiliation>
</author>
</analytic>
<monogr></monogr>
<series>
<title level="j">Journal of Computing in Higher Education</title>
<title level="j" type="abbrev">J. Comput. High. Educ.</title>
<idno type="ISSN">1042-1726</idno>
<imprint>
<publisher>Springer US</publisher>
<pubPlace>Boston</pubPlace>
<date type="published" when="1990-12-01">1990-12-01</date>
<biblScope unit="volume">1</biblScope>
<biblScope unit="issue">2</biblScope>
<biblScope unit="page" from="3">3</biblScope>
<biblScope unit="page" to="26">26</biblScope>
</imprint>
<idno type="ISSN">1042-1726</idno>
</series>
<idno type="istex">0261DF9B24207ABDE17B70D0C15901A0384F243B</idno>
<idno type="DOI">10.1007/BF02941632</idno>
<idno type="ArticleID">BF02941632</idno>
<idno type="ArticleID">Art1</idno>
</biblStruct>
</sourceDesc>
<seriesStmt>
<idno type="ISSN">1042-1726</idno>
</seriesStmt>
</fileDesc>
<profileDesc>
<textClass></textClass>
<langUsage>
<language ident="en">en</language>
</langUsage>
</profileDesc>
</teiHeader>
<front>
<div type="abstract" xml:lang="en">Abstract: THE WAY IN WHICH TEXT IS represented on a computer affects the kinds of uses to which it can be put by its creator and by subsequent users. The electronic document model currently in use is impoverished and restrictive. The authors argue that text is best represented as an ordered hierarchy of content object (OHCO), because that is what text really is. This model conforms with emerging standards such as SGML and contains within it advantages for the writer, publisher, and researcher. The authors then describe how the hierarchical model can allow future use and reuse of the document as a database, hypertext, or network.</div>
</front>
</TEI>
<istex>
<corpusName>springer</corpusName>
<author>
<json:item>
<name>Steven J. DeRose</name>
<affiliations>
<json:string>praXis, USA</json:string>
</affiliations>
</json:item>
<json:item>
<name>David G. Durand</name>
<affiliations>
<json:string>Brandeis University, USA</json:string>
</affiliations>
</json:item>
<json:item>
<name>Elli Mylonas</name>
<affiliations>
<json:string>Harvard University, USA</json:string>
</affiliations>
</json:item>
<json:item>
<name>Allen H. Renear</name>
<affiliations>
<json:string>Brown University, USA</json:string>
</affiliations>
</json:item>
</author>
<articleId>
<json:string>BF02941632</json:string>
<json:string>Art1</json:string>
</articleId>
<language>
<json:string>eng</json:string>
</language>
<originalGenre>
<json:string>OriginalPaper</json:string>
</originalGenre>
<abstract>Abstract: THE WAY IN WHICH TEXT IS represented on a computer affects the kinds of uses to which it can be put by its creator and by subsequent users. The electronic document model currently in use is impoverished and restrictive. The authors argue that text is best represented as an ordered hierarchy of content object (OHCO), because that is what text really is. This model conforms with emerging standards such as SGML and contains within it advantages for the writer, publisher, and researcher. The authors then describe how the hierarchical model can allow future use and reuse of the document as a database, hypertext, or network.</abstract>
<qualityIndicators>
<score>6.272</score>
<pdfVersion>1.3</pdfVersion>
<pdfPageSize>432 x 648 pts</pdfPageSize>
<refBibsNative>false</refBibsNative>
<keywordCount>0</keywordCount>
<abstractCharCount>636</abstractCharCount>
<pdfWordCount>7192</pdfWordCount>
<pdfCharCount>39871</pdfCharCount>
<pdfPageCount>24</pdfPageCount>
<abstractWordCount>106</abstractWordCount>
</qualityIndicators>
<title>What is text, really?</title>
<genre>
<json:string>research-article</json:string>
</genre>
<host>
<volume>1</volume>
<pages>
<last>26</last>
<first>3</first>
</pages>
<issn>
<json:string>1042-1726</json:string>
</issn>
<issue>2</issue>
<subject>
<json:item>
<value>Education</value>
</json:item>
<json:item>
<value>Educational Technology</value>
</json:item>
<json:item>
<value>Learning & Instruction</value>
</json:item>
<json:item>
<value>Higher Education</value>
</json:item>
</subject>
<journalId>
<json:string>12528</json:string>
</journalId>
<genre>
<json:string>journal</json:string>
</genre>
<language>
<json:string>unknown</json:string>
</language>
<title>Journal of Computing in Higher Education</title>
<publicationDate>1990</publicationDate>
<copyrightDate>1990</copyrightDate>
</host>
<publicationDate>1990</publicationDate>
<copyrightDate>1990</copyrightDate>
<doi>
<json:string>10.1007/BF02941632</json:string>
</doi>
<id>0261DF9B24207ABDE17B70D0C15901A0384F243B</id>
<score>0.22700542</score>
<fulltext>
<json:item>
<original>true</original>
<mimetype>application/pdf</mimetype>
<extension>pdf</extension>
<uri>https://api.istex.fr/document/0261DF9B24207ABDE17B70D0C15901A0384F243B/fulltext/pdf</uri>
</json:item>
<json:item>
<original>false</original>
<mimetype>application/zip</mimetype>
<extension>zip</extension>
<uri>https://api.istex.fr/document/0261DF9B24207ABDE17B70D0C15901A0384F243B/fulltext/zip</uri>
</json:item>
<istex:fulltextTEI uri="https://api.istex.fr/document/0261DF9B24207ABDE17B70D0C15901A0384F243B/fulltext/tei">
<teiHeader>
<fileDesc>
<titleStmt>
<title level="a" type="main" xml:lang="en">What is text, really?</title>
<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>Springer US</publisher>
<pubPlace>Boston</pubPlace>
<availability>
<p>SPRINGER</p>
</availability>
<date>1990</date>
</publicationStmt>
<sourceDesc>
<biblStruct type="inbook">
<analytic>
<title level="a" type="main" xml:lang="en">What is text, really?</title>
<author corresp="yes">
<persName>
<forename type="first">Steven</forename>
<surname>DeRose</surname>
</persName>
<affiliation>praXis, USA</affiliation>
</author>
<author>
<persName>
<forename type="first">David</forename>
<surname>Durand</surname>
</persName>
<affiliation>Brandeis University, USA</affiliation>
</author>
<author>
<persName>
<forename type="first">Elli</forename>
<surname>Mylonas</surname>
</persName>
<affiliation>Harvard University, USA</affiliation>
</author>
<author>
<persName>
<forename type="first">Allen</forename>
<surname>Renear</surname>
</persName>
<affiliation>Brown University, USA</affiliation>
</author>
</analytic>
<monogr>
<title level="j">Journal of Computing in Higher Education</title>
<title level="j" type="abbrev">J. Comput. High. Educ.</title>
<idno type="JournalID">12528</idno>
<idno type="pISSN">1042-1726</idno>
<idno type="IssueArticleCount">7</idno>
<idno type="VolumeIssueCount">2</idno>
<imprint>
<publisher>Springer US</publisher>
<pubPlace>Boston</pubPlace>
<date type="published" when="1990-12-01"></date>
<biblScope unit="volume">1</biblScope>
<biblScope unit="issue">2</biblScope>
<biblScope unit="page" from="3">3</biblScope>
<biblScope unit="page" to="26">26</biblScope>
</imprint>
</monogr>
<idno type="istex">0261DF9B24207ABDE17B70D0C15901A0384F243B</idno>
<idno type="DOI">10.1007/BF02941632</idno>
<idno type="ArticleID">BF02941632</idno>
<idno type="ArticleID">Art1</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc>
<creation>
<date>1990</date>
</creation>
<langUsage>
<language ident="en">en</language>
</langUsage>
<abstract xml:lang="en">
<p>Abstract: THE WAY IN WHICH TEXT IS represented on a computer affects the kinds of uses to which it can be put by its creator and by subsequent users. The electronic document model currently in use is impoverished and restrictive. The authors argue that text is best represented as an ordered hierarchy of content object (OHCO), because that is what text really is. This model conforms with emerging standards such as SGML and contains within it advantages for the writer, publisher, and researcher. The authors then describe how the hierarchical model can allow future use and reuse of the document as a database, hypertext, or network.</p>
</abstract>
<textClass>
<keywords scheme="Journal Subject Group">
<list>
<label>O</label>
<label>O21000</label>
<label>O22000</label>
<label>O36000</label>
<item>
<term>Education</term>
</item>
<item>
<term>Educational Technology</term>
</item>
<item>
<term>Learning & Instruction</term>
</item>
<item>
<term>Higher Education</term>
</item>
</list>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change when="1990-12-01">Published</change>
<change xml:id="refBibs-istex" who="#ISTEX-API" when="2016-3-20">References added</change>
<change xml:id="refBibs-istex" who="#ISTEX-API" when="2016-07-25">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/0261DF9B24207ABDE17B70D0C15901A0384F243B/fulltext/txt</uri>
</json:item>
</fulltext>
<metadata>
<istex:metadataXml wicri:clean="Springer, Publisher found" wicri:toSee="no header">
<istex:xmlDeclaration>version="1.0" encoding="UTF-8"</istex:xmlDeclaration>
<istex:docType PUBLIC="-//Springer-Verlag//DTD A++ V2.4//EN" URI="http://devel.springer.de/A++/V2.4/DTD/A++V2.4.dtd" name="istex:docType"></istex:docType>
<istex:document>
<Publisher>
<PublisherInfo>
<PublisherName>Springer US</PublisherName>
<PublisherLocation>Boston</PublisherLocation>
</PublisherInfo>
<Journal>
<JournalInfo JournalProductType="ArchiveJournal" NumberingStyle="Unnumbered">
<JournalID>12528</JournalID>
<JournalPrintISSN>1042-1726</JournalPrintISSN>
<JournalTitle>Journal of Computing in Higher Education</JournalTitle>
<JournalAbbreviatedTitle>J. Comput. High. Educ.</JournalAbbreviatedTitle>
<JournalSubjectGroup>
<JournalSubject Code="O" Type="Primary">Education</JournalSubject>
<JournalSubject Code="O21000" Priority="1" Type="Secondary">Educational Technology</JournalSubject>
<JournalSubject Code="O22000" Priority="2" Type="Secondary">Learning & Instruction</JournalSubject>
<JournalSubject Code="O36000" Priority="3" Type="Secondary">Higher Education</JournalSubject>
</JournalSubjectGroup>
</JournalInfo>
<Volume>
<VolumeInfo TocLevels="0" VolumeType="Regular">
<VolumeIDStart>1</VolumeIDStart>
<VolumeIDEnd>1</VolumeIDEnd>
<VolumeIssueCount>2</VolumeIssueCount>
</VolumeInfo>
<Issue IssueType="Regular">
<IssueInfo TocLevels="0">
<IssueIDStart>2</IssueIDStart>
<IssueIDEnd>2</IssueIDEnd>
<IssueArticleCount>7</IssueArticleCount>
<IssueHistory>
<CoverDate>
<DateString>Winter 1990</DateString>
<Year>1990</Year>
<Month>12</Month>
</CoverDate>
</IssueHistory>
<IssueCopyright>
<CopyrightHolderName>Springer</CopyrightHolderName>
<CopyrightYear>1990</CopyrightYear>
</IssueCopyright>
</IssueInfo>
<Article ID="Art1">
<ArticleInfo ArticleType="OriginalPaper" ContainsESM="No" Language="En" NumberingStyle="Unnumbered" TocLevels="0">
<ArticleID>BF02941632</ArticleID>
<ArticleDOI>10.1007/BF02941632</ArticleDOI>
<ArticleSequenceNumber>1</ArticleSequenceNumber>
<ArticleTitle Language="En">What is text, really?</ArticleTitle>
<ArticleFirstPage>3</ArticleFirstPage>
<ArticleLastPage>26</ArticleLastPage>
<ArticleHistory>
<RegistrationDate>
<Year>2008</Year>
<Month>8</Month>
<Day>29</Day>
</RegistrationDate>
</ArticleHistory>
<ArticleCopyright>
<CopyrightHolderName>Springer</CopyrightHolderName>
<CopyrightYear>1990</CopyrightYear>
</ArticleCopyright>
<ArticleGrants Type="Regular">
<MetadataGrant Grant="OpenAccess"></MetadataGrant>
<AbstractGrant Grant="OpenAccess"></AbstractGrant>
<BodyPDFGrant Grant="Restricted"></BodyPDFGrant>
<BodyHTMLGrant Grant="Restricted"></BodyHTMLGrant>
<BibliographyGrant Grant="Restricted"></BibliographyGrant>
<ESMGrant Grant="Restricted"></ESMGrant>
</ArticleGrants>
<ArticleContext>
<JournalID>12528</JournalID>
<VolumeIDStart>1</VolumeIDStart>
<VolumeIDEnd>1</VolumeIDEnd>
<IssueIDStart>2</IssueIDStart>
<IssueIDEnd>2</IssueIDEnd>
</ArticleContext>
</ArticleInfo>
<ArticleHeader>
<AuthorGroup>
<Author AffiliationIDS="Aff1" CorrespondingAffiliationID="Aff1">
<AuthorName DisplayOrder="Western">
<GivenName>Steven</GivenName>
<GivenName>J.</GivenName>
<FamilyName>DeRose</FamilyName>
</AuthorName>
</Author>
<Author AffiliationIDS="Aff2">
<AuthorName DisplayOrder="Western">
<GivenName>David</GivenName>
<GivenName>G.</GivenName>
<FamilyName>Durand</FamilyName>
</AuthorName>
</Author>
<Author AffiliationIDS="Aff3">
<AuthorName DisplayOrder="Western">
<GivenName>Elli</GivenName>
<FamilyName>Mylonas</FamilyName>
</AuthorName>
</Author>
<Author AffiliationIDS="Aff4">
<AuthorName DisplayOrder="Western">
<GivenName>Allen</GivenName>
<GivenName>H.</GivenName>
<FamilyName>Renear</FamilyName>
</AuthorName>
</Author>
<Affiliation ID="Aff1">
<OrgName>praXis</OrgName>
<OrgAddress>
<Country>USA</Country>
</OrgAddress>
</Affiliation>
<Affiliation ID="Aff2">
<OrgName>Brandeis University</OrgName>
<OrgAddress>
<Country>USA</Country>
</OrgAddress>
</Affiliation>
<Affiliation ID="Aff3">
<OrgName>Harvard University</OrgName>
<OrgAddress>
<Country>USA</Country>
</OrgAddress>
</Affiliation>
<Affiliation ID="Aff4">
<OrgName>Brown University</OrgName>
<OrgAddress>
<Country>USA</Country>
</OrgAddress>
</Affiliation>
</AuthorGroup>
<Abstract ID="Abs1" Language="En">
<Heading>Abstract</Heading>
<Para>THE WAY IN WHICH TEXT IS represented on a computer affects the kinds of uses to which it can be put by its creator and by subsequent users. The electronic document model currently in use is impoverished and restrictive. The authors argue that text is best represented as an ordered hierarchy of content object (OHCO), because that is what text really is. This model conforms with emerging standards such as SGML and contains within it advantages for the writer, publisher, and researcher. The authors then describe how the hierarchical model can allow future use and reuse of the document as a database, hypertext, or network.</Para>
</Abstract>
</ArticleHeader>
<NoBody></NoBody>
</Article>
</Issue>
</Volume>
</Journal>
</Publisher>
</istex:document>
</istex:metadataXml>
<mods version="3.6">
<titleInfo lang="en">
<title>What is text, really?</title>
</titleInfo>
<titleInfo type="alternative" contentType="CDATA" lang="en">
<title>What is text, really?</title>
</titleInfo>
<name type="personal" displayLabel="corresp">
<namePart type="given">Steven</namePart>
<namePart type="given">J.</namePart>
<namePart type="family">DeRose</namePart>
<affiliation>praXis, USA</affiliation>
<role>
<roleTerm type="text">author</roleTerm>
</role>
</name>
<name type="personal">
<namePart type="given">David</namePart>
<namePart type="given">G.</namePart>
<namePart type="family">Durand</namePart>
<affiliation>Brandeis University, USA</affiliation>
<role>
<roleTerm type="text">author</roleTerm>
</role>
</name>
<name type="personal">
<namePart type="given">Elli</namePart>
<namePart type="family">Mylonas</namePart>
<affiliation>Harvard University, USA</affiliation>
<role>
<roleTerm type="text">author</roleTerm>
</role>
</name>
<name type="personal">
<namePart type="given">Allen</namePart>
<namePart type="given">H.</namePart>
<namePart type="family">Renear</namePart>
<affiliation>Brown University, USA</affiliation>
<role>
<roleTerm type="text">author</roleTerm>
</role>
</name>
<typeOfResource>text</typeOfResource>
<genre type="research-article" displayLabel="OriginalPaper"></genre>
<originInfo>
<publisher>Springer US</publisher>
<place>
<placeTerm type="text">Boston</placeTerm>
</place>
<dateIssued encoding="w3cdtf">1990-12-01</dateIssued>
<copyrightDate encoding="w3cdtf">1990</copyrightDate>
</originInfo>
<language>
<languageTerm type="code" authority="rfc3066">en</languageTerm>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<physicalDescription>
<internetMediaType>text/html</internetMediaType>
</physicalDescription>
<abstract lang="en">Abstract: THE WAY IN WHICH TEXT IS represented on a computer affects the kinds of uses to which it can be put by its creator and by subsequent users. The electronic document model currently in use is impoverished and restrictive. The authors argue that text is best represented as an ordered hierarchy of content object (OHCO), because that is what text really is. This model conforms with emerging standards such as SGML and contains within it advantages for the writer, publisher, and researcher. The authors then describe how the hierarchical model can allow future use and reuse of the document as a database, hypertext, or network.</abstract>
<relatedItem type="host">
<titleInfo>
<title>Journal of Computing in Higher Education</title>
</titleInfo>
<titleInfo type="abbreviated">
<title>J. Comput. High. Educ.</title>
</titleInfo>
<genre type="journal" displayLabel="Archive Journal"></genre>
<originInfo>
<dateIssued encoding="w3cdtf">1990-12-01</dateIssued>
<copyrightDate encoding="w3cdtf">1990</copyrightDate>
</originInfo>
<subject>
<genre>Journal-Subject-Group</genre>
<topic authority="SpringerSubjectCodes" authorityURI="O">Education</topic>
<topic authority="SpringerSubjectCodes" authorityURI="O21000">Educational Technology</topic>
<topic authority="SpringerSubjectCodes" authorityURI="O22000">Learning & Instruction</topic>
<topic authority="SpringerSubjectCodes" authorityURI="O36000">Higher Education</topic>
</subject>
<identifier type="ISSN">1042-1726</identifier>
<identifier type="JournalID">12528</identifier>
<identifier type="IssueArticleCount">7</identifier>
<identifier type="VolumeIssueCount">2</identifier>
<part>
<date>1990</date>
<detail type="volume">
<number>1</number>
<caption>vol.</caption>
</detail>
<detail type="issue">
<number>2</number>
<caption>no.</caption>
</detail>
<extent unit="pages">
<start>3</start>
<end>26</end>
</extent>
</part>
<recordInfo>
<recordOrigin>Springer, 1990</recordOrigin>
</recordInfo>
</relatedItem>
<identifier type="istex">0261DF9B24207ABDE17B70D0C15901A0384F243B</identifier>
<identifier type="DOI">10.1007/BF02941632</identifier>
<identifier type="ArticleID">BF02941632</identifier>
<identifier type="ArticleID">Art1</identifier>
<accessCondition type="use and reproduction" contentType="copyright">Springer, 1990</accessCondition>
<recordInfo>
<recordContentSource>SPRINGER</recordContentSource>
<recordOrigin>Springer, 1990</recordOrigin>
</recordInfo>
</mods>
</metadata>
<enrichments>
<istex:refBibTEI uri="https://api.istex.fr/document/0261DF9B24207ABDE17B70D0C15901A0384F243B/enrichments/refBib">
<teiHeader></teiHeader>
<text>
<front></front>
<body></body>
<back>
<listBibl>
<biblStruct xml:id="b0">
<monogr>
<title level="m" type="main">Association of American Publishers Reference manual for markup of electronic manuscripts</title>
<imprint>
<date type="published" when="1986"></date>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b1">
<monogr>
<title level="m" type="main">Generalized markup for literary text. Literary and Linguistic Computing</title>
<author>
<persName>
<forename type="first">D</forename>
<forename type="middle">T</forename>
<surname>Barnard</surname>
</persName>
</author>
<author>
<persName>
<forename type="first">A</forename>
<surname>Fraser</surname>
</persName>
</author>
<author>
<persName>
<forename type="first">G</forename>
<surname>Logan</surname>
</persName>
</author>
<imprint>
<date type="published" when="1988"></date>
<biblScope unit="page" from="26" to="31"></biblScope>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b2">
<monogr>
<title level="m" type="main">Why use SGML? Electronic Publishing</title>
<author>
<persName>
<forename type="first">D</forename>
<surname>Barron</surname>
</persName>
</author>
<imprint>
<date type="published" when="1989"></date>
<biblScope unit="page" from="3" to="24"></biblScope>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b3">
<monogr>
<title level="m" type="main">The author's guide to SGML</title>
<author>
<persName>
<forename type="first">M</forename>
<surname>Bryan</surname>
</persName>
</author>
<imprint>
<date type="published" when="1988"></date>
<publisher>Addison-Wesley</publisher>
<pubPlace>New York</pubPlace>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b4">
<analytic>
<title level="a" type="main">Markup systems and the future of scholarly text processing</title>
<author>
<persName>
<forename type="first">J</forename>
<surname>Coombs</surname>
</persName>
</author>
<author>
<persName>
<forename type="first">A</forename>
<surname>Renear</surname>
</persName>
</author>
<author>
<persName>
<forename type="first">S</forename>
<forename type="middle">J</forename>
<surname>Derose</surname>
</persName>
</author>
</analytic>
<monogr>
<title level="j">Communications of the ACM</title>
<imprint>
<biblScope unit="volume">30</biblScope>
<biblScope unit="issue">11</biblScope>
<biblScope unit="page" from="933" to="947"></biblScope>
<date type="published" when="1987"></date>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b5">
<monogr>
<title level="m" type="main">CDWord tutorial</title>
<author>
<persName>
<forename type="first">S</forename>
<forename type="middle">J</forename>
<surname>Derose</surname>
</persName>
</author>
<imprint>
<date type="published" when="1989"></date>
<publisher>Dallas Theological Seminary</publisher>
<pubPlace>Dallas</pubPlace>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b6">
<analytic>
<title level="a" type="main">Searching for information in a hypertext medical handbook</title>
<author>
<persName>
<forename type="first">M</forename>
<surname>Frisse</surname>
</persName>
</author>
</analytic>
<monogr>
<title level="m">Hypertext '87 Proceedings. Chapel Hill</title>
<meeting>
<address>
<addrLine>North Carolina ; New York</addrLine>
</address>
</meeting>
<imprint>
<publisher>ACM</publisher>
<date type="published" when="1987"></date>
<biblScope unit="page" from="57" to="66"></biblScope>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b7">
<analytic>
<title level="a" type="main">A generalized approach to document markup</title>
<author>
<persName>
<forename type="first">C</forename>
<forename type="middle">F</forename>
<surname>Goidfarb</surname>
</persName>
</author>
</analytic>
<monogr>
<title level="j">Proceedings of the ACM SIGPLAN-SIGOA Symposium on Text Manipulation</title>
<imprint>
<publisher>ACM</publisher>
<publisher>ACM</publisher>
<biblScope unit="page" from="68" to="73"></biblScope>
<date type="published" when="1981"></date>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b8">
<analytic>
<title level="a" type="main">Trends and standards in document representation</title>
<author>
<persName>
<forename type="first">V</forename>
<surname>Toloboff</surname>
</persName>
</author>
</analytic>
<monogr>
<title level="m">Text Processing and Document Manipulation</title>
<editor>J.C. Van Vliet 0Ed</editor>
<meeting>
<address>
<addrLine>Cambridge</addrLine>
</address>
</meeting>
<imprint>
<publisher>Cambridge University Press</publisher>
<date type="published" when="1986"></date>
<biblScope unit="page" from="107" to="124"></biblScope>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b9">
<analytic>
<title level="a" type="main">Information Processing-Text and Office Systems-Standard Generalized Markup Language (SGML)</title>
</analytic>
<monogr>
<title level="j">ISO</title>
<imprint>
<date type="published" when="1986"></date>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b10">
<monogr>
<title level="m" type="main">FRESS Resource Manual The Chicago Guide to Preparing Electronic Manuscripts</title>
<author>
<persName>
<forename type="first">J</forename>
<surname>Prusky</surname>
</persName>
</author>
<imprint>
<date type="published" when="1978"></date>
<publisher>Brown University. University of Chicago University of Chicago Press</publisher>
<pubPlace>Chicago</pubPlace>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b11">
<monogr>
<title level="m" type="main">Data liberation, or, Goals for a next generation software application architecture. (forthcoming)</title>
<author>
<persName>
<forename type="first">R</forename>
<surname>Weissman</surname>
</persName>
</author>
<imprint>
<date type="published" when="1990"></date>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b12">
<monogr>
<title level="m" type="main">He has consulted on a variety of projects in computational linguistics, hypermedia, and related fields In 1979 he became director of the FRESS hypertext system project, and most recently has served as a technical writer and design consultant for the CD Word biblical hypertext project . He has published papers on descriptive markup, hypertext, natural language processing, artificial intelligence and other topics. He is now the Senior Scientist at praXis, a RI-based firm developing new services and technologies for large-scale electronic books</title>
<author>
<persName>
<forename type="first">Steven</forename>
<forename type="middle">J</forename>
<surname>Derose</surname>
</persName>
</author>
<imprint>
<date type="published" when="1989"></date>
</imprint>
</monogr>
</biblStruct>
<biblStruct xml:id="b13">
<analytic>
<title level="a" type="main">Since then he has worked for a number of companies in the areas of computer typesetting systems, spelling correction, and operating systems. Currently, he is Manager of Technical Services for Brandeis University Computing Services. He is also serving on the Syntax and Metalanguage Committee of the Text Encoding Intitiative</title>
</analytic>
<monogr>
<title level="m">His research interests include structured text editing interfaces, hypertext systems, and system designs for supporting cooperative work</title>
<imprint>
<date type="published" when="1983"></date>
</imprint>
</monogr>
</biblStruct>
</listBibl>
</back>
</text>
</istex:refBibTEI>
<json:item>
<type>refBibs</type>
<uri>https://api.istex.fr/document/0261DF9B24207ABDE17B70D0C15901A0384F243B/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 000199 | SxmlIndent | more

Ou

HfdSelect -h $EXPLOR_AREA/Data/Istex/Corpus/biblio.hfd -nk 000199 | 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:0261DF9B24207ABDE17B70D0C15901A0384F243B
   |texte=   What is text, really?
}}

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