Hi,
I notice that fetch:content-type()[1] returns "application/octet-stream" for files with the commonly used XProc file extensions *.xpl and *.xproc. This seems to be driven from the list in src/main/resources/media-types.properties [2] Would it be possible to add these extensions as "application/*xproc*+xml" or add a mechanism to allow extension/customisation? Maybe similar to [3] For static files served from jetty adding mime-mapping elements to web.xml works [4]
/Andy
[1] http://docs.basex.org/wiki/Fetch_Module#fetch:content-type [2] https://github.com/BaseXdb/basex/blob/master/basex-core/ src/main/resources/media-types.properties [3] http://docs.oracle.com/javase/7/docs/api/javax/activation/ MimetypesFileTypeMap.html [4] https://stackoverflow.com/questions/33803109/how-can-i-set-mime-mapping-to-a...
Hi Andy,
Adding the extensions statically is surely the least effort for now.
I can add the following two mappings:
xpl=application/xml xproc=application/xml
Are some more that I should include?
Thanks, Christian
On Fri, Jun 9, 2017 at 11:49 AM, Andy Bunce bunce.andy@gmail.com wrote:
Hi,
I notice that fetch:content-type()[1] returns "application/octet-stream" for files with the commonly used XProc file extensions *.xpl and *.xproc. This seems to be driven from the list in src/main/resources/media-types.properties [2] Would it be possible to add these extensions as "application/xproc+xml" or add a mechanism to allow extension/customisation? Maybe similar to [3] For static files served from jetty adding mime-mapping elements to web.xml works [4]
/Andy
[1] http://docs.basex.org/wiki/Fetch_Module#fetch:content-type [2] https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/resources/m... [3] http://docs.oracle.com/javase/7/docs/api/javax/activation/MimetypesFileTypeM... [4] https://stackoverflow.com/questions/33803109/how-can-i-set-mime-mapping-to-a...
Hi Christian,
Just these two I am thinking about at the moment.
Is there some reason not to go with "application/*xproc*+xml"? [1] Many in the existing list are in this style e.g. atom=application/atom+xml svg=image/svg+xml lostxml=application/lost+xml
And it looks like BaseX will treat it as XML [2]
/Andy [1] https://www.w3.org/XML/XProc/docs/langspec.html#media-type-registration [2] https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/ba...
On 9 June 2017 at 11:01, Christian Grün christian.gruen@gmail.com wrote:
Hi Andy,
Adding the extensions statically is surely the least effort for now.
I can add the following two mappings:
xpl=application/xml xproc=application/xml
Are some more that I should include?
Thanks, Christian
On Fri, Jun 9, 2017 at 11:49 AM, Andy Bunce bunce.andy@gmail.com wrote:
Hi,
I notice that fetch:content-type()[1] returns "application/octet-stream"
for
files with the commonly used XProc file extensions *.xpl and *.xproc. This seems to be driven from the list in src/main/resources/media-types.properties [2] Would it be possible to add these extensions as "application/xproc+xml"
or
add a mechanism to allow extension/customisation? Maybe similar to [3] For static files served from jetty adding mime-mapping elements to
web.xml
works [4]
/Andy
[1] http://docs.basex.org/wiki/Fetch_Module#fetch:content-type [2] https://github.com/BaseXdb/basex/blob/master/basex-core/
src/main/resources/media-types.properties
[3] http://docs.oracle.com/javase/7/docs/api/javax/activation/
MimetypesFileTypeMap.html
set-mime-mapping-to-a-file-served-as-static-content-by- jetty-runner/33809187#33809187
Is there some reason not to go with "application/xproc+xml"? [1]
Should be fine. So I guess "application/xpl+xml" would be the better choice as well?
And it looks like BaseX will treat it as XML [2]
Exactly ;)
[1] https://www.w3.org/XML/XProc/docs/langspec.html#media-type-registration [2] https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/ba...
On 9 June 2017 at 11:01, Christian Grün christian.gruen@gmail.com wrote:
Hi Andy,
Adding the extensions statically is surely the least effort for now.
I can add the following two mappings:
xpl=application/xml xproc=application/xml
Are some more that I should include?
Thanks, Christian
On Fri, Jun 9, 2017 at 11:49 AM, Andy Bunce bunce.andy@gmail.com wrote:
Hi,
I notice that fetch:content-type()[1] returns "application/octet-stream" for files with the commonly used XProc file extensions *.xpl and *.xproc. This seems to be driven from the list in src/main/resources/media-types.properties [2] Would it be possible to add these extensions as "application/xproc+xml" or add a mechanism to allow extension/customisation? Maybe similar to [3] For static files served from jetty adding mime-mapping elements to web.xml works [4]
/Andy
[1] http://docs.basex.org/wiki/Fetch_Module#fetch:content-type [2]
https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/resources/m... [3]
http://docs.oracle.com/javase/7/docs/api/javax/activation/MimetypesFileTypeM... [4]
https://stackoverflow.com/questions/33803109/how-can-i-set-mime-mapping-to-a...
So I guess "application/xpl+xml" would be the better choice as well?
My understanding multiple extensions in use but same mimetype of "xproc+xml". As with
xq=application/xquery xqm=application/xquery xquery=application/xquery xqy=application/xquery
Although I note the list has:
xsl=text/xml xslt=application/xslt+xml
On 9 June 2017 at 11:49, Christian Grün christian.gruen@gmail.com wrote:
Is there some reason not to go with "application/xproc+xml"? [1]
Should be fine. So I guess "application/xpl+xml" would be the better choice as well?
And it looks like BaseX will treat it as XML [2]
Exactly ;)
[1]
https://www.w3.org/XML/XProc/docs/langspec.html#media-type-registration
[2]
https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/ba...
On 9 June 2017 at 11:01, Christian Grün christian.gruen@gmail.com
wrote:
Hi Andy,
Adding the extensions statically is surely the least effort for now.
I can add the following two mappings:
xpl=application/xml xproc=application/xml
Are some more that I should include?
Thanks, Christian
On Fri, Jun 9, 2017 at 11:49 AM, Andy Bunce bunce.andy@gmail.com
wrote:
Hi,
I notice that fetch:content-type()[1] returns
"application/octet-stream"
for files with the commonly used XProc file extensions *.xpl and *.xproc. This seems to be driven from the list in src/main/resources/media-types.properties [2] Would it be possible to add these extensions as
"application/xproc+xml"
or add a mechanism to allow extension/customisation? Maybe similar to
[3]
For static files served from jetty adding mime-mapping elements to web.xml works [4]
/Andy
[1] http://docs.basex.org/wiki/Fetch_Module#fetch:content-type [2]
https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/resources/m...
[3]
http://docs.oracle.com/javase/7/docs/api/javax/activation/MimetypesFileTypeM...
[4]
https://stackoverflow.com/questions/33803109/how-can-i-set-mime-mapping-to-a...
My understanding multiple extensions in use but same mimetype of "xproc+xml".
Sorry, I didn’t get it… Would you recommend the following mappings?
xpl=application/xproc+xml xproc=application/xproc+xml
Although I note the list has:
xsl=text/xml xslt=application/xslt+xml
I have adopted most of the entries from existing mime type lists, so I assume that various assignments could be updated. XSL seems to be a tricky case [1,2]; I would be happy to change the current assignment if someone reading this believes the current assignments are not the best choices.
[1] http://www.dpawson.co.uk/xsl/sect2/mimetypes.html [2] https://stackoverflow.com/questions/6715767/what-content-type-should-be-used...
Would you recommend the following mappings?
xpl=application/xproc+xml xproc=application/xproc+xml
Yes. /Andy
On 9 June 2017 at 12:10, Christian Grün christian.gruen@gmail.com wrote:
My understanding multiple extensions in use but same mimetype of "xproc+xml".
Sorry, I didn’t get it… Would you recommend the following mappings?
xpl=application/xproc+xml xproc=application/xproc+xml
Although I note the list has:
xsl=text/xml xslt=application/xslt+xml
I have adopted most of the entries from existing mime type lists, so I assume that various assignments could be updated. XSL seems to be a tricky case [1,2]; I would be happy to change the current assignment if someone reading this believes the current assignments are not the best choices.
[1] http://www.dpawson.co.uk/xsl/sect2/mimetypes.html [2] https://stackoverflow.com/questions/6715767/what- content-type-should-be-used-for-xmlxsl-presentation
Perfect. And thanks for your suggestions on how to customize mime types in the future.
On Fri, Jun 9, 2017 at 1:12 PM, Andy Bunce bunce.andy@gmail.com wrote:
Would you recommend the following mappings?
xpl=application/xproc+xml xproc=application/xproc+xml
Yes. /Andy
On 9 June 2017 at 12:10, Christian Grün christian.gruen@gmail.com wrote:
My understanding multiple extensions in use but same mimetype of "xproc+xml".
Sorry, I didn’t get it… Would you recommend the following mappings?
xpl=application/xproc+xml xproc=application/xproc+xml
Although I note the list has:
xsl=text/xml xslt=application/xslt+xml
I have adopted most of the entries from existing mime type lists, so I assume that various assignments could be updated. XSL seems to be a tricky case [1,2]; I would be happy to change the current assignment if someone reading this believes the current assignments are not the best choices.
[1] http://www.dpawson.co.uk/xsl/sect2/mimetypes.html [2] https://stackoverflow.com/questions/6715767/what-content-type-should-be-used...
Hi all,
Dear Christian, I hope you are doing well.
On the same subject, would it be possible for the REST interface to handle PUT requests of
application/vnd.api+jsonhttp://www.iana.org/assignments/media-types/application/vnd.api+json
resources (http://jsonapi.org/) like JSON ones ?
Best regards,
Fabrice
De : basex-talk-bounces@mailman.uni-konstanz.de [mailto:basex-talk-bounces@mailman.uni-konstanz.de] De la part de Andy Bunce Envoyé : vendredi 9 juin 2017 12:38 À : Christian Grün Cc : basex-talk@mailman.uni-konstanz.de Objet : Re: [basex-talk] fetch:content-type file: customisation
Hi Christian, Just these two I am thinking about at the moment.
Is there some reason not to go with "application/xproc+xml"? [1] Many in the existing list are in this style e.g. atom=application/atom+xml svg=image/svg+xml lostxml=application/lost+xml And it looks like BaseX will treat it as XML [2] /Andy [1] https://www.w3.org/XML/XProc/docs/langspec.html#media-type-registration [2] https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/ba...
On 9 June 2017 at 11:01, Christian Grün <christian.gruen@gmail.commailto:christian.gruen@gmail.com> wrote: Hi Andy,
Adding the extensions statically is surely the least effort for now.
I can add the following two mappings:
xpl=application/xml xproc=application/xml
Are some more that I should include?
Thanks, Christian
On Fri, Jun 9, 2017 at 11:49 AM, Andy Bunce <bunce.andy@gmail.commailto:bunce.andy@gmail.com> wrote:
Hi,
I notice that fetch:content-type()[1] returns "application/octet-stream" for files with the commonly used XProc file extensions *.xpl and *.xproc. This seems to be driven from the list in src/main/resources/media-types.properties [2] Would it be possible to add these extensions as "application/xproc+xml" or add a mechanism to allow extension/customisation? Maybe similar to [3] For static files served from jetty adding mime-mapping elements to web.xml works [4]
/Andy
[1] http://docs.basex.org/wiki/Fetch_Module#fetch:content-type [2] https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/resources/m... [3] http://docs.oracle.com/javase/7/docs/api/javax/activation/MimetypesFileTypeM... [4] https://stackoverflow.com/questions/33803109/how-can-i-set-mime-mapping-to-a...
Hi Fabrice,
I guess it would be better to use RESTXQ for building responses that match the JSON API specification. Did you try that already?
Cheers Christian
Am 09.06.2017 15:11 schrieb "Fabrice ETANCHAUD" <fetanchaud@pch.cerfrance.fr
:
Hi all,
Dear Christian, I hope you are doing well.
On the same subject, would it be possible for the REST interface to handle PUT requests of
application/vnd.api+json http://www.iana.org/assignments/media-types/application/vnd.api+json
resources (http://jsonapi.org/) like JSON ones ?
Best regards,
Fabrice
*De :* basex-talk-bounces@mailman.uni-konstanz.de [mailto: basex-talk-bounces@mailman.uni-konstanz.de] *De la part de* Andy Bunce *Envoyé :* vendredi 9 juin 2017 12:38 *À :* Christian Grün *Cc :* basex-talk@mailman.uni-konstanz.de *Objet :* Re: [basex-talk] fetch:content-type file: customisation
Hi Christian,
Just these two I am thinking about at the moment.
Is there some reason not to go with "application/*xproc*+xml"? [1] Many in the existing list are in this style e.g. atom=application/atom+xml svg=image/svg+xml
lostxml=application/lost+xml
And it looks like BaseX will treat it as XML [2]
/Andy [1] https://www.w3.org/XML/XProc/docs/langspec.html#media-type-registration [2] https://github.com/BaseXdb/basex/blob/master/basex-core/ src/main/java/org/basex/util/http/MediaType.java#L148
On 9 June 2017 at 11:01, Christian Grün christian.gruen@gmail.com wrote:
Hi Andy,
Adding the extensions statically is surely the least effort for now.
I can add the following two mappings:
xpl=application/xml xproc=application/xml
Are some more that I should include?
Thanks, Christian
On Fri, Jun 9, 2017 at 11:49 AM, Andy Bunce bunce.andy@gmail.com wrote:
Hi,
I notice that fetch:content-type()[1] returns "application/octet-stream"
for
files with the commonly used XProc file extensions *.xpl and *.xproc. This seems to be driven from the list in src/main/resources/media-types.properties [2] Would it be possible to add these extensions as "application/xproc+xml" or add a mechanism to allow extension/customisation? Maybe similar to [3] For static files served from jetty adding mime-mapping elements to web.xml works [4]
/Andy
[1] http://docs.basex.org/wiki/Fetch_Module#fetch:content-type [2] https://github.com/BaseXdb/basex/blob/master/basex-core/
src/main/resources/media-types.properties
[3] http://docs.oracle.com/javase/7/docs/api/javax/activation/
MimetypesFileTypeMap.html
set-mime-mapping-to-a-file-served-as-static-content-by- jetty-runner/33809187#33809187
Hi Christian,
Yes I already used RestXQ to implement JSON API partially, you are right, RestXQ is the only way serverside. The need in REST was only for blind storage of redirected json-api responses, that can also be done with RestXQ.
Thank you Christian for providing us with such a flexible software !
Best regards, Fabrice
De : Christian Grün [mailto:christian.gruen@gmail.com] Envoyé : dimanche 11 juin 2017 22:00 À : Fabrice ETANCHAUD Cc : Andy Bunce; BaseX Objet : RE: [basex-talk] fetch:content-type file: customisation
Hi Fabrice,
I guess it would be better to use RESTXQ for building responses that match the JSON API specification. Did you try that already?
Cheers Christian
Am 09.06.2017 15:11 schrieb "Fabrice ETANCHAUD" <fetanchaud@pch.cerfrance.frmailto:fetanchaud@pch.cerfrance.fr>: Hi all,
Dear Christian, I hope you are doing well.
On the same subject, would it be possible for the REST interface to handle PUT requests of
application/vnd.api+jsonhttp://www.iana.org/assignments/media-types/application/vnd.api+json
resources (http://jsonapi.org/) like JSON ones ?
Best regards,
Fabrice
De : basex-talk-bounces@mailman.uni-konstanz.demailto:basex-talk-bounces@mailman.uni-konstanz.de [mailto:basex-talk-bounces@mailman.uni-konstanz.demailto:basex-talk-bounces@mailman.uni-konstanz.de] De la part de Andy Bunce Envoyé : vendredi 9 juin 2017 12:38 À : Christian Grün Cc : basex-talk@mailman.uni-konstanz.demailto:basex-talk@mailman.uni-konstanz.de Objet : Re: [basex-talk] fetch:content-type file: customisation
Hi Christian, Just these two I am thinking about at the moment.
Is there some reason not to go with "application/xproc+xml"? [1] Many in the existing list are in this style e.g. atom=application/atom+xml svg=image/svg+xml lostxml=application/lost+xml And it looks like BaseX will treat it as XML [2] /Andy [1] https://www.w3.org/XML/XProc/docs/langspec.html#media-type-registration [2] https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/ba...
On 9 June 2017 at 11:01, Christian Grün <christian.gruen@gmail.commailto:christian.gruen@gmail.com> wrote: Hi Andy,
Adding the extensions statically is surely the least effort for now.
I can add the following two mappings:
xpl=application/xml xproc=application/xml
Are some more that I should include?
Thanks, Christian
On Fri, Jun 9, 2017 at 11:49 AM, Andy Bunce <bunce.andy@gmail.commailto:bunce.andy@gmail.com> wrote:
Hi,
I notice that fetch:content-type()[1] returns "application/octet-stream" for files with the commonly used XProc file extensions *.xpl and *.xproc. This seems to be driven from the list in src/main/resources/media-types.properties [2] Would it be possible to add these extensions as "application/xproc+xml" or add a mechanism to allow extension/customisation? Maybe similar to [3] For static files served from jetty adding mime-mapping elements to web.xml works [4]
/Andy
[1] http://docs.basex.org/wiki/Fetch_Module#fetch:content-type [2] https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/resources/m... [3] http://docs.oracle.com/javase/7/docs/api/javax/activation/MimetypesFileTypeM... [4] https://stackoverflow.com/questions/33803109/how-can-i-set-mime-mapping-to-a...
basex-talk@mailman.uni-konstanz.de
-
Andy Bunce -
Christian Grün -
Fabrice ETANCHAUD