Folks- FWIW, I have now reimplemented and relaunched
http://www.t4gm.infoas an unpublished linked data resource, with its
behavior largely
consistent with the discussion on this thread. The new site links to a
Github repository https://github.com/bradleypallen/t4gm-unpublished, and
the CKAN Data
Leigh- This is great. The question that comes up for me out of what you've
written for unpublishing brings me back to Antoine's question: is it
appropriate to use a relation other than owl:sameAs that more specific to
the domain of the affected datasets being mapped, or is the nature of
Tim- OK, I'm game. I am in the process of hacking together a small redirect
server that would replace the existing site, and can easily incorporate the
ability to return something like the following on a request for the root
resource:
@prefix rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns# .
Perfect. I was hoping that might be the case. I'll proceed to update the
record.
Bradley P. Allen
http://bradleypallen.org
On Wed, May 30, 2012 at 4:12 PM, Richard Cyganiak rich...@cyganiak.dewrote:
Bradley,
On 30 May 2012, at 23:03, Bradley Allen wrote:
I'm regret to say that I'd already
Antoine- Thanks for the pointer to the previous discussion, which I regret
to say I had missed; the use case is almost the same and it is an approach
that yields a softer landing in those cases where people/agents have been
dependent on the resources being sunsetted. So I'm going to instead follow
Back in 2009, as an experiment in working with RDFa and linked data, I
created t4gm.info. It is based solely on US Library of Congress library
linked data (specifically, the Thesaurus for Graphical Materials), which at
the time I created the site didn't have any equivalently accessible linked
Gregg- I think this is nicely done and a great contribution to
Monday's call, but I have some comments on terminology as it relates
to section 3.1.
In item 2 of the numbered list in that section, the phrase
conceptional graph appears; I assume that's a typo for the phrase
conceptual graph, which
Nathan- I think you are overly discounting scalability problems with
fragment URIs.
Most of the use cases I am dealing with in moving linked data into
production at Elsevier entail SKOS concept schemes with concepts
numbering in the 100,000's to millions, which will be constantly under
curation,
Bradley Allen wrote:
Nathan- I guess I'm not being clear about my problem. How do you get a
REST API to work with fragment URIs? - BPA
Bradley P. Allen
http://bradleypallen.org
On Wed, Nov 10, 2010 at 12:33 PM, Nathan nat...@webr3.org wrote:
Bradley Allen wrote:
Nathan- I think you
://example.org/people/sue#me, is un-RESTful:
PUT http://example.org/people/sue
ps: I use fragments, and update descriptions RESTfully, never ever had a
problem yet.
Regards,
Nathan
Bradley Allen wrote:
The assumption then would be that each representation would in the
limit have
Thanks; that's a useful example. So the convention in that case is to
append '#concept' to the end of the IR?
Bradley P. Allen
http://bradleypallen.org
On Wed, Nov 10, 2010 at 3:07 PM, Toby Inkster t...@g5n.co.uk wrote:
On Wed, 10 Nov 2010 12:30:35 -0800
Bradley Allen bradley.p.al
://bradleypallen.org
On Wed, Nov 10, 2010 at 3:13 PM, Bradley Allen
bradley.p.al...@gmail.com wrote:
Thanks; that's a useful example. So the convention in that case is to
append '#concept' to the end of the IR?
Bradley P. Allen
http://bradleypallen.org
On Wed, Nov 10, 2010 at 3:07 PM, Toby Inkster t
Basically what you are saying is: if I have a single URI that responds
to an HTTP GET with (X)HTML+RDFa by default, and supports other RDF
serializations through content negotiation, then all of that can be
done without recourse to a 303 redirect and should be perfectly
compatible with linked data
On Thu, Nov 4, 2010 at 9:13 AM, Ian Davis m...@iandavis.com wrote:
On Thu, Nov 4, 2010 at 4:07 PM, Bradley Allen bradley.p.al...@gmail.com
wrote:
Basically what you are saying is: if I have a single URI that responds
to an HTTP GET with (X)HTML+RDFa by default, and supports other RDF
wrote:
On 11/4/10 12:25 PM, Bradley Allen wrote:
On Thu, Nov 4, 2010 at 9:13 AM, Ian Davis m...@iandavis.com wrote:
On Thu, Nov 4, 2010 at 4:07 PM, Bradley Allen bradley.p.al...@gmail.com
wrote:
Basically what you are saying is: if I have a single URI that responds
to an HTTP GET with (X)HTML
Folks- I'm looking for a relation with domain skos:Concept or one of
its superclasses that can replace what skos:subject originally stood
for; effectively, the inverse of dc:subject. Interestingly, AFAICT
neither of DC*, SIOC, SALT or BIBO have something like this.
foaf:publications is close but
Bradley Allen schrieb:
Apologies if you've seen this on the LOD or SW lists, but it is
probably better posed to this audience: is there any best practice or,
failing that, good ideas for representing homonymy in SKOS? Best I can
come up with is subclassing skos:semanticRelation with something
Twitter failed to cough up an answer, so I'll try the lists: is there
any best practice or, failing that, good ideas for representing
homonymy in SKOS? Best I can come up with is subclassing
skos:semanticRelation with something like skos:hasHomonym, and letting
the client sort out which of the
Kingsley-
On Fri, Jun 26, 2009 at 11:40 AM, Kingsley Idehenkide...@openlinksw.com wrote:
Mark: Should we be describing our docs for Google, fundamentally? I really
think Google should actually recalibrate back to the Web etc..
The correct question to ask, and the one that I believe Mark is
I agree that both is better, but there is a catch.
As did Toby with his system, in http://t4gm.info, I serve up both
XHTML+RDFa and perform content negotiation, generating triples in the
MIME type expected by a given RDF-accepting user agent by redirecting
the given static XHTML+RDFa page through
This is one of the issues I am trying to address with http://t4gm.info.
There the notion of autocomplete filtering for SKOS concepts combined with
content negotiation allows one to have one's cake and eat it too, at least
as far user-friendly URL lookup is concerned; because of the use of
, Jan 19, 2009 at 3:15 AM, Tom Heath tom.he...@talis.com wrote:
Bradley,
As Kingsley says, very cool!
Is there any risk of this going the same way as lcsh.info? :(
Hope not,
Tom.
2009/1/15 Kingsley Idehen kide...@openlinksw.com:
On 1/14/09 6:13 AM, Bradley Allen wrote:
t4gm.info
t4gm.info http://www.t4gm.info is a simple, lightweight and
DRYhttp://en.wikipedia.org/wiki/DRYLinked Open Data rendering in
XHTML+RDFa of the Library
of Congress http://www.loc.gov/index.html' Thesaurus for Graphic
Materialshttp://lcweb2.loc.gov/pp/tgmhtml/tgmabt.html.
Details about its use and
23 matches
Mail list logo
