Hi all,
I've just created a GSIP for the support of AuthorityURL and
Identifier elements in WMS GetCapabilities documents.
Here's the GSIP URL:
<http://geoserver.org/display/GEOS/GSIP+65+-+Support+for+WMS+AuthorityURL+and+Identifier>
Patches linked from the proposal. Thoughts and feedback welcome.
Thanks,
Gabriel.
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Nice proposal Gabriel, thorough and well written. One thing I want to bring up relates to the recent keyword proposal. In that proposal we added a new interface (KeywordInfo) but instead of adding KeywordInfoImpl and updates CatalogFactory i just added a class Keyword, meant to be instantiated directly. Part of the reason I did this was to facilitate the move from String to KeywordInfo for client code.
I wonder if the same pattern should be taken for all “non top level” config/catalog objects. And by non top level i mean objects/classes that are not added directly to the catalog/config.
Anyways, not a blocker by any means for this proposal… although I would like to see things get consistent but since i am the one who broke the pattern I am willing to put in the time to fix it 
+1 on the proposal.
On Mon, Oct 17, 2011 at 10:15 PM, Gabriel Roldan <groldan@anonymised.com> wrote:
Hi all,
I’ve just created a GSIP for the support of AuthorityURL and
Identifier elements in WMS GetCapabilities documents.Here’s the GSIP URL:
<http://geoserver.org/display/GEOS/GSIP+65±+Support+for+WMS+AuthorityURL+and+Identifier>Patches linked from the proposal. Thoughts and feedback welcome.
Thanks,
Gabriel.–
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Tue, Oct 18, 2011 at 6:15 AM, Gabriel Roldan <groldan@anonymised.com…> wrote:
Hi all,
I’ve just created a GSIP for the support of AuthorityURL and
Identifier elements in WMS GetCapabilities documents.Here’s the GSIP URL:
<http://geoserver.org/display/GEOS/GSIP+65±+Support+for+WMS+AuthorityURL+and+Identifier>Patches linked from the proposal. Thoughts and feedback welcome.
Hmmm… I’ll keep it short: +1
:-p
Cheers
Andrea
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
Thanks both for the quick reaction.
One remaining question is whether we want to implement the forwards
compatibility proposal or not. It is not a blocker by any means, we
can go without it, but I just wonder whether it would even be a good
precedent for future changes. That is, there is the possibility of
being forward comatible, I just can't decide whether it's a good thing
or not. Perhaps you can think of any gotcha or why it wouldn't be
convenient?
TIA,
Gabriel.
On Tue, Oct 18, 2011 at 11:20 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:
On Tue, Oct 18, 2011 at 6:15 AM, Gabriel Roldan <groldan@anonymised.com> wrote:
Hi all,
I've just created a GSIP for the support of AuthorityURL and
Identifier elements in WMS GetCapabilities documents.Here's the GSIP URL:
<http://geoserver.org/display/GEOS/GSIP+65+-+Support+for+WMS+AuthorityURL+and+Identifier>
Patches linked from the proposal. Thoughts and feedback welcome.
Hmmm... I'll keep it short: +1
:-p
Cheers
Andrea--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech leadVia Poggio alle Viti 1187
55054 Massarosa (LU)
Italyphone: +39 0584 962313
fax: +39 0584 962313http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf-------------------------------------------------------
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
On Tue, Oct 18, 2011 at 10:48 AM, Justin Deoliveira
<jdeolive@anonymised.com> wrote:
Nice proposal Gabriel, thorough and well written. One thing I want to bring
up relates to the recent keyword proposal. In that proposal we added a new
interface (KeywordInfo) but instead of adding KeywordInfoImpl and updates
CatalogFactory i just added a class Keyword, meant to be instantiated
directly. Part of the reason I did this was to facilitate the move from
String to KeywordInfo for client code.
I wonder if the same pattern should be taken for all "non top level"
config/catalog objects. And by non top level i mean objects/classes that are
not added directly to the catalog/config.
That's a really good point. I'm willing to get rid of the
CatalogFactory additions for this proposal in order to defer the
discussion about instantiation "value types" (not *Info and hence no
id, meaning they're subject to a containment relationship), so that if
we eventually decide to go that route these additions are non
disruptive, or if we decide the opposite it's easier to add the
factory methods at a later stage.
Will update patch an proposal accordingly.
Cheers,
Gabriel
Anyways, not a blocker by any means for this proposal... although I would
like to see things get consistent but since i am the one who broke the
pattern I am willing to put in the time to fix it
+1 on the proposal.On Mon, Oct 17, 2011 at 10:15 PM, Gabriel Roldan <groldan@anonymised.com>
wrote:Hi all,
I've just created a GSIP for the support of AuthorityURL and
Identifier elements in WMS GetCapabilities documents.Here's the GSIP URL:
<http://geoserver.org/display/GEOS/GSIP+65+-+Support+for+WMS+AuthorityURL+and+Identifier>
Patches linked from the proposal. Thoughts and feedback welcome.
Thanks,
Gabriel.--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
On Tue, Oct 18, 2011 at 1:41 PM, Gabriel Roldan <groldan@anonymised.com> wrote:
Thanks both for the quick reaction.
One remaining question is whether we want to implement the forwards
compatibility proposal or not. It is not a blocker by any means, we
can go without it, but I just wonder whether it would even be a good
precedent for future changes. That is, there is the possibility of
being forward comatible, I just can’t decide whether it’s a good thing
or not. Perhaps you can think of any gotcha or why it wouldn’t be
convenient?
Interesting approach… Obviously being forward compatible would be great… but I wonder if we will start getting into revision hell… since various changes will only be forward compatible after a paritcular revision. Whereas our backward compatibility story is pretty clear. Anyways, no strong option… i will leave it to whether to implement it hear… applying it across the board moving forward will probably require some more discussion though.
TIA,
Gabriel.On Tue, Oct 18, 2011 at 11:20 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:On Tue, Oct 18, 2011 at 6:15 AM, Gabriel Roldan <groldan@anonymised.com> wrote:
Hi all,
I’ve just created a GSIP for the support of AuthorityURL and
Identifier elements in WMS GetCapabilities documents.Here’s the GSIP URL:
<http://geoserver.org/display/GEOS/GSIP+65±+Support+for+WMS+AuthorityURL+and+Identifier>
Patches linked from the proposal. Thoughts and feedback welcome.
Hmmm… I’ll keep it short: +1
:-p
Cheers
Andrea–
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech leadVia Poggio alle Viti 1187
55054 Massarosa (LU)
Italyphone: +39 0584 962313
fax: +39 0584 962313http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
–
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On Wed, Oct 19, 2011 at 10:45 AM, Justin Deoliveira
<jdeolive@anonymised.com> wrote:
Interesting approach... Obviously being forward compatible would be great...
but I wonder if we will start getting into revision hell... since various
changes will only be forward compatible after a paritcular
revision. Whereas our backward compatibility story is pretty clear. Anyways,
no strong option... i will leave it to whether to implement it hear...
applying it across the board moving forward will probably require some more
discussion though.
Agreed. So I'll go ahead (once/if I get enough +1`s) without it, and
keep it in mind as a possible approach if need be in the future.
Thanks,
Gabriel
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Gabriel,
the proposal is good and the functionality is nice to have other than required for Inspire … what it’s not very clear to me if we are going to save values on MetadataMap or not for backward compatibility.
In any case +1 on my side too.
Alessio.
Ing. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: (+39) 0584 96.23.13
fax: (+39) 0584 96.23.13
mobile:(+39) 331 62.33.686
On Wed, Oct 19, 2011 at 5:32 PM, Gabriel Roldan <groldan@anonymised.com> wrote:
On Wed, Oct 19, 2011 at 10:45 AM, Justin Deoliveira
<jdeolive@anonymised.com> wrote:Interesting approach… Obviously being forward compatible would be great…
but I wonder if we will start getting into revision hell… since various
changes will only be forward compatible after a paritcular
revision. Whereas our backward compatibility story is pretty clear. Anyways,
no strong option… i will leave it to whether to implement it hear…
applying it across the board moving forward will probably require some more
discussion though.Agreed. So I’ll go ahead (once/if I get enough +1`s) without it, and
keep it in mind as a possible approach if need be in the future.Thanks,
Gabriel–
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
On Thu, Oct 20, 2011 at 1:23 PM, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:
Gabriel,
the proposal is good and the functionality is nice to have other than required for Inspire … what it’s not very clear to me if we are going to save values on MetadataMap or not for backward compatibility.
we do save them in MetadataMap for the 2.1.x series, yes. On the 2.2.x+ series we have the serialized form as normal attributes and support for reading the 2.1.x serialized form out of the metadata map in case you’re upgrading.
In any case +1 on my side too.
Thanks! with that I think the proposal is good to know. Commits coming.
Cheers,
Gabriel
Alessio.
Ing. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italyphone: (+39) 0584 96.23.13
fax: (+39) 0584 96.23.13
mobile:(+39) 331 62.33.686http://www.geo-solutions.it
http://geo-solutions.blogspot.com
http://www.linkedin.com/in/alessiofabiani
http://twitter.com/geosolutions_itOn Wed, Oct 19, 2011 at 5:32 PM, Gabriel Roldan <groldan@anonymised.com> wrote:
On Wed, Oct 19, 2011 at 10:45 AM, Justin Deoliveira
<jdeolive@anonymised.com01…> wrote:Interesting approach… Obviously being forward compatible would be great…
but I wonder if we will start getting into revision hell… since various
changes will only be forward compatible after a paritcular
revision. Whereas our backward compatibility story is pretty clear. Anyways,
no strong option… i will leave it to whether to implement it hear…
applying it across the board moving forward will probably require some more
discussion though.Agreed. So I’ll go ahead (once/if I get enough +1`s) without it, and
keep it in mind as a possible approach if need be in the future.Thanks,
Gabriel–
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
+1.
Gabriel, this is necessary functionality and you appear to have addressed all the issues.
I don't think we guarantee that data directories used on 2.2 will work with 2.1. I would tend to avoid forward compatibility as it would set an awkward precedent. I am however comfortable with all of the approaches in your proposal.
As an aside, while we are storing JSON in XML, which I find inherently amusing, I thought I should mention JSONx, an XML encoding for JSON:
http://tools.ietf.org/html/draft-rsalz-jsonx-00
http://www.ibm.com/developerworks/xml/library/x-db2JSONpt1/
What a tangled web.
Kind regards,
Ben.
On 18/10/11 12:15, Gabriel Roldan wrote:
Hi all,
I've just created a GSIP for the support of AuthorityURL and
Identifier elements in WMS GetCapabilities documents.Here's the GSIP URL:
<http://geoserver.org/display/GEOS/GSIP+65+-+Support+for+WMS+AuthorityURL+and+Identifier>Patches linked from the proposal. Thoughts and feedback welcome.
Thanks,
Gabriel.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
Thanks Ben.
On Thu, Oct 20, 2011 at 11:13 PM, Ben Caradoc-Davies
<Ben.Caradoc-Davies@anonymised.com> wrote:
+1.
Gabriel, this is necessary functionality and you appear to have addressed
all the issues.I don't think we guarantee that data directories used on 2.2 will work with
2.1. I would tend to avoid forward compatibility as it would set an awkward
precedent. I am however comfortable with all of the approaches in your
proposal.
agreed. That was withdrawn.
As an aside, while we are storing JSON in XML, which I find inherently
amusing, I thought I should mention JSONx, an XML encoding for JSON:
http://tools.ietf.org/html/draft-rsalz-jsonx-00
http://www.ibm.com/developerworks/xml/library/x-db2JSONpt1/What a tangled web.
indeed!
best,
Gabriel.
Kind regards,
Ben.
Hello,
I'd like to give some feedback for the current implementation, from a
users point of view ...
If the user has defined an incorrect (not malformed) URL, its not
possible to add other identifiers. The user doesn't get any feedback,
that the URL is invalid, properly is possible to add a field
validation (leave field and prompt an error message right below,
disable dependent actions/buttons, links)?
Cheers,
Frank
2011/10/21 Gabriel Roldan <groldan@anonymised.com>:
Thanks Ben.
On Thu, Oct 20, 2011 at 11:13 PM, Ben Caradoc-Davies
<Ben.Caradoc-Davies@anonymised.com> wrote:+1.
Gabriel, this is necessary functionality and you appear to have addressed
all the issues.I don't think we guarantee that data directories used on 2.2 will work with
2.1. I would tend to avoid forward compatibility as it would set an awkward
precedent. I am however comfortable with all of the approaches in your
proposal.agreed. That was withdrawn.
As an aside, while we are storing JSON in XML, which I find inherently
amusing, I thought I should mention JSONx, an XML encoding for JSON:
http://tools.ietf.org/html/draft-rsalz-jsonx-00
http://www.ibm.com/developerworks/xml/library/x-db2JSONpt1/What a tangled web.
indeed!
best,
Gabriel.Kind regards,
Ben.------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@anonymised.com Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Hi Frank,
good suggestions. Would you create a jira ticket for it and assign it to me?
TIA,
Gabriel
On Fri, Oct 21, 2011 at 5:30 PM, Frank Gasdorf
<fgdrf@anonymised.com> wrote:
Hello,
I'd like to give some feedback for the current implementation, from a
users point of view ...If the user has defined an incorrect (not malformed) URL, its not
possible to add other identifiers. The user doesn't get any feedback,
that the URL is invalid, properly is possible to add a field
validation (leave field and prompt an error message right below,
disable dependent actions/buttons, links)?Cheers,
Frank2011/10/21 Gabriel Roldan <groldan@anonymised.com>:
Thanks Ben.
On Thu, Oct 20, 2011 at 11:13 PM, Ben Caradoc-Davies
<Ben.Caradoc-Davies@anonymised.com> wrote:+1.
Gabriel, this is necessary functionality and you appear to have addressed
all the issues.I don't think we guarantee that data directories used on 2.2 will work with
2.1. I would tend to avoid forward compatibility as it would set an awkward
precedent. I am however comfortable with all of the approaches in your
proposal.agreed. That was withdrawn.
As an aside, while we are storing JSON in XML, which I find inherently
amusing, I thought I should mention JSONx, an XML encoding for JSON:
http://tools.ietf.org/html/draft-rsalz-jsonx-00
http://www.ibm.com/developerworks/xml/library/x-db2JSONpt1/What a tangled web.
indeed!
best,
Gabriel.Kind regards,
Ben.------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@anonymised.com Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.