http://hostname/browse/shows/234/seasons

This example URL is for an SCBP “search” action, and it returns a list of seasons for the show with an id value of 234. In this example, “234″ is an explicit value for the show id parameter. In this case the id value is passed as part of the url path, instead of a query parameter. The “/seasons” section of the url path represents an implicit parameter value with the meaning: type=”seasonal_series”. The meaning of this implicit parameter value would be discovered via the service’s SCBP WADL.

<scsp version=x.x>
    <response>
        <code>1</code>
        <message>Success.</message>
    </response>
    <capabilities>
        <subscription_duration>45</subscription_duration>    [A]
        <renewal_period>15</renewal_period>    [B]
    </capabilities>
</scsp>

[A] The number of calendar days during which the subscription is active. After this period the subscription will expire.

[B] The number of calendar days prior to the subscription expiration during which the service will allow renewal requests for the subscription. For example, if a subscription_duration is 45 and the renewal_period is 15, then 30 days after the subscription starts the service will allow a renewal request to avoid expiration. The renewal will result in a new subscription for 45 days starting from the time of renewal. Thus, the perceived subscription duration is 30 days (monthly) with a 15 day grace period for renewal.

<scsp version=x.x>
    <response>
        <code>1</code>
        <message>Your transaction was completed.</message>
    </response>
    <drm type="marlinbb">
        ...
    </drm>
    <session>348t39ghqi4ho3u4</response>
</sctp>

Note: In the case of protected content, success returns a DRM action token to acquire the subscription node.

<scsp version=x.x>
    <response>
        <code>1</code>
        <message>Your transaction was completed</message>
    </response>
    <drm type="marlinbb">
        ...
    </drm>
</scsp>

1 (success)
-1 (unknown error)
-3 (content not valid)
-8 (user not logged in)
-12 (extended error information available)
-15 (renewal too early)
-24 (missing element)

Note: In the case of protected content, success returns a DRM action token to purge the subscription node.

<scsp version=x.x>
    <response>
        <code>1</code>
        <message>Your transaction was completed</message>
        <count>5</count>
    </response>
    <subscriptions>
        <subscription>
            <id>6<id>
            <expiration>2007-04-28</expiration>
            <renew>/transact/subscribe_channel/6</renew>
            <type>Channel</type>
            <title>Cartoon Network</title>
        </subscription>
        <subscription>
            <id>7<id>
            <expiration>2008-05-31</expiration>
            <renew>/transact/subscribe_channel/7</renew>
            <type>Channel</type>
            <title>CBS</title>
        </subscription>
        ⋮
    </subscriptions>
    <drm type="marlinbb">    [A]
        ...
    </drm>
</scsp>

[A] In the case of protected content, success returns any DRM data necessary to acquire the subscription nodes listed in the response. If the service allows a renewal grace period, and the account has entered that grace period (which is some portion of time before the actual expiration of the subscription), then the service should return the DRM data needed to acquire a renewed subscription. In such as case the DRM data should allow for a subscription period which includes the grace period. For example a 30-day subscription may actually deliver DRM data for a 45-day subscription, allowing for a 15 day grace period for renewal.

Also, a service may set the expiration date of subsequent subscription nodes to be the period of time until the next account billing cycle, instead of a consistent period of time from the point of renewal. For example, a 45-day subscription with a 15-day renewal period may be renewed 35 days from the last renewal, and in this case the service may deliver a 40-day subscription in order to keep the account billing cycle on the same day each month. There is no requirement for how the service determines subscription durations upon each renewal. This is a service implementation choice.