[esip-semantictech] Fwd: FW: Add Sweet Ontology to SDWBP 6.2 Expressing Spatial Data
soren scott
sorenscott at gmail.com
Thu Apr 7 15:09:14 EDT 2016
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> 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
just a head's up - taking a bit of a sabbatical so if i don't
get back to you right away, no worries.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-semanticweb/attachments/20160407/89b7da58/attachment.html>
More information about the esip-semanticweb
mailing list