[Mapbender-dev] GSoC 09: CSW - Draft CAT table and storage of XML
Mifan Careem
mifan at opensource.lk
Fri Jun 5 15:53:25 EDT 2009
Hi list,
I am in the process of creating the schema for storing catalog entries,
as drafted by Armin here in section 7 -the draft table for cat:
http://www.mapbender.org/CSW_Requirements#TODOs
Should we store the whole GetCapabilites document in the table and at
the same time store some of the values from the GetCapabilities.xml as
fields in the same table itself? If so, should stuff like the URLs be
stored in fields or should they be picked up from the XML doc as and
when needed?
What operational metadata should ideally be stored in
cat_op_getcapabilities, cat_op_describerecord etc.? For e.g, for the
cat_op_getrecordbyid section, would storing something like this be
sufficient?
<Operation name="GetRecordById">
−
<DCP>
−
<HTTP>
<Get xlink:href="http://apollo.erdas.com/apollo-catalog/wrs/WRS?"
xlink:type="simple"/>
<Post xlink:href="http://apollo.erdas.com/apollo-catalog/wrs/WRS"
xlink:type="simple"/>
</HTTP>
</DCP>
−
<Parameter name="outputFormat">
<Value>text/xml</Value>
<Value>application/xml</Value>
</Parameter>
−
<Parameter name="elementSetName">
<Value>full</Value>
<Value>brief</Value>
<Value>summary</Value>
</Parameter>
−
<Parameter name="outputSchema">
<Value>http://www.opengis.net/cat/csw/2.0.2</Value>
</Parameter>
</Operation>
Please let me know
Regards
Mifan
More information about the Mapbender_dev
mailing list