Hi,

this is my first try to jump into this discussion. May be some questions are
already answered...

On Mit, 27 Sep 2000, you wrote:
> What an XML Update Language SHOULD BE:
> --------------------------------------
> 
>    - A simple, yet powerful query, aggregation,  and update language
>      for XML repositories.

+1

>    - Implementation agnostic.  We should not define how and where a
>      repository stores its data.

I see this XUpdate language as the opposite of XPath. Where XPath applies
read-only queries, XUpdate will apply read-write queries. XPath defines the
query what to search in the document, but not where to find the documents to
query. So why should XUpdate define where to find the documents to update?

>    - A framework for querying and building document sets in disparate
>      locations.

The location of the document to update should be defined in the query?

>    - A harness for executing implementation-specific logic.

Can you explain this a little bit more? What can I expect from this harness?

>    - Built on top of existing W3C standards like XPath and XPointer.

+1

>    - Open to future extensibility.

+1

> What an XML Update Language SHOULD NOT BE:
> ------------------------------------------
> 
>    - A swiss-army knife that tries to be everything to everyone.

+1

>    - A transformation language like XSLT (been done).

Hmm, XSLT does exactly what we want to do: transformation of a document or at
least the content of a document. What is the disadvantage of using XSLT?

>    - A document-centric query language like XQL or XPath (been done).
>    - Designed specifically favoring a vendor's current implementation.
>      (Unless that implementation meets every proposed requirement)

+1

>    - Designed dependant on a XML object or parser model (DOM, SAX).

+1

> 
> XML Update Language Implementations MUST:
> -----------------------------------------
> 
>    - Provide a minimal set of standardized base logic as determined by
>      the XML:DB initiative.  This logic includes string, math, and
>      date manipulation routines.

Hmm, how will you ensure the correctness of datatypes? Schema?

Lars
-- 
___________________________________________________________________
Lars Martin                                 mailto:[EMAIL PROTECTED]
SMB GmbH                                     http://www.smb-tec.com

------------------------------------------------------------------
Post a message:          mailto:[EMAIL PROTECTED]
Unsubscribe:             mailto:[EMAIL PROTECTED]
Contact adminstrator:    mailto:[EMAIL PROTECTED]
Read archived messages:  http://www.xmldb.org/
------------------------------------------------------------------

Reply via email to