I have put together a quick proposal and patch to allow for supporting specifying metadata on service and layer keywords. The current proposal is here:
I have put together a quick proposal and patch to allow for supporting specifying metadata on service and layer keywords. The current proposal is here:
The proposal makes sense and seems rather complete.
The backwards compatibility strategy is also good, though I don’t see escaping for
the separators: are they invalid characters in the keyword, language or vocabulary
expressions?
Besides this issue, +1
Thinking out loud, expression a keyword becomes more work, might be interesting
to have a way to copy them from another layer.
I think others have expressed a desire to have existing layers act as “templates”
for new layers. Anyways, just a random thought, not actually related to the
proposal
Cheers
Andrea
–
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
I have put together a quick proposal and patch to allow for supporting specifying metadata on service and layer keywords. The current proposal is here:
The proposal makes sense and seems rather complete.
The backwards compatibility strategy is also good, though I don’t see escaping for
the separators: are they invalid characters in the keyword, language or vocabulary
expressions?
Ahh good point. As far as WMS and OWS go they can be arbitrary strings to @ and ; are valid. Will escape them.
Besides this issue, +1
Thinking out loud, expression a keyword becomes more work, might be interesting
to have a way to copy them from another layer.
I think others have expressed a desire to have existing layers act as “templates”
for new layers. Anyways, just a random thought, not actually related to the
proposal
Yeah that is a cool idea… template layers like we have template styles… would be a fun one to implement
Cheers
Andrea
–
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
Q: do you have a real example of what vocabulary can be?
Q: Did you consider integration with InternationalString?
–
Jody Garnett
On Thursday, 29 September 2011 at 1:38 PM, Justin Deoliveira wrote:
Hi all,
I have put together a quick proposal and patch to allow for supporting specifying metadata on service and layer keywords. The current proposal is here:
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
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-d2dcopy1
Q: do you have a real example of what vocabulary can be?
Here is an example from the actual ticket:
infoMapAccessService
Hydrography
Q: Did you consider integration with InternationalString?
I had not but that is an interesting thought… I guess we could make KeywordInfo.value an international string. However it might be overkill here… i don’t really need to convert between languages… just associate a language with a string. Which InterationalString doesn’t really seem to provide.
–
Jody Garnett
On Thursday, 29 September 2011 at 1:38 PM, Justin Deoliveira wrote:
Hi all,
I have put together a quick proposal and patch to allow for supporting specifying metadata on service and layer keywords. The current proposal is here:
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
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-d2dcopy1
Okay that works for me; was trying to figure it out looks like one of those silly “domain of discourse” ideas.
Q: Did you consider integration with InternationalString?
I had not but that is an interesting thought… I guess we could make KeywordInfo.value an international string. However it might be overkill here… i don’t really need to convert between languages… just associate a language with a string. Which InterationalString doesn’t really seem to provide.
Well the thing is a lot of the implementations do provide that; it is just that InternationalString is a nice way to throw them around a program and mark down something that “has translations”. I had a couple goes making something for keyword but did not like any of them especially.
class KeywordString extends InternationalString {
Set getKeywords();
String toString();
String toString( Locale );
}
Okay that works for me; was trying to figure it out looks like one of those silly “domain of discourse” ideas.
Q: Did you consider integration with InternationalString?
I had not but that is an interesting thought… I guess we could make KeywordInfo.value an international string. However it might be overkill here… i don’t really need to convert between languages… just associate a language with a string. Which InterationalString doesn’t really seem to provide.
Well the thing is a lot of the implementations do provide that; it is just that InternationalString is a nice way to throw them around a program and mark down something that “has translations”. I had a couple goes making something for keyword but did not like any of them especially.
class KeywordString extends InternationalString {
Set getKeywords();
String toString();
String toString( Locale );
}
Jody
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2
