FW: [xri] Special XRI TC call on IRI Normalization 5pm Pacific Tuesday 9/13

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

A reminder of the call being held now. See the end of this message for
call-in details.

For reference during the call, below is an excerpt of section 2.3.1 of the
current XRI Syntax 2.0 Committee Draft 01 that will be discussed on the
call.

=Drummond 

***START***

2.3.1 Transforming XRI References into IRI and URI References
Although XRIs are intended to be used by applications that understand them
natively, it may also be desirable to use them in contexts that do not
recognize an XRI reference but that allow an Internationalized Resource
Identifier reference as described in [IRI], or a fully-conformant URI
reference as defined by [URI]. 

This section specifies the steps for transforming an XRI reference into a
valid IRI reference. At the completion of these steps, the XRI reference is
in IRI-Normal Form. An XRI reference in IRI-Normal Form may then be mapped
into a valid URI reference by following the algorithms defined in section
3.1 of [IRI]. After that mapping, the XRI reference is in URI-Normal Form.
Applications MUST transform XRI references to IRI references using the
following steps (or a process that achieves exactly the same result). Before
applying these steps, the XRI reference must be in XRI-normal form as
defined in section 2.1.4.

1.	If the XRI reference is not encoded in UTF-8, convert the XRI
reference to a sequence of characters encoded in UTF-8, normalized according
to Normalization Form C (NFC) as defined in [UTR15].

2.	If the XRI reference is not relative (i.e., if it matches the "XRI"
ABNF production) and the optional "xri://" prefix has been omitted, prepend
"xri://" to the XRI reference.

3.	Optionally add XRI metadata using cross-references as defined in
section 2.1.4.1. Note that the addition of XRI metadata may change the
resulting IRI or URI reference for the purposes of comparison. The
significance or insignificance of specific types of XRI metadata is
specified in Extensible Resource Identifier (XRI) Metadata V2.0
[XRIMetadata].

4.	Apply the XRI escaping rules defined in section 2.3.2. Note that
this step is not idempotent (i.e., it may yield a different result if
applied more than once), so it is very important that implementers not apply
this step more than once to avoid changing the semantics of the identifier.
At the completion of step 4, the percent-encoded XRI reference may be used
as an IRI reference. An XRI reference in this form is said to be in
IRI-normal form.

Applying this conversion does not change the equivalence of the identifier,
with the possible exception of the addition of XRI metadata as discussed in
Step 3.

In general, an application SHOULD use the least-transformed version
appropriate for the context in which the identifier appears. For example, if
the context allows an XRI reference directly, the identifier SHOULD be an
XRI reference in XRI-normal form as described in section 2.1.4. If the
context allows an IRI reference but not an XRI reference, the identifier
SHOULD be in IRI-normal form. Only when context allows neither XRI nor IRI
references should URI-normal form be used.


***END***

-----Original Message-----
From: Drummond Reed [mailto:drummond.reed@cordance.net] 
Sent: Monday, September 12, 2005 11:48 PM
To: xri@lists.oasis-open.org
Subject: [xri] Special XRI TC call on IRI Normalization 5pm Pacific Tuesday
9/13

XRI TC Members and Observers,

To move quickly to close on as many XRI 2.0 Committee Draft 02 open issues
as possible, a special unofficial telecon on the IRI normalization issue
(Syntax Issue #4: IRI Normalization,
http://wiki.oasis-open.org/xri/Xri2Cd02/SyntaxChanges#head-0ae1d82d936b9f755
8ddbf9315f985974d7fd290) will be held at 5pm Pacific tomorrow (Tuesday) USA,
which will be 8pm EST, 9am Tokyo and 10pm Sydney.

The reason for the short notice is that this is the only time this week that
we could get Nat Sakimura of NRI (based in Toyko) and Wil Tan of NeuStar
(based in Australia) on the phone together, and they represent the two TC
members with the greatest expertise on the subject of IRIs and the difficult
choices of normalization algorithms.

Feel free to join us on this call if you are interested in this topic,.
Logistics follow below.

=Drummond 

TO ACCESS THE AUDIO CONFERENCE:
Dial In Number: 571-434-5750
Conference ID: 5474

TO ACCESS THE WEB CONFERENCE:
If web conferencing is used, it will prompt you to install a couple of
drivers. Click on the link below:

	http://conferencemanager.neustar.com/Login/ParticipantLogIn.asp 



---------------------------------------------------------------------
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