From christian.gruen at gmail.com Tue Apr 16 07:11:46 2019 From: christian.gruen at gmail.com (=?UTF-8?Q?Christian_Gr=C3=BCn?=) Date: Tue, 16 Apr 2019 16:11:46 +0200 Subject: [xquery-talk] [ANN] BaseX 9.2: The Spring Edition In-Reply-To: References: Message-ID: Dear all, We are more than pleased to announce version 9.2 of BaseX, our XML framework, database system and XQuery 3.1 processor: http://basex.org/ This time, we have put a special focus on performance improvements: XQUERY PERFORMANCE - comparisons will more often be rewritten to hash joins - optimized access to subsequences and single sequence items - consistent propagation of static types to evaluation results - improved static typing of function items (maps, arrays) - more aggressive pre-evaluation at compile time STORAGE PERFORMANCE - large databases will be opened faster - regular storage offset will be computed at runtime GENERAL XQUERY FEATURES - no need to import basex-api modules anymore! - Archive Module: archive:create-from, new options - Database Module: directory-based access via db:dir - Profiling Module: new functions (prof:gc, prof:runtime) - Validation Module: assign XSD validation features - WebSocket Module: query scheduling via ws:eval - Utility Module: various new helper functions - XSLT Module: support for XML Catalogs (thank you Liam) NEW OPTIONS - RESTXQERRORS: Suppress parsing errors at runtime - FULLPLAN: comprehensive query plan information FULLTEXT FEATURES - stemmer for Arabic texts added USER INTERFACES - GUI: better support for latest JDK versions (incl. OpenJDK) - DBA: revised search features in log panel For a more comprehensive list of added and updated features. please check out our documentation: http://docs.basex.org/. We are looking forward to your feedback. Have fun with the new release, Your BaseX Team From mixich.andreas at gmail.com Tue Apr 16 19:24:25 2019 From: mixich.andreas at gmail.com (Andreas Mixich) Date: Wed, 17 Apr 2019 04:24:25 +0200 Subject: [xquery-talk] When to us xs:string or xs:anyURI ? Message-ID: <081981a0-46c1-00a4-3a03-2bb6ca44010d@gmail.com> Hello, I wonder, what dis/advantages it would have to use the xs:anyURI datatype for IRIs instead of xs:string. Looking around, it seems, that most people do not care for the xs:anyURI and use xs:string instead, since that is easier to handle (type casting works only one-directional with xs:anyURI). What was the rationale behind creating an xs:anyURI datatype? According to http://www.datypic.com/sc/xsd/t-xsd_anyURI.html ? [...]The only values that are not accepted are ones that make inappropriate ? use of reserved characters, such as ones that contain multiple?|#|?characters ? or have?|%|?characters that are not followed by two hexadecimal digits.[...] As XQuery users, what would you prefer in a module library for functions, that take or return IRIs? What would you expect in a module library, that acts as a "swiss army knife" for IRIs? -- Goody Bye, Minden j?t, Mit freundlichen Gr??en, Andreas Mixich From mike at saxonica.com Wed Apr 17 02:37:13 2019 From: mike at saxonica.com (Michael Kay) Date: Wed, 17 Apr 2019 10:37:13 +0100 Subject: [xquery-talk] When to us xs:string or xs:anyURI ? In-Reply-To: <081981a0-46c1-00a4-3a03-2bb6ca44010d@gmail.com> References: <081981a0-46c1-00a4-3a03-2bb6ca44010d@gmail.com> Message-ID: <18F20C90-9361-4423-A438-64D1EDB7D76F@saxonica.com> In the standard function library we adopted the approach that for input parameters, relevant functions should accept xs:string; for function results, they should return an xs:anyURI. That recognizes the one-way casting effect. xs:anyURI is a bit of a mess. XQuery supports it only because it already existed in XSD. Michael Kay Saxonica > On 17 Apr 2019, at 03:24, Andreas Mixich wrote: > > Hello, > > I wonder, what dis/advantages it would have to use the xs:anyURI > datatype for IRIs > instead of xs:string. Looking around, it seems, that most people do not > care for > the xs:anyURI and use xs:string instead, since that is easier to handle > (type casting works only one-directional with xs:anyURI). > > What was the rationale behind creating an xs:anyURI datatype? > According to http://www.datypic.com/sc/xsd/t-xsd_anyURI.html > > [...]The only values that are not accepted are ones that make > inappropriate > use of reserved characters, such as ones that contain > multiple |#| characters > or have |%| characters that are not followed by two hexadecimal > digits.[...] > > As XQuery users, what would you prefer in a module library for > functions, that take > or return IRIs? What would you expect in a module library, that acts as > a "swiss army > knife" for IRIs? > > -- > Goody Bye, Minden j?t, Mit freundlichen Gr??en, > Andreas Mixich > > _______________________________________________ > talk at x-query.com > http://x-query.com/mailman/listinfo/talk From mixich.andreas at gmail.com Wed Apr 17 02:50:22 2019 From: mixich.andreas at gmail.com (Andreas Mixich) Date: Wed, 17 Apr 2019 11:50:22 +0200 Subject: [xquery-talk] When to us xs:string or xs:anyURI ? In-Reply-To: <18F20C90-9361-4423-A438-64D1EDB7D76F@saxonica.com> References: <081981a0-46c1-00a4-3a03-2bb6ca44010d@gmail.com> <18F20C90-9361-4423-A438-64D1EDB7D76F@saxonica.com> Message-ID: On Wed, Apr 17, 2019 at 11:37 AM Michael Kay wrote: > In the standard function library we adopted the approach that for input > parameters, relevant functions should accept xs:string; for function > results, they should return an xs:anyURI. That recognizes the one-way > casting effect. > Okay, than that's what I am going to do as well. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: