That clears that up (dry-run v. draft). But I don't think the API has a dry-run setter. The really clever might be able to inject the appropriate element.
On Sep 28, 12:36 am, Celebird <[EMAIL PROTECTED]> wrote: > dry-run and draft are completely different. > > draft is for hiding items -- making them > invisible via snippets and unsearchable > by setting the item's status. > > dry-run is for validation -- submits no data, > and is activated as a flag to the service-uri. > > the combination is a sandbox of sorts -- > items can first be validated via dry-run; > then, using your dashboard, the edit-and-preview of draft > items may catch obvious disapproval issues for example. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Base Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Base-data-API?hl=en -~----------~----~----~----~------~----~------~--~---
