Re: WebID default serialization for WebID 2.x

On 1/21/22 7:49 PM, Melvin Carvalho wrote:
>
>
> On Sat, 22 Jan 2022 at 01:38, Kingsley Idehen <kidehen@openlinksw.com> 
> wrote:
>
>     On 1/21/22 7:09 PM, Jonas Smedegaard wrote:
>     > Quoting Sebastian Hellmann (2022-01-22 00:21:49)
>     >> Hi Jonas,
>     >>
>     >> a question: I am having trouble finding the current spec. Also
>     I can not
>     >> find anything about NetID. See more inline.
>     > Current draft of the WebID spec is this:
>     > https://www.w3.org/2005/Incubator/webid/spec/identity/
>     >
>     > NetID is a superset of WebID defined by Kingsley Idehen:
>     >
>     https://www.openlinksw.com/describe/?url=http%3A%2F%2Fdata.openlinksw.com%2Foplweb%2Fglossary-term%2FNetID%23this&graph=urn%3Adata%3Aopenlink%3Aglossary
>     <https://www.openlinksw.com/describe/?url=http%3A%2F%2Fdata.openlinksw.com%2Foplweb%2Fglossary-term%2FNetID%23this&graph=urn%3Adata%3Aopenlink%3Aglossary>
>
>
>     Hi Jonas,
>
>     Thank you!
>
>     Even I forgot about our glossary [1] :)
>
>     We can certainly flesh out additional information via said glossary.
>
>     Related Links
>
>     [1] https://github.com/OpenLinkSoftware/glossaries -- Github Repo
>
>
> FYI: There's also a stub entry for NetID in the RWW CG wiki:
>
> https://www.w3.org/community/rww/wiki/NetID
>
> If there was desire to flesh that out and/or translate it into a spec, 
> that could be done too


Hi Melvin,

None whatsoever on my part personally, or indirectly via OpenLink.

These endeavors don't amount to anything, in my vast experience with RDF 
and Linked Data principles.

Building useful tools using "best practices" is what works. Once the 
tools are in place, the journey to de facto and final standard begins.

Specs first, is back to front, in my experience and humble opinion.

Software Engineers are still engineers at heart i.e., the need to get 
stuff done, on budget, using a high degree of pragmatism.

As you know, HTML didn't trigger the Web explosion because every HTML 
user read and understood the HTML specs. It exploded because Mosaic 
produced a Browser with a "View Source" feature. Early adopters used 
copy & paste patterns to drive the early Web explosion.

RDF and deployment using Linked Data principles didn't have a "View 
Source" feature equivalent circa 2007. Thus, we ended up on a protracted 
journey with stealthy results that still lack broader market 
understanding and appreciation.

Related

[1] https://twitter.com/kidehen/status/1481295845257617412 -- Thread 
about Web Data Commons which adds a new dimension to the stealthy growth 
of RDF deployed using Linked Data principles


-- 
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