Database.com Metadata API Developer's Guide - Salesforce.com

Metadata TypesQueueProfile30.0The wildcard “*” on CustomObject does not match standard objects and this helps to avoid making unintended, high-impactprofile changes. If you create a few custom objects in a Developer Edition organization, retrieve() the information, andsubsequently deploy() the custom objects to your production organization, the profile and field-level security for all yourstandard objects, such as Account, and standard fields are not overwritten unless you explicitly create separate types elementsfor the standard objects or fields.Metadata API intentionally makes it somewhat difficult to include standard fields in retrieve() calls in order to preventunexpected profile changes. However, you can still retrieve and deploy profile permissions for custom and standard fields instandard objects, such as Account.The next package.xml file allows you to return profile permissions for Account standard and custom fields. Note how thestandard Account object is defined in a types element by specifying it as a member of a CustomObject type.AccountCustomObject*Profile30.0The final package.xml file allows you to return profile permissions for the MyCustomField__c custom field in the Accountobject.Account.MyCustomField__cCustomField*Profile30.0QueueRepresents a holding area for items before they are processed.Declarative Metadata File Suffix and Directory LocationThe file suffix for queue components is .queue and components are stored in the queues directory of the correspondingpackage directory. This component supports cases, leads, service contracts (if Entitlements are enabled), and custom objects.VersionQueue components are available in API version 24.0 and later.137