IETF Logo Mail Archive

Re: [siprec] draft-ram-siprec-metadata-format-01

Peter Saint-Andre <stpeter@stpeter.im> Thu, 31 March 2011 09:05 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: siprec@core3.amsl.com
Delivered-To: siprec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6099628C1BF for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 02:05:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.583
X-Spam-Level:
X-Spam-Status: No, score=-101.583 tagged_above=-999 required=5 tests=[AWL=-0.784, BAYES_00=-2.599, J_CHICKENPOX_210=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_29=0.6, USER_IN_WHITELIST=-100]
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 dK98z+uEKgfR for <siprec@core3.amsl.com>; Thu, 31 Mar 2011 02:05:12 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 11DA328C1B6 for <siprec@ietf.org>; Thu, 31 Mar 2011 02:05:12 -0700 (PDT)
Received: from dhcp-12cb.meeting.ietf.org (dhcp-12cb.meeting.ietf.org [130.129.18.203]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9D69540022; Thu, 31 Mar 2011 03:08:41 -0600 (MDT)
Message-ID: <4D944429.10607@stpeter.im>
Date: Thu, 31 Mar 2011 11:06:49 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <4D93ADCB.2050106@stpeter.im> <4D94416E.7070102@cisco.com>
In-Reply-To: <4D94416E.7070102@cisco.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms010205070802020502050307"
Cc: "siprec@ietf.org" <siprec@ietf.org>
Subject: Re: [siprec] draft-ram-siprec-metadata-format-01
X-BeenThere: siprec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Recording Working Group Discussion List <siprec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/siprec>
List-Post: <mailto:siprec@ietf.org>
List-Help: <mailto:siprec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/siprec>, <mailto:siprec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 09:05:13 -0000

I am booked through 11 PM tonight.

Tomorrow I have the following windows of time:

07:00-07:30
15:15-16:00

Naturally that time might get filled if issues come up in some of my
working groups. :)

On 3/31/11 10:55 AM, Paul Kyzivat wrote:
> Peter/Joe,
> 
> Do either of you have any time in the remainder of the week when some of
> us could sit and try to sort out the right way to do the extension data?
> I doubt it would take very long.
> 
>     Thanks,
>     Paul
> 
> On 3/30/2011 6:25 PM, Peter Saint-Andre wrote:
>> Here is some quick feedback on draft-ram-siprec-metadata-format-01. I
>> hope to review it more fully soon.
>>
>> 1. I would change application/recording to application/recording+xml in
>> accordance with RFC 3023 (many specs illustrate the use of XML media
>> types -- see for example RFC 4287).
>>
>> 2. The large number of<extensiondata/>  elements is a bit confusing in
>> the examples.
>>
>> 3. In Section 5.1, the example has one<extensiondata/>  element
>> qualified by the 'urn:ietf:params:xml:ns:siprec' namespace (no other
>> namespace is defined) and then multiple<extensiondata/>  elements
>> qualified by other namespaces ('http://example.com/groupapp',
>> 'http://example.com/sessionapp', etc.). Although those other namespaces
>> are certainly *allowed* to use "extensiondata" as an element name
>> (that's the beauty of namespaces), it is confusing in this document.
>> Perhaps you even meant to have<extensiondata/>  elements qualified by
>> the 'urn:ietf:params:xml:ns:siprec' and then child elements qualified by
>> other namespaces (in accordance with the schema). However, that is not
>> clear in the spec.
>>
>> 4. There is no built-in datatype for xs:urnuuid, xs:streamMode,
>> xs:requester, and so on. See W3C XML Schema Part 2:
>>
>>     http://www.w3.org/TR/xmlschema-2/#built-in-datatypes
>>
>> 5. The data in the<name/>  elements with xml:lang="it" really should be
>> Giulietta Capuleti and Romeo Montecchi. ;-)
>>
>> Peter
>>
>>
>>
>>
>> _______________________________________________
>> siprec mailing list
>> siprec@ietf.org
>> https://www.ietf.org/mailman/listinfo/siprec
> _______________________________________________
> siprec mailing list
> siprec@ietf.org
> https://www.ietf.org/mailman/listinfo/siprec


-- 
Peter Saint-Andre
https://stpeter.im/

v2.23.0 | Report a Bug | By Email