[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XPattern Specification

• To: Alan Gutierrez <alan-xml-dev@e...>
• Subject: Re: XPattern Specification
• From: david.lyon@c...
• Date: Wed, 19 Jan 2005 16:03:39 +1100
• Cc: 'xml-dev' <xml-dev@l...>
• In-reply-to: <20050119044318.GF26849@m...>
• References: <20050116220239.GB10592@m...> <41EBAA9F.3080204@g...> <41EBC8B1.2040701@w...> <20050117144625.GA17626@m...> <41EBDB33.7050104@g...> <20050117155017.GC17990@m...> <41EBE6D1.407@g...> <20050117164510.GF17990@m...> <41ECDF1C.2080004@g...> <41ED1786.10301@w...> <20050119044318.GF26849@m...>
• User-agent: Internet Messaging Program (IMP) 3.2.6

>     Can't we think about how we'd use the langauge? Taking about
>     what we want to scratch out of XPath is jumping the gun.

>
>     I don't want to have you think that I'm suggesting an STX or
>     XUpdate like language, so much as I am considering applications.

If anybody can put together a "Grid" language for xml, that
would be useful.

Take for example, a price update event, that comes out of
a diff and looks like:

           <Product Item>
            Product_ID&="74332"
            Name&="IBM A50 DT P4 3EGHz 256MBDDR 40GB CD XPP"
            Availability&="InStock"
-           List_Price$=1183.00
+           List_Price$=1147.00
           </Product Item>

How could that be taken and then applied as an 'event' onto
an inventory system?

I know it's not a "generic" problem, rather a specific one,
but price changes do happen an awful lot in the real world
and it would be cool to have some sort of clever solution to
this.

To translate what is required, a price has changed in a
supplier catalog and the inventory system would need to
be updated in real-time.

Throughout the day, there are thousands of these darn
events.

Regards

David



----------------------------------------------------------------

• Follow-Ups:
  • Re: XPattern Specification
    • From: Alan Gutierrez <alan-xml-dev@e...>

• References:
  • XPattern Specification
    • From: Alan Gutierrez <alan-xml-dev@e...>
  • Re: XPattern Specification
    • From: Petr Cimprich <petr@g...>
  • Re: XPattern Specification
    • From: Karl Waclawek <karl@w...>
  • Re: XPattern Specification
    • From: Alan Gutierrez <alan-xml-dev@e...>
  • Re: XPattern Specification
    • From: Petr Cimprich <petr@g...>
  • Re: XPattern Specification
    • From: Alan Gutierrez <alan-xml-dev@e...>
  • Re: XPattern Specification
    • From: Petr Cimprich <petr@g...>
  • Re: XPattern Specification
    • From: Alan Gutierrez <alan-xml-dev@e...>
  • Re: XPattern Specification
    • From: Petr Cimprich <petr@g...>
  • Re: XPattern Specification
    • From: Karl Waclawek <karl@w...>
  • Re: XPattern Specification
    • From: Alan Gutierrez <alan-xml-dev@e...>

• Prev by Date: [xpattern] Stream Order Operator
• Next by Date: Re: XPattern Specification
• Previous by thread: Re: XPattern Specification
• Next by thread: Re: XPattern Specification
• Index(es):
  • Date
  • Thread