4 Matching Annotations
  1. Sep 2019
    1. Of course, as organizations disolve and mutate, there is nothing to stop one organization from taking over the support of  the archives another.  Forthis purpose, it would be very useful to have a syntax for putting a date into a domain name.  This would allow a system to find an archive server.  Imaging that, failing to find "info.cern.ch", one could search back and find an entry "info.cern.ch.1994" which pointed to www.w3.org as a current server holding archive information for info.cern.ch as it was in 1994, with, of course,  pointers to newer versions of the documents.

      This document talks about content negotiation being used to request an audio version of a resource, no protocol-level negotiation of time versioning appears here.

    1. On the other hand, a resource may be generic in that as a concept it is well specified but not so specifically specified that it can only be represented by a single bit stream. In this case, other URIs may exist which identify a resource more specifically. These other URIs identify resources too, and there is a relationship of genericity between the generic and the relatively specific resource.

      I was not aware of this page when the Web Annotations WG was working through its specifications. The word "Specific Resource" used in the Web Annotations Data Model Specification always seemed adequate, but now I see that it was actually quite a good fit.

    1. HTTPRange-14
    2. we can't expect english words to exist to capture exactly the concepts

      We commit, by using these terms, to "inscription error"<sup>[1]</sup>.