...
- Managementsamenvatting
- Probleemstelling
- Eisen en randvoorwaarden
- Mogelijke oplossingen
- Conclusie
Wiki Markup [Literatuur|#Literatuur}] [Bijlage 1 Begrippen|#Bijlage1] [Bijlage 2. Voorstel voor gefaseerde implementatie URN:NBN in DARE-verband|#Bijlage2]\\ \\ \\ \| Status versie 0.6: besproken en goedgekeurd in de vergadering van de Repository Managers \\ d.d. 5 april 2007, DARE, SURF, Utrecht. \\ Wijzigingen: \\ 1. In het schema: "Huidige Identifiers voor "information assets"" (pg 5) zijn wijzigingen \\ opgenomen voor de Technische Universiteit Eindhoven en de Rijks Universiteit Groningen. \\ 2. Op pg 7 is een betere verwijzing opgenomen naar: Hans-Werner Hilse and Jochen Kothe, Implementing Persistent Identifiers \[Hilse/Kothe, 2006\]. \\ 3. Op de kaft is het DARE-logo opgenomen \| \\ \\ *Werkgroep* De werkgroep _persistente identifi{_}ers was als volgt samengesteld: Niels Rozenboom, Universiteit Leiden Maarten Hoogerwerf, DANS Peter Ruijgrok, Universiteit Utrecht Laurens Sesink, DANS Hubert Krekels, Wageningen Universiteit Maurice Vanderfeesten, DARE Marlon Domingus, Universiteit Leiden (vz) \\ \\ \\
...
Wiki Markup |
---|
*Resource* \[W3C-definitie\] \\ This specification does not limit the scope of what might be a resource; rather, the term "resource" is used in a general sense for whatever might be identified by a URI. Familiar examples include an electronic document, an image, a source of information with a consistent purpose (e.g., "today's weather report for Los Angeles"), a service (e.g., an HTTP-to-SMS gateway), and a collection of other resources. A resource is not necessarily accessible via the Internet; e.g., human beings, corporations, and bound books in a library can also be resources. Likewise, abstract concepts can be resources, such as the operators and operands of a mathematical equation, the types of a relationship (e.g., "parent" or "employee"), or numeric values (e.g., zero,one, and infinity). \\ Zie: Tim Berners-Lee, Roy T. Fielding, Larry Masinter. (January 2005). "Uniform Resource Identifier (URI): Generic Syntax". Internet Society. RFC 3986; STD 66. [http://gbiv.com/protocols/uri/rfc/rfc3986.html]<span style="color: #0000ff"><a href="http://gbiv.com/protocols/uri/rfc/rfc3986.html">http://gbiv.com/protocols/uri/rfc/rfc3986.html</a></span>\\ \\ *URL* \[W3C-definitie\] The term "Uniform Resource Locator" (URL) refers to the subset of URIs that, in addition to identifying a resource, provide a means of locating the resource by describing its primary access mechanism (e.g., its network "location"). Zie: Tim Berners-Lee, Roy T. Fielding, Larry Masinter. (January 2005). "Uniform Resource Identifier (URI): Generic Syntax". Internet Society. RFC 3986; STD 66. [http://gbiv.com/protocols/uri/rfc/rfc3986.html]<span style="color: #0000ff"><a href="http://gbiv.com/protocols/uri/rfc/rfc3986.html">http://gbiv.com/protocols/uri/rfc/rfc3986.html</a></span>\\ *URI* \[W3C-definitie\] A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. The following are two example URIs and their component parts: \\ foo://example.com:8042/over/there?name=ferret#nose \_/\______\__\__\__\__/___\__\__\__/ \_\__\____\__/ \__/ |
scheme authoritypathquery fragment
_____________________ | __ |
...