RE: [xri] Update to Metadata Issue #1: Add $t Tag for Identifier Metadata

["Drummond Reed" <drummond.reed@cordance.net>]

Marty,

Excellent point. I'm surprised I didn't see the parallel earlier myself.

This should make the job of crafting a proposed draft of the $t text much
easier since we can just use $l as a template. The only difference is that
we don't yet have a spec to point to, so we have to explain that we're
delegating to another XRI TC spec. I'd propose to call that the XRI
Identifier Type Specification.

=Drummond 

-----Original Message-----
From: Schleiff, Marty [mailto:marty.schleiff@boeing.com] 
Sent: Friday, September 23, 2005 11:49 AM
To: xri@lists.oasis-open.org
Subject: RE: [xri] Update to Metadata Issue #1: Add $t Tag for Identifier
Metadata

Hi All,

I'm kicking myself now because I didn't think of saying the following
during the conference call. I hope it clarifies.

There is good precedent for the $t proposal in the exising $l metadata
tag:

The valid language tags that can immediately follow $l are described in
another spec. The valid identifier type values that could immediately
follow $t would be listed in another specification.

The namespace of language tags is administered by IANA. The namespace of
identifier types would be administered by an appropriate authority.

The language tags inform the consuming application how the XRI, or
sub-segment of the XRI, is intended to be understood, interpreted, or
pronounced. The identifier type values would inform a consuming
application how the XRI, or sub-segment of the XRI, should be processed,
normalized, checked for equivalence, resolved, etc.

The spec says $l language tags are significant in XRI resolution. Dave
says the $t identifier types would be significant to resolution.

Hope this helps.

Marty.Schleiff@boeing.com; CISSP
Associate Technical Fellow - Cyber Identity Specialist
Computing Security Infrastructure
(425) 957-5667

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php