Re: [apps-discuss] Apps-team review of draft-ietf-xcon-common-data-model-25.txt

Oscar Novo <> Wed, 20 April 2011 08:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A12AEE0796 for <>; Wed, 20 Apr 2011 01:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6xczKbnCQGMP for <>; Wed, 20 Apr 2011 01:23:52 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A782CE0791 for <>; Wed, 20 Apr 2011 01:23:51 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bd5ae000002ba3-55-4dae9816aaa4
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id E4.83.11171.6189EAD4; Wed, 20 Apr 2011 10:23:51 +0200 (CEST)
Received: from ([]) by ([]) with mapi; Wed, 20 Apr 2011 10:23:50 +0200
From: Oscar Novo <>
To: Tim Bray <>
Date: Wed, 20 Apr 2011 10:23:49 +0200
Thread-Topic: Apps-team review of draft-ietf-xcon-common-data-model-25.txt
Thread-Index: Acv+uR7GNEOyA2B+R6KH0b+M5XvAzgAeoBEg
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
X-Mailman-Approved-At: Wed, 20 Apr 2011 08:10:49 -0700
Cc: "" <>, "" <>, S Moonesamy <>, Gonzalo Camarillo <>, "" <>, "" <>
Subject: Re: [apps-discuss] Apps-team review of draft-ietf-xcon-common-data-model-25.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 20 Apr 2011 08:23:52 -0000


Thanks for your feedback. Section "3.1 Data Model Format" already take care of explaining your suggestion: 

   "A conference object document is an XML [W3C.REC-xml-20001006]
   document that MUST be well formed and SHOULD be valid.  Conference
   object documents MUST be based on Extensible Markup Language (XML)
   1.0 and SHOULD be encoded using UTF-8." 



-----Original Message-----
From: Tim Bray [] 
Sent: 19. huhtikuuta 2011 20:42
To: Oscar Novo
Cc:; S Moonesamy;; Gonzalo Camarillo;;
Subject: Re: Apps-team review of draft-ietf-xcon-common-data-model-25.txt

Looks good. Follow up:

On Tue, Apr 19, 2011 at 5:16 AM, Oscar Novo <> wrote:

> General issue: There is much discussion of the values of various elements.  There seems little discussion of whether exact case matching is required, whether white-space on either side of the designated values is allowed, and so on.  Is this obvious from the context of the other SIP RFCs?  It would trouble me as an implementor.
>  There are a couple of nits below where I've called this out.
> [ON] The RELAX NG shema is defining the syntactic of the elements. That's why the text is not giving any clear guidance about it. The implementor just has to follow the RELAX NG schema defined in this document.

So I think you need a paragraph in your introduction saying that the syntax of element values is constrained by the provided RNG grammar, which is normative; the text in the main body of the specification is explanatory, but implementation MUST generate and parse content conforming to the schema.

> 4.4.1 "The <allow-conference-event-subscription> element represents a 
> boolean action. " - should 'action' be 'value'? (this idiom also 
> appears several more times in the draft)
> [ON] I would say it's right. The element represents a boolean action. That's mean, the action can only take two boolean values.

The term "boolean" has well-defined semantics in math and in computer language type theory.  It is not applicable to an "action" in either of these senses.  But I don't care, it's obvious what you mean.