Re: [XCON] CPCP Issue 36: Removing Common Policy XML from Schema
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [XCON] CPCP Issue 36: Removing Common Policy XML from Schema



I think its a bad idea to re-defined the schema for common-policy. For problem (1), you can just define a new condition - <any-identity>, and leave the existing identity in common policy alone. For (2), its fine to say it has no meaning.

-Jonathan R.

hisham.khartabil at nokia.com wrote:

This issue affects both draft-ietf-xcon-cpcp-00.txt and
draft-ietf-xcon-conference-policy-privileges-00.txt.

Both these drafts re-define the common-policy schema defined in the
common policy draft. There are 2 reasons for this:

1. We define the <any> and <external-list> elements in <identity>.
The identity element is in common-policy defines <id> but does not
allow the extensibility of the <identity> element.

2. The <sphere> element defined in common-policy has limited use in
presence and is not useful for CPCP.

The latter can be easily fixed with some text saying to ignore the
<sphere> element if it appears. The former is harder to fix and
requires some schema re-design in common-policy.

Any ideas what to do here? I'll forward this email to geopriv for
their comments and suggestions.

Regards, Hisham

_______________________________________________ XCON mailing list XCON at ietf.org https://www1.ietf.org/mailman/listinfo/xcon


-- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Chief Technology Officer Parsippany, NJ 07054-2711 dynamicsoft jdrosen at dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com

_______________________________________________
XCON mailing list
XCON at ietf.org
https://www1.ietf.org/mailman/listinfo/xcon




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.