software !
Best regards,
Fabrice
De : Christian Grün [mailto:christian.gr...@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
*De :* basex-talk-boun...@mailman.uni-konstanz.de [mailto:
basex-talk-boun...@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
Best regards,
Fabrice
De : basex-talk-boun...@mailman.uni-konstanz.de
[mailto:basex-talk-boun...@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-typ
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 wrote:
>>Would you recommend the following mappings?
>
>>xpl=application/xproc+xml
>>xproc=application/xproc+xml
>
> Yes.
> /Andy
>
> On 9 June
>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 wrote:
> > My understanding multiple extensions in use but same mimetype of
> > "xproc+xml".
>
> Sorry, I didn’t
> 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
>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
> 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
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
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 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
11 matches
Mail list logo