Steve Harris wrote:
On 20 May 2009, at 16:38, Kingsley Idehen wrote:
Steve Harris wrote:
Alternatively you could put that data in a RDF store, and just serve
up the fragments using a wrapped CONSTRUCT query.
That's what we do for qdos.com, eg
http://qdos.com/user/Steve-Harris/18b6f60b41e05a
On 20 May 2009, at 16:38, Kingsley Idehen wrote:
Steve Harris wrote:
Alternatively you could put that data in a RDF store, and just
serve up the fragments using a wrapped CONSTRUCT query.
That's what we do for qdos.com, eg
http://qdos.com/user/Steve-Harris/18b6f60b41e05aaa418565ebfe901d6b/r
Steve Harris wrote:
Alternatively you could put that data in a RDF store, and just serve
up the fragments using a wrapped CONSTRUCT query.
That's what we do for qdos.com, eg
http://qdos.com/user/Steve-Harris/18b6f60b41e05aaa418565ebfe901d6b/rdfxml
and it's pretty efficient, more efficient th
On 20 May 2009, at 15:48, Yves Raimond wrote:
Hello!
Not very linked data friendly (you'll end up with a large
proportion of
repeated triples in identical graphs, with different graph URIS), but
certainly better than nothing.
Just jumping on that - is that an issue? I would think not, as y
Alternatively you could put that data in a RDF store, and just serve
up the fragments using a wrapped CONSTRUCT query.
That's what we do for qdos.com, eg
http://qdos.com/user/Steve-Harris/18b6f60b41e05aaa418565ebfe901d6b/rdfxml
and it's pretty efficient, more efficient that storing 1000 separ
Hello!
> Not very linked data friendly (you'll end up with a large proportion of
> repeated triples in identical graphs, with different graph URIS), but
> certainly better than nothing.
Just jumping on that - is that an issue? I would think not, as you may
want to repeat information across differ
Steve Harris wrote:
> Very cool resource.
>
> On 20 May 2009, at 10:18, Libby Miller wrote:
>>> Individual commodity descriptions can be retrieved as follows:
>>>
>>> http://openean.kaufkauf.net/id/EanUpc_
>>>
>>> Example:
>>>
>>> http://openean.kaufkauf.net/id/EanUpc_0001067792600
>>
>> This seem
Hi Steve,
as I replied to Libby (but did not include all mailing lists): The whole
data set is served from currently 100 smaller files, which will be
broken down to 1000 files shortly. For various reasons however, we don't
want to serve one file per element, because that will create a huge
ove
Very cool resource.
On 20 May 2009, at 10:18, Libby Miller wrote:
Individual commodity descriptions can be retrieved as follows:
http://openean.kaufkauf.net/id/EanUpc_
Example:
http://openean.kaufkauf.net/id/EanUpc_0001067792600
This seems to give me multiple product descriptions - am I
m
Hi Libby,
That's rather fabulous! Can you give some information about how often
this dataset is updated, and what's its geographical and product type
reach?
Thanks! This particular data set is a rather static collection and has a
bias towards US products. It will soon be complemented by a mo
hi Martin,
On 20 May 2009, at 09:58, Martin Hepp (UniBW) wrote:
1. OpenEAN data set: 1 million EAN/UPC codes plus respective labels
---
The full data set is at
http://openean.kaufkauf.net/id/
That's rather fabulous! Can you giv
Dear all:
Thanks to the help of several partners, there are now new data sets and
tools related to the GoodRelations ontology for e-commerce:
1. OpenEAN data set: 1 million EAN/UPC codes plus respective labels
---
The full data set
12 matches
Mail list logo