Shouldn't the path component of the URIs be percent-encoded? That is, http://uri4uri.net/uri/%0Ahttp%3A%2F%2Fdbpedia.org%2Fresource%2FCopenhagen
instead of http://uri4uri.net/uri/http://dbpedia.org/resource/Copenhagen Martynas graphity.org On Mon, Apr 1, 2013 at 11:37 AM, Christopher Gutteridge <[email protected]> wrote: > Well if I've understood correctly, uri4uri is an extreme version of > reification. rdfs: gave a way to describe a triple in triples but it still > related resources together, not the identifiers for those resources. That > makes it impossible to make statements about, say, what authority assigned > the URI and when. > > > > On 01/04/2013 08:49, Michael Brunnbauer wrote: >> >> Hello Chris, >> >> what a great step forward ! Now if the RDF WG would adopt this proposal, >> LOD and RDF would really be ready to save the world! >> >> http://www.brunni.de/extending_the_rdf_triple_model.html >> >> Regards, >> >> Michael Brunnbauer >> >> On Mon, Apr 01, 2013 at 12:13:19AM +0100, Christopher Gutteridge wrote: >>> >>> Apparently http://uri4uri.net/ launched today and claims to solves many >>> of the problems of Linked data. It looks promising.. >>> >>> -- >>> Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg >>> >>> University of Southampton Open Data Service: >>> http://data.southampton.ac.uk/ >>> You should read the ECS Web Team blog: >>> http://blogs.ecs.soton.ac.uk/webteam/ >>> > > -- > Christopher Gutteridge -- http://users.ecs.soton.ac.uk/cjg > > University of Southampton Open Data Service: http://data.southampton.ac.uk/ > You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/ > >
