There's a lot to be said for keeping things very simple.
Over in the biodiversity informatics community we've adopted Life
Science Identifiers (LSID) as our identifier of choice, which require
special software to both serve and resolve, plus the added
complication of convincing your friendl
Hi Christopher,
> Q1) Should HtPLDotW be updated to remove references to
> "Dereferencing HTTP URIs" in favor of "Cool URIs for the
> Semantic Web"
Yes. The HtPLDotW document is from 2007 and urgently needs updating.
We are planning to do this during the summer, so expect a new version in
fall.
I wanted to say something about picking URIs during my
lightning talk at an upcoming Semantic Web Dallas meetup.
But I've run into a problem reconciling the recommendations
in HtPLDotW with the recommendations in "Cool URIs don't
change" (and my own experience with enterprise databases
and natural
I'm putting together a quick presentation on 303s and
Linked Data for the local Dallas Semantic Web Meetup
(it's part of a series of 10-minute lightning presentations)
I've got a couple of questions. They start out nitpicky
and pedantic (but I have some more entertaining ones
for later)
So, to st
I am finding the current discussion really difficult.
Those who do not learn from history are condemned to repeat it.
As an example:
In the 1980s there were a load of hypertext systems that required the users
to do a bunch of stuff to buy into them. They had great theoretical bases,
and their prop
DNS trickery is the ultimate step for a fully flexible architecture.
Unfortunately it requires to have some admin rights over your own
domain. Something uber difficult in companies.
A workaround would be to create a top domain name, something like
..uris (or more realistically cooluris.net), with
Externalizing the 303 feature is the good idea, imo.
But such a service should also handle the content negociation feature.
So the 303 may redirect to different URLs depending on the content
negociated. This makes the service more complex internally but
provides a very relevant service for RDF pub
That's what this code does. It intercepts the 404 at the server and returns
results depending on the redirect rules.
2009/7/9 Peter Krantz
> On Thu, Jul 9, 2009 at 12:27, Richard Light
> wrote:
>
> >
> > Attached is an IIS Active Server Page which handles 404 "page not found"
> > errors. The l
On Thu, Jul 9, 2009 at 10:46 AM, Pierre-Antoine
Champin wrote:
>
> However, some people will still be concerned about naming their resources
> under a domain that is not theirs. That is not only a matter of
> URI-prettiness, but also of relying on an external service, which may cease
> to exist tom
Dear all:
Great news: ANY site owner in the world has now a clear incentive to add
GoodRelations meta-data in RDFa to his/her page:
As of now, Yahoo will display price and offering details and other
meta-data of any e-commerce Web page if the site owner uses
GoodRelations vocabulary elements.
I like this! :)
However, some people will still be concerned about naming their
resources under a domain that is not theirs. That is not only a matter
of URI-prettiness, but also of relying on an external service, which may
cease to exist tomorrow.
However, this could easily be solved. All w
(Discussing 303-redirect services, such as http://t-d-b.org/ or
http://thing-described-by.org/ )
On Thu 09/07/09 6:12 AM , Olivier Rossel olivier.ros...@gmail.com sent:
> Externalizing the 303 feature is the good idea, imo.
>
> But such a service should also handle the content negociation fea
In message ,
Juan Sequeda writes
Hi Richard
This is a great addition to the ConNeg 303 section on linkeddata.org.
Awesome!
However, would you be able to host the source code and then I can just
link to it from linkeddata.org?
In due course. I'll let you know ...
Richard
--
Richard Light
Hi Richard
This is a great addition to the ConNeg 303 section on linkeddata.org.
Awesome!
However, would you be able to host the source code and then I can just link
to it from linkeddata.org?
Thanks
Juan Sequeda, Ph.D Student
Dept. of Computer Sciences
The University of Texas at Austin
www.jua
In message <7b9ad66d0907090406t37f29aa0qc7271d094914...@mail.gmail.com>,
Peter Krantz writes
Attached is an IIS Active Server Page which handles 404 "page not found"
errors. The logic is that since the abstract URLs/PSIs representing a
concept/subject do not have a corresponding page, they wil
Hi,
As a personal project I've been working on a conversion of the discogs
[1] music database into Linked Data [2].
The database, which is regularly exported and is under a Public Domain
license, includes medata about approximately 1.2m artists and over
100k labels, and 1.5m releases,
The first
On Thu, Jul 9, 2009 at 12:27, Richard Light wrote:
>
> Attached is an IIS Active Server Page which handles 404 "page not found"
> errors. The logic is that since the abstract URLs/PSIs representing a
> concept/subject do not have a corresponding page, they will end up here.
This sounds interesti
Let us say we have a document at http://example.org/document.html, and that
document also contains meta data describing it embedded via RDFa.
Can we refer to the meta data triples in the document with a URI like
http://example.org/document.html#about ?
How can we serve a different presentation to
On 09/07/2009 07:56, "Peter Ansell" wrote:
> 2009/7/9 Juan Sequeda :
>> On Jul 9, 2009, at 2:25 AM, Hugh Glaser wrote:
>>> Mind you, it does mean that you should make sure that you don't put too
>>> many
>>> LD URIs in one document.
>>> If dbpedia decided to represent all the RDF in one documen
Hashed URIs can bring other problems.
For example, if I have a service http://mydata.org/uri that takes a
URI and returns what it knows about the thing identified by that URI
and I pass it a hash URI, e.g. http://ci.nii.ac.jp/naid/110006281382#article
, my browser will trim #article and send
In message
@ecs.soton.ac.uk>, Hugh Glaser writes
Hash URIs are very valuable in linked data, precisely *because* they
can't be directly requested from a server - they allow us to bypass
the whole HTTP 303 issue.
Mind you, it does mean that you should make sure that you don't put too many
LD U
On 9 Jul 2009, at 05:10, Sergey Chernyshev wrote:
I think that if your goal is to publish it to public, publish in
all formats, including CSV or vcard as long as there is at least
one tool that will potentially consume this information.
I used to ascribe to this philosophy. I offered feeds
On 9 Jul 2009, at 07:44, Juan Sequeda wrote:
On Jul 9, 2009, at 2:25 AM, Hugh Glaser wrote:
Mind you, it does mean that you should make sure that you don't
put too many
LD URIs in one document.
If dbpedia decided to represent all the RDF in one document, and
then use
hash URIs, it would
2009/7/9 Juan Sequeda :
> On Jul 9, 2009, at 2:25 AM, Hugh Glaser wrote:
>> On 09/07/2009 00:38, "Toby A Inkster" wrote:
>>
>>> On 8 Jul 2009, at 19:58, Seth Russell wrote:
>>>
Is it not true that everything past the hash (#alice) is not
transmitted back to the server when a browser cli
24 matches
Mail list logo
