- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Thu, 9 Aug 2018 20:35:38 +0200
- To: Alexandre Bourlier <alexandre@happy-dev.fr>
- Cc: LDP Next <public-ldpnext@w3.org>, Sylvain Le Bon <sylvain@happy-dev.fr>
- Message-ID: <CAKaEYh+=rs3oxhmSo__gh8pC5YS=xLtv=vtyvzNNNNH9OUwwcA@mail.gmail.com>
On 9 August 2018 at 18:57, Alexandre Bourlier <alexandre@happy-dev.fr> wrote: > Hi Cody, Melvin, Andrew, > Hi everyone, > > Thank you so much for your responses, and sorry to reach back to you that > late. > > We do have an eye on SoLiD, we even have a trainee (Samy Vincent) working > with them, but we want to implement the standards in a very lightweight > technology that we can easily extend and customize to suit our needs. > The gap required to tweak SoLiD suite is a little too high for us, so we > extended the Django REST Framework API. It allows us to be very agile. > > I'll take a look at Stencil. > > My first question would be : When I receive a resource, it has properties, > for instance an "avatar" property of type "image/jpeg". > By default, our component will display it as plain text, meaning it will > output its URL to the view. > What I would like is for the component to understand that this "avatar" > property is of type image, so that it displays the image instead of > outputting its URL to the end user. > > I see two ways to do this : > - checking the extension of the property (not very reliable) > - issuing a HEAD HTTP request and inspect the "Content-Type" header > returned. This doesn't seem desirable as it actually means issuing a > additional request per property which sounds insane performance wise. > > I am hoping there is a way for us to convey the property type within the > resource, so our components can directly use the appropriate widgets to > render them. > So far we do the matching manually but it will stop working in a real > federated environment. > > Would you have any suggestion regarding the best way to convey the type of > properties, and to interpret them? > Great! Yes, we have met Samy in our Solid chat room. Is a lot of fun interacting with him :) https://www.w3.org/DesignIssues/HTTPFilenameMapping.html This design issue may be interesting to you, re content types > > Thank you so much for your insights on this. > All the best ! > > On Mon, Jul 30, 2018 at 4:44 PM Cody Burleson <cody.burleson@base22.com> > wrote: > >> Hi, Alexandre, >> >> >> >> I think this is really the only “living” (though not active) group >> related to LDP. So, I think you’ve probably got the right place in terms of >> being able to reach people who may have been involved in the spec or >> otherwise understand it. >> >> >> >> Speaking of web components, check out the Stencil >> <https://stenciljs.com/> web component compiler if you haven’t already. >> I’ve been pretty impressed with it. The folks at Ionic just used it to >> rewrite all of Ionic to be standards compliant Web Components. I don’t work >> for Ionic or anything; I just think they’re Stencil CLI is great. >> >> >> >> >> >> -- >> >> Cody Burleson >> >> >> >> *From: *<alexandre.bourlier@gmail.com> on behalf of Alexandre Bourlier < >> alexandre@happy-dev.fr> >> *Date: *Monday, July 30, 2018 at 7:49 AM >> *To: *LDP Next <public-ldpnext@w3.org> >> *Cc: *Sylvain Le Bon <sylvain@happy-dev.fr> >> *Subject: *Hello LDP Next >> *Resent-From: *LDP Next <public-ldpnext@w3.org> >> *Resent-Date: *Monday, July 30, 2018 at 7:49 AM >> >> >> >> Good afternoon gentlemen, >> >> >> >> With Sylvain Le Bon (in cc) that some of you know, we are launching a >> company called Startin'blox. >> >> Startin'blox is a set a web components that implement the LDP standards >> to build interoperable apps more easily. >> >> >> >> What we want it to build an eco-system of such apps. We have got half a >> dozen companies interested. >> >> >> >> We bump into limitations, of the spec itself and also our knowledge and >> understanding of it. >> >> Where would be the good place for us to expose the challenges we are >> facing and be able to ask our questions ? >> >> >> >> All the best ! >> >> >> -- >> >> >> >> Alexandre BOURLIER >> >> 06 51 71 08 21 >> >> http://happy-dev.fr >> > > > -- > > Alexandre BOURLIER > 06 51 71 08 21 > http://happy-dev.fr >
Received on Thursday, 9 August 2018 18:36:04 UTC