Exploration
Accueil
Racine
Exploration
Accueil
Racine

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.

SGML : Show me which road I'm on

Identifieur interne : 002866 ( Main/Exploration ); précédent : 002865; suivant : 002867

SGML : Show me which road I'm on

Auteurs : M. Vulpe [Canada]

Source :

RBID : Pascal:98-0138545

Descripteurs français

English descriptors

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.


Affiliations:

Links toward previous steps (curation, corpus...)

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 wicri:level="1">
<inist:fA14 i1="01">
<s1>Infrastructures for Information Inc.</s1>
<s2>Toronto</s2>
<s3>CAN</s3>
<sZ>1 aut.</sZ>
</inist:fA14>
<country>Canada</country>
<wicri:noRegion>Infrastructures for Information Inc.</wicri:noRegion>
</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>
<idno type="wicri:Area/PascalFrancis/Curation">000499</idno>
<idno type="wicri:Area/PascalFrancis/Checkpoint">000324</idno>
<idno type="wicri:explorRef" wicri:stream="PascalFrancis" wicri:step="Checkpoint">000324</idno>
<idno type="wicri:Area/Main/Merge">002999</idno>
<idno type="wicri:Area/Main/Curation">002866</idno>
<idno type="wicri:Area/Main/Exploration">002866</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 wicri:level="1">
<inist:fA14 i1="01">
<s1>Infrastructures for Information Inc.</s1>
<s2>Toronto</s2>
<s3>CAN</s3>
<sZ>1 aut.</sZ>
</inist:fA14>
<country>Canada</country>
<wicri:noRegion>Infrastructures for Information Inc.</wicri:noRegion>
</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>
<keywords scheme="Wicri" type="topic" xml:lang="fr">
<term>Historique</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>
<affiliations>
<list>
<country>
<li>Canada</li>
</country>
</list>
<tree>
<country name="Canada">
<noRegion>
<name sortKey="Vulpe, M" sort="Vulpe, M" uniqKey="Vulpe M" first="M." last="Vulpe">M. Vulpe</name>
</noRegion>
</country>
</tree>
</affiliations>
</record>

Pour manipuler ce document sous Unix (Dilib)

EXPLOR_STEP=$WICRI_ROOT/Wicri/Informatique/explor/SgmlV1/Data/Main/Exploration

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

Ou

HfdSelect -h $EXPLOR_AREA/Data/Main/Exploration/biblio.hfd -nk 002866 | SxmlIndent | more

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

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

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