1. Is there a way to import previously created xsd schemas when defining Business Data?
In Advanced this is trivial, and it seems that, at least when consuming a Web Service, this is possible in Standard as well. I am not consuming a Web Service, but I am creating one in Process Designer that will kick off a BPD. The business objects have already been defined and are being used in production by other tools, such as Broker. If this is not possible, I think the only alternative is to place Broker flows in front of BPM that massage the data on the way in and out.
2. Is it possible to force a Web Service definition to honor Advanced Parameter Properties for Business Objects?
When defining a Web Service, Process Designer does not output schema that matches the internal schema for the Business Data objects. I have tried setting the "enable-advanced-parameter-properties-for-wsdl" property to true, but it still does not pick up things like "List Item Name" properties. The list items in the resulting WSDL are always named "item". This is related to the above question as I am attempting to define Business Data objects in a way that the incoming structure matches what the original schemas define (they just happen to have wrapped lists already).