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

Dzonatas Sol <dzonatas@gmail.com> Wed, 30 March 2011 22:47 UTC

Return-Path: <dzonatas@gmail.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 BE6F928C0F7 for <vwrap@core3.amsl.com>; Wed, 30 Mar 2011 15:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.518
X-Spam-Level:
X-Spam-Status: No, score=-3.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, 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 q0fj6QGXSR1H for <vwrap@core3.amsl.com>; Wed, 30 Mar 2011 15:47:55 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id E69F828C0F1 for <vwrap@ietf.org>; Wed, 30 Mar 2011 15:47:54 -0700 (PDT)
Received: by iye19 with SMTP id 19so1990997iye.31 for <vwrap@ietf.org>; Wed, 30 Mar 2011 15:49:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=oqD01kU1z3dGpx6w/9RBdW2WLtmtnd5TVdtEHWzu+IA=; b=ZSqcYghH2RTxs2+1qmWmhgsZZaZU2G61uMcKz/N5AaF3ASW11qwgl+4pkG4kN441m0 fvcqQrJ9M2LIqSgu9rp1P5wrpsSrNeP4PO1ZvUcrVFtaHYx7ncTThP6sbe/Oe8szmHOZ MRXxk/x6C2iqXTonUwF4BUj3SJHd8c6tCo0nk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=hXNBfT5ATHWY31TDk0fBrvgKNivATWcCuHCHCZ5kIGRFNxVMR3glq3WARuJz6ZNBh8 lJchTfreq2tJ6YuLgjdhIz1exmAo7oPLOr5rW8KJIR5D7GabmnUjlhWkrZvxj/ny7BJ2 6h27xHfbH7WfGDbzZ3bx84U2qfuAv1BoTkfBE=
Received: by 10.42.155.194 with SMTP id v2mr1934220icw.491.1301525373744; Wed, 30 Mar 2011 15:49:33 -0700 (PDT)
Received: from [192.168.0.50] (adsl-71-137-195-251.dsl.scrm01.pacbell.net [71.137.195.251]) by mx.google.com with ESMTPS id y10sm299087iba.63.2011.03.30.15.49.28 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 Mar 2011 15:49:32 -0700 (PDT)
Message-ID: <4D93B378.8030302@gmail.com>
Date: Wed, 30 Mar 2011 15:49:28 -0700
From: Dzonatas Sol <dzonatas@gmail.com>
User-Agent: Mozilla-Thunderbird 2.0.0.24 (X11/20100329)
MIME-Version: 1.0
To: Morgaine <morgaine.dinova@googlemail.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>
In-Reply-To: <AANLkTinx2borySJgim+bAQd3p5M6iV6uZchd+CKhi1Xp@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: vwrap@ietf.org
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 22:47:55 -0000

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