- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Sat, 11 Nov 2023 14:24:14 -0500
- To: public-webid <public-webid@w3.org>
- Message-ID: <787a1262-199e-4dcd-8f76-8b0b9e3be1ec@openlinksw.com>
On 11/11/23 12:48 PM, Melvin Carvalho wrote:
>
> Issue raised: https://github.com/w3c/WebID/issues/21
>
> Once the superset specification has been drafted, we will also need
> subset specs as outlined in #17 <https://github.com/w3c/WebID/issues/17>
>
> Which ones should be selected?
>
> Here's my votes:
>
> +1 JSON-LD
> +1 Turtle
>
> -1 RDFa
> -1 anything that mandates XHTML
>
> +0 everything else
>
> The reasoning behind this is to align with current adoption,
> popularity with web developers, backwards compatibility, and areas
> that have a chance of achieving broad adoption and growth.
>
> Happy to hear other opinions on this.
>
FWIW -- Turtle should be considered an option (MAY) rather than a
requirement (SHOULD). The Web is already replete with WebIDs and
WebID-Profile documents, predominantly comprising:
1. HTML documents.
2. Embedded structured data islands (rich metadata) formulated in
entity relationship graph format using any combination of JSON-LD,
Microdata, RDFa, or Plain Old Semantic HTML (POSH) – with JSON-LD
leading in terms of future adoption growth.
While the world may not be eagerly awaiting, nor particularly concerned
about, a WebID specification, having a spec that formalizes an already
widely used pattern would be beneficial.
Historically, such advice has often been disregarded in the context of
W3C specifications, leading to outcomes where developers largely ignore
these specifications, opting instead to develop broadly adopted yet
flawed solutions. This situation persists while the relevant W3C spec
remains mired in ongoing and repetitive debate.
Having been involved in this field for an extended period, I can only
offer advice based on substantial evidence and extensive experience
across various levels.
--
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
Received on Saturday, 11 November 2023 19:24:24 UTC