automated disapproval should happen fairly quickly -- specialist disapproval could be a few minutes or years.
i believe there is an extensive list of tests from google. disapproval unrelated to attributes directly are problematic; but there should be a fairly extensive list of affiliate websites and the like; realistically, google-base requires specialist for the very reason that no algorithm can detect all possible rules, policies, or terms-of-service violations. any serious disapproval inspection would need to include the same similar process of carefully reading all rules, policies, and terms to compare them against the items and websites being considered for submission -- by a person; i believe tom can spot a knockoff within a few picoseconds. there are middle-ground disapproval scenarios; as example, google-base rules describe that titles and descriptions should match website landing-page's; we've written code to test that; and there are similar examples for almost all attributes defined by google -- there's also matching items against a known list of knockoffs and illicit words. by definition disapproval is usually policy related -- but "disapproval" related to attributes themselves are usually by rejecting improper values, most well-defined. the rather extensive list of tests from google can be translated into all manner of implementations. e.g. # #define GB_ERRNO1 "not a number" #define GB_ERRNO18 "unknown year" #define GB_ERRNO53 "error missing title" #define GB_ERRNO54 "warning duplicate title" #define GB_ERRNO68 "invalid format" #define GB_ERRNO72 "unknown item-type" #define GB_ERRNO79 "too many characters" #define GB_ERRNO82 "bad or unknown price" #define GB_ERRNO90 "html-tag warning" #define GB_ERRNO92 "unbalanced quote" #define GB_ERRNO93 "item tab count error" #define GB_ERRNO94 "invalid expiration" #define GB_ERRNO95 "bad image_link content from website" #define GB_ERRNO98 "title content website mismatch" #define GB_ERRNO109 "XML invalid c: namespace declaration" #define GB_ERRNO110 "XML invalid namespace" #define GB_ERRNO112 "XML Parsing error" #define GB_ERRNO113 "XML Format error" #define GB_ERRNO114 "XML UnsupportedEncoding" #define GB_ERRNO117 "XML Entity name must immediately follow the '&'" # --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
