head 1.9; access; symbols; locks; strict; comment @# @; 1.9 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.8; 1.8 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.7; 1.7 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.6; 1.6 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.5; 1.5 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.4; 1.4 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.3; 1.3 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.2; 1.2 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next 1.1; 1.1 date 2007.01.09.00.00.00; author MoinMoin; state Exp; branches; next ; desc @Initial revision @ 1.9 log @Revision 9 @ text @---+ CustomSearchProposalOne A proposal to fit the CustomSearch requirements. The ResponseStructure (starting with ) is defined here in a simple xml schema alike way. The PyWrapper already uses a simliar structure as the ResponseStructure proposed here to store and map any ConceptualSchema. The implemented PyWrapperAlgorithm for creating a valid xml output for a given ResponseStructure has proven to work when substituting the ConceptualBinding with an actual database mapping (table.attribute) of a specific provider. For counting matches and returned records as well as the paging mechanism we need to give a RecordDefinition here, listing concepts from within our custom record structure. See RecordDefinition for more details. ---+++++ Request
...
/Taxon * * * * * Ast*
with* indicating repeatable elements
---+++++ Response
...
* * 45.40 13.10 43.10 12.70
with* indicating repeatable elements
@ 1.8 log @Revision 8 @ text @d21 1 a21 1 * @ 1.7 log @Revision 7 @ text @d19 1 a19 1 /Taxon d21 1 a21 1 d23 1 a23 1 d27 1 a27 1 d29 1 a29 1 d42 2 d54 2 a55 2 d66 2 @ 1.6 log @Revision 6 @ text @d9 1 a9 1 For counting matches and returned records as well as the paging mechanism we need to give a Record Definition here, listing concepts from within our custom record structure. See Record Definition for more details. @ 1.5 log @Revision 5 @ text @d9 1 @ 1.4 log @Revision 4 @ text @d17 1 a17 1 d36 1 a36 1 @ 1.3 log @Revision 3 @ text @d17 1 a17 1 d20 1 a20 1 d28 2 a29 2 @ 1.2 log @Revision 2 @ text @d3 7 @ 1.1 log @Initial revision @ text @d39 17 @