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

Thu Aug 4 14:44:26 EDT 2016

Hi Lewis,

I just forked https://github.com/ESIPFed/stc (at https://github.com/xdomes/
stc) with the preliminary idea of our X-DOMES team potentially contributing
is some way (then submitting pull requests as a typical workflow).

Right now, a quick question: By looking a bit more closely, seems like the
contents are already in html form. Perhaps there's some other place where
the actual "source" of the contents is located? If so, how is the output
being generated? With this information we would be able to do some local
tests before submitting any pull requests, etc.  Apologies if this
information has already been discussed (I just very recently joined the
list).

Thanks,
Carlos

On Wed, Aug 3, 2016 at 4:57 PM, Mcgibbney, Lewis J (398M) via
esip-semanticweb <esip-semanticweb at lists.esipfed.org> wrote:

> Hi Michael,
> Thanks for your updates. I’ve duly updates the document which can again be
> found at the link below
>
> https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html
>
> Would be great if people are able to send in pull requests however we can
> discuss this at our next meeting.
> Thanks again.
>
> 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
>
>
>
>  Dare Mighty Things
>
> From: "HUHNS, MICHAEL" <HUHNS at mailbox.sc.edu>
> Date: Wednesday, August 3, 2016 at 1:49 PM
> To: Lewis John McGibbney <lewis.j.mcgibbney at jpl.nasa.gov>
> Cc: "pouchard at purdue.edu" <pouchard at purdue.edu>, ESIP Semantic Web
> Cluster <esip-semanticweb at lists.esipfed.org>
> Subject: RE: Semantic Technologies Group Community Ontology Repository
> (COR) Use Cases & Requirements
>
> Hi Lewis,
>
>
>
> Thanks for initiating this document! Below and attached is a draft of
> several use cases that Line and I have constructed for the *Semantic
> Repository Implementation* (good name). I have tried to use the GitHub
> template you created. Please let me know if there is a better way for us to
> contribute our use cases. That is, should I modify the GitHub document
> directly?
>
>
>
> Cheers,
>
> Mike
>
>
>
> *Use Case 1. Browsing a Portal for a Relevant Ontology.*
>
>
>
> Suppose an earth scientist is gathering data about the properties of
> seawater, such as salinity and parts-per-million of manganese, and decides
> to record the values in a database. What should the scientist choose for
> the name of the table and the names of its columns? An appropriate ontology
> provides a standard vocabulary that relates the database to the data
> recorded by other scientists.
>
>
>
> a.      The scientist should be able to browse existing ontologies at a
> portal to find ones relevant to the scientist’s needs.
>
> b.      The scientist should be able to search the portal for concepts of
> interest.
>
>
>
>
>
> *Use Case 2. Extending and Editing an Existing Ontology.*
>
>
>
> Once an earth scientist has located an ontology in a portal that matches
> the scientist’s interest, the scientist should be able to add new domain
> concepts to the ontology and modify existing concepts for improvement or
> correction. The changed ontology should be stored as a new version and
> should not simply replace the original version.
>
>
>
>
>
> *Use Case 3. Matching Concepts among Ontologies.*
>
>
>
> Each concept in an ontology should be mapped to concepts it matches in
> other ontologies. Exact matches based on string matching of concept names
> should be provided automatically by the portal. The portal should also
> support matches entered manually.
>
>
>
>
>
> *Use Case 4. Annotating Text.*
>
>
>
> A portal should provide a means to annotate text by inserting links to
> ontology concepts into the text.
>
>
>
>
>
> *Use Case 5. Subsetting Ontologies into Projects.*
>
>
>
> If (someday) there are large numbers of ontologies in the portal, the
> portal should support a means to identify subsets of ontologies that can be
> searched and viewed separately.
>
>
>
>
>
> *Use Case 6. User Access.*
>
>
>
> A portal should provide both a GUI and a SPARQL endpoint for accessing its
> functionality and its stored ontologies and concepts.
>
>
>
>
>
> *From:* esip-semanticweb [mailto:esip-semanticweb-
> bounces at lists.esipfed.org <esip-semanticweb-bounces at lists.esipfed.org>] *On
> Behalf Of *Mcgibbney, Lewis J (398M) via esip-semanticweb
> *Sent:* Sunday, July 24, 2016 12:25 AM
> *To:* esip-semanticweb at lists.esipfed.org
> *Subject:* [esip-semantictech] Semantic Technologies Group Community
> Ontology Repository (COR) Use Cases & Requirements
>
>
>
> 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
>
>
>
>            [image: cid:B64E75D4-880E-4E68-AD66-B77E74DCB19A]
>
>
>
>  Dare Mighty Things
>
>
> _______________________________________________
> esip-semanticweb mailing list
> esip-semanticweb at lists.esipfed.org
> http://lists.deltaforce.net/mailman/listinfo/esip-semanticweb
>
>

-- 
Carlos A. Rueda, PhD
Software Engineer
Monterey Bay Aquarium Research Institute - mbari.org
carueda at mbari.org - 831-775-1929
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-semanticweb/attachments/20160804/73ad2b12/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2CB3CA5F-DC06-45EF-ADDA-C49A41A8C401[7].png
Type: image/png
Size: 3425 bytes
Desc: not available
URL: <http://lists.deltaforce.net/pipermail/esip-semanticweb/attachments/20160804/73ad2b12/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 3041 bytes
Desc: not available
URL: <http://lists.deltaforce.net/pipermail/esip-semanticweb/attachments/20160804/73ad2b12/attachment-0003.png>