Non locator use of URIs

NAVIGATION

CATEGORIES

REFERRENCE

If you have some good idea, Cilck and mail to us please...

LINKS

Home » XML

Non locator use of URIs
5 answers - 589 bytes -
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//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
K 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.
No.1 | | 1606 bytes | |
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//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 K 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-F instances: one maps a
local name to a URI string recognized by an XSL-F engine as
representing a particular colour rendering system. Then, in the
XSL-F, one engages the use of a colour system through the local name.

No namespace resolution is at all involved in these distinctions.

. . . . . . . . . . Ken
No.2 | | 1023 bytes | |
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//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
K 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.

SVG feature strings:

/niklas

Niklas Gustavsson
http://www.protocol7.com
mailto:niklas (AT) protocol7 (DOT) com

The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of ASIS <http://www.oasis-open.org>

The list archives are at

To subscribe or unsubscribe from this list use the subscription
manager: <>
No.3 | | 1703 bytes | |
XQuery 1.0 and XPath 2.0 error identifiers are URIs that are not required
(or expected?) to be resolvable.

Hope this helps,
Jim

At 12/24/2005 09:46 AM, 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//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 K
>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.

Jim Melton Editor of IS/IEC 9075-* (SQL) Phone: +1.801.942.0144
Co-Chair, W3C XML Query WG; F& (etc.) editor Fax : +1.801.942.3345
Corporation Email: jim dot melton at oracle dot com
1930 Viscounti Drive Standards email: jim dot melton at acm dot org
Sandy, UT 84093-1063 USA Personal email: jim at melton dot name

= Facts are facts. But any opinions expressed are the opinions =
= only of myself and may or may not reflect the opinions of anybody =
= else with whom I may or may not have discussed the issues at hand. =

The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of ASIS <http://www.oasis-open.org>

The list archives are at

To subscribe or unsubscribe from this list use the subscription
manager: <>
No.4 | | 400 bytes | |
12/25/05, Elliotte Harold <elharo (AT) metalab (DOT) unc.eduwrote:
I'm collecting a list of non-locating, identifying uses of URIs. e.g.
where are URIs used in practice as identifying strings?

This might fit in the SemWeb construct, but in Topic Maps the concept
of PSI (Published Subject Indicator) [persistant identifiers] are
unresolvable URI's.
(#)

Alex
No.5 | | 273 bytes | |
Jim Melton wrote:
XQuery 1.0 and XPath 2.0 error identifiers are URIs that are not
required (or expected?) to be resolvable.
The same is true also for collations in XQuery 1.0/XSLT 2.0.
RELAX NG uses URIs to identify datatype libraries.
Jirka

Re: Non locator use of URIs

EMSDN.COM

Question 'Non locator use of URIs' on 'XML'

XML

Non locator use of URIs