RE: linking to external xml and xsd sources

> 
> 2) linking to model and instance
> 
> are the model and instance elements required to appear in the 
> XForm document
> itself or can they be linked to like this ???
> 
> <model src="http://www.schema-provider.net/purchaseOrder.xsd"/>
> <instance src="http://www.data-provider.net/purchaseOrder.xml"/>
> 
> As XForms "will be designed to cleanly distinguish between 
> form instance
> data, form description ... and form presentation" [cite] this 
> should be no
> problem. 

I think we meant logically separated and not physically separated. 

But I would certainly support, and has proposed to the list long ago, that it should be possible to have the data model in a separate document; the client may  even use the URL to identify a "well-known" data model; and does not have to download the data model document.


> 
> But it brings up a whole bunch of new requirements like
> 
>   a) selecting subsets of the instance data :
> 
>       <instance src="http://www.data-provider.net/purchaseOrder.xml" 
>                     where="purchaseOrder/shipTo[name]='Alice Smith'"/>
>

Yes, we will have to think about how we refer to the data model from the instance. For example, it could be:

<instance id="f1" modelLocation="http://www.ericsson.se/phonenumbers" />



>   b) resolving concurrent updates / locking:
> 
>       <instance src="http://www.data-provider.net/purchaseOrder.xml" 
>                     where="purchaseOrder/shipTo[name]='Alice Smith'"
>                     for-update="true" />
> 
>   c) re-ordering instance-data
> 
>   d) caching instance data at client-side / persistence of cached data
> 
>

Not sure the ability to refer to an external data model implies that we must support all this. But (d) is related to SEND.


PS

Received on Sunday, 10 September 2000 05:13:55 UTC