Sorry, I wasn't suggesting that there exists freely available software (from google or otherwise) to do the verification. But I guess I would like some thing a little more concrete from google about what is tested and how. I'll happily write tests against that definition. Call me lazy, but since one runs some risk of getting a client booted out for certain types transgressions I think an explicit definition is not asking too much. In the extreme cases, reacting (asynchronously) to rejected items can be a case of closing the barn door after the horses have left.
Thanks as always for your comments and clarifications. On Feb 2, 9:01 pm, Celebird <[email protected]> wrote: > there's no automated pre-verification > software from google that i know about. > > there's no api or similar solution for the > disapproval definitions; but i believe there > is enough explicit and implicit definitions > in existing documentation to write fairly > accurate and extensive safeguards -- > i've reached over 150 so far. > > the key word is *should* happen fairly quickly -- > there may be only a few attributes that are both > defined as causing disapproval and offer recovery; > this is probably as purposeful as the police not > issuing warnings at every traffic violation. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
