< draft-ietf-simple-winfo-format-03.txt		draft-ietf-simple-winfo-format-04.txt >
	Internet Engineering Task Force SIMPLE WG		Internet Engineering Task Force SIMPLE WG
	Internet Draft J. Rosenberg		Internet Draft J. Rosenberg
	dynamicsoft		dynamicsoft
	draft-ietf-simple-winfo-format-03.txt		draft-ietf-simple-winfo-format-04.txt
	December 3, 2002		January 31, 2003
	Expires: June 2003		Expires: July 2003
	An Extensible Markup Language (XML) Based Format for		An Extensible Markup Language (XML) Based Format
	Watcher Information		for Watcher Information
	STATUS OF THIS MEMO		STATUS OF THIS MEMO
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026.		all provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 7, line 5 ¶		skipping to change at page 7, line 5 ¶
	comparing the ID in the "id" attribute of the "watcher" element with		comparing the ID in the "id" attribute of the "watcher" element with
	the ID associated with the row. If the watcher doesn't exist in the		the ID associated with the row. If the watcher doesn't exist in the
	table, a row is added, and its state is set to the information from		table, a row is added, and its state is set to the information from
	that "watcher" element. If the watcher does exist, its state is		that "watcher" element. If the watcher does exist, its state is
	updated to be the information from that "watcher" element. If a row		updated to be the information from that "watcher" element. If a row
	is updated or created, such that its state is now terminated, that		is updated or created, such that its state is now terminated, that
	entry MAY be removed from the table at any time.		entry MAY be removed from the table at any time.
	5 Example		5 Example
	The following is an example of watcher information for a presentity,		The following is an example of watcher information for a presentity,
	who is a professor. There are two watchers, one from a university,		who is a professor. There are two watchers, userA and userB.
	and another from an organization.
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo"		<watcherinfo xmlns="urn:ietf:params:xml:ns:watcherinfo"
	version="0" state="full">		version="0" state="full">
	<watcher-list resource="sip:professor@university.edu" package="presence">		<watcher-list resource="sip:professor@example.net" package="presence">
	<watcher status="active"		<watcher status="active"
	id="8ajksjda7s"		id="8ajksjda7s"
	duration-subscribed="509"		duration-subscribed="509"
	event="approved" >sip:subcriber@university.edu</watcher>		event="approved" >sip:userA@example.net</watcher>
	<watcher status="pending"		<watcher status="pending"
	id="hh8juja87s997-ass7"		id="hh8juja87s997-ass7"
	display-name="Mr. Subscriber"		display-name="Mr. Subscriber"
	event="subscribe">sip:subcriber@organization.org</watcher>		event="subscribe">sip:userB@example.org</watcher>
	</watcher-list>		</watcher-list>
	</watcherinfo>		</watcherinfo>
	6 XML Schema		6 XML Schema
	The following is the schema definition of the watcherinfo document		The following is the schema definition of the watcherinfo document
	format:		format:
	<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"		<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
	targetNamespace="urn:ietf:params:xml:ns:watcherinfo"		targetNamespace="urn:ietf:params:xml:ns:watcherinfo"
	skipping to change at page 12, line 34 ¶		skipping to change at page 12, line 34 ¶
	dynamicsoft		dynamicsoft
	72 Eagle Rock Avenue		72 Eagle Rock Avenue
	East Hanover, NJ 07936		East Hanover, NJ 07936
	email: jdrosen@dynamicsoft.com		email: jdrosen@dynamicsoft.com
	12 Normative References		12 Normative References
	[1] A. B. Roach, "Session initiation protocol (sip)-specific event		[1] A. B. Roach, "Session initiation protocol (sip)-specific event
	notification," RFC 3265, Internet Engineering Task Force, June 2002.		notification," RFC 3265, Internet Engineering Task Force, June 2002.
	[2] J. Rosenberg, "A session initiation protocol (SIP)event		[2] J. Rosenberg, "A watcher information event template-package for
	template-package for watcher information," Internet Draft, Internet		the session initiation protocol (SIP)," internet draft, Internet
	Engineering Task Force, May 2002. Work in progress.		Engineering Task Force, Dec. 2002. Work in progress.
	[3] S. Bradner, "Key words for use in RFCs to indicate requirement		[3] S. Bradner, "Key words for use in rfcs to indicate requirement
	levels," RFC 2119, Internet Engineering Task Force, Mar. 1997.		levels," RFC 2119, Internet Engineering Task Force, Mar. 1997.
	[4] W. W. W. C. (W3C), "Extensible markup language (xml) 1.0." The		[4] T. Bray, J. Paoli, and C. M. Sperberg-McQueen, "Extensible markup
	XML 1.0 spec can be found at http://www.w3.org/TR/1998/REC-xml-		language (XML) 1.0 (second edition)," W3C Recommendation REC-xml-
	19980210.		20001006, World Wide Web Consortium (W3C), Oct. 2000. Available at
			http://www.w3.org/XML/.
	[5] R. Moats, "URN syntax," RFC 2141, Internet Engineering Task		[5] R. Moats, "URN syntax," RFC 2141, Internet Engineering Task
	Force, May 1997.		Force, May 1997.
	[6] R. Moats, "A URN namespace for IETF documents," RFC 2648,		[6] R. Moats, "A URN namespace for IETF documents," RFC 2648,
	Internet Engineering Task Force, Aug. 1999.		Internet Engineering Task Force, Aug. 1999.
	[7] M. Mealling, "The IETF XML registry," Internet Draft, Internet		[7] M. Mealling, "The IETF XML registry," internet draft, Internet
	Engineering Task Force, July 2002. Work in progress.		Engineering Task Force, July 2002. Work in progress.
	[8] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J.		[8] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. R. Johnston, J.
	Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP: session		Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP: session
	initiation protocol," RFC 3261, Internet Engineering Task Force, June		initiation protocol," RFC 3261, Internet Engineering Task Force, June
	2002.		2002.
	[9] M. Murata, S. S. Laurent, and D. Kohn, "XML media types," RFC		[9] M. Murata, S. S. Laurent, and D. Kohn, "XML media types," RFC
	3023, Internet Engineering Task Force, Jan. 2001.		3023, Internet Engineering Task Force, Jan. 2001.
	[10] J. Rosenberg, "Session initiation protocol (SIP) extensions for		[10] J. Rosenberg, "A presence event package for the session
	presence," Internet Draft, Internet Engineering Task Force, May 2002.		initiation protocol (SIP)," internet draft, Internet Engineering Task
	Work in progress.		Force, Dec. 2002. Work in progress.
	13 Informative References		13 Informative References
	[11] M. Day, J. Rosenberg, and H. Sugano, "A model for presence and		[11] M. Day, J. Rosenberg, and H. Sugano, "A model for presence and
	instant messaging," RFC 2778, Internet Engineering Task Force, Feb.		instant messaging," RFC 2778, Internet Engineering Task Force, Feb.
	2000.		2000.
			Intellectual Property Statement
			The IETF takes no position regarding the validity or scope of any
			intellectual property or other rights that might be claimed to
			pertain to the implementation or use of the technology described in
			this document or the extent to which any license under such rights
			might or might not be available; neither does it represent that it
			has made any effort to identify any such rights. Information on the
			IETF's procedures with respect to rights in standards-track and
			standards-related documentation can be found in BCP-11. Copies of
			claims of rights made available for publication and any assurances of
			licenses to be made available, or the result of an attempt made to
			obtain a general license or permission for the use of such
			proprietary rights by implementors or users of this specification can
			be obtained from the IETF Secretariat.
			The IETF invites any interested party to bring to its attention any
			copyrights, patents or patent applications, or other proprietary
			rights which may cover technology that may be required to practice
			this standard. Please address the information to the IETF Executive
			Director.
	Full Copyright Statement		Full Copyright Statement
	Copyright (c) The Internet Society (2002). All Rights Reserved.		Copyright (c) The Internet Society (2003). All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published		or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any		and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph are		kind, provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other		the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of		Internet organizations, except as needed for the purpose of
End of changes. 14 change blocks.
	23 lines changed or deleted		45 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/