🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.text.sgml
Article #157

Re: Path Specification in External Entity Declarations

#157
From: Erik Naggum
Date: Wed, 26 Aug 1992 21:27
47 lines
2593 bytes
Eliot Kimber <DRMACRO@RALVM13.VNET.IBM.COM> writes:
|
:
|   For example, say I have an entity reference that resolves to a
|   database query to get the value of IBM stock at the moment the
|   entity is referenced.  Clearly the stock value changes second by
|   second, so a strict reading of ISO 8879 cannot be satisfied because
|   the entity will likely have a different value at every occurrence.

I see nothing in the standard which precludes having entities whose
entity text has different values each time it's referenced.  However,
I also see nothing in the standard which says that the entity manager
is not allowed to cache the entity text, but must access the physical
storage of the entity each time.  In fact, a pretty good case can be
made for requiring entity texts to be static with respect to an
invocation of the parser.

:
|   Note too that SDIF interchange cannot be reliably implemented
|   between systems that have different filesystem structures unless
|   they share a common entity declaration convention.  Such a
|   convention is outside the scope of SGML or SDIF definitions and is
|   thus application-dependent.

Hmmm.  I'm admittedly not very well versed in SDIF, but from my past
couple of readings of the standard, as well as a scan now, it appears
that system identifiers will be assigned by the SDIF unpacker, and not
use the system identifiers of the source environment, just as I'm
assuming in my scheme to resolve public identifiers.  In fact, the note
to definition 4.13 says as much:

4.13 SDIF unpacker:  A program that decomposes an SDIF data stream into
     its constituent entities.

     NOTE -- If necessary, the SDIF unpacker will modify the system
	  identifiers of markup declarations to be consistent with
	  storage addresses in its environment.

So what you said is actually wrong.

Best regards,
</Erik>
--
Erik Naggum             |  ISO  8879 SGML     |      +47 295 0313
                        |  ISO 10744 HyTime   |
<erik@naggum.no>        |  ISO 10646 UCS      |      Memento, terrigena.
<enag@ifi.uio.no>       |  ISO  9899 C        |      Memento, vita brevis.
Technical Details
Message-ID: <23320F@erik.naggum.no>
Path: arc1-ca.pugleaf.net!sparky!uunet!pipex!unipalm!uknet!mcsun!sunic!aun.uninett.no!nuug!ifi.uio.no!SGML
References: <9208242114.AA13720@ucbvax.Berkeley.EDU>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!pipex!unipalm!uknet!mcsun!sunic!aun.uninett.no!nuug!ifi.uio.no!SGML
From: SGML@ifi.uio.no (Erik Naggum)
Newsgroups: comp.text.sgml
Subject: Re: Path Specification in External Entity Declarations
Message-ID: <23320F@erik.naggum.no>
Date: 26 Aug 92 21:27:09 GMT
References: <9208242114.AA13720@ucbvax.Berkeley.EDU>
Organization: Department of Informatics, University of Oslo, Norway
Lines: 42