[
Lists Home |
Date Index |
Thread Index
]
At 2005-12-24 11:46 -0500, Elliotte Harold wrote:
>I'm collecting a list of non-locating, identifying uses of URIs.
>e.g. where are URIs used in practice as identifying strings? So far I have:
>
>XML Namespaces
>SAX Feature and Properties
>Atom IDs
>RDF/Owl/SemWeb
>XML encryption data types and algorithms
>XML canonicalization algorithms
>
>Can anyone add to this list? The criterion is that the URI is not
>necessarily resolvable, and not intended primarily to be resolved.
>It's OK is some can be (e.g. RDDL documents for XML namespaces) as
>long as it doesn't have to be to serve its main function.
(1) To qualify the top-level constructs of XSLT stylesheets: every
named user stylesheet construct in XSLT is a namespace-qualified
name, though most people use no namespace for these names. It is
important in top-level constructs to use namespace qualification when
using the import tree to pull in many stylesheet fragments from
different development teams. To ensure no unintended name conflicts
you want to isolate the top-level constructs with unique namespace URI strings.
(2) To identify colour profiles in XSL-FO instances: one maps a
local name to a URI string recognized by an XSL-FO engine as
representing a particular colour rendering system. Then, in the
XSL-FO, one engages the use of a colour system through the local name.
No namespace resolution is at all involved in these distinctions.
. . . . . . . . . . . Ken
--
Upcoming XSLT/XSL-FO hands-on courses: Denver,CO March 13-17,2006
World-wide on-site corporate, govt. & user group XML/XSL training.
G. Ken Holman mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/
Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05 http://www.CraneSoftwrights.com/x/bc
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
|
