Changes between Version 13 and Version 14 of SigMmt/Templates/TemplateIds

Timestamp:

09/15/10 17:41:13 (14 years ago)

Author:

rahul (IP: 115.240.90.67)

Comment:

--

SigMmt/Templates/TemplateIds

@@ -150 +150 @@
 
 Robin
+
+------
+
+[Copied Robin's last post and adding inline comments from Rahul]
+
+Hi Rahul,
+
+I think the flaw with URI's is that they are not pure identifiers. They have an address in them and I think we are abusing the purpose of that address.
+
+[rahul] - Actually, I did not mean this (the abusing of the address part). I think you are talking about resolvable ids, if yes then that is slightly different from what I am saying. First statement could be difference between URN and URL.
+
+  
+What is most important about a URI is that it provides truly global unique identifiers.  The reason why an address is included is that it is the address of the identifier issuing authority or endpoint – and nothing more.  The address included in the URI should never be interpreted as the status, state, or location of the thing that is being identified.
+
+  
+[rahul] - Agree.
+
+ 
+That is what is messing us up.
+
+[rahul] - it could be, but certainly not the focus of this thread (unless, i am misunderstanding your point, are you referring to resolvable URLs?). 
+
+ 
+I fully agree in federation of RDL content.  There is no need to put RDL content in one place.  And separating RDL content at various endpoints based on any reason including ownership, status, etc is fine by me.  So I think we are aligned there.
+
+
+[rahul] - Great! I think that was almost 90% of focus of this thread.
+
+
+However, I do not think the identifier issuing authority must be at the endpoint where the RDL thing is being accessed.  It could be the same but there should never be a requirement that it is the same.
+
+
+[rahul] - couldn't agree more. Can I put it like : "URIs used for ids need not be resolvable".
+
+
+If we bind interpretation of status, state, access location, etc of RDL content into the identifier then I think we are in big trouble.  The reason is that the identifier must be forever but its status, state, location, etc in time and space will not be forever.
+
+ 
+[rahul] - Agreed.
+
+ 
+When http://rdlfacade.org was created its sole purpose was to be an identifier issuing authority.  We never intend initial content of whatever status, state, or location to be originated there or even end up there.
+So if you use URI’s in a pure KISS (Keep It Simple Stupid) manner, then we can continue to generate identifiers free of its status, state, location, etc and have the most reliable identifiers at the lowest cost possible.
+
+
+[rahul] - completely agree.
+
+ 
+