Having those could justify to rename this package to webprofiled.
@elf-pavlik What do you think?
Strangely enough
curl -X GET profiles.allmende.io/provider/75afcff7-4723-41ea-96ba-f583861573c6
doesn't render HTML, despite there's a Person.hbs, but
curl -H "Accept: application/ld+json" -X GET profiles.allmende.io/provider/75afcff7-4723-41ea-96ba-f583861573c6
indicates it as "@type":"Person".
Maybe it is because http://plp.hackers4peace.net/context.jsonld doesn't redirect to http://ld.hackers4peace.net/contexts/plp.jsonld and we cannot determine the @type properly?
Can we consider
daemon.get('/:uuid', function(req, res){
storage.get(req.uri) // -> doc
.then(function(doc){
res.format({
'text/html': function(){
var type = doc.type;
// handle case of array
if(typeof type == 'object') type = type[0];
res.render(type, doc);
},
to work properly? I wouldn't know how to trace it.
We cannot view all profiles in the browser, possibly due to missing views in
Having those could justify to rename this package to
webprofiled
. @elf-pavlik What do you think?Strangely enough
doesn't render HTML, despite there's a Person.hbs, but
indicates it as
"@type":"Person"
. Maybe it is becausehttp://plp.hackers4peace.net/context.jsonld
doesn't redirect tohttp://ld.hackers4peace.net/contexts/plp.jsonld
and we cannot determine the@type
properly?Can we consider
to work properly? I wouldn't know how to trace it.