[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: How did "public identifier" get its name...

• To: xml-dev@l...
• Subject: Re: How did "public identifier" get its name...
• From: Norman Walsh <ndw@n...>
• Date: Thu, 31 Jul 2003 09:21:43 -0400
• In-reply-to: <15725CF6AFE2F34DB8A5B4770B7334EE022DC5D2@h...> (ClaudeL. Bullard's message of "Fri, 18 Jul 2003 11:02:19 -0500")
• References: <15725CF6AFE2F34DB8A5B4770B7334EE022DC5D2@h...>
• User-agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3 (gnu/linux)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

/ "Bullard, Claude L (Len)" <clbullar@i...> 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@S...    | 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-----

• References:
  • RE: How did "public identifier" get its name...
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: Re: Defining non-WXS datatypes
• Next by Date: RE: URN vs URL
• Previous by thread: RE: How did "public identifier" get its name...
• Next by thread: RE: How did "public identifier" get its name...
• Index(es):
  • Date
  • Thread