[
Lists Home |
Date Index |
Thread Index
]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
/ "Bullard, Claude L (Len)" <clbullar@ingr.com> was heard to say:
| Yes, there are implementations that map PUBLIC identifiers to
| web identifiers. For them that needs 'em, use 'em. OTW, not.
XML Catalogs, for example. And vice versa, RFC 3151 for example.
| If you are using the web as your mass storage device, you
| don't need public identifiers for much if anything although
| they are still used in DOCTYPE declarations.
One of the nice features of DOCTYPE declarations that I haven't seen
mentioned very often is the fact that they allow you to specify both
a name and an address. So Joe User sends me
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"file:///c:/path/to/some/place/docbookx.dtd">
and it *just works* on my machine because I can map from the public
identifier to a local identifier.
<!DOCTYPE article SYSTEM "file:///c:/path/to/some/place/docbookx.dtd">
is just about useless on anyone's system except Joe User's. As is
<article xsi:schemaLocation="file:///c:/path/to/some/place/docbookx.xsd">
but, alas, there's no obvious way to specify the public identifier in XSD.
You can use RFC 3151, but no one does.
Be seeing you,
norm
- --
Norman.Walsh@Sun.COM | On the other hand, you have different fingers.
XML Standards Architect |
Web Tech. and Standards |
Sun Microsystems, Inc. |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>
iD8DBQE/KRfnOyltUcwYWjsRAri+AJ9WNP8eudpEx2DitOQhtX6HkdwsQgCffre9
wDt86NvYNvH2mn17nrzz9ZU=
=iV99
-----END PGP SIGNATURE-----
|
