[esip-semantictech] [PROPOSAL] Create a Linked Data-as-a-Service (LDaaS) Service for COR

Thu Jan 10 11:38:00 EST 2019

Couple of thoughts here Lewis.  I love the enthusiasm and direction of the work and proposals, very gratifying and appropriate.

I think people will get a little confused about how LDaaS is different than a COR API (which exists). I can see the answer in broad terms but my brain needs a sharper hook to hang onto.  Also, be aware there is an initiative in Europe to provide a common API service across multiple repositories. I don’t think either of these points should discourage your vision, just inform it slightly.

I think it would be great if you could be at US2TS this year to talk about these products and your vision for LDaaS. It’s a big opportunity for connections and for learning state of the US scene, and how COR might fit. (I’m not yet sure I can make it, quite likely I can not, unfortunately.)

also for advancing the auto-notification processing in COR, thanks to you and Carlos both.

Regarding "I feel that there is much more we could be doing with COR to enable more widespread use of vocabularies and ontologies in knowledge-based systems.”: Yes, I live life with that feeling. :-)  
- The piece I think is most needed are tools that make it simple to do high value things: converting vocabularies to ontologies (COR has most of that, its SKOS format could be updated for current best practices though); use a vocabulary or a branch of one in a web form or data system form; evaluate the completeness and quality of the vocabulary and its descriptive metadata; convert a resource to an Excel spreadsheet or graphical view for people who value that.
- The other (!) most-needed piece is getting a lot of vocabularies into COR, so that it is a go-to resource. (Sooner or later an organization will propose and establish a major repository of earth science vocabularies, and if COR has the lead in that it may be adopted for that project.)  
- Oh, and a key COR  development effort is to make the important resources stand out, so the testing and in-progress resources are no longer swamping the list. (See “evaluate completeness and quality” item.)

And finally, re Mark’s comment to coordinate with NERC: Yes, absolutely. I’ve coordinated with them on many occasions, and at least once gotten permission to ‘republish’ their resources, *as soon as we have the ability to update our resources automatically*.  We’ll need to renew that conversation before trying to do it—I know Roy is emeritus but I don’t think he’s still king ;-) —but perhaps we are getting close.  (I would have wished for the resource to go into MMI ORR, but now, not so sure. Maybe the COR committee can discuss options for MMI ORR vis-a-vis COR in this year 2019.)

John

---------------------------------------
John Graybeal
jbgraybeal at mindspring.com
650-450-1853
skype: graybealski
linkedin: http://www.linkedin.com/in/johngraybeal/

> On Jan 8, 2019, at 11:14, Mcgibbney, Lewis J (398M) via esip-semanticweb <esip-semanticweb at lists.esipfed.org> wrote:
> 
> Hi Folks,
> Based on positive feedback, I went ahead and made a wiki page to capture information as the concept matures. So far the initiative has attracted interest from two parties so there is certainly scope to prototype the LDaaS concept.
> I will also note here, that the LDaaS effort aligns with numerous items outlined within the Semantic Technologies Roadmap [1] presented to us by Peter Fox back in August, 2018.
> As we’ve not done a great deal with the treasure trove of information the Roadmap documents provide us with, I hope that the LDaaS effort can address that.
> Feedback appreciated, hope to see lots of you at ESIP next week ☺
> Lewis
>  
> [0] https://wiki.esipfed.org/index.php/LDaaS <https://wiki.esipfed.org/index.php/LDaaS>
> [1] http://wiki.esipfed.org/index.php/File:Semanticwebinfusionroadmap1.71gapanalysis-2018.pptx <http://wiki.esipfed.org/index.php/File:Semanticwebinfusionroadmap1.71gapanalysis-2018.pptx>
>  
>  
> Dr. Lewis John McGibbney Ph.D., B.Sc.
> Data Scientist II
> Computer Science for Data Intensive Applications Group (398M)
> Instrument Software and Science Data Systems Section (398)
> Jet Propulsion Laboratory
> California Institute of Technology 
> 4800 Oak Grove Drive
> Pasadena, California 91109-8099
> Mail Stop : 158-256C
> Tel:  (+1) (818)-393-7402
> Cell: (+1) (626)-487-3476
> Fax:  (+1) (818)-393-1190
> Email: lewis.j.mcgibbney at jpl.nasa.gov <mailto:lewis.j.mcgibbney at jpl.nasa.gov>
> ORCID: orcid.org/0000-0003-2185-928X <http://orcid.org/0000-0003-2185-928X>
>  
>            <image001.png>
>  
>  Dare Mighty Things
>  
> From: "Mcgibbney, Lewis J (398M)" <Lewis.J.McGibbney at jpl.nasa.gov <mailto:Lewis.J.McGibbney at jpl.nasa.gov>>
> Date: Thursday, January 3, 2019 at 3:16 AM
> To: "esip-semanticweb at lists.esipfed.org <mailto:esip-semanticweb at lists.esipfed.org>" <esip-semanticweb at lists.esipfed.org <mailto:esip-semanticweb at lists.esipfed.org>>
> Subject: [PROPOSAL] Create a Linked Data-as-a-Service (LDaaS) Service for COR
>  
> Hi Folks,
>  
> I would like to plant a seed for discussion over the next month or so which would enable the Semantic Technologies Committee, through the Community Ontology Repository (COR) to provide an LDaaS service to the ESSI community.
>  
> Why???
> COR enables data publishers to publish structured data so that it can be interlinked and become more useful. Right now, it is mostly being used as a repository for ontologies and other vocabularies and I personally believe that a lot of people do not know what they can do with it or that they do not understand how it could be useful for them. I feel that there is much more we could be doing with COR to enable more widespread use of vocabularies and ontologies in knowledge-based systems.
>  
> What is LDaaS and how would it work?
> Put simply LDaaS would be a hosted service we would offer which would provide the underlying software stack and networking requirements to enable data providers to publish structured data as linked data using their own URI’s. Either they purchase the URI they wish to use or else we create one for them.
> SWEET is the primary example of how LDaaS would work
> ·         We choose and purchased a top-level domain namespace e.g. http://sweetontology.net <http://sweetontology.net/>
> ·         We put in place the HTTP redirects such that any requests to the above namespace resolve to the COR-service which both hosts and serves the SWEET resources.
> ·         The COR service also sits in the background enabling applications to query linked data resources via a standards-based query language over HTTP (SPARQL-over-HTTP). Additionally it provides a lot of additional functionality such as content negotiation.
> We (Carlos and a few others who have been working on COR in the background) have documented how this works in practice at [0]. Essentially for each new resource which comes in, we replicate the process at [0] which subsequently streamlines the publication process for data providers. They can then interact with the data as they would if they had provisioned a fully managed, correctly networked linked data software stack.
>  
> In my opinion this takes the concept of COR as a community ontology repository to something entirely new e.g. we are going way beyond the ‘repository’ portion of the statement.
>  
> So, what are the proposed steps forward?
> We run a small pilot which would demonstrate the capability. Between now and the upcoming ESIP Meeting in around 2 weeks’ time we should identify a suitable data provider/customer who would be interested in using a hosted service as described above. 
> Once we have proved the concept, we can make a formal announcement to the wider ESIP community and also to the following arenas
> ·         Ruth Duerr - EarthCube Semantics Working Group
> ·         Soren Scott - RDA Provenance Working Group
> ·         Stephen Richard - RDA Vocab Services, Terminology IG, and DataType Registry Working Groups
> ·         Stace Beaulieu - USGS CDI Semantic Web Working Group
> ·         Adam Shepherd - The Ontolog Community
> ·         Lewis McGibbney <http://wiki.esipfed.org/index.php?title=User:Lmcgibbn&action=edit&redlink=1> - Spatial Data on the Web (SDW) <http://w3c.github.io/sdw/%7CW3C+OGC>
> ·         Bhaskar Ramachandran - The International Association for Ontology and its Applications (IAOA), http://www.iaoa.org/ <http://www.iaoa.org/>
> ·         Pascal Hitzler - Ontology Design & Patterns Association
> ·         John Graybeal - Lead of MMI ORR, BioPortal projects
> Are there any comments on the above? Thank you for your consideration and for reading through.
> Lewis
>  
> [0] https://github.com/ESIPFed/sweet/wiki/sweetontology.net <https://github.com/ESIPFed/sweet/wiki/sweetontology.net>
>  
> Dr. Lewis John McGibbney Ph.D., B.Sc.
> Data Scientist II
> Computer Science for Data Intensive Applications Group (398M)
> Instrument Software and Science Data Systems Section (398)
> Jet Propulsion Laboratory
> California Institute of Technology 
> 4800 Oak Grove Drive
> Pasadena, California 91109-8099
> Mail Stop : 158-256C
> Tel:  (+1) (818)-393-7402
> Cell: (+1) (626)-487-3476
> Fax:  (+1) (818)-393-1190
> Email: lewis.j.mcgibbney at jpl.nasa.gov <mailto:lewis.j.mcgibbney at jpl.nasa.gov>
> ORCID: orcid.org/0000-0003-2185-928X <http://orcid.org/0000-0003-2185-928X>
>  
>            <image002.png>
>  
>  Dare Mighty Things
> _______________________________________________
> esip-semanticweb mailing list
> esip-semanticweb at lists.esipfed.org <mailto:esip-semanticweb at lists.esipfed.org>
> https://lists.esipfed.org/mailman/listinfo/esip-semanticweb <https://lists.esipfed.org/mailman/listinfo/esip-semanticweb>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-semanticweb/attachments/20190110/b83e7b4b/attachment-0001.html>