Re: [vwrap] vwrap Digest, Vol 11, Issue 24

Morgaine <morgaine.dinova@googlemail.com> Wed, 30 March 2011 23:07 UTC

Return-Path: <morgaine.dinova@googlemail.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F25528C0E8 for <vwrap@core3.amsl.com>; Wed, 30 Mar 2011 16:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.876
X-Spam-Level:
X-Spam-Status: No, score=-2.876 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AKI6mXlU+5px for <vwrap@core3.amsl.com>; Wed, 30 Mar 2011 16:07:24 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 9960428C0F1 for <vwrap@ietf.org>; Wed, 30 Mar 2011 16:07:23 -0700 (PDT)
Received: by qwg5 with SMTP id 5so1333076qwg.31 for <vwrap@ietf.org>; Wed, 30 Mar 2011 16:09:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=2qDPEayPjDvHQh/r6q1UR38GX0gXlPohy62E7YiryhY=; b=E1iCFuHVUeWTaXIZKz1XLMI4nD2QyrpBNvvC4gOuNfBQA3fAzETw8tL6jjksmGV6i+ sy3X7DmiFvPcG9J/ettL+berZsFrCFLwZdwwReADONRHxbBScTHGW+bBJwu1kbOvutk5 gajHtqhwQYFtLRxUMSqMFPDfLKRqyvbwl9530=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=hH19gHeTByLrP8quUPha8JergrfQg74LVa8jL4mnPcsqUC/YjzTnhU0b2OEIvER7cc wOLtMlX56kNZoD4/LEReD5mWjk9U2HcOxw/2qk/Znv0AA3Kv1JT2ZB5kn4kRkSEZWoya hWRZVlKhQ1pCVTMTwlqXpJD/ahTgOa1YYq8c0=
MIME-Version: 1.0
Received: by 10.229.78.228 with SMTP id m36mr1636580qck.109.1301526542552; Wed, 30 Mar 2011 16:09:02 -0700 (PDT)
Received: by 10.229.211.84 with HTTP; Wed, 30 Mar 2011 16:09:02 -0700 (PDT)
In-Reply-To: <4D93B378.8030302@gmail.com>
References: <mailman.119.1301425219.8353.vwrap@ietf.org> <AANLkTimW_yvXG3bfnTJuQ8B3fuw5z4=+mryvKETu+6Ja@mail.gmail.com> <AANLkTimB+8BMR9OvacF6JqnOf6MrD2_XUCjfAVyS5Vws@mail.gmail.com> <AANLkTinx2borySJgim+bAQd3p5M6iV6uZchd+CKhi1Xp@mail.gmail.com> <4D93B378.8030302@gmail.com>
Date: Thu, 31 Mar 2011 00:09:02 +0100
Message-ID: <AANLkTikk70SFJo-cQs3v9U152iiEGYpTrjkyZFfYLwCz@mail.gmail.com>
From: Morgaine <morgaine.dinova@googlemail.com>
To: vwrap@ietf.org
Content-Type: multipart/alternative; boundary="00235429d3563c114c049fbb4325"
Subject: Re: [vwrap] vwrap Digest, Vol 11, Issue 24
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 23:07:25 -0000

COLLADA is not *only* an interchange format, despite being defined for that
purpose originally.  Many applications now use it as their native graphics
file format, the archetypal case being Google Earth.  I expect such use to
become ever more common in the future.


Morgaine.





=======================

On Wed, Mar 30, 2011 at 11:49 PM, Dzonatas Sol <dzonatas@gmail.com> wrote:

> Remember, that COLLADA is only an exchange format, not the format for which
> something is being rendered from or to. Please make sure your semantic usage
> of such at least complies when you try to argue with it.
>
>
> Morgaine wrote:
>
>> This is the last vestige of where that term is commonly encountered, as
>> *Service Level Semantic Interoperability*.� Is it relevant to us?� Yes, a
>> little.� For example, it would do us no good to transport Collada meshes
>> from an asset service to a client that tries to render them as some other
>> graphics format --- that would create a semantic mishap, because one party
>> thinks that the items means one thing and another party applies a different
>> semantic.� So yes, there is a little more for us to consider here, but it's
>> not a lot.� In most part we have already stated the solution every time that
>> we have mentioned MIME types for describing content.� This is mostly a
>> solved problem.
>>
>>
>
> --
> --- https://twitter.com/Dzonatas_Sol ---
> Web Development, Software Engineering, Virtual Reality, Consultant
>
>