This is a set of test case documents for checking Code Style servlets. Follow the test case links below, view and validate the source code to confirm correct operation. Test case summaries describe the expected outcome.
This servlet converts Dublin Core metadata in XHTML to RDF. The XHTML source documents are divided between those with "Original" DC in HTML source markup and the "New" recommended scheme specified by http://dublincore.org/documents/2003/11/30/dcq-html/. See Section 3 for compatibility details.
Much of the metadata in these test cases are dummy values for testing, and include test document URIs for checking the default value (the document URL) can be overridden in the XHTML. The servlet URLs have a &type=text parameter appended to set the content type to text/plain. Remove this parameter to get an RDF content type suitable for your user agent.
The source document uses the original DC in HTML scheme. Should generate a mixture of dc and dcterms namespace elements with test content that indicates the specified scheme of the original XHTML elements, where present. DC element-only content is listed first, followed by qualified elements.
As above, but this XHTML source has lower case DC identifiers and element names. Processing should be case insensitive and generate output equivalent to that above.
Source: http://www.codestyle.org/test/rdf-DCOriginalLower.htm
meta elements, mixed case RDF
This source contains DC qualifiers and encoding schemes that use the new DCTERMS prefix. The output should be equivalent to the two cases above.
Source: http://www.codestyle.org/test/rdf-DCNewMetaElements.htm
meta elements, lower case RDF
As above with lower case dc. and dcterms. prefixes. The output should be equivalent to the two cases above.
Source: http://www.codestyle.org/test/rdf-DCNewMetaElementsLower.htm
This source contains DC elements and qualifiers in HTML link elements using the new scheme prefixes. All href attributes should be presented as rdf:resource attributes on the relevant element, or an rdf:about attribute on a nested rdf:Description element. Includes one non-DC link element, which should not be processed. Also includes a document-specified URI identifier, which should override the public URL of the document (the default).
All but the principal identifier and dc:source link to http://dublincore.org/documents/2003/11/30/dcq-html/ should have dc:language/dcterms:RFC1766 values copied from the links' hreflang attribute.
Source: http://www.codestyle.org/test/rdf-DCNewLinkElements.htm
link elements with rev attributes RDF
As above, but all metadata links' rel attributes changed to rev. Not relevant or applicable to all properties, but all checked for test purposes. Should produce RDF equivalent to above.
Source: http://www.codestyle.org/test/rdf-DCNewLinkElementsRev.htm
link elements mixed with standard types RDF
As above, but mixed with other HTML link types. Various combinations to check cases, including surplus spaces and multiple relations between elements and single URLs, view source for details. Should produce RDF similar to the case above with some variations for the special cases.
Source: http://www.codestyle.org/test/rdf-DCNewLinkElementsMixed.htm
link elements mixed with standard types, lower case RDF
As above, but all Dublin Core identifiers and qualifier prefixes are lower case. Should produce equivalent RDF output to above.
Source: http://www.codestyle.org/test/rdf-DCNewLinkElementsMixed.htm
link elements with additional attributes RDF
Additional link element title, type and charset attributes. Should produce nested dc and dcterms elements for the linked documents. Where charset is given but not type, no dc:format/dcterms:IMT element is generated.
Source: http://www.codestyle.org/test/rdf-DCNewLinkElementsPlus.htm
