Re: Proposed constraint

On 1/3/24 7:55 PM, Nathan Rixham wrote:
> The "name" field under the "@type": "Person" clearly states her name 
> as "Beena Ammanath". This is a clear and unambiguous identification of 
> the person in question.
>
>  "@type": "Person"


That isn't in dispute, since you are referring to content that resides 
in a document i.e., nothing to do with how the aforementioned entity is 
named.

Naming comprises both denotation and connotation. You can't leave out 
the denotation aspect, which has a lot to do with why this has been 
thorny for years re HTTP URIs.

As I've suggested, we can get out of this quagmire by focusing on the 
WebID Profile Document oriented specification.

IMHO, simply using the term WebID loosely, or mangling it in a recursive 
acronym (e.g, WebID and Identity Discovery [WebID]) will not solve the 
fundamental problem at hand.

Kingsley

>
> On Thu, 4 Jan 2024, 00:17 Kingsley Idehen, <kidehen@openlinksw.com> wrote:
>
>
>     On 1/3/24 6:50 PM, Nathan Rixham wrote:
>     > I would like to propose that any WebID specification authored by
>     this
>     > group must provide a testable way to determine that a WebID
>     denotes an
>     > Agent.
>     >
>     > Baked into that is is the most basic agreement we can make, that a
>     > WebID refers to an Agent, and not a pipe.
>
>
>     Hi Nathan,
>
>     I believe you are speaking, more specifically, about any WebID
>     related
>     specification where entity relationship type semantics are
>     machine-computable.
>
>     In the age of LLMs, prose constructed using natural language is
>     increasingly machine-computable :)
>
>     Related
>
>     [1]
>     https://netid-qa.openlinksw.com:8443/chat/?chat_id=s-J929kamx9sxLCMCSR4QpUsueqXQHjd3MMyVr5P1Vi4pn
>
>     -- machine-computable profile data explorations, in the age of LLMs
>
>     -- 
>     Happy New Year!
>
>     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
>
>

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