Re: PURLs don't matter, at least in the LOD world
On Fri, Feb 17, 2012 at 7:02 PM, David Wood da...@3roundstones.com wrote: Given what I personally know of the state of US Government agencies, I'll take your bet whether the Web services of the Library of Congress or OCLC lasts longer :) You might look back at the tortured history of id.loc.gov before we agree to a figure. At least w/ the tortured history of id.loc.gov and lcsh.info I was able to permanently redirect lcsh.info to the appropriate places on id.loc.gov when lcsh.info was slated for retirement. That way anybody who was scrubbing their links (notably the search engines more than the semantic web community) would have updated their links. I'm with Hugh, putting all your identifier eggs in the basket of purl.org (or any 3rd party service) isn't an excuse for not thoughtfully managing your URL namespaces and DNS. Perhaps that's tilting at windmills, but so be it. In my opinion more still needs to be done to educate people about how web architecture actually works instead of getting them to invest in niche software solutions, maintained by a handful of people with consulting contracts on the line. //Ed
Re: PURLs don't matter, at least in the LOD world
On 2/19/12 8:21 AM, Ed Summers wrote: On Fri, Feb 17, 2012 at 7:02 PM, David Woodda...@3roundstones.com wrote: Given what I personally know of the state of US Government agencies, I'll take your bet whether the Web services of the Library of Congress or OCLC lasts longer :) You might look back at the tortured history of id.loc.gov before we agree to a figure. At least w/ the tortured history of id.loc.gov and lcsh.info I was able to permanently redirect lcsh.info to the appropriate places on id.loc.gov when lcsh.info was slated for retirement. That way anybody who was scrubbing their links (notably the search engines more than the semantic web community) would have updated their links. I'm with Hugh, putting all your identifier eggs in the basket of purl.org (or any 3rd party service) isn't an excuse for not thoughtfully managing your URL namespaces and DNS. Perhaps that's tilting at windmills, but so be it. In my opinion more still needs to be done to educate people about how web architecture actually works instead of getting them to invest in niche software solutions, maintained by a handful of people with consulting contracts on the line. //Ed +1 -- Regards, Kingsley Idehen Founder CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen smime.p7s Description: S/MIME Cryptographic Signature
Re: [http-range14] how to publish RDF for Information Resources
On 2/19/12 7:12 PM, Andrea Perego wrote: An alternative would be using wdrs:describedby [1], a property defined in the POWDER-S ontology. The only issue is that the corresponding W3C Recommendation [2] specifies on this property a domain restriction which still needs to be amended, as discussed in [3,4]. Yes, see: http://linkeddata.informatik.hu-berlin.de/uridbg/index.php?url=http://dbpedia.org/page/Linked_Data_structureacceptheader=useragentheader= . Note: rev=describedby relation exposed via Link: and link/ . -- Regards, Kingsley Idehen Founder CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen smime.p7s Description: S/MIME Cryptographic Signature
