OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] The purpose of a namespace URI is ...

Liam R E Quin scripsit:

> But I'm not convinced: public identifiers need indirection, and if you
> have indirection you can ue indirection for the system identifiers too.

You were there and I was not, but what I understood was that public ids
were absolute names and system ids were meaningful to the current process.
So given a URI as a public id, you could dereference it if no system id
was present, or you could make use of the system id to find a specific
copy of it.  So an XHTML DOCTYPE might look like any of these:

<!DOCTYPE html SYSTEM "../dtds/mini-html.dtd">

<!DOCTYPE html PUBLIC "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

> The contribution of public ids was their structure, and the idea of
> giving something a name, not the fact that they didn't actually work :-)

*Formal* public ids have a structure, but public ids didn't have to
be formal.

John Cowan      cowan@ccil.org         http://www.ccil.org/~cowan
Statistics don't help a great deal in making important decisions.
Most people have more than the average number of feet, but I'm not about
to start a company selling shoes in threes. --Ross Gardler

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS