it depends for what item-type and how the xml is being used. general attribute and value rules depend on the item-type;
xml format details depend on how the xml is being used -- upload as a data-feed-file, sent as an api batch file, or inserted via the api. if the example is for the products item-type, as an atom 1.0 data-feed-file, then that's incorrect. please see here for products item-type details and samples: http://base.google.com/support/bin/answer.py?answer=73932 per-item id attributes must be unique per item and must never change; for example, you might use the item's uri or a database primary key. google-base will use per-item id's to help track each item -- forever. the feed-file id attribute is a side-effect of using the atom format; this is for your internal use and isn't used by google-base directly. as to the steps, it rather depends on individual requirements and how you want google-base integrated with your website -- the steps outline are certainly one solution; for example, after the first few successful uploads via the control-panel i might then switch to using ftp to upload the data-feed-file or simply have a scheduled feed grab the data-feed-file. also, your database might have a tab-delimited export feature which might make the process even simpler. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
