Create edu.adoc

id/Internet2/edu.adoc

@@ -0,0 +1,35 @@
+===== T&I namespaces and assigned identifiers belong to one of the following Types
+
+
+* OIDs
+* URNs
+* URLs
+* Namespaces
+* Specs
+* Schema
+* Fed entities(?)
+
+===== Consolidated registry for the above
+
+
+* Construct a Trust and Identity registry tree, top level of which should be 'https://id.internet2.edu/ti'.  
+* Next path element under /ti is one item from the controlled enum:  oid', 'urn', 'url', 'spec', 'schema'
+** E.g.'https://id.internet2.edu/ti/urn'
+* Final fragment (after #) is an identifier of the type labeled by the parent node and must be unique within the scope of that parent
+** E.g. https://id.internet2.edu/ti/urn#mace:osu.edu
+* All Registry URLs must be
+** Resolvahle
+** Immutable
+* What should the unique identifier resolve to? 
+** A populated instance of a defined data structure TBD
+
+* Open Issue: What should be included in the Entry data structure?
+
+====== Management of the Registry
+
+* There must be defined processes for assigning URLs of each Type
+** The current process for assigning MACE URNs provides a starting point model for such processes
+* There should be a Registrar responsible for Registry operations overall
+* Delegated admins may be assigned responsibilities for specific entry Types
+* Processes mush be reliable and timely
+