Subject: [Simple] Comments on draft-ietf-simple-xcap-list-usage-03

From: [email-masked]
Date: Wed, 28 Jul 2004 16:42:06 +0300

Most of the comments are nits. When fixed, I believe the draft is ready.

Abstract and Intro
---------------------

They talk about presence list service. Where is presence list service defined. Where is presence list server defined? I think any reference to this service should be removed from the abstract. It can be defined in the introduction before it is used as an example for resource lists.

- 1st para in abstract: s/ can created / can be created

Section 3.1
-------------

- 6th para: s/ sequence elements / sequence of elements
- 7th para: s/ <entry-ref&gt / <entry-ref>
- 7th para: s/ <entry / <entry>
- 10th para:  s/ are the purposes / are for the purposes

- an <external> reference a <list>. Any reason why it cannot reference and <entry>? I don't feel strongly about this.

- I don't feel strongly about this either, but I was just wondering about the possibility of the server just using an <entry> element instead of the <external> and <entry-ref> element. The server would realise that it needs to retrieve a referenced entry by examining the URI in the entry. If it is an XCAP URI, then it knows it needs to fetch it.

Section 3.4.4
--------------

- It does not stat how uniqueness is determined to the "name" attribute.

Section 3.4.6
---------------

- last para: "Any characters that are escape encoded are un-escaped,
   and only re-escaped if they cannot be represented within their
   component of the URL"

What does the second part of that sentence mean? Please elaborate.

Section 4.4.4
--------------

- last bullet: s/ fail the with / fail with

Section 4.5
------------

- last bullet: s/ <external< / <external>

Section 8.2
------------

- Reference 17 is not used anywhere. Remove.

Regards,
Hisham

_______________________________________________
Simple mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/simple