SgmlV1, PascalFrancis, Corpus, bibRecord, 000320

SGML : Show me which road I'm on

Identifieur interne : 000320 ( PascalFrancis/Corpus ); précédent : 000319; suivant : 000321

SGML : Show me which road I'm on

Auteurs : M. Vulpe

Source :

RBID : Pascal:98-0138545

Descripteurs français

Pascal (Inist)
- Langage ordinateur, Description, Historique, Objectif, Application, Langage description donnée, Norme SGML.

English descriptors

KwdEn :
- Application, Case history, Computer language, Data description language, Description, Objective, SGML standard.

Abstract

The promise of SGML is that if you separate form from content, a miracle occurs. Data integrity is preserved across platforms, applications, and soup recipes. The reality is a return to the bad old days of proprietary hardwired solutions. Appreciating what SGML brings to the table requires an understanding both of its origins and of its characteristics. SGML is not what it appears to beat first glance. In this paper, well look at: where SGML came from; how a business case can (or cannot) be made for SGML ; what alternatives exist today; attempts to "fix" SGML, to make it address today's problems; and how SGML can be rescued from obscurity by the redefining of its role.

Notice en format standard (ISO 2709)

Pour connaître la documentation sur le format Inist Standard.

A08	`01`	`1`	`ENG`	`@1 SGML : Show me which road I'm on`
A09	`01`	`1`	`ENG`	`@1 Museums and the Web : Los Angeles CA, March 1997, selected papers`
A11	`01`	`1`		`@1 VULPE (M.)`
A12	`01`	`1`		`@1 BEARMAN (David) @9 ed.`
A12	`02`	`1`		`@1 TRANT (Jennifer) @9 ed.`
A14	`01`			`@1 Infrastructures for Information Inc. @2 Toronto @3 CAN @Z 1 aut.`
A20				`@1 235-241`
A21				`@1 1997`
A23	`01`			`@0 ENG`
A25	`01`			`@1 Archives & Museum Informatics @2 Pittsburgh PA`
A26	`01`			`@0 1-885626-13-4`
A30	`01`	`1`	`ENG`	`@1 Museums and the Web. Conference @2 1 @3 Los Angeles CA USA @4 1997-03`
A43	`01`			`@1 INIST @2 Y 31732 @5 354000077547580200`
A44				`@0 0000 @1 © 1998 INIST-CNRS. All rights reserved.`
A45				`@0 8 ref.`
A47	`01`	`1`		`@0 98-0138545`
A60				`@1 C`
A61				`@0 A`
A66	`01`			`@0 USA`
C01	`01`		`ENG`	@0 The promise of SGML is that if you separate form from content, a miracle occurs. Data integrity is preserved across platforms, applications, and soup recipes. The reality is a return to the bad old days of proprietary hardwired solutions. Appreciating what SGML brings to the table requires an understanding both of its origins and of its characteristics. SGML is not what it appears to beat first glance. In this paper, well look at: where SGML came from; how a business case can (or cannot) be made for SGML ; what alternatives exist today; attempts to "fix" SGML, to make it address today's problems; and how SGML can be rescued from obscurity by the redefining of its role.
C02	`01`	`X`		`@0 001A01G02A`
C02	`02`	`X`		`@0 205`
C03	`01`	`X`	`FRE`	`@0 Langage ordinateur @5 01`
C03	`01`	`X`	`ENG`	`@0 Computer language @5 01`
C03	`01`	`X`	`SPA`	`@0 Lenguaje computadora @5 01`
C03	`02`	`X`	`FRE`	`@0 Description @5 02`
C03	`02`	`X`	`ENG`	`@0 Description @5 02`
C03	`02`	`X`	`GER`	`@0 Beschreibung @5 02`
C03	`02`	`X`	`SPA`	`@0 Descripción @5 02`
C03	`03`	`X`	`FRE`	`@0 Historique @5 03`
C03	`03`	`X`	`ENG`	`@0 Case history @5 03`
C03	`03`	`X`	`GER`	`@0 Entwicklungsgeschichte @5 03`
C03	`03`	`X`	`SPA`	`@0 Histórica @5 03`
C03	`04`	`X`	`FRE`	`@0 Objectif @5 04`
C03	`04`	`X`	`ENG`	`@0 Objective @5 04`
C03	`04`	`X`	`SPA`	`@0 Objetivo @5 04`
C03	`05`	`X`	`FRE`	`@0 Application @5 05`
C03	`05`	`X`	`ENG`	`@0 Application @5 05`
C03	`05`	`X`	`GER`	`@0 Anwendung @5 05`
C03	`05`	`X`	`SPA`	`@0 Aplicación @5 05`
C03	`06`	`X`	`FRE`	`@0 Langage description donnée @5 06`
C03	`06`	`X`	`ENG`	`@0 Data description language @5 06`
C03	`06`	`X`	`SPA`	`@0 Lenguaje descripción dato @5 06`
C03	`07`	`X`	`FRE`	`@0 Norme SGML @4 CD @5 96`
C03	`07`	`X`	`ENG`	`@0 SGML standard @4 CD @5 96`
N21				`@1 089`

Format Inist (serveur)

NO :	PASCAL 98-0138545 INIST
ET :	SGML : Show me which road I'm on
AU :	VULPE (M.); BEARMAN (David); TRANT (Jennifer)
AF :	Infrastructures for Information Inc./Toronto/Canada (1 aut.)
DT :	Congrès; Niveau analytique
SO :	Museums and the Web. Conference/1/1997-03/Los Angeles CA USA; Etats-Unis; Pittsburgh PA: Archives & Museum Informatics; Da. 1997; Pp. 235-241; ISBN 1-885626-13-4
LA :	Anglais
EA :	The promise of SGML is that if you separate form from content, a miracle occurs. Data integrity is preserved across platforms, applications, and soup recipes. The reality is a return to the bad old days of proprietary hardwired solutions. Appreciating what SGML brings to the table requires an understanding both of its origins and of its characteristics. SGML is not what it appears to beat first glance. In this paper, well look at: where SGML came from; how a business case can (or cannot) be made for SGML ; what alternatives exist today; attempts to "fix" SGML, to make it address today's problems; and how SGML can be rescued from obscurity by the redefining of its role.
CC :	001A01G02A; 205
FD :	Langage ordinateur; Description; Historique; Objectif; Application; Langage description donnée; Norme SGML
ED :	Computer language; Description; Case history; Objective; Application; Data description language; SGML standard
GD :	Beschreibung; Entwicklungsgeschichte; Anwendung
SD :	Lenguaje computadora; Descripción; Histórica; Objetivo; Aplicación; Lenguaje descripción dato
LO :	INIST-Y 31732.354000077547580200
ID :	98-0138545

Links to Exploration step

Pascal:98-0138545

Le document en format XML

<record><TEI><teiHeader><fileDesc><titleStmt><title xml:lang="en" level="a">SGML : Show me which road I'm on</title>
<author><name sortKey="Vulpe, M" sort="Vulpe, M" uniqKey="Vulpe M" first="M." last="Vulpe">M. Vulpe</name>
<affiliation><inist:fA14 i1="01"><s1>Infrastructures for Information Inc.</s1>
<s2>Toronto</s2>
<s3>CAN</s3>
<sZ>1 aut.</sZ>
</inist:fA14>
</affiliation>
</author>
</titleStmt>
<publicationStmt><idno type="wicri:source">INIST</idno>
<idno type="inist">98-0138545</idno>
<date when="1997">1997</date>
<idno type="stanalyst">PASCAL 98-0138545 INIST</idno>
<idno type="RBID">Pascal:98-0138545</idno>
<idno type="wicri:Area/PascalFrancis/Corpus">000320</idno>
</publicationStmt>
<sourceDesc><biblStruct><analytic><title xml:lang="en" level="a">SGML : Show me which road I'm on</title>
<author><name sortKey="Vulpe, M" sort="Vulpe, M" uniqKey="Vulpe M" first="M." last="Vulpe">M. Vulpe</name>
<affiliation><inist:fA14 i1="01"><s1>Infrastructures for Information Inc.</s1>
<s2>Toronto</s2>
<s3>CAN</s3>
<sZ>1 aut.</sZ>
</inist:fA14>
</affiliation>
</author>
</analytic>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc><textClass><keywords scheme="KwdEn" xml:lang="en"><term>Application</term>
<term>Case history</term>
<term>Computer language</term>
<term>Data description language</term>
<term>Description</term>
<term>Objective</term>
<term>SGML standard</term>
</keywords>
<keywords scheme="Pascal" xml:lang="fr"><term>Langage ordinateur</term>
<term>Description</term>
<term>Historique</term>
<term>Objectif</term>
<term>Application</term>
<term>Langage description donnée</term>
<term>Norme SGML</term>
</keywords>
</textClass>
</profileDesc>
</teiHeader>
<front><div type="abstract" xml:lang="en">The promise of SGML is that if you separate form from content, a miracle occurs. Data integrity is preserved across platforms, applications, and soup recipes. The reality is a return to the bad old days of proprietary hardwired solutions. Appreciating what SGML brings to the table requires an understanding both of its origins and of its characteristics. SGML is not what it appears to beat first glance. In this paper, well look at: where SGML came from; how a business case can (or cannot) be made for SGML ; what alternatives exist today; attempts to "fix" SGML, to make it address today's problems; and how SGML can be rescued from obscurity by the redefining of its role.</div>
</front>
</TEI>
<inist><standard h6="B"><pA><fA08 i1="01" i2="1" l="ENG"><s1>SGML : Show me which road I'm on</s1>
</fA08>
<fA09 i1="01" i2="1" l="ENG"><s1>Museums and the Web : Los Angeles CA, March 1997, selected papers</s1>
</fA09>
<fA11 i1="01" i2="1"><s1>VULPE (M.)</s1>
</fA11>
<fA12 i1="01" i2="1"><s1>BEARMAN (David)</s1>
<s9>ed.</s9>
</fA12>
<fA12 i1="02" i2="1"><s1>TRANT (Jennifer)</s1>
<s9>ed.</s9>
</fA12>
<fA14 i1="01"><s1>Infrastructures for Information Inc.</s1>
<s2>Toronto</s2>
<s3>CAN</s3>
<sZ>1 aut.</sZ>
</fA14>
<fA20><s1>235-241</s1>
</fA20>
<fA21><s1>1997</s1>
</fA21>
<fA23 i1="01"><s0>ENG</s0>
</fA23>
<fA25 i1="01"><s1>Archives & Museum Informatics</s1>
<s2>Pittsburgh PA</s2>
</fA25>
<fA26 i1="01"><s0>1-885626-13-4</s0>
</fA26>
<fA30 i1="01" i2="1" l="ENG"><s1>Museums and the Web. Conference</s1>
<s2>1</s2>
<s3>Los Angeles CA USA</s3>
<s4>1997-03</s4>
</fA30>
<fA43 i1="01"><s1>INIST</s1>
<s2>Y 31732</s2>
<s5>354000077547580200</s5>
</fA43>
<fA44><s0>0000</s0>
<s1>© 1998 INIST-CNRS. All rights reserved.</s1>
</fA44>
<fA45><s0>8 ref.</s0>
</fA45>
<fA47 i1="01" i2="1"><s0>98-0138545</s0>
</fA47>
<fA60><s1>C</s1>
</fA60>
<fA61><s0>A</s0>
</fA61>
<fA66 i1="01"><s0>USA</s0>
</fA66>
<fC01 i1="01" l="ENG"><s0>The promise of SGML is that if you separate form from content, a miracle occurs. Data integrity is preserved across platforms, applications, and soup recipes. The reality is a return to the bad old days of proprietary hardwired solutions. Appreciating what SGML brings to the table requires an understanding both of its origins and of its characteristics. SGML is not what it appears to beat first glance. In this paper, well look at: where SGML came from; how a business case can (or cannot) be made for SGML ; what alternatives exist today; attempts to "fix" SGML, to make it address today's problems; and how SGML can be rescued from obscurity by the redefining of its role.</s0>
</fC01>
<fC02 i1="01" i2="X"><s0>001A01G02A</s0>
</fC02>
<fC02 i1="02" i2="X"><s0>205</s0>
</fC02>
<fC03 i1="01" i2="X" l="FRE"><s0>Langage ordinateur</s0>
<s5>01</s5>
</fC03>
<fC03 i1="01" i2="X" l="ENG"><s0>Computer language</s0>
<s5>01</s5>
</fC03>
<fC03 i1="01" i2="X" l="SPA"><s0>Lenguaje computadora</s0>
<s5>01</s5>
</fC03>
<fC03 i1="02" i2="X" l="FRE"><s0>Description</s0>
<s5>02</s5>
</fC03>
<fC03 i1="02" i2="X" l="ENG"><s0>Description</s0>
<s5>02</s5>
</fC03>
<fC03 i1="02" i2="X" l="GER"><s0>Beschreibung</s0>
<s5>02</s5>
</fC03>
<fC03 i1="02" i2="X" l="SPA"><s0>Descripción</s0>
<s5>02</s5>
</fC03>
<fC03 i1="03" i2="X" l="FRE"><s0>Historique</s0>
<s5>03</s5>
</fC03>
<fC03 i1="03" i2="X" l="ENG"><s0>Case history</s0>
<s5>03</s5>
</fC03>
<fC03 i1="03" i2="X" l="GER"><s0>Entwicklungsgeschichte</s0>
<s5>03</s5>
</fC03>
<fC03 i1="03" i2="X" l="SPA"><s0>Histórica</s0>
<s5>03</s5>
</fC03>
<fC03 i1="04" i2="X" l="FRE"><s0>Objectif</s0>
<s5>04</s5>
</fC03>
<fC03 i1="04" i2="X" l="ENG"><s0>Objective</s0>
<s5>04</s5>
</fC03>
<fC03 i1="04" i2="X" l="SPA"><s0>Objetivo</s0>
<s5>04</s5>
</fC03>
<fC03 i1="05" i2="X" l="FRE"><s0>Application</s0>
<s5>05</s5>
</fC03>
<fC03 i1="05" i2="X" l="ENG"><s0>Application</s0>
<s5>05</s5>
</fC03>
<fC03 i1="05" i2="X" l="GER"><s0>Anwendung</s0>
<s5>05</s5>
</fC03>
<fC03 i1="05" i2="X" l="SPA"><s0>Aplicación</s0>
<s5>05</s5>
</fC03>
<fC03 i1="06" i2="X" l="FRE"><s0>Langage description donnée</s0>
<s5>06</s5>
</fC03>
<fC03 i1="06" i2="X" l="ENG"><s0>Data description language</s0>
<s5>06</s5>
</fC03>
<fC03 i1="06" i2="X" l="SPA"><s0>Lenguaje descripción dato</s0>
<s5>06</s5>
</fC03>
<fC03 i1="07" i2="X" l="FRE"><s0>Norme SGML</s0>
<s4>CD</s4>
<s5>96</s5>
</fC03>
<fC03 i1="07" i2="X" l="ENG"><s0>SGML standard</s0>
<s4>CD</s4>
<s5>96</s5>
</fC03>
<fN21><s1>089</s1>
</fN21>
</pA>
</standard>
<server><NO>PASCAL 98-0138545 INIST</NO>
<ET>SGML : Show me which road I'm on</ET>
<AU>VULPE (M.); BEARMAN (David); TRANT (Jennifer)</AU>
<AF>Infrastructures for Information Inc./Toronto/Canada (1 aut.)</AF>
<DT>Congrès; Niveau analytique</DT>
<SO>Museums and the Web. Conference/1/1997-03/Los Angeles CA USA; Etats-Unis; Pittsburgh PA: Archives & Museum Informatics; Da. 1997; Pp. 235-241; ISBN 1-885626-13-4</SO>
<LA>Anglais</LA>
<EA>The promise of SGML is that if you separate form from content, a miracle occurs. Data integrity is preserved across platforms, applications, and soup recipes. The reality is a return to the bad old days of proprietary hardwired solutions. Appreciating what SGML brings to the table requires an understanding both of its origins and of its characteristics. SGML is not what it appears to beat first glance. In this paper, well look at: where SGML came from; how a business case can (or cannot) be made for SGML ; what alternatives exist today; attempts to "fix" SGML, to make it address today's problems; and how SGML can be rescued from obscurity by the redefining of its role.</EA>
<CC>001A01G02A; 205</CC>
<FD>Langage ordinateur; Description; Historique; Objectif; Application; Langage description donnée; Norme SGML</FD>
<ED>Computer language; Description; Case history; Objective; Application; Data description language; SGML standard</ED>
<GD>Beschreibung; Entwicklungsgeschichte; Anwendung</GD>
<SD>Lenguaje computadora; Descripción; Histórica; Objetivo; Aplicación; Lenguaje descripción dato</SD>
<LO>INIST-Y 31732.354000077547580200</LO>
<ID>98-0138545</ID>
</server>
</inist>
</record>

Pour manipuler ce document sous Unix (Dilib)

EXPLOR_STEP=$WICRI_ROOT/Wicri/Informatique/explor/SgmlV1/Data/PascalFrancis/Corpus

HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000320 | SxmlIndent | more

HfdSelect -h $EXPLOR_AREA/Data/PascalFrancis/Corpus/biblio.hfd -nk 000320 | SxmlIndent | more

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

{{Explor lien
   |wiki=    Wicri/Informatique
   |area=    SgmlV1
   |flux=    PascalFrancis
   |étape=   Corpus
   |type=    RBID
   |clé=     Pascal:98-0138545
   |texte=   SGML : Show me which road I'm on
}}

This area was generated with Dilib version V0.6.33.
Data generation: Mon Jul 1 14:26:08 2019. Site generation: Wed Apr 28 21:40:44 2021

	Serveur d'exploration sur SGML
	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.

Serveur d'exploration sur SGML

SGML : Show me which road I'm on

SGML : Show me which road I'm on

Source :

Descripteurs français

English descriptors

Abstract

Notice en format standard (ISO 2709)

Format Inist (serveur)

Links to Exploration step

Le document en format XML

Pour manipuler ce document sous Unix (Dilib)

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