IABPartnerInfoType - should Address and PrimaryContact be XSD required?

Coordinator
Mar 3, 2009 at 4:24 PM
Edited Mar 3, 2009 at 5:29 PM
As discussed in January, of course everyone "would like" to have an address and primary contact for all trading partners involved. The question is whether the XSD should be strict and require values for these elements, or whether we should use documentation and best practices to "strongly encourage" this information. The element IABPartnerInfoType is currently the base for Advertiser, Agency, Publisher and Partner. This means all would follow the same restrictions.

The case I mentioned on the call is when there is both an advertiser and agency involved. The current schema would force an Address and Contact for both Advertiser and Agency. Looking through some publisher orders in our systems, I know there are many cases where the Agency will not tell the publisher who the Contact is at the Advertiser. (perhaps on purpose) In addition, it's less critical for the publisher to have stored the Advertiser address since billing and correspondence is typically just with the Agency.

Example of minimum required fields to represent an Advertiser in above scenario in the current schema:

    <Advertiser>
        <Role>Advertiser</Role>
        <PrimaryID idOwner="AAAA registry">
            <IdValue>2F9C0543-71CC-41bc-B7C6-59CD4047C628</IdValue>
        </PrimaryID>
        <Name>Fed Ex</Name>
        <Address>
            <CountryCode>US</CountryCode>
            <DeliveryAddress></DeliveryAddress>
        </Address>
        <PrimaryContact>
            <IABTypeOfContact>Primary</IABTypeOfContact>
            <PersonName>
                <GivenName>Not</GivenName>
                <FamilyName>Known</FamilyName>
            </PersonName>
        </PrimaryContact>
    </Advertiser>

Suggestion - make Address and PrimaryContact optional so that Advertiser could be represented as:

    <Advertiser>
        <Role>Advertiser</Role>
        <PrimaryID idOwner="AAAA registry">
            <IdValue>2F9C0543-71CC-41bc-B7C6-59CD4047C628</IdValue>
        </PrimaryID>
        <Name>Fed Ex</Name>
    </Advertiser>