[esip-semantictech] Semantic Technologies Group Community Ontology Repository (COR) Use Cases & Requirements

Wed Aug 3 20:12:17 EDT 2016

Hi John,
I’ve addressed 1) from your below comments. The updated Editors DRAFT can be located at
https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html
Thanks

Dr. Lewis John McGibbney Ph.D., B.Sc.
Data Scientist II
Computer Science for Data Intensive Applications Group 398M
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

           [cid:F9B62432-7E30-4F38-9305-F501802C2F33]

 Dare Mighty Things

From: John Graybeal <jbgraybeal at mindspring.com<mailto:jbgraybeal at mindspring.com>>
Date: Tuesday, July 26, 2016 at 10:37 PM
To: Lewis John McGibbney <lewis.j.mcgibbney at jpl.nasa.gov<mailto:lewis.j.mcgibbney at jpl.nasa.gov>>, "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: Re: [esip-semantictech] Semantic Technologies Group Community Ontology Repository (COR) Use Cases & Requirements

Lewis,

What a great resource! I hope it continues to turn into a full STC document.  ReSpec looks cool too, nice to see that.

I had just a few questions/comments, the first is I think for you, and is the most essential in the short term:

1) There are two deployed semantic repository solutions hosted by ESIP; the proper name of one is the ESIP Community Ontology Repository, and the proper name of the second is the ESIP Semantic Portal. (The first based on MMI’s ORR, the second on Stanford’s BioPortal.)  Others may be forthcoming. Your document uses the term Community Ontology Repository throughout; sometimes it is clearly referring to *any* repository solution, sometimes it seems like it refers to the ESIP COR instance, and a lot of times it could be referring to that.  Can we please change the wording to make the generic references different in some way (lower case, at a minimum; but “ESIP semantic repository implementation” for example would be entirely unambiguous, capitalized or not).

2) To the STC community. I have of course worked with a number of specifications of ontology repository requirements and use cases. I wasn’t sure how these relate to this initiative — do we want to capture all requirements and use cases from any source, or just ones that fit known requirements of ESIP (and presumably EarthCube) community members, or something in between? How will we prioritize?

3) I notice there’s a 4D space-time requirement, I think this is just a place-holder — can you confirm?

john

On Jul 23, 2016, at 21:25, Mcgibbney, Lewis J (398M) via esip-semanticweb <esip-semanticweb at lists.esipfed.org<mailto:esip-semanticweb at lists.esipfed.org>> wrote:

Hi Folks,
Off the back of a productive week @ESIP Summer meeting, and particularly from our meeting on Friday, I took the initiative to bootstrap a driven effort to address the Community Ontology Repository (COR) conundrum!
Based heavily off of the Specification documents we produce over @W3C, I began working on an Editor’s DRAFT document titled 'Semantic Technologies Group Community Ontology Repository (COR) Use Cases & Requirements’ (UCR).
The document itself can be located at [0]. This (and all documentation mentioned herein) resides at a new repository I created for our Committee at [2]. If you require access and wish to help us populate UCR's then please let us know here and we can organize the contributions.
We have a landing page which describes all current working activity, this can be found at [3].
Right now the document is of course in DRAFT form and is in need of some peer review and corrections, however it is a start and I hope it can be useful for our community to clarify and move on with the COR effort.
@Tom & Beth, it would be great if we could talk this through at the next committee telecon. I have no issues talking this through and talking about people can contribute UCR’s which will be available at [2].
Was great to see many new faces this last week @ESIP. A really good crowd of people within this committee and I am glad to be part of this work as we move forward.
Thanks for now
Lewis

[0] https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html
[1] https://github.com/esipfed/stc
[2] https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html#UseCases
[3] https://esipfed.github.io/stc

Dr. Lewis John McGibbney Ph.D., B.Sc.
Data Scientist II
Computer Science for Data Intensive Applications Group 398M
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>

           <2CB3CA5F-DC06-45EF-ADDA-C49A41A8C401.png>

 Dare Mighty Things
_______________________________________________
esip-semanticweb mailing list
esip-semanticweb at lists.esipfed.org<mailto:esip-semanticweb at lists.esipfed.org>
http://lists.deltaforce.net/mailman/listinfo/esip-semanticweb

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-semanticweb/attachments/20160804/ee4bd5ca/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2CB3CA5F-DC06-45EF-ADDA-C49A41A8C401[8].png
Type: image/png
Size: 3425 bytes
Desc: 2CB3CA5F-DC06-45EF-ADDA-C49A41A8C401[8].png
URL: <http://lists.deltaforce.net/pipermail/esip-semanticweb/attachments/20160804/ee4bd5ca/attachment.png>