[API-TestSuite] Proposal for filter test cases

Dear all,

as Joakim told us, we have to integrate test cases for filter criteria in the API test suite to leave the current status. To move on quickly, i had a discussion with Werner as well as Thomas (responsible for one of the reference implementations). We decided to include test cases proofing the filter criteria on the basis of language selection.

Due to heavy schedule, i want to keep modification on a very low rate. I propose to add the following to filter test cases to the DublinCore example:

* title:

table entry:

D2-f	 :: DC :: title :: filter criteria "de" language :: passed :: not supported :: passed :: title filter response for "de" language

with the following input data:

<!-- calling DE language -->
<metadata xmlns="http://www.ukoln.ac.uk/metadata/dcdot/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dc="http://purl.org/dc/elements/1.1/"xsi:schemaLocation="http://www.ukoln.ac.uk/metadata/dcdot/ http://www.ukoln.ac.uk/metadata/dcdot/dcdot.xsd">
<dc:title xml:lang="en">Dublin Core Tutorial</dc:title>
</metadata>

and this output data:

[ { "MediaAnnotation" : {
       "propertyName" : "",
       "value" : "",
       "language" : "",
       "sourceFormat" : "",
       "fragmentIdentifier" : "",
       "mappingType" : "",
       "statusCode" : 204
       }
} ]


* description:

table entry:

D9-f	 :: DC :: description :: filter criteria "de" language :: passed :: not supported :: passed :: description filter response for "de" language

with the following input data:

<!-- calling DE language -->
<metadata xmlns="http://www.ukoln.ac.uk/metadata/dcdot/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dc="http://purl.org/dc/elements/1.1/"xsi:schemaLocation="http://www.ukoln.ac.uk/metadata/dcdot/ http://www.ukoln.ac.uk/metadata/dcdot/dcdot.xsd">
<dc:description xml:lang="en">
Learning Advanced Web Design can be fun and easy! Learn how to design web pages with proper tags, styles, and scripting.
</dc:description>
</metadata>

and this output data:

[ { "MediaAnnotation" : {
       "propertyName" : "",
       "value" : "",
       "language" : "",
       "sourceFormat" : "",
       "fragmentIdentifier" : "",
       "mappingType" : "",
       "statusCode" : 204
       }
} ]

The positive effect is, that with this solution, there is no need to change a example file, or a RDF file. It should be also sufficient as proof of concept. Thomas will integrate it in the reference implementation accordingly. So, if we decide to go for these, include it in the test suite and mark them green for implementation 1 and 3.

Cheers.
_____________________________
Dipl. Inf. Florian Stegmaier
Chair of Distributed Information Systems
University of Passau
Innstr. 43
94032 Passau

Room 248 ITZ

Tel.: +49 851 509 3063
Fax: +49 851 509 3062

http://www.mendeley.com/profiles/florian-stegmaier/
http://twitter.com/fstegmai
_____________________________



_____________________________
Dipl. Inf. Florian Stegmaier
Chair of Distributed Information Systems
University of Passau
Innstr. 43
94032 Passau

Room 248 ITZ

Tel.: +49 851 509 3063
Fax: +49 851 509 3062

http://www.mendeley.com/profiles/florian-stegmaier/
http://twitter.com/fstegmai
_____________________________

Received on Thursday, 10 May 2012 07:13:07 UTC