- From: Sean Martin <sjmm@us.ibm.com>
- Date: Sun, 18 Jun 2006 09:04:26 -0400
- To: public-semweb-lifesci@w3.org
- Cc: Eric Neumann <eneumann@teranode.com>
- Message-ID: <OF7542A912.DA237AF1-ON85257191.0043317B-85257191.0047BDE9@us.ibm.com>
Eric Neumann <eneumann@teranode.com> wrote on 06/17/2006 12:33:25 PM: > May I ask all the contributors to include HTML links to any acronyms > they reference (e.g., NAPTR)? This will make it easier for the rest of > us to catch up quickly, and to eventually collect the approaches out > there into a comprehensive list of viable implementations. > > thanks, > Eric > Quite right Eric. My apologies everyone. Here follow the recent references: NAPTR stands for Naming Authority Pointer [1] and is a newer type of DNS record that supports regular expression based rewriting. Several NAPTR records can be chained together creating fairly sophisticated URI rewriting rules. A record can go through any number of rewrites before reaching a terminal condition. - this is actually much simpler than the example listed in Wikipedia would lead one to believe at first. Section 13.3 (page 26) of the LSID specification [2] has a relatively straightforward explanation of how this can work. DDDS or The Dynamic Delegation Discovery System [3] [4] is used to implement lazy binding of strings to data, in order to support dynamically configured delegation systems. SRV or Service Record Service record [5] is a category of data in the Internet Domain Name System specifying information on available services. LSID or Life Science Identifier [6] - for those who want to know what these really are and what they were created for, please read this overview [1] http://en.wikipedia.org/wiki/NAPTR [2] http://www.omg.org/cgi-bin/apps/doc?dtc/04-05-01.pdf [3] http://en.wikipedia.org/wiki/DDDS [4] http://tools.ietf.org/html/3401 [5] http://en.wikipedia.org/wiki/SRV_record [6] http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?cmd=Retrieve&db=pubmed&dopt=Abstract&list_uids=15153306&query_hl=3&itool=pubmed_docsum Kindest regards, Sean --- Sean Martin IBM Corp.
Received on Sunday, 18 June 2006 13:04:37 UTC