Hello Joseph, you've hit on a limitation in the HTTP protocol. Although n2t.net
does a 302 temporary redirect, not a 301 permanent redirect, still, users will see local URLs in their browsers and will end up bookmarking those local URLs.
acting as a proxy isn't feasible. For one thing there would be technical problems related to security: a resource that appears to be hosted at n2t.net
would not be able to load ancillary resources located at the local repository due to web browser same-domain security policy. For another, there would be a loss of trust. Imagine for a moment that n2t.net
acted as a proxy for the New York Times. How would you know you were reading the authentic New York Times when the URLs you see all start with n2t.net
? You wouldn't. Google recently launched its own proxy delivery service (AMP, accelerated mobile pages), which has been widely criticized on this point (in effect, the system requires readers to completely and implicitly trust Google).
Current best practice is for local repositories to advertise their PIDs, both in human-readable landing pages ("cite this resource as...") and in machine-readable forms (metadata, related links).
> You received this message because you are subscribed to the Google Groups ARKs group. To post to this group, send email to arks-...@googlegroups.com
. To unsubscribe from this group, send email to arks-forum+...@googlegroups.com
. For more options, visit this group at https://groups.google.com/d/forum/arks-forum?hl=en
> You received this message because you are subscribed to the Google Groups "ARKs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to arks-forum+...@googlegroups.com
> To view this discussion on the web visit https://groups.google.com/d/msgid/arks-forum/c7b85dd3-270d-463e-b1b3-87875f5dfadan%40googlegroups.com