default search action
James Winterbottom
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
Journal Articles
- 2019
- [j2]Urban Sedlar, James Winterbottom, Bostjan Tavcar, Janez Sterle, Jaka Cijan, Mojca Volk:
Next Generation Emergency Services Based on the Pan-European Mobile Emergency Application (PEMEA) Protocol: Leveraging Mobile Positioning and Context Information. Wirel. Commun. Mob. Comput. 2019: 1408784:1-1408784:10 (2019) - 2011
- [j1]Richard L. Barnes, James Winterbottom, Martin Dawson:
Internet geolocation and location-based services. IEEE Commun. Mag. 49(4): 102-108 (2011)
Conference and Workshop Papers
- 2023
- [c2]Evangelos K. Markakis, Anton Donner, Jumoke Olumide, James Winterbottom, Michelle Wetterwald:
An early View on the work of STF 623 in the Emergency Communications Network Resilience and Preparedness. CPS-IoT Week Workshops 2023: 300-301 - 2017
- [c1]Marco Manso, Barbara Guerra, Bertrand Casse, James Winterbottom, Mihai Buf, Cristian Patachia, Vlad Sorici:
Next Generation Emergency Services - The Transformation Launched by the NEXES Action. EPS 2017
Informal and Other Publications
- 2020
- [i13]James Winterbottom, Roland Jesske, Bruno Chatras, Andrew Hutton:
Location Source Parameter for the SIP Geolocation Header Field. RFC 8787: 1-8 (2020) - 2016
- [i12]James Winterbottom, Hannes Tschofenig, Laura Liess:
A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) Protocol. RFC 7840: 1-16 (2016) - [i11]Randall Gellens, Brian Rosen, Hannes Tschofenig, Roger Marshall, James Winterbottom:
Additional Data Related to an Emergency Call. RFC 7852: 1-113 (2016) - 2015
- [i10]Martin Thomson, James Winterbottom:
Representation of Uncertainty and Confidence in the Presence Information Data Format Location Object (PIDF-LO). RFC 7459: 1-39 (2015) - 2014
- [i9]Martin Thomson, James Winterbottom:
Using Device-Provided Location-Related Measurements in Location Configuration Protocols. RFC 7105: 1-74 (2014) - [i8]Richard L. Barnes, Martin Thomson, James Winterbottom, Hannes Tschofenig:
Location Configuration Extensions for Policy Management. RFC 7199: 1-20 (2014) - 2013
- [i7]James Winterbottom, Martin Thomson, Richard L. Barnes, Brian Rosen, Robins George:
Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO). RFC 6848: 1-21 (2013) - 2012
- [i6]James Winterbottom, Hannes Tschofenig, Henning Schulzrinne, Martin Thomson:
A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD). RFC 6753: 1-25 (2012) - 2011
- [i5]James Winterbottom, Martin Thomson, Hannes Tschofenig, Richard L. Barnes:
Use of Device Identity in HTTP-Enabled Location Delivery (HELD). RFC 6155: 1-27 (2011) - 2010
- [i4]James Winterbottom, Martin Thomson:
Specifying Holes in Location-to-Service Translation (LoST) Service Boundaries. RFC 5964: 1-11 (2010) - [i3]Martin Thomson, James Winterbottom:
Discovering the Local Location Information Server (LIS). RFC 5986: 1-16 (2010) - 2009
- [i2]James Winterbottom, Martin Thomson, Hannes Tschofenig:
GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations. RFC 5491: 1-28 (2009) - 2008
- [i1]Martin Thomson, James Winterbottom:
Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO). RFC 5139: 1-14 (2008)
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from , , and to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-04-24 23:12 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint