[esip-semantictech] Add Sweet Ontology to SDWBP 6.2 Expressing Spatial Data

[Mcgibbney, Lewis J (398M)]

Thank you for clarifying Tom.

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:7D610922-A7BA-4C7B-86E2-257011D3B88E]

 Dare Mighty Things

From: Tom Narock <tnarock at marymount.edu<mailto:tnarock at marymount.edu>>
Date: Sunday, April 10, 2016 at 12:05 PM
To: John Graybeal <jbgraybeal at mindspring.com<mailto:jbgraybeal at mindspring.com>>
Cc: Line C Pouchard <pouchard at purdue.edu<mailto:pouchard at purdue.edu>>, Lewis John McGibbney <lewis.j.mcgibbney at jpl.nasa.gov<mailto:lewis.j.mcgibbney at jpl.nasa.gov>>, ESIP Semantic Web Cluster <esip-semanticweb at lists.esipfed.org<mailto:esip-semanticweb at lists.esipfed.org>>, soren scott <sorenscott at gmail.com<mailto:sorenscott at gmail.com>>
Subject: Re: [esip-semantictech] Add Sweet Ontology to SDWBP 6.2 Expressing Spatial Data

Hi all,

Yes, these discussions are all referring to the same SWEET ontology. JPL provides the physical infrastructure for hosting and maintenance of the SWEET ontology. As referred to in Peter’s statements, ESIP had worked up a policy to handle the governance of the ontology and any change/update requests, which could then be passed to Thomas Huang at JPL for implementation.

The procedure had a lot of effort and planning behind it, but a few challenges have come up in the past year or so. JPL’s local governance policy has meant that SWEET is not completely open source and there have been related challenges in capturing feedback and requests from the community.

Thomas and Lewis are currently working at JPL to completely open source SWEET so it can truly become a community-wide resource and they are continuing to promote it to the community. In conjunction with them, the ESIP Semantic Technologies committee is thinking through additional ways to capture feedback from the community on SWEET.

Hope this helps clear up some of the confusion. Thanks to Peter, Thomas, and many others, SWEET has been steadily transitioning into a completely open community ontology. We’re continuing to work out some details and find the most effective and efficient way to govern this ontology.

Tom


On Apr 9, 2016, at 7:17 PM, John Graybeal via esip-semanticweb <esip-semanticweb at lists.esipfed.org<mailto:esip-semanticweb at lists.esipfed.org>> wrote:

Line, all,

In one or two previous ESIP forums, a statement something like this was made: "ESIP has agreed to take responsibility for managing the SWEET ontologies." The first time I heard it was a long time ago, I think well before last summer's meeting.

Thomas Huang's email says the current official home for SWEET ontologies is still JPL.

Careful parsing of the exact statements (as opposed to my vague memory of them) might reveal there is no conflict. But it sure is confusing.

john


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

On Apr 8, 2016, at 12:22, Pouchard, Line C via esip-semanticweb <esip-semanticweb at lists.esipfed.org<mailto:esip-semanticweb at lists.esipfed.org>> wrote:

Soren:
I don’t understand what you mean by the question “is it the same SWEET”?  Can you please clarify?
Line

From: "sorenscott at gmail.com<mailto:sorenscott at gmail.com>" <sorenscott at gmail.com<mailto:sorenscott at gmail.com>>
Date: Thursday, April 7, 2016 at 3:09 PM
To: Line Pouchard <pouchard at purdue.edu<mailto:pouchard at purdue.edu>>
Cc: "Mcgibbney, Lewis J (398M)" <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] Fwd: FW: Add Sweet Ontology to SDWBP 6.2 Expressing Spatial Data

I'm glad you mentioned that, Line. Peter mentioned an existing governance policy for SWEET updates at ESIP and that changes had occurred at the DC meeting. So are we talking the same SWEET now? Would be nice to clarify.

Cheers,
Soren

On Wednesday, April 6, 2016, Pouchard, Line C via esip-semanticweb <esip-semanticweb at lists.esipfed.org<mailto:esip-semanticweb at lists.esipfed.org>> wrote:
Dear all:

I agree that Sweet has been and continues to be an important resource for the ESIP community.  It is hosted in the ESIP Semantic Portal, and as one of the Testbed projects, we provided rdf mappings to other ontologies.

Through the years I have heard at ESIP that there were very good modules but also problematic constructs in SWEET without getting details on what these issues are.

I would suggest that we start by just building a list of what these are, an ESIP wiki page may be enough to get started.  This also helps in sorting out the priorities and getting a quick overview of the issues.

Line

Sent from my iPhone
Line Pouchard
Purdue University Libraries

> On Apr 6, 2016, at 6:51 AM, Mcgibbney, Lewis J (398M) via esip-semanticweb <esip-semanticweb at lists.esipfed.org<javascript:;>> wrote:
>
> Hi John,
> Answers inline
>
>
> On 4/5/16, 9:00 AM, "esip-semanticweb on behalf of
> esip-semanticweb-request at lists.esipfed.org<javascript:;>"
> <esip-semanticweb-bounces at lists.esipfed.org<javascript:;> on behalf of
> esip-semanticweb-request at lists.esipfed.org<javascript:;>> wrote:
>
>>
>> Message: 2
>> Date: Mon, 4 Apr 2016 22:25:25 -0700
>> From: John Graybeal <jbgraybeal at mindspring.com<javascript:;>>
>> To: "esip-semanticweb at lists.esipfed.org<javascript:;>"
>>    <esip-semanticweb at lists.esipfed.org<javascript:;>>
>> Subject: Re: [esip-semantictech] Fwd: FW: Add Sweet Ontology to SDWBP
>>    6.2    Expressing Spatial Data
>> Message-ID: <39C0E4A6-CECF-4032-8408-D4D94D3E5D1F at mindspring.com<javascript:;>>
>> Content-Type: text/plain; charset=windows-1252
>>
>> This may be sideline-cheering at best, but I want to offer my support for
>> anything that can be done to advance SWEET. It has always been a
>> marvelous resource in my book, and I would love to see it (and its
>> founder, by implication) get the respect I think it deserves.
>
> Agreed!
>
>>
>> I think especially valuable is the idea of adding issues to an issue
>> tracker, so that the community can see and comment upon them openly.
>
> +1
>
>>
>> Perhaps if the issue tracker can get started, community members who had
>> such concerns can volunteer them for entry in the tracker. Even if they
>> are assessed as not valid, it will be helpful to have them documented,
>> IMHO.
>
> I am over attending ESDSWG meeting at Goddard this week and hope to meet
> with Thomas Huang to discuss the concerns and observation that there is an
> entire community requirement for SWEET to not stagnate. People do care
> about it but it seems that not much work is/can be done due to where it is
> hosted and an ill defined contribution model. This needs to be addressed.
> Where there¹s smoke there¹s fire.
>
>>
>> Finally, although I think SWEET already has a rehosting solution, I would
>> like to offer whatever MMI's repositories can do to support addressing
>> some of Simon's concerns. I have a notional internet-based scheme in mind
>> that could make the original SWEET URIs resolvable, even as they are
>> hosted in an MMI (or other URI-resolving) repository. If that notion
>> might be a useful contribution, I'd be happy to share it. (Warning: It's
>> not fully vetted. Could use help with that.)
>
> That sounds excellent. I also see no reason that this ESIP community could
> not essentially host the ontology and the resolve service. It would be
> great if there were more long term curators of SWEET. Right now the list
> of stewards seems extremely thinŠ due to this many past and present users
> seem to be looking elsewhere.
> Lewis
>
> _______________________________________________
> esip-semanticweb mailing list
> esip-semanticweb at lists.esipfed.org<javascript:;>
> http://lists.deltaforce.net/mailman/listinfo/esip-semanticweb
_______________________________________________
esip-semanticweb mailing list
esip-semanticweb at lists.esipfed.org<javascript:;>
http://lists.deltaforce.net/mailman/listinfo/esip-semanticweb


--

Soren Scott
Research Coder
The Ronin Institute for Independent Scholarship
soren.scott at ronininstitute.org<mailto:soren.scott at ronininstitute.org>

just a head's up - taking a bit of a sabbatical so if i don't
get back to you right away, no worries.

_______________________________________________
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

_______________________________________________
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/20160411/662884be/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2CB3CA5F-DC06-45EF-ADDA-C49A41A8C401[3].png
Type: image/png
Size: 3425 bytes
Desc: 2CB3CA5F-DC06-45EF-ADDA-C49A41A8C401[3].png
URL: <http://lists.deltaforce.net/pipermail/esip-semanticweb/attachments/20160411/662884be/attachment-0001.png>