Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Feasibility of "do all application coding in the XML

From: "James Fuller" <james.fuller.2007@-----.--->
To: "Robert Koberg" <rob@------.--->
Date: 12/2/2008 2:49:00 PM
On Tue, Dec 2, 2008 at 2:53 PM, Robert Koberg <rob@k...> wrote:
>
> On Dec 2, 2008, at 8:20 AM, Christoph LANGE wrote:
>
>> On Tuesday 02 December 2008 12:52:15 James Fuller wrote:
>>>
>>> u might want to take another look at xquery  ... I have found that
>>> most of the functional idioms are doable with extensions (1st class
>>> funcs) and XQuery lends itself readily to working with XML... u may
>>> even find you can port your code through time by directly using your
>>> existing xslt transforms from within XQuery as you figure out
>>> refactoring them.
>>
>> Thanks, sounds interesting!  Now that I only have basic knowledge about
>> XQuery, could you tell me
>>
>> * how to use XSL transformations from within XQuery
>
> very clumsily if you are using an XML DB, losing the advantage that you gain
> by the XML DB

w/o functional idioms then yes I agree, but once funcs are first class
then all that awkwardness goes away.

please expand ?

>> * where to find such functional extensions
>> ?
>
> You *get* to make/maintain different XQuery templates for each processor you
> want to try out/use.


I agree that we need the equiv of EXSLT for XQuery quick ...
functional sigs are all different everywhere and all this is just
vendor lockin in a new disguise.

> XQuery - the thinking man's PHP (but without PHP's standardization)

hehe, I never knew that php had standardisation (I assume u being
ironic??) and dont get me started on the probs associated with php
(all funcs in the same namespace is a start ...)

... as for xquery it was never intended to be used as a replacement
for php ... its an answer to sql

The relational data model is based on set theory and predicate logic.
Data is represented as n-ary relations and the use of relational
algebra is applicable. XQuery addresses the need of the xml data
model.

that being said XQuery is a useful language in its own right, just as
much as XSLT is.

Jim Fuller
> -Rob
>
>>
>>
>> Then, I'm not so sure whether XQuery is the right solution for my problem,
>> as
>> the processing order in which I do most of my XML->RDF extraction is a
>> depth-first recursive traversal of the input tree, i.e. what XSLT gives me
>> for
>> free.
>>
>> Thanks in advance,
>>
>> Christoph
>>
>> --
>> Christoph Lange, Jacobs Univ. Bremen, http://kwarc.info/clange, Skype
>> duke4701
>>
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l...
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent