Re: Use Cases for the Temporal Read-Write Web

On 5/20/21 11:15 AM, Melvin Carvalho wrote:
>
>
> On Thu, 20 May 2021 at 17:04, Kingsley Idehen <kidehen@openlinksw.com
> <mailto:kidehen@openlinksw.com>> wrote:
>
>     On 5/20/21 7:52 AM, Melvin Carvalho wrote:
>>     Continuing previous discussion, while noting we've not fully
>>     defined a temporal read-write web, I wanted to use this thread to
>>     capture use cases that come up, and to allow adding to them
>>
>>     *Use-Case Example - Augmenting Music Data [Creator Conundurum]*
>>     Author: Kingsley Idehen
>>
>>     Problem: Creator Conundurum
>>
>>     I *painstakingly* put together an RDF document that provides
>>     details about the Beatles that's missing from DBpedia, Wikidata,
>>     and Musicbrainz such as:
>>
>>     1. Song Instrumentalists
>>
>>     2. Recording Location
>>
>>     3. Song Producer
>>
>>     4. Instruments per song
>>
>>     5. etc..
>>
>>     I want to publish this to the Web, but not for $0.00 since there
>>     is a serious opportunity cost associated with the production of
>>     the work in question.
>>
>>     Challenges:
>>
>>     1. How do I express and assert ownership?
>>
>>     1. How do I track use over time and receive appropriate monetary
>>     credits?
>>
>>     Blockchain offers me NFTs as a potential ownership assertion
>>     mechanism. It also offers an ability for me to track credits due
>>     over time via a Smart Contract.
>>
>>     Issues with Blockchain:
>>
>>     1. Which of the zillion tokens + platform combos to I choose from?
>>     2. Ultimately, do any of these actually scale to the levels
>>     required?
>>
>>     **
>>     **
>>     **Use-Case Example - Step Counter
>>     **
>>     Author: Melvin Carvalho
>>
>>     Let's say I want to make a simple step counter.  It hooks into my
>>     smart watch.  It hooks into my phone pedometer, my treadmill, a
>>     bunch of stuff running at the same time.  It then wants to store
>>     my data, and ensure that all devices can write to the store
>>     without conflicts.  Also, importantly the store might go down in
>>     a DB or a pod or git, and it should just be able to come back up
>>     elsewhere, ditto the bot that is managing all of this.
>>
>>
>>     Feel free to add use cases, we could then transfer them to the
>>     wiki or into a document
>
>
>     Ideally, we should describe use-cases in structured form and save
>     to a generally accessible data space on the Web. This could even
>     happen via github.
>
>     A Use-Case have the following attributes:
>
>     1. Problem
>     2. Solution
>     3. Creator
>     4. Related Items
>
>     In a sense its similar to Questions and Answers i.e., a Question
>     is associated with "Accepted Answers"  and "Suggested Answers" .
>
>     Thoughts?
>
>
> Sounds good!  We dont have a github area, right now.  Perhaps the w3c
> could make a repo for us, but I'm not sure who to ask about that ...
>  


Can we not create our own?


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