RE: [xri] Outline for XRI Primer

["Lindelsee, Mike " <mlindels@visa.com>]

I really like the new approach, Drummond.  It focuses in on the heart of
the matter.

Mike

>-----Original Message-----
>From: Drummond Reed [mailto:drummond.reed@cordance.net] 
>Sent: Thursday, February 10, 2005 5:40 PM
>To: Lindelsee, Mike ; xri@lists.oasis-open.org
>Subject: RE: [xri] Outline for XRI Primer
>
>Great stuff! This really helps me understand the logic of your ranking.
>
>The larger issue this brings up is the many different 
>perspectives we bring
>to the question of "Why XRIs?" It's entirely possible that 
>among the editors
>(let alone the entire TC), if we asked everyone to stack rank 
>the features
>by importance, we'd get 7 different lists.
>
>And that's not a bad thing. It's a GOOD thing. That's why 
>we're all on this
>TC together. We all have different use cases that have 
>different priorities
>for different features.
>
>The challenge it presents us is how we come together on one 
>Primer that's
>designed to quickly orient a newcomer by answering the following two
>questions:
>
>1) Why might I want to use XRIs - what problems do they help 
>me solve that
>URIs alone don't? 
>
>2) How do XRIs, XRI resolution, and XRI metadata help me solve these
>problems?
>
>As I write this, I'm already seeing a new approach to the 
>outline, which is
>to focus less on which feature is more/less important (because that
>ultimately can only be determined by the reader) and more on 
>providing clear
>articulations of:
>
>a) The types of problems XRIs are designed to help solve (problems of
>federating identifiers across distributed systems, problems of 
>maintaining
>persistent relationships, problems of sharing identifiers across many
>contexts, problems of providing identifier interoperability across many
>different disparate systems.)
>
>b) How XRIs are designed to solve these problems (how they can 
>be used to
>federate systems, how they can be used to provide persistent
>identity/linking, how they can be used to share identifiers 
>across contexts,
>how they can be used to provide identifier interoperability 
>across disparate
>systems).
>
>The first part could be a relatively short, crisp description 
>of the types
>of problems XRIs are designed to solve. The second part can be 
>a sequence of
>example usage scenarios that show how how it can be done (all 
>feeding off
>each other so we don't have to set up new example scenarios 
>over and over
>again.)
>
>So the high-level outline becomes:
>
>1) Introduction (very short)
>
>2) The Types of Problems XRIs Are Designed to Solve
>
>3) How XRIs Can Help Solve These Problems: Example Usage Scenarios
>
>4) A Brief Guide to the Normative 2.0 Specifications
>
>Appendix A: Glossary
>
>How does this new high-level approach sound?
>
>=Drummond 
>