Serving "application/tei+xml" from Cocoon - Revision history

Piotr Banski: +link, +category

2016-07-11T01:28:41Z

+link, +category

Conal at 04:57, 22 October 2010

2010-10-22T04:57:41Z

Conal at 04:57, 22 October 2010

2010-10-22T04:57:25Z

Conal at 04:53, 22 October 2010

2010-10-22T04:53:21Z

Conal at 04:52, 22 October 2010

2010-10-22T04:52:11Z

Conal at 04:50, 22 October 2010

2010-10-22T04:50:47Z

Conal at 04:45, 22 October 2010

2010-10-22T04:45:30Z

Conal at 04:43, 22 October 2010

2010-10-22T04:43:27Z

Conal at 04:36, 22 October 2010

2010-10-22T04:36:50Z

Conal: New page: = How to serve TEI XML from Cocoon with the content-type "application/tei+xml" = Most websites which publish TEI XML documents describe them with the content type "application/xml" or "te...

2010-10-22T04:35:46Z

New page: = How to serve TEI XML from Cocoon with the content-type "application/tei+xml" = Most websites which publish TEI XML documents describe them with the content type "application/xml" or "te...

New page

= How to serve TEI XML from Cocoon with the content-type "application/tei+xml" =

Most websites which publish TEI XML documents describe them with the content type "application/xml" or "text/xml". These are two labels for XML files in general, and don't identify the files as specifically ''TEI'' XML. By using the content type "application/tei+xml", a webserver can make the specific claim that the XML file is TEI rather than any other kind of XML. This has the advantage that browsers can be configured to handle TEI files distinctly from the way they handle other XML files (for instance, by opening them in an XML editor).

= Simple configuration =

To specify the content type, simply configure a serializer in your sitemap.xmap file, and then invoke the serializer in your TEI pipeline.

To declare the serializer:

<pre><nowiki>
<serializer mime-type="application/tei+xml" name="tei" src="org.apache.cocoon.serialization.XMLSerializer"/>
</nowiki></pre>

Invoking the serializer:

<pre><nowiki>
<serialize type="tei"/>
</pre></nowiki>

= Preferred configuration =

Most browsers will adequately display generic XML but will not be configured to handle the specific content type "application/tei+xml". For this reason, it's usually better to serve the TEI as "application/tei+xml" only if the browser specifically asks for it, and otherwise to serve it as the generic "application/xml".

In Cocoon, you can use a [http://cocoon.apache.org/2.1/userdocs/regular-expression-header-selector.html RegexpHeaderSelector] to determine if a browser is prepared to handle the specific content type. The following Cocoon sitemap shows a Reg

<pre><nowiki>
<?xml version="1.0" encoding="UTF-8"?>
<sitemap xmlns="http://apache.org/cocoon/sitemap/1.0">
<components>

<serializers>
<serializer mime-type="application/xml" name="xml" src="org.apache.cocoon.serialization.XMLSerializer"/>
<serializer mime-type="application/tei+xml" name="tei" src="org.apache.cocoon.serialization.XMLSerializer"/>
</serializers>

<selectors>
<selector name="accept-content-type" src="org.apache.cocoon.selection.RegexpHeaderSelector">
<pattern xmlns="" name="tei">application/tei\+xml</pattern>
<header-name xmlns="">accept</header-name>
</selector>
</selectors>
</components>

<resources>


<resource name="serialize-tei">
<select type="accept-content-type">
<when test="tei">
<serialize type="tei"/>
</when>
<otherwise>
<serialize type="xml"/>
</otherwise>
</select>
</resource>
</resources>

<pipelines>
<pipeline>
<match pattern="transcript/*.xml">
<generate src="tei/{1}.xml"/>
<call resource="serialize-tei"/>
</match>
</pipeline>
</pipelines>

</sitemap>
</pre></nowiki>

@@ Line 1: / Line 1: @@
 Most websites which publish TEI XML documents describe them with the content type "application/xml" or "text/xml". These are two labels for XML files in general, and don't identify the files as specifically ''TEI'' XML. By using the content type "application/tei+xml", a webserver can make the specific claim that the XML file is TEI rather than any other kind of XML. This has the advantage that browsers can be configured to handle TEI files distinctly from the way they handle other XML files (for instance, by opening them in an XML editor).
-This page describes how to configure [[Apache Cocoon]] to serve TEI content as "application/tei+xml".
+This page describes how to configure [[Apache Cocoon]] to serve TEI content as "[[TEI media type|application/tei+xml]]".
 = Simple configuration =

@@ Line 1: / Line 1: @@
 Most websites which publish TEI XML documents describe them with the content type "application/xml" or "text/xml". These are two labels for XML files in general, and don't identify the files as specifically ''TEI'' XML. By using the content type "application/tei+xml", a webserver can make the specific claim that the XML file is TEI rather than any other kind of XML. This has the advantage that browsers can be configured to handle TEI files distinctly from the way they handle other XML files (for instance, by opening them in an XML editor).
-This page describes how to configure [Apache Cocoon] to serve TEI content as "application/tei+xml".
+This page describes how to configure [[Apache Cocoon]] to serve TEI content as "application/tei+xml".
 = Simple configuration =

← Older revision		Revision as of 04:57, 22 October 2010
Line 1:		Line 1:
	Most websites which publish TEI XML documents describe them with the content type "application/xml" or "text/xml". These are two labels for XML files in general, and don't identify the files as specifically ''TEI'' XML. By using the content type "application/tei+xml", a webserver can make the specific claim that the XML file is TEI rather than any other kind of XML. This has the advantage that browsers can be configured to handle TEI files distinctly from the way they handle other XML files (for instance, by opening them in an XML editor).		Most websites which publish TEI XML documents describe them with the content type "application/xml" or "text/xml". These are two labels for XML files in general, and don't identify the files as specifically ''TEI'' XML. By using the content type "application/tei+xml", a webserver can make the specific claim that the XML file is TEI rather than any other kind of XML. This has the advantage that browsers can be configured to handle TEI files distinctly from the way they handle other XML files (for instance, by opening them in an XML editor).
		+
		+	This page describes how to configure [Apache Cocoon] to serve TEI content as "application/tei+xml".

	= Simple configuration =		= Simple configuration =

← Older revision		Revision as of 04:53, 22 October 2010
Line 1:		Line 1:
−	~~= How to serve TEI XML from Cocoon with the content-type "application/tei+xml" =~~
−
	Most websites which publish TEI XML documents describe them with the content type "application/xml" or "text/xml". These are two labels for XML files in general, and don't identify the files as specifically ''TEI'' XML. By using the content type "application/tei+xml", a webserver can make the specific claim that the XML file is TEI rather than any other kind of XML. This has the advantage that browsers can be configured to handle TEI files distinctly from the way they handle other XML files (for instance, by opening them in an XML editor).		Most websites which publish TEI XML documents describe them with the content type "application/xml" or "text/xml". These are two labels for XML files in general, and don't identify the files as specifically ''TEI'' XML. By using the content type "application/tei+xml", a webserver can make the specific claim that the XML file is TEI rather than any other kind of XML. This has the advantage that browsers can be configured to handle TEI files distinctly from the way they handle other XML files (for instance, by opening them in an XML editor).

← Older revision		Revision as of 04:50, 22 October 2010
Line 76:		Line 76:
	</sitemap>		</sitemap>
	</nowiki></pre>		</nowiki></pre>
		+
		+	== Configuring your browser to request "application/tei+xml" ==
		+
		+	Using this configuration, you will need to configure your browser to declare that it's prepared to accept "application/tei+xml".
		+
		+	To configure Firefox, enter "about:config" into the address bar, find the key called "network.http.accept.default" and change it to include "application/tei+xml" in the list of acceptable content types, e.g.:
		+
		+	<pre>text/html;q=0.7,application/xhtml+xml;q=0.8,application/tei+xml;q=0.7,application/xml;q=0.6,/;q=0.4,application/json;q=0.5</pre>

@@ Line 13: / Line 13: @@
 </nowiki></pre>
-Invoking the serializer:
+To invoke the serializer:
 <pre><nowiki>
 <serialize type="tei"/>
 </nowiki></pre>
 = Preferred configuration =

@@ Line 68: / Line 68: @@
 			<match pattern="transcript/*.xml">
 				<generate src="tei/{1}.xml"/>
 				<call resource="serialize-tei"/>
 			</match>

@@ Line 5: / Line 5: @@
 = Simple configuration =
-To specify the content type, simply configure a serializer in your sitemap.xmap file, and then invoke the serializer in your TEI pipeline.
+To specify the content type, simply configure a TEI [http://cocoon.apache.org/2.1/userdocs/xml-serializer.html XML serializer] in your sitemap.xmap file, and then invoke the serializer in your TEI pipelines.
 To declare the serializer:
@@ Line 23: / Line 23: @@
 Most browsers will adequately display generic XML but will not be configured to handle the specific content type "application/tei+xml". For this reason, it's usually better to serve the TEI as "application/tei+xml" only if the browser specifically asks for it, and otherwise to serve it as the generic "application/xml".
-In Cocoon, you can use a [http://cocoon.apache.org/2.1/userdocs/regular-expression-header-selector.html RegexpHeaderSelector] to determine if a browser is prepared to handle the specific content type. The following Cocoon sitemap shows a Reg
+In Cocoon, you can use a [http://cocoon.apache.org/2.1/userdocs/regular-expression-header-selector.html RegexpHeaderSelector] to determine if a browser is prepared to handle the specific content type. The following Cocoon sitemap file shows:
 <pre><nowiki>