RE: [rights-examples] ln005: use case with markup for review

Title: RE: [rights-examples] ln005: use case with markup for review

One easy suggestion: MPEG is sending us their CD for review, so we can use the real MPEG draft extension for things like play.  I'm not sure when this will arrive, but it should be any day now (I'm surprised its not already here).  In any event, it can already be downloaded from

http://mpeg.telecomitalialab.com/working_documents/mpeg-21/rel/REL_cd.zip

The other thing is that the "play" right doesn't have any meaning without a resource.  The reason resource is optional is for rights like "walk" that don't have "direct objects".  So, we need to do something with respect to that.  Here are some suggestions:

<grant> 

        <forAll varName="content"> 

                <mySystem:contentOfClass method="contentHeader" class="http://www.lexisnexis.com/whatever/blues"/> 

        </forAll> 

        <dcx:play/> 

        <resource varRef="content"/> 

        <sx:territory> 

                <sx:location> 

                        <sx:country>US</sx:country> 

                </sx:location> 

                <sx:location> 

                        <sx:country>CA</sx:country> 

                </sx:location> 

                <sx:location> 

                        <sx:country>MX</sx:country> 

                </sx:location> 

        </sx:territory> 

</grant>

or

<grant> 

        <forAll varName="content"/> 

        <dcx:play/> 

        <resource varRef="content"/> 

        <allConditions>

                <mySystem:contentClass method="contentHeader">

                        <resource varRef="content"/>

                        <class>http://www.lexisnexis.com/whatever/blues</class>

                </mySystem:contentClass>

                <sx:territory> 

                        <sx:location> 

                                <sx:country>US</sx:country> 

                        </sx:location> 

                        <sx:location> 

                                <sx:country>CA</sx:country> 

                        </sx:location> 

                        <sx:location> 

                                <sx:country>MX</sx:country> 

                        </sx:location> 

                </sx:territory> 

        </allConditions>

</grant>

or

<grant> 

        <forAll varName="content"/> 

        <mx:play/> 

        <diReference varRef="content"/> 

        <allConditions>

                <mx:diCriteria>

                        <mx:diReference varRef="content"/>

                        <xmlExpression>

                                didl:Descriptor/

                                didl:Statement/

                                myMetadataScheme:genre = "blues"

                        </xmlExpression>

                </mx:diCriteria>

                <sx:territory> 

                        <sx:location> 

                                <sx:country>US</sx:country> 

                        </sx:location> 

                        <sx:location> 

                                <sx:country>CA</sx:country> 

                        </sx:location> 

                        <sx:location> 

                                <sx:country>MX</sx:country> 

                        </sx:location> 

                </sx:territory> 

        </allConditions>

</grant>

the last of these in conjunction with

<DIDL>

        <Item>

                <Descriptor>

                        <Statement>

                                <myMetadataScheme:genre>blues</myMetadataScheme:genre>

                        </Statement>

                </Descriptor>

                <Component>

                        ...

                </Component>

        </Item>

</DIDL>

I'm curious about your reaction to the e-mail I sent earlier (http://lists.oasis-open.org/archives/rights-examples/200207/msg00009.html) talking about these options?

Thanks,

Thomas.

-----Original Message-----

From: DuCharme, Bob (LNG) [mailto:]

Sent: Thursday, July 18, 2002 9:54 AM

To: ''

Subject: [rights-examples] ln005: use case with markup for review

I was able to implement the markup with XrML 2.1, so there's only one file

below. I should have mentioned in my last post that the original natural

language description of the use case is included in a header comment for

each XML file. 

If there are no suggestions for improving the markup, I will post it to the

RLTC's web site.

Bob

<!-- start of ln005.xml -->

<license xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

         xsi:noNamespaceSchemaLocation="xrml2core.xsd"

        

xmlns:sx="http://www.xrml.org/schema/2002/05/xrml2sx"

                        xmlns:dcx="http://www.snee.com/ns/dcx"

                        xmlns="http://www.xrml.org/schema/2002/05/xrml2core"

                        licenseId="ln005"

>

<!-- 

scenario ln005

This article may only be viewed by customers in the United States, Canada,

and Mexico. They may view it or print it, but may not save it as a disk

file.

 -->

  <grant>

    <dcx:play/> <!-- "render the work in a transient form" i.e. read it -->

         <sx:territory>

           <sx:location>

                  <sx:country>US</sx:country>

                </sx:location>

           <sx:location>

                  <sx:country>CA</sx:country>

                </sx:location>

           <sx:location>

                  <sx:country>MX</sx:country>

                </sx:location>

         </sx:territory>

  </grant>

  <grant>

         <dcx:print/>

         <sx:territory>

           <sx:location>

                  <sx:country>US</sx:country>

                </sx:location>

           <sx:location>

                  <sx:country>CA</sx:country>

                </sx:location>

           <sx:location>

                  <sx:country>MX</sx:country>

                </sx:location>

         </sx:territory>

  </grant>

</license>

<!-- end of ln005.xml -->

----------------------------------------------------------------

To subscribe or unsubscribe from this elist use the subscription

manager: <http://lists.oasis-open.org/ob/adm.pl>