= google summer of code 2011 - inspire view service support =

[https://svn.osgeo.org/mapserver/sandbox/inspire_soc2011 source code repository]

=== tasks ===
 ==== multi language support ====

 * [http://lists.osgeo.org/pipermail/mapserver-inspire/2011-May/000057.html summary]

|| ||'''A[[br]] language specific metadata values''' [[br]] [[br]] "wms_title" "my title" [[br]] "wms_title" "mein titel"||'''B [[br]] language dependent reference data''' [[br]] [[br]] DATA "shapes/rivers_eng.shp" [[br]] DATA "shapes/rivers_ger.shp"|| ||
||'''1[[br]]key extension'''||"wms_title_eng" "my title" [[br]] "wms_title_ger" "mein titel"||---|| main question: should resolution happen at [[br]] i) write time, i.e. only wms_title goes into mapobject [[br]]  or [[br]] ii) read time, i.e. everything goes into mapobject, [[br]] corresponding key e.g. wms_title_ger is used for reading [[br]] [[br]] mapfile maintainable? validation? ||
||'''2[[br]] runtime substitution''' ||---||DATA "shapes/rivers_%language%.shp" [[br]] [[br]] with ''language'' being a request parameter or global setting || already [http://mapserver.org/cgi/runsub.html implemented] in mapserver for certain parameters [[br]] [[br]] all required substitution scenarios (parameters) covered?  ||
||'''3[[br]]  externalization''' [[br]] [[br]] using external files [[br]] lang.eng  [[br]] lang.ger || "wms_title" "IDC_TITLE" [[br]] [[br]] IDC_TITLE=my title [[br]] IDC_TITLE=mein titel || DATA "IDC_SHAPES_RIVERS" [[br]] [[br]] IDC_SHAPES_RIVERS=shapes/rivers_eng.shp [[br]]  IDC_SHAPES_RIVERS=shapes/rivers_ger.shp [[br]] or [[br]] IDC_SHAPES_RIVERS=shapes/eng/rivers.shp [[br]] IDC_SHAPES_RIVERS=shapes/ger/rivers.shp|| common way of internationalization,  [[br]] many tools available to externalize strings [[br]] [[br]] at which time the externalized [[br]] value should be resolved (while parsing mapfile,  [[br]] during msApplySubstitutions, ...)?||
...

=== status reports ===

 * [http://lists.osgeo.org/pipermail/soc/2011-May/001302.html week 0]