From b6f23740fb2648267c9e001fc5774367b69d11a6 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Sat, 17 Oct 2009 02:53:27 +0000 Subject: [PATCH] 0.3 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3550 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0227.xml | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/xep-0227.xml b/xep-0227.xml index 439d123b..4930212e 100644 --- a/xep-0227.xml +++ b/xep-0227.xml @@ -28,6 +28,18 @@ henoch@dtek.chalmers.se legoscia@jabber.cd.chalmers.se + + Waqas + Hussain + waqas20@gmail.com + waqas@jaim.at + + + 0.3 + 2009-10-16 + wh +

Modified to include feedback received during the initial Last Call. Added sections for privacy lists and incoming subscriptions, as well as text on XInclude security.

 + 0.2 2007-12-13 @@ -280,7 +292,7 @@ -

An exporting server may split the data in several files by using the XInclude <include/> element. An importing server MUST support <include/> elements having an 'href' attribute containing a relative URI, having no 'parse' attribute, and having no 'xpointer' attribute; it MAY support other kinds of <include/> elements. An exporting server SHOULD NOT include and an importing server SHOULD NOT process <include/> elements which are decendents, but not children of the <user/> element (since these may be part of user data).

+

An exporting server may split the data in several files by using the XInclude <include/> element. An importing server MUST support <include/> elements having an 'href' attribute containing a relative URI, having no 'parse' attribute, and having no 'xpointer' attribute; it MAY support other kinds of <include/> elements. An exporting server SHOULD NOT include and an importing server SHOULD NOT process <include/> elements which are descendants, but not children of the <user/> element (since these may be part of user data).

If an exporting server chooses to split the data into several files, it SHOULD use the following scheme:

@@ -351,7 +363,7 @@

Exported data files are to be handled with care, since they contain data that users expect to be protected, in particular passwords. An exporting server SHOULD make sure that the generated file is not accessible to unauthorized persons, e.g. by enforcing strict file permissions.

-

XInclude <include/> elements which are indirect descendents of the <user/> element SHOULD be treated as opaque user data, and SHOULD NOT be processed.

+

XInclude <include/> elements which are indirect descendants of the <user/> element SHOULD be treated as opaque user data, and SHOULD NOT be processed.