< draft-ietf-geopriv-loc-filters-00.txt		draft-ietf-geopriv-loc-filters-01.txt >
	WG R. Mahy		WG R. Mahy
	Internet-Draft Plantronics		Internet-Draft Plantronics
	Expires: September 21, 2006 March 20, 2006		Intended status: Standards Track March 4, 2007
			Expires: September 5, 2007
	A Document Format for Filtering and Reporting Location Notications in		A Document Format for Filtering and Reporting Location Notications in
	the Presence Information Document Format Location Object (PIDF-LO)		the Presence Information Document Format Location Object (PIDF-LO)
	draft-ietf-geopriv-loc-filters-00.txt		draft-ietf-geopriv-loc-filters-01.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	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
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 35 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on September 21, 2006.		This Internet-Draft will expire on September 5, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	This document describes filters which limit asynchronous location		This document describes filters which limit asynchronous location
	notifications to compelling events. The resulting location		notifications to compelling events. The resulting location
	information is conveyed in existing location formats wrapped in		information is conveyed in existing location formats wrapped in
	GEOPRIV privacy extensions to the Presence Information Document		GEOPRIV privacy extensions to the Presence Information Document
	Format (PIDF-LO). Location disclosure is limited to voluntary		Format (PIDF-LO). Location disclosure is limited to voluntary
	disclosure by a notifier that possesses credentials for the named		disclosure by a notifier that possesses credentials for the named
	resource.		resource.
	Table of Contents		Table of Contents
	1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Definition of Location Filter Format . . . . . . . . . . . . . 3		3. Definition of Location Filter Format . . . . . . . . . . . . . 3
	3.1 Horizontal and Vertical Movement . . . . . . . . . . . . . 4		3.1. Horizontal and Vertical Movement . . . . . . . . . . . . . 4
	3.2 Changes in value . . . . . . . . . . . . . . . . . . . . . 5		3.2. Changes in value . . . . . . . . . . . . . . . . . . . . . 5
	3.3 Containment Within a Region . . . . . . . . . . . . . . . 6		3.3. Containment Within a Region . . . . . . . . . . . . . . . 6
	3.4 XML Schema for filter format . . . . . . . . . . . . . . . 9		3.4. XML Schema for filter format . . . . . . . . . . . . . . . 9
	4. Containment schema . . . . . . . . . . . . . . . . . . . . . . 10		4. Containment schema . . . . . . . . . . . . . . . . . . . . . . 10
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 12		5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
	6.1 MIME Registration for		6.1. MIME Registration for
	application/location-delta-filter+xml . . . . . . . . . . 13		application/location-delta-filter+xml . . . . . . . . . . 13
	6.2 URN Sub-Namespace Registration for		6.2. URN Sub-Namespace Registration for
	urn:ietf:params:xml:ns:location-filter . . . . . . . . . . 13		urn:ietf:params:xml:ns:location-filter . . . . . . . . . . 13
	6.3 Schema Registration For location-filter . . . . . . . . . 14		6.3. Schema Registration For location-filter . . . . . . . . . 14
	6.4 URN Sub-Namespace Registration for		6.4. URN Sub-Namespace Registration for
	urn:ietf:params:xml:ns:pidf:geopriv10:containment . . . . 14		urn:ietf:params:xml:ns:pidf:geopriv10:containment . . . . 14
	6.5 Schema Registration For containment . . . . . . . . . . . 15		6.5. Schema Registration For containment . . . . . . . . . . . 15
	7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15		7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15		8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
	8.1 Normative References . . . . . . . . . . . . . . . . . . . 15		8.1. Normative References . . . . . . . . . . . . . . . . . . . 15
	8.2 Informational References . . . . . . . . . . . . . . . . . 16		8.2. Informational References . . . . . . . . . . . . . . . . . 16
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . 16		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16
	Intellectual Property and Copyright Statements . . . . . . . . 17		Intellectual Property and Copyright Statements . . . . . . . . . . 17
	1. Conventions		1. Conventions
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC-2119 [2].		document are to be interpreted as described in RFC-2119 [2].
	2. Overview		2. Overview
	Conveying static location in PIDF-LO [1] bodies is straightforward.		Conveying static location in PIDF-LO [1] bodies is straightforward.
	However the difficult part about asynchronous notification of		However the difficult part about asynchronous notification of
	location information is that many forms of location are measured as a		location information is that many forms of location are measured as a
	continuous gradient. Unlike notifications using discreet quantities,		continuous gradient. Unlike notifications using discreet quantities,
	it is difficult to know when a change in location is large enough to		it is difficult to know when a change in location is large enough to
	warrant a notification. Moreover, different applications require a		warrant a notification. Moreover, different applications require a
	skipping to change at page 3, line 47 ¶		skipping to change at page 3, line 47 ¶
	and accuracy, without having to poll or flood the network with		and accuracy, without having to poll or flood the network with
	notifications which are not important to the application.		notifications which are not important to the application.
	Notifications should only happen when the notification would be		Notifications should only happen when the notification would be
	considered an Interesting Event to the subscriber. This section of		considered an Interesting Event to the subscriber. This section of
	this document defines an XML filter format to describe interesting		this document defines an XML filter format to describe interesting
	conditions or events. The terminal elements in this format are		conditions or events. The terminal elements in this format are
	defined in terms of existing Geographic Markup Language (GML) [9]		defined in terms of existing Geographic Markup Language (GML) [9]
	data types.		data types.
	This document also defines a MIME type for this location filter		This document also defines a MIME type for this location filter
	format: application/location-delta-filter+xml.		format: application/location-delta-filter+xml.
	This document defines the following as an initial list of Interesting		This document defines the following as an initial list of Interesting
	Events:		Events:
	1. the resource moves more than a specific distance horizontally or		1. the resource moves more than a specific distance horizontally or
	vertically since the last notification		vertically since the last notification
	2. the resource exceeds a specific speed		2. the resource exceeds a specific speed
	3. the resource enters or exits one or more GML objects (for		3. the resource enters or exits one or more GML objects (for
	example, a set of 2-dimensional or 3-dimensional regions)		example, a set of 2-dimensional or 3-dimensional regions)
	included or referenced in the filter.		included or referenced in the filter.
	skipping to change at page 4, line 28 ¶		skipping to change at page 4, line 28 ¶
	This URN is:		This URN is:
	urn:ietf:params:xml:ns:location-filter		urn:ietf:params:xml:ns:location-filter
	The filter format starts with a top-level XML element called		The filter format starts with a top-level XML element called
	"<location-filter>", which contains one or more filter events. The		"<location-filter>", which contains one or more filter events. The
	semantics of multiple elements inside a location-filter is a logical		semantics of multiple elements inside a location-filter is a logical
	OR. In other words, if any of the individual filter events occurs,		OR. In other words, if any of the individual filter events occurs,
	the event satisfies the location-filter and triggers a notification.		the event satisfies the location-filter and triggers a notification.
	3.1 Horizontal and Vertical Movement		3.1. Horizontal and Vertical Movement
	The movedHoriz and movedVert filter events each indicate a minimum		The movedHoriz and movedVert filter events each indicate a minimum
	horizontal motion or vertical distance (respectively) that the		horizontal motion or vertical distance (respectively) that the
	resource must have moved from the location of the resource when the		resource must have moved from the location of the resource when the
	last notification was sent in order to trigger this event. The		last notification was sent in order to trigger this event. The
	distance is measured absolutely from the point of last notification		distance is measured absolutely from the point of last notification
	rather than in terms of cumulative motion (For example, someone		rather than in terms of cumulative motion (For example, someone
	pacing inside a room will not trigger an event if the trigger		pacing inside a room will not trigger an event if the trigger
	threshold is slightly larger than the room.) Each of these events		threshold is slightly larger than the room.) Each of these events
	can only appear once in a location-filter. These events have an		can only appear once in a location-filter. These events have an
	skipping to change at page 5, line 19 ¶		skipping to change at page 5, line 19 ¶
	<movedVert uom="urn:ogc:def:uom:EPSG::9001">3</movedVert>		<movedVert uom="urn:ogc:def:uom:EPSG::9001">3</movedVert>
	</location-filter>		</location-filter>
	If the resource exceeds 3 meters per second (10.8 km/h), send a		If the resource exceeds 3 meters per second (10.8 km/h), send a
	notification:		notification:
	<location-filter>		<location-filter>
	<speedExceeds uom="#mps">3</speedExceeds>		<speedExceeds uom="#mps">3</speedExceeds>
	</location-filter>		</location-filter>
	3.2 Changes in value		3.2. Changes in value
	The valueChanges filter event contains a string which is interpreted		The valueChanges filter event contains a string which is interpreted
	as an XPath [6] expression evaluated within the context of the		as an XPath [6] expression evaluated within the context of the
	location-info element of the PIDF-LO document which would be		location-info element of the PIDF-LO document which would be
	generated by the notification. The XPath expression MUST evaluate to		generated by the notification. The XPath expression MUST evaluate to
	only a single Xpath node. If the value of any of the elements in the		only a single Xpath node. If the value of any of the elements in the
	resulting node changes, then the filter event is triggered. Note		resulting node changes, then the filter event is triggered. Note
	that the value of the resulting node changes if any of those nodes or		that the value of the resulting node changes if any of those nodes or
	subnodes transitions from having a value to having no value or vice		subnodes transitions from having a value to having no value or vice
	versa. A location-filter may contain multiple valueChanges filters.		versa. A location-filter may contain multiple valueChanges filters.
	skipping to change at page 6, line 46 ¶		skipping to change at page 6, line 46 ¶
	Filter Document:		Filter Document:
	<location-filter		<location-filter
	xmlns="urn:ietf:params:xml:ns:location-filter"		xmlns="urn:ietf:params:xml:ns:location-filter"
	xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civilLoc">		xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civilLoc">
	<valueChanges>cl:civilAddress/cl:A1</valueChanges>		<valueChanges>cl:civilAddress/cl:A1</valueChanges>
	<valueChanges>cl:civilAddress/cl:A2</valueChanges>		<valueChanges>cl:civilAddress/cl:A2</valueChanges>
	<valueChanges>cl:civilAddress/cl:A3</valueChanges>		<valueChanges>cl:civilAddress/cl:A3</valueChanges>
	<valueChanges>cl:civilAddress/cl:PC</valueChanges>		<valueChanges>cl:civilAddress/cl:PC</valueChanges>
	</location-filter>		</location-filter>
	3.3 Containment Within a Region		3.3. Containment Within a Region
	Finally, the "enterOrExit" filter event is satisfied when the		Finally, the "enterOrExit" filter event is satisfied when the
	resource enters or exits a named 2-dimensional or 3-dimensional		resource enters or exits a named 2-dimensional or 3-dimensional
	region described by one of the shapes defined in [8]. These regions		region described by one of the shapes defined in [8]. These regions
	can be defined using inline snippets of GML, or externally referenced		can be defined using inline snippets of GML, or externally referenced
	using a URI (Uniform Resource Identifier).		using a URI (Uniform Resource Identifier).
	These regions need a unique name or identifier so location with		These regions need a unique name or identifier so location with
	respect to these regions can be described later (for example in a		respect to these regions can be described later (for example in a
	notification). These regions are currently described as GML		notification). These regions are currently described as GML
	Features so they can be named with a GML Name. Ideally each		Features so they can be named with a GML Name. Ideally each
	region could be described instead as a GML geometry with some		region could be described instead as a GML geometry with some
	associated name or identifier.		associated name or identifier.
	Any 2-dimensional region MUST be defined using the EPSG 4326		Any 2-dimensional region MUST be defined using the EPSG 4326
	coordinate reference system. Any 3-dimensional region MUST be		coordinate reference system. Any 3-dimensional region MUST be
	defined using the EPSG 4979 coordinate reference system. A location-		defined using the EPSG 4979 coordinate reference system. A location-
	skipping to change at page 9, line 16 ¶		skipping to change at page 9, line 16 ¶
	<enterOrExit>		<enterOrExit>
	<my:ParkingGarage		<my:ParkingGarage
	xlink:href="http://server.example.com/loc-defs/bldg-mgr/parking"/>		xlink:href="http://server.example.com/loc-defs/bldg-mgr/parking"/>
	</enterOrExit>		</enterOrExit>
	<enterOrExit>		<enterOrExit>
	<my:ConferenceRooms		<my:ConferenceRooms
	xlink:href="http://server.example.com/loc-defs/userdef/confrooms"/>		xlink:href="http://server.example.com/loc-defs/userdef/confrooms"/>
	</enterOrExit>		</enterOrExit>
	</location-filter>		</location-filter>
	3.4 XML Schema for filter format		3.4. XML Schema for filter format
	The XML Schema for this format is defined below.		The XML Schema for this format is defined below.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:location-filter"		targetNamespace="urn:ietf:params:xml:ns:location-filter"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:gml="http://www.opengis.net/gml">		xmlns:gml="http://www.opengis.net/gml">
	<xs:element name="location-filter">		<xs:element name="location-filter">
	skipping to change at page 10, line 4 ¶		skipping to change at page 10, line 4 ¶
	<xs:element name="enterOrExit" type="gml:FeaturePropertyType"		<xs:element name="enterOrExit" type="gml:FeaturePropertyType"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	<!-- Do we want to include this to allow new filters? -->		<!-- Do we want to include this to allow new filters? -->
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:element>		</xs:element>
	</xs:schema>		</xs:schema>
			<?xml version="1.0" encoding="UTF-8"?>
			<xs:schema
			targetNamespace="urn:ietf:params:xml:ns:location-filter"
			xmlns:xs="http://www.w3.org/2001/XMLSchema"
			xmlns:gml="http://www.opengis.net/gml">
			<xs:element name="location-filter">
			<xs:complexType>
			<xs:sequence>
			<xs:element name="movedHoriz" type="gml:MeasureType"
			minOccurs="0" maxOccurs="1"/>
			<xs:element name="movedVert" type="gml:MeasureType"
			minOccurs="0" maxOccurs="1"/>
			<xs:element name="speedExceeds" type="gml:MeasureType"
			minOccurs="0" maxOccurs="1"/>
			<!-- this type needs to hold an XPath statement -->
			<xs:element name="valueChanges" type="xs:string"
			minOccurs="0" maxOccurs="unbounded"/>
			<xs:element name="enterOrExit" type="gml:FeaturePropertyType"
			minOccurs="0" maxOccurs="unbounded"/>
			<!-- Do we want to include this to allow new filters? -->
			<xs:any namespace="##other" processContents="lax"
			minOccurs="0" maxOccurs="unbounded"/>
			</xs:sequence>
			</xs:complexType>
			</xs:element>
			</xs:schema>
	4. Containment schema		4. Containment schema
	This section describes a schema for describing the resource's		This section describes a schema for describing the resource's
	location relative to a region or list of regions which might contain		location relative to a region or list of regions which might contain
	the resource. (These regions can be defined dynamically in an		the resource. (These regions can be defined dynamically in an
	"enterOrExit" element in a subscription filter, or defined on the		"enterOrExit" element in a subscription filter, or defined on the
	notifier using some out-of-band mechanism.) The "pidfResource"		notifier using some out-of-band mechanism.) The "pidfResource"
	element is placed inside the location-info element in a PIDF-LO		element is placed inside the location-info element in a PIDF-LO
	document. The pidfResource element can contain zero or more		document. The pidfResource element can contain zero or more
	skipping to change at page 13, line 7 ¶		skipping to change at page 13, line 10 ¶
	Location information is typically very privacy sensitive. As such,		Location information is typically very privacy sensitive. As such,
	GEOPRIV requires that notifications MUST be encrypted and integrity		GEOPRIV requires that notifications MUST be encrypted and integrity
	protected.		protected.
	Additional privacy and security considerations are discussed in		Additional privacy and security considerations are discussed in
	detail in [7].		detail in [7].
	6. IANA Considerations		6. IANA Considerations
	6.1 MIME Registration for application/location-delta-filter+xml		6.1. MIME Registration for application/location-delta-filter+xml
	MIME media type name: application		MIME media type name: application
	MIME subtype name: application/location-delta-filter+xml		MIME subtype name: application/location-delta-filter+xml
	Required parameters: none.		Required parameters: none.
	Optional parameters: none.		Optional parameters: none.
	Encoding considerations: Same as for XML.		Encoding considerations: Same as for XML.
	skipping to change at page 13, line 39 ¶		skipping to change at page 13, line 42 ¶
	information.		information.
	Additional information:		Additional information:
	1. Magic number(s): N/A		1. Magic number(s): N/A
	2. File extension(s): N/A		2. File extension(s): N/A
	3. Macintosh file type code: N/A		3. Macintosh file type code: N/A
	6.2 URN Sub-Namespace Registration for		6.2. URN Sub-Namespace Registration for
	urn:ietf:params:xml:ns:location-filter		urn:ietf:params:xml:ns:location-filter
	This section registers a new XML namespace, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
	[12].		[12].
	URI: The URI for this namespace is		URI: The URI for this namespace is
	urn:ietf:params:xml:ns:location-filter.		urn:ietf:params:xml:ns:location-filter.
	Registrant Contact: IETF, GEOPRIV working group, <geopriv@ietf.org>,
	as delegated by the IESG <iesg@ietf.org>.
			Registrant Contact: IETF, GEOPRIV working group, <geopriv@ietf.org>,
			as delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	BEGIN		BEGIN
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"		<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
	"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">		"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml">		<html xmlns="http://www.w3.org/1999/xhtml">
	<head>		<head>
	<meta http-equiv="content-type"		<meta http-equiv="content-type"
	content="text/html;charset=iso-8859-1"/>		content="text/html;charset=iso-8859-1"/>
	<title>Location Filter Namespace</title>		<title>Location Filter Namespace</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for PIDF-LO Location Filters</h1>		<h1>Namespace for PIDF-LO Location Filters</h1>
	<h2>urn:ietf:params:xml:ns:location-filter</h2>		<h2>urn:ietf:params:xml:ns:location-filter</h2>
	<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>		<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
	</body>		</body>
	</html>		</html>
	END		END
	6.3 Schema Registration For location-filter		6.3. Schema Registration For location-filter
	This specification registers a schema, as per the guidelines in [12].		This specification registers a schema, as per the guidelines in [12].
	URI: please assign.		URI: please assign.
	Registrant Contact: IETF, GEOPRIV Working Group		Registrant Contact: IETF, GEOPRIV Working Group
	(geopriv@ietf.org), as delegated by the IESG (iesg@ietf.org).		(geopriv@ietf.org), as delegated by the IESG (iesg@ietf.org).
	XML: The XML can be found as the sole content of Section 3.4.		XML: The XML can be found as the sole content of Section 3.4.
	6.4 URN Sub-Namespace Registration for		6.4. URN Sub-Namespace Registration for
	urn:ietf:params:xml:ns:pidf:geopriv10:containment		urn:ietf:params:xml:ns:pidf:geopriv10:containment
	This section registers a new XML namespace, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
	[12].		[12].
	URI: The URI for this namespace is		URI: The URI for this namespace is
	urn:ietf:params:xml:ns:pidf:geopriv10:containment.		urn:ietf:params:xml:ns:pidf:geopriv10:containment.
	Registrant Contact: IETF, GEOPRIV working group, <geopriv@ietf.org>,		Registrant Contact: IETF, GEOPRIV working group, <geopriv@ietf.org>,
	as delegated by the IESG <iesg@ietf.org>.		as delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	BEGIN		BEGIN
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"		<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
	"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">		"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml">		<html xmlns="http://www.w3.org/1999/xhtml">
	<head>		<head>
	<meta http-equiv="content-type"		<meta http-equiv="content-type"
	skipping to change at page 15, line 23 ¶		skipping to change at page 15, line 23 ¶
	<title>PIDF-LO Location Containment Namespace</title>		<title>PIDF-LO Location Containment Namespace</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for PIDF-LO location containment elements</h1>		<h1>Namespace for PIDF-LO location containment elements</h1>
	<h2>urn:ietf:params:xml:ns:pidf:geopriv10:containment</h2>		<h2>urn:ietf:params:xml:ns:pidf:geopriv10:containment</h2>
	<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>		<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
	</body>		</body>
	</html>		</html>
	END		END
	6.5 Schema Registration For containment		6.5. Schema Registration For containment
	This specification registers a schema, as per the guidelines in [12].		This specification registers a schema, as per the guidelines in [12].
	URI: please assign.		URI: please assign.
	Registrant Contact: IETF, GEOPRIV Working Group		Registrant Contact: IETF, GEOPRIV Working Group
	(geopriv@ietf.org), as delegated by the IESG (iesg@ietf.org).		(geopriv@ietf.org), as delegated by the IESG (iesg@ietf.org).
	XML: The XML can be found as the sole content of Section 4.		XML: The XML can be found as the sole content of Section 4.
	7. Acknowledgments		7. Acknowledgments
	Thanks to Allan Thompson, James Winterbottom, and Martin Thomson for		Thanks to Allan Thompson, James Winterbottom, and Martin Thomson for
	their comments.		their comments.
	8. References		8. References
	8.1 Normative References		8.1. Normative References
	[1] Peterson, J., "A Presence-based GEOPRIV Location Object Format",		[1] Peterson, J., "A Presence-based GEOPRIV Location Object
	RFC 4119, December 2005.		Format", RFC 4119, December 2005.
	[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
	Levels", BCP 14, RFC 2119, March 1997.		Levels", BCP 14, RFC 2119, March 1997.
	[3] Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler,		[3] Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler,
	"Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml,		"Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml,
	October 2000, <http://www.w3.org/TR/REC-xml>.		October 2000, <http://www.w3.org/TR/REC-xml>.
	[4] Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, "XML		[4] Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, "XML
	Schema Part 1: Structures", W3C REC-xmlschema-1, May 2001,		Schema Part 1: Structures", W3C REC-xmlschema-1, May 2001,
	<http://www.w3.org/TR/xmlschema-1/>.		<http://www.w3.org/TR/xmlschema-1/>.
	[5] Bray, T., Hollander, D., and A. Layman, "Namespaces in XML",		[5] Bray, T., Hollander, D., and A. Layman, "Namespaces in XML",
	W3C REC-xml-names, January 1999,		W3C REC-xml-names, January 1999,
	<http://www.w3.org/TR/REC-xml-names>.		<http://www.w3.org/TR/REC-xml-names>.
	[6] Clark, J. and S. DeRose, "XML Path Language (XPath) Version		[6] Clark, J. and S. DeRose, "XML Path Language (XPath) Version
	1.0", W3C Recommendation xpath, November 1999,		1.0", W3C Recommendation xpath, November 1999,
	<http://www.w3.org/TR/xpath>.		<http://www.w3.org/TR/xpath>.
	[7] Tschofenig, H., "GEOPRIV PIDF-LO Usage Clarification,		[7] Tschofenig, H., "GEOPRIV PIDF-LO Usage Clarification,
	Considerations and Recommendations",		Considerations and Recommendations",
	draft-ietf-geopriv-pdif-lo-profile-03 (work in progress),		draft-ietf-geopriv-pdif-lo-profile-05 (work in progress),
	March 2006.		October 2006.
	[8] Thomson, M., "Geodetic Shapes for the Representation of		[8] Thomson, M., "Geodetic Shapes for the Representation of
	Uncertainty in PIDF-LO", draft-thomson-geopriv-geo-shape-00		Uncertainty in PIDF-LO", draft-thomson-geopriv-geo-shape-03
	(work in progress), February 2006.		(work in progress), December 2006.
	[9] OpenGIS, "Open Geography Markup Language (GML) Implementation		[9] OpenGIS, "Open Geography Markup Language (GML) Implementation
	Specification", OpenGIS OGC 02-023r4, January 2003,		Specification", OpenGIS OGC 02-023r4, January 2003,
	<http://www.opengis.org/techno/implementation.htm>.		<http://www.opengis.org/techno/implementation.htm>.
	8.2 Informational References		8.2. Informational References
	[10] Moats, R., "URN Syntax", RFC 2141, May 1997.		[10] Moats, R., "URN Syntax", RFC 2141, May 1997.
	[11] Moats, R., "A URN Namespace for IETF Documents", RFC 2648,		[11] Moats, R., "A URN Namespace for IETF Documents", RFC 2648,
	August 1999.		August 1999.
	[12] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,		[12] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	January 2004.		January 2004.
	Author's Address		Author's Address
	Rohan Mahy		Rohan Mahy
	Plantronics		Plantronics
	345 Encincal Street		345 Encincal Street
	Santa Cruz, CA		Santa Cruz, CA
	USA		USA
	Email: rohan@ekabal.com		Email: rohan@ekabal.com
	Intellectual Property Statement		Full Copyright Statement
			Copyright (C) The IETF Trust (2007).
			This document is subject to the rights, licenses and restrictions
			contained in BCP 78, and except as set forth therein, the authors
			retain all their rights.
			This document and the information contained herein are provided on an
			"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
			OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
			THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
			OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
			THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
			WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
			Intellectual Property
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to		Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be		on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.		found in BCP 78 and BCP 79.
	skipping to change at page 17, line 29 ¶		skipping to change at page 17, line 45 ¶
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any		The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary		copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at		this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.		ietf-ipr@ietf.org.
	Disclaimer of Validity
	This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Copyright Statement
	Copyright (C) The Internet Society (2006). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.
	Acknowledgment		Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is provided by the IETF
	Internet Society.		Administrative Support Activity (IASA).
End of changes. 42 change blocks.
	80 lines changed or deleted		112 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/