RE: [xml-dev] [ANN] Ipedo XML Database 3.1 Now Available

["Chris Parkerson" <cparkerson@ipedo.com>]

Dare:

More answers:

1)  Just like anyone else that would take this risk to make customers
happy, we'll cross that bridge when we get to it and provide any
necessary migration path for our customers to the final specification.
We had to do the same for XML Schema when we were implementing early
drafts.  Supporting the standard is important, but not as important as
serving our customers' needs.

2)  (From our XQuery engineers): The result of your query is the boolean
value "false" since the constructed element foo gets a type annotation
of "xs:anyType".  If the constructed element had been "validated" (i.e.,
a validate expression was used to validate the constructed element with
respect to the schema definitions in scope), it would have had a type
annotation corresponding to fooType, and the "instance of" operator
would have returned "true".

Hope this helps,
Chris
 
Chris Parkerson
Product Manager
http://www.ipedo.com
Direct (650)306-4027
Fax    (650)306-4001



-----Original Message-----
From: Dare Obasanjo [mailto:dareo@microsoft.com] 
Sent: Monday, July 22, 2002 5:50 PM
To: Chris Parkerson; xml-dev@lists.xml.org
Subject: RE: [xml-dev] [ANN] Ipedo XML Database 3.1 Now Available


Thanks for your response.

So now I have more questions: 

1.) So what happens if the XQuery WG decides to add update syntax &
semantics which differ significantly from Jonathan Robie's draft as
happened with Microsoft with both XSL/XSLT and XDR/XSD? 

2.) So since you have schema importation abilities and schema aware
processing can you tell me the results of this query according to your
product 

Given the following schema

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";
  elementFormDefault="qualified"
  targetNamespace="http://www.example.com";
  xmlns:myns="http://www.example.com";>

 <xs:element name="foo" type="myns:fooType" />

  <xs:complexType name="fooType" >  
   <xs:element name="bar" minOccurs="3" maxOccurs="6" />
  </xs:complexType>

</xs:schema>

and the query

	schema namespace myns="http://www.example.com"; at
"http:/www.example.com/foo.xsd"
	$foo = <myns:foo>{
document("http://www.example.org/bar.xml";)//myns:bar }</myns:foo>
	$foo instance of element of type myns:fooType

what is the result according to your product or do the above 3 lines
utilize an unsupported feature? 

Thanks again for your answers. 

-- 
PITHY WORDS OF WISDOM 
He who laughs last didn't catch on very fast, did he? 

This posting is provided "AS IS" with no warranties, and confers no
rights. 



> -----Original Message-----
> From: Chris Parkerson [mailto:cparkerson@ipedo.com]
> Sent: Monday, July 22, 2002 5:34 PM
> To: Dare Obasanjo; xml-dev@lists.xml.org
> Subject: RE: [xml-dev] [ANN] Ipedo XML Database 3.1 Now Available
> 
> 
> Dare:
> 
> Answers to your questions:
> 
> - We implemented the SoftwareAG XQuery update proposal
> presented by Jonathan Robie with a few extensions.  Our goal 
> is to bring our XQuery update implementation in-line quickly 
> with whatever the final spec is.
> 
> - We support the data types defined in XML Schema - Part 2
> (DataTypes) 
> <http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/>.  So, 
> we import our type definitions from the schema: either the 
> schema of the document being queried (which we know, if it is 
> stored in a typed collection) or a schema defined with the 
> XQuery SCHEMA function (for documents stored in untyped 
> collections for which we do not know the schema).
> 
> We have two members on the XML Query Working Group monitoring
> everything to make sure our implementations are not too far 
> off.  But, we can't and our customers cannot wait for the W3C 
> to hash everything out, so we move on =>
> 
> Hope this helps,
> Chris
>  
> Chris Parkerson
> Product Manager
> http://www.ipedo.com
> Direct (650)306-4027
> Fax    (650)306-4001
> 
> 
> 
> -----Original Message-----
> From: Dare Obasanjo [mailto:dareo@microsoft.com]
> Sent: Monday, July 22, 2002 4:16 PM
> To: Chris Parkerson; xml-dev@lists.xml.org
> Subject: RE: [xml-dev] [ANN] Ipedo XML Database 3.1 Now Available
> 
> 
> > -----Original Message-----
> > From: Chris Parkerson [mailto:cparkerson@ipedo.com]
> > Sent: Monday, July 22, 2002 4:03 PM
> > To: xml-dev@lists.xml.org
> > Subject: [xml-dev] [ANN] Ipedo XML Database 3.1 Now Available
> > 
> > 
> > Ipedo has released a new vision of it's award-winning XML product
> > suite. This new version includes an updated version of the 
> Ipedo XML
> > Database, PC Magazine's Editor's Choice
> > <http://www.pcmag.com/article2/0,4149,63211,00.asp> for Best XML 
> > Database, and Ipedo Web Express, a toolkit that accelerates 
> > development of XML-based J2EE web applications. Other new 
> features in
> > the 3.1 release include:
> > - Update support via XQuery - extensions to Ipedo's XQuery interface

> > to support granular XML updates, in-line with the current update 
> > syntax proposals before the W3C
> 
> Two questions:
> 
> 1.) What update syntax proposals before the W3C?
> 
> 2.) According to your website's[0] "Features At A Glance"
> section your product has 
> 
>    * Support for the latest XML standards including XML
> Schema, XQuery and XSLT
> 
> Given that the current XQuery working draft[1] states
> 
> "XQuery is a strongly typed language. Rules for assigning
> types to XQuery expressions are described in [XQuery 1.0 
> Formal Semantics]. A query may import type definitions from a 
> Schema, according to rules that will be specified in a future 
> edition of [XQuery 1.0 Formal Semantics]."
> 
> 
> I am curious as to how you guys support XQuery since the type
> system, schema importation and the entire formal semantics is 
> pretty much still in a state of flux with significant 
> questions still to be answered. Does Ipedo implement the 
> XQuery type system? If so which W3C document does it conform 
> to and if not isn't that the whole point of XQuery? 
> 
> I guess I could just download the trial version (if there are no legal
> issues) but its always good to talk to XQuery implementers
> since I don't think I've read or heard any opinions/comments 
> about it from anyone that doesn't work for MS. 
> 
> 
> [0] http://www.ipedo.com/html/products_xml_dat.html
> [1] http://www.w3.org/TR/2002/WD-xquery-20020430
> 
> --
> PITHY WORDS OF WISDOM 
> Going the speed of light is bad for your age.
> 
> This posting is provided "AS IS" with no warranties, and
> confers no rights. 
> 
> 
> 
>