fetch:content-type file: customisation

On Fri, Jun 9, 2017 at 11:49 AM, Andy Bunce <bunce.andy at 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 > [4] > https://stackoverflow.com/questions/33803109/how-can-i-set-mime-mapping-to-a-file-served-as-static-content-by-jetty-runner/33809187#33809187

On 9 June 2017 at 11:01, Christian Grün <christian.gruen at 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 at 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 > > [4] > > https://stackoverflow.com/questions/33803109/how-can-i- > 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]

> And it looks like BaseX will treat it as XML [2]

> [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 at 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 at 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 >> > [4] >> > >> > https://stackoverflow.com/questions/33803109/how-can-i-set-mime-mapping-to-a-file-served-as-static-content-by-jetty-runner/33809187#33809187 > >

>So I guess "application/xpl+xml" would be the better choice as well?

On 9 June 2017 at 11:49, Christian Grün <christian.gruen at 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]

> > [2] > >

> > > > On 9 June 2017 at 11:01, Christian Grün <christian.gruen at 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 at gmail.com> wrote: > >> > Hi, > >> > > >> > I notice that fetch:content-type()[1] returns

> >> > 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

> >> > or > >> > add a mechanism to allow extension/customisation? Maybe similar to

> >> > 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] > >> > > >> >

> >> > [3] > >> > > >> >

> >> > [4] > >> > > >> >

> > > >

> My understanding multiple extensions in use but same mimetype of > "xproc+xml".

> Although I note the list has: > > xsl=text/xml > xslt=application/xslt+xml

>Would you recommend the following mappings? >xpl=application/xproc+xml >xproc=application/xproc+xml

On 9 June 2017 at 12:10, Christian Grün <christian.gruen at 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 >

On Fri, Jun 9, 2017 at 1:12 PM, Andy Bunce <bunce.andy at 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 at 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 > >

De : basex-talk-bounces at mailman.uni-konstanz.de [mailto:basex-talk-bounces at mailman.uni-konstanz.de] De la part de Andy Bunce Envoyé : vendredi 9 juin 2017 12:38 À : Christian Grün Cc : basex-talk at 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 at gmail.com<mailto:christian.gruen at 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 at gmail.com<mailto:bunce.andy at 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 > [4] > https://stackoverflow.com/questions/33803109/how-can-i-set-mime-mapping-to-a-file-served-as-static-content-by-jetty-runner/33809187#33809187

>:

*De :* basex-talk-bounces at mailman.uni-konstanz.de [mailto: basex-talk-bounces at mailman.uni-konstanz.de] *De la part de* Andy Bunce *Envoyé :* vendredi 9 juin 2017 12:38 *À :* Christian Grün *Cc :* basex-talk at 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 at 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 at 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 > [4] > https://stackoverflow.com/questions/33803109/how-can-i- set-mime-mapping-to-a-file-served-as-static-content-by- jetty-runner/33809187#33809187

De : Christian Grün [mailto:christian.gruen at 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 at pch.cerfrance.fr<mailto:fetanchaud at 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 at mailman.uni-konstanz.de<mailto:basex-talk-bounces at mailman.uni-konstanz.de> [mailto:basex-talk-bounces at mailman.uni-konstanz.de<mailto:basex-talk-bounces at mailman.uni-konstanz.de>] De la part de Andy Bunce Envoyé : vendredi 9 juin 2017 12:38 À : Christian Grün Cc : basex-talk at mailman.uni-konstanz.de<mailto:basex-talk at 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 at gmail.com<mailto:christian.gruen at 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 at gmail.com<mailto:bunce.andy at 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 > [4] > https://stackoverflow.com/questions/33803109/how-can-i-set-mime-mapping-to-a-file-served-as-static-content-by-jetty-runner/33809187#33809187