Re: Proposal: Add JSON-LD to WebID Identity Spec

On Wed, 16 Sep 2020 at 14:15, Henry Story <henry.story@bblfish.net> wrote:

> Hi,
>
>   Thanks to Martynas for pinging me on Gitter.
>
> Yes, this sounds like a good idea.
>
> I think WebID-spec has aged pretty well.
>

I also think the spec has aged pretty well

Some feedback from working with webid for 10+ years, in no particular order

1 working with two or more files that must be kept in sync is hard

2 (related) conneg is hard

3 turtle is a tough sell outside of the rdf community

4 parsing is hard, and carries an overhead

5. working with redirects is hard

>
>
> I would need to find out if I still have access to the CVS
> repository, or how to get it.
>
> Henry
>
>
> > On 5 Sep 2020, at 23:24, Melvin Carvalho <melvincarvalho@gmail.com>
> wrote:
> >
> >
> >
> > On Thu, 27 Aug 2020 at 17:28, Kingsley Idehen <kidehen@openlinksw.com>
> wrote:
> > On 8/26/20 10:24 PM, Kingsley Idehen wrote:
> >> On 8/26/20 12:48 PM, Melvin Carvalho wrote:
> >>> The current WebID Identity and Discovery Editor's Draft is now 6.5
> years old
> >>>
> >>> https://www.w3.org/2005/Incubator/webid/spec/identity/
> >>>
> >>> In that time Identity and deployments have evolved, and we have learnt
> more through implementation experience
> >>>
> >>> IMHO the major significant development of the last 5+ years revolves
> around JSON-LD and deployment through schema.org
> >>>
> >>> This is now deployed on many millions of sites and many billions of
> web pages
> >>>
> >>> I propose that we modernize the WebID spec to add JSON-LD consistent
> with the new deployment information
> >>>
> >>> Hopefully this is a no-brainer
> >>>
> >>> Comments welcome!
> >>>
> >>> Agree / Disagree / Thoughts?
> >
> >
> > Hi Henry,
> >
> > How do we edit the WebID draft document?
> >
> > We need to be able to update this spec so that we have up-to-date
> collateral for articulating its virtues to a variety of developer
> communities. As you already know, the "PasswordLess Authentication" meme is
> gaining momentum across a variety of "Web Developer" communities thereby
> making action and timing crucial :)
> >
> >
> > Perhaps someone on this list is able to contact Henry and ask his
> thoughts
> >
> > Alternatively we could possibly go for 2 co-chairs of the group, which
> is normally a good idea for community groups, if anyone has time to help
> >
> > --
> > Regards,
> >
> > Kingsley Idehen
> > Founder & CEO
> > OpenLink Software
> > Home Page:
> > http://www.openlinksw.com
> >
> > Community Support:
> > https://community.openlinksw.com
> >
> > Weblogs (Blogs):
> > Company Blog:
> > https://medium.com/openlink-software-blog
> >
> > Virtuoso Blog:
> > https://medium.com/virtuoso-blog
> >
> > Data Access Drivers Blog:
> > https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
> >
> >
> > Personal Weblogs (Blogs):
> > Medium Blog:
> > https://medium.com/@kidehen
> >
> > Legacy Blogs:
> > http://www.openlinksw.com/blog/~kidehen/
> >
> >
> > http://kidehen.blogspot.com
> >
> >
> > Profile Pages:
> > Pinterest:
> > https://www.pinterest.com/kidehen/
> >
> > Quora:
> > https://www.quora.com/profile/Kingsley-Uyi-Idehen
> >
> > Twitter:
> > https://twitter.com/kidehen
> >
> > Google+:
> > https://plus.google.com/+KingsleyIdehen/about
> >
> > LinkedIn:
> > http://www.linkedin.com/in/kidehen
> >
> >
> > Web Identities (WebID):
> > Personal:
> > http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i
> >
> >         :
> >
> http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
> >
> >
> >
>
> Henry Story
>
> https://co-operating.systems
> WhatsApp, Signal, Tel: +33 6 38 32 69 84‬
> Twitter: @bblfish
>
>