docstring-develop — Project development discussions.

[Docstring-develop] CVS: dps HISTORY.txt,1.1.1.1,1.2

[David G. <go...@us...>]

Update of /cvsroot/docstring/dps
In directory usw-pr-cvs1:/tmp/cvs-serv14101/dps

Modified Files:
	HISTORY.txt 
Log Message:
brought up to date

Index: HISTORY.txt
===================================================================
RCS file: /cvsroot/docstring/dps/HISTORY.txt,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** HISTORY.txt	2001/07/22 22:36:34	1.1.1.1
--- HISTORY.txt	2001/07/29 15:55:48	1.2
***************
*** 9,12 ****
--- 9,20 ----
  
  
+ Release 0.4? (pending)
+ ========================
+ 
+ * spec/gdpi.dtd: Fixed typos & omissions; now validates.
+ 
+ * spec/pdpi.dtd: Fixed typos; now validates.
+ 
+ 
  Release 0.3 (2001-07-19)
  ========================
***************
*** 102,110 ****
  
      David Ascher, Fred Drake, Jim Fulton, Peter Funk, Doug Hellmann,
!     Juergen Hermann, Tony Ibbs, Daniel Larsson, Marc-Andre Lemburg,
!     Wolfgang Lipp, Edward Loper, Ken Manheimer, Michel Pelletier, Sam
!     Penrose, Tim Peters, Tavis Rudd, Bob Tolbert, Laurence Tratt,
!     Guido van Rossum, Barry Warsaw, Edward Welbourne, Ka-Ping Yee,
!     Moshe Zadka
  
  (I'm still waiting for contributions of tasty snacks, computer
--- 110,118 ----
  
      David Ascher, Fred Drake, Jim Fulton, Peter Funk, Doug Hellmann,
!     Juergen Hermann, Tony Ibbs, Garth Kidd, Daniel Larsson, Marc-Andre
!     Lemburg, Wolfgang Lipp, Edward Loper, Ken Manheimer, Michel
!     Pelletier, Sam Penrose, Tim Peters, Tavis Rudd, Bob Tolbert,
!     Laurence Tratt, Guido van Rossum, Barry Warsaw, Edward Welbourne,
!     Ka-Ping Yee, Moshe Zadka
  
  (I'm still waiting for contributions of tasty snacks, computer

RE: [Docstring-develop] DTD patches

[Garth T K. <ga...@de...>]

>> I've looked into it a little more. From my `reading`_, system
>> identifiers are compulsory::
>
> Thanks for your research. Please go ahead with the system identifiers.

Done. I've also closed tracker items #444342, #444347, and #444348.

> Yet *another* difference between XML and SGML.

I don't know enough about either to really comment. :)

Regards,
Garth.

Re: [Docstring-develop] DTD patches

[David G. <dgo...@bi...>]

> I've looked into it a little more. From my `reading`_, system
> identifiers are compulsory::

Thanks for your research. Please go ahead with the system identifiers.

Yet *another* difference between XML and SGML.

RE: [Docstring-develop] DTD patches

[Garth T K. <ga...@de...>]

>> I'd rather *not* put system identifiers in the DTDs themselves.

I've looked into it a little more. From my `reading`_, system
identifiers are compulsory::

  External Entity Declaration
  [75]    ExternalID    ::=    'SYSTEM' S SystemLiteral
                             | 'PUBLIC' S PubidLiteral S SystemLiteral

.. _reading: http://www.w3.org/TR/2000/REC-xml-20001006#dt-extent

We've got to give it a URI reference of some sort. Giving the http URL
of the DTD doesn't make sense (otherwise we'd have to update the web
site to test changes), so ``"gpdi.dtd"`` et al look like our only hope.
What am I missing?

<rummage rummage>

It looks like SystemLiteral has been compulsory since `March 1997`_::

  5. Should production 69 (external ID) be changed to make the
     SystemLiteral optional?

     Unanimous: leave it required.

.. _March 1997:
http://lists.w3.org/Archives/Public/w3c-sgml-wg/1997Mar/0446.html

It looks like there are other times when SystemLiterals are optional
(for example, when specifying a NOTATION declaration in RDF), and that
makes sense to me -- an RDF parser can't necessarily depend on having
either net access or a copy of any DTD someone happens to refer to.

In a DTD, though, the parser *must* be able to get hold of the external
DTD to which you're referring otherwise it can't validate the XML being
handed to it, hence SystemLiteral's compulsory nature. Not all parsers
will know how to look up all PubidLiterals, so we need the SystemLiteral
as a backup.

There was an awful lot of thrash in the mailing list about the decision
to make SystemLiterals compulsory. Having read a fair bit, I can see
why -- they got so confused about the Moby Dick analogy that nobody
could see beyond the cloud of dust. :) That said, three years after the
thrash the spec still reads as above.

Regards,
Garth.

RE: [Docstring-develop] DTD patches

[Garth T K. <ga...@de...>]

> I've set up syncmail for this one too (but not executable either :-(;
> could you put in a support request for me please?).

Done.

> > Shall I check my DTD patches into docstring?
>
> You guessed it, I never validated the DTDs.

Ha! Sprung!

> They were just my notes for the element hierarchy. But it would be
> nice if they worked :-).

It'd certainly help with validating editors.

> All: Can XMLSpy use the dps.cat catalog file to resolve
> public entities?

I wish.

> I'd rather *not* put system identifiers in the DTDs themselves.

Is it such a pain if we're only putting in pathless identifiers?
``c:\this\that\gpdi.dtd`` would be criminal. ``gpdi.dtd`` by itself
seems harmless enough.

> #444342: The DTD is soextblx.dtd (the name does have
> meaning); mapped in dps.cat. No fixes should be necessary.

Aah, so I should make the local mapping ``soextblx.dtd``. If I correct
it.

> #444347 & #444348: Good catch on the typos.

Ta.

> Apart from the PUBLIC identifiers (see above), please do check in
> the fixes.

Done.

> BTW, did you add the "Interface (example)" bug category?

I think that's a default.

> (If you're keen, please add: documentation, specification, tests,
> DPS code. To Bugs & Patches. And default them to be assigned to
> me. [If I'm being too cheeky, please ignore.])

You'll need to give me permissions for tracker management, but I'm happy
to do it. Just call me Igor. :)

Regards,
Garth.

[Docstring-develop] DTD patches

[David G. <dgo...@bi...>]

Time to subscribe to another list! :-) I've set up syncmail for this one too
(but not executable either :-(; could you put in a support request for me
please?).

    http://lists.sourceforge.net/lists/listinfo/docstring-develop

> Shall I check my DTD patches into docstring?

You guessed it, I never validated the DTDs. They were just my notes for the
element hierarchy. But it would be nice if they worked :-).

Bugs:

All: Can XMLSpy use the dps.cat catalog file to resolve public entities? The
PUBLIC -> system identifier mappings for the DTD components are all in
there. I'd rather *not* put system identifiers in the DTDs themselves.

#444342: The DTD is soextblx.dtd (the name does have meaning); mapped in
dps.cat. No fixes should be necessary.

#444347 & #444348: Good catch on the typos. Apart from the PUBLIC
identifiers (see above), please do check in the fixes.

BTW, did you add the "Interface (example)" bug category? If so, what does it
mean? (If you're keen, please add: documentation, specification, tests, DPS
code. To Bugs & Patches. And default them to be assigned to me. [If I'm
being too cheeky, please ignore.])

Thanks.

David