[sldev] Call for requirements: ISO MPEG-V (mpeg for virtual worlds) Deadline: July 16, 2008

Bj Raz whitequill.bj at gmail.com
Sat May 31 23:32:55 PDT 2008


I think this doesn't' fit in what is being said at this moment, but this is
what I see as what the new standard doing.

What I see here is the possibility for inter continuity between objects
within other virtual worlds, like WoW and characters to come and interact
with in SL.  Now you are breaching 3D worlds and making them one world. each
world can go to SL.  That is what I see.  Avatar transport between 3D
worlds.  Data encapsulation, from one platform (virtual world) to another.
 WoW -> SL

On Mon, May 26, 2008 at 4:59 PM, Lawson English <lenglish5 at cox.net> wrote:

> Lawson English wrote:
>
>> Tateru Nino wrote:
>> [...]
>>
>>> The way I see it, it doesn't matter actually much *what* it is carrying.
>>> Ultimately we're talking about a transport protocol. Now, so long as the
>>> transport protocol is (a) bi-directional, and (b) supports connections to
>>> arbitrary network endpoints, and (c) is relatively legally unencumbered
>>> (requires no particular licensing to use or implement), and (d) relatively
>>> technically unencumbered (doesn't hamper or impede things to the point where
>>> there is no point in actually using it) -- well, then we'd be gold.
>>>
>>
>> Those seem to be the very issues that MPEG-4 lacks. Allisa mentioned other
>> initiatives that are meant to be about networking protocols and it sounds
>> like those issues ARE addressed there, specifically in MPEG-21/SC29(?).
>>
>>
>> Lawson
>>
>>  Lots of intereseting stuff here, especially concerning digital rights and
> permissions. I'm putting a link to MPEG-21 on the AW Groupies page (thanks
> Allisa):
>
> http://www.chiariglione.org/mpeg/standards/mpeg-21/mpeg-21.htm#_Toc23297977
>
>
> 5.5 MPEG-21 Part 5 – Rights Expression Language
>
> Following an extensive requirements gathering process, which started in
> January 2001, MPEG issued a Call for Proposals during its July meeting in
> Sydney for a Rights Data Dictionary and a Rights Expression Language.
> Responses to this Call were processed during the December meeting in Pattaya
> and the evaluation process established an approach for going forward with
> the development of a specification, expected to be an International Standard
> in late 2003.
>
> A Rights Expression Language is seen as a machine-readable language that
> can declare rights and permissions using the terms as defined in the Rights
> Data Dictionary.
>
> The REL is intended to provide flexible, interoperable mechanisms to
> support transparent and augmented use of digital resources in publishing,
> distributing, and consuming of digital movies, digital music, electronic
> books, broadcasting, interactive games, computer software and other
> creations in digital form, in a way that protects digital content and
> honours the rights, conditions, and fees specified for digital contents. It
> is also intended to support specification of access and use controls for
> digital content in cases where financial exchange is not part of the terms
> of use, and to support exchange of sensitive or private digital content.
>
> The Rights Expression Language is also intended to provide a flexible
> interoperable mechanism to ensure personal data is processed in accordance
> with individual rights and to meet the requirement for Users to be able to
> express their rights and interests in a way that addresses issues of privacy
> and use of personal data.
>
> A standard Rights Expression Language should be able to support guaranteed
> end-to-end interoperability, consistency and reliability between different
> systems and services. To do so, it must offer richness and extensibility in
> declaring rights, conditions and obligations, ease and persistence in
> identifying and associating these with digital contents, and flexibility in
> supporting multiple usage/business models.
>
> 5.5.1 MPEG REL Data model
>
> MPEG REL adopts a simple and extensible data model for many of its key
> concepts and elements.
>
> The MPEG REL data model for a rights expression consists of four basic
> entities and the relationship among those entities. This basic relationship
> is defined by the MPEG REL assertion "grant". Structurally, an MPEG REL
> grant consists of the following:
>
> The principal to whom the grant is issued
> The right that the grant specifies
> The resource to which the right in the grant applies
> The condition that must be met before the right can be exercised
>
> [etc]
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20080601/3ff2f7d2/attachment.htm


More information about the SLDev mailing list