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

Oscar Novo <oscar.novo@ericsson.com> Wed, 20 April 2011 08:23 UTC

From: Oscar Novo <oscar.novo@ericsson.com>
To: Tim Bray <tbray@textuality.com>
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: <58E207308662A748A4AC1ECB4E88561408142CBBE6@ESESSCMS0355.eemea.ericsson.se>
References: <BANLkTikd6=Bo4db3N4x9TFKKoKPUWOGMig@mail.gmail.com> <58E207308662A748A4AC1ECB4E88561408142CB8CA@ESESSCMS0355.eemea.ericsson.se> <BANLkTinLaisSOaAYJZ0s2QK6WBWpzxc3BA@mail.gmail.com>
In-Reply-To: <BANLkTinLaisSOaAYJZ0s2QK6WBWpzxc3BA@mail.gmail.com>
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
Cc: "Dave.Morgan@fmr.com" <Dave.Morgan@fmr.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, S Moonesamy <sm+ietf@elandsys.com>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "jari.urpalainen@nokia.com" <jari.urpalainen@nokia.com>, "alan.b.johnston@gmail.com" <alan.b.johnston@gmail.com>
Subject: Re: [apps-discuss] Apps-team review of draft-ietf-xcon-common-data-model-25.txt
Precedence: list

Hi,

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." 

Cheers,

Oscar

-----Original Message-----
From: Tim Bray [mailto:tbray@textuality.com] 
Sent: 19. huhtikuuta 2011 20:42
To: Oscar Novo
Cc: apps-discuss@ietf.org; S Moonesamy; alan.b.johnston@gmail.com; Gonzalo Camarillo; Dave.Morgan@fmr.com; jari.urpalainen@nokia.com
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 <oscar.novo@ericsson.com> 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.

[apps-discuss] Apps-team review of draft-ietf-xco… Tim Bray
Re: [apps-discuss] Apps-team review of draft-ietf… Oscar Novo
Re: [apps-discuss] Apps-team review of draft-ietf… Tim Bray
Re: [apps-discuss] Apps-team review of draft-ietf… Oscar Novo