DanC_MSP: AOB... geopriv and radius..
DanC_MSP: hmmm... another IANA registry..
DanC_MSP: geopriv charter
DanC_MSP: wow... milestones in this year! (though still in the past, Feb 05)
DanC_MSP: discussion o e) draft-thomson-domain-auth ...
DanC_MSP: in the 62nd IETF
DanC_MSP: "new Domain Auth elt , peer with PIDF status element". "signatures are RFC3275." "XML transform..."
DanC_MSP: Jon Peterson at the mic...
DanC_MSP: geopriv@ietf.xmpp.org logs
DanC_MSP: James Winterbottom is a name on the slides
DanC_MSP: commentor at the mic says "I wrote an ID on doing this with SIP". SIP seems to be doing everything
DanC_MSP: discussing draft-thomson-domain-auth
DanC_MSP: hm... 7.1 URN Sub-Namespace Registration for urn:ietf:params:xml:ns:pidf:geopriv10:domain-auth
DanC_MSP: moving on to c) draft-winterbottom-http-location-delivery
DanC_MSP: "HTTP Enabled Location Delivery (HELD)" James Winterbottom
DanC_MSP: HTTP Enabled Location Delivery (HELD)
DanC_MSP: chair says some folks did something related but different earlier, went away, and have come back... "we have to decide what to do about HTTP"
DanC_MSP: IANA considerations (section 7): "A new DNS services (SVR) field type of LOCSERV+HTTP with a protocol type of TCP is required in order for a client-device to discover the Location Server in the access network."
DanC_MSP: JamesW said "I thought about doing this in SIP" earlier. SIP and HTTP are almost the same but different. hmm.
DanC_MSP: lots of reference to PIDF-LO... gotta figure out what that is...
DanC_MSP: Q: how can you prevent me from pretending to be you and getting your location? A: good point.
DanC_MSP: PIDF-LO references seem to be grounded in A Presence-based GEOPRIV Location Object Format
DanC_MSP: sigh... targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10
DanC_MSP: PIDF-LO is an XML syntax, specified using XML Schema
DanC_MSP: eek! "Basic Location Request... made using HTTP post"
DanC_MSP: aha! slides on the web (in ppt, zipped) via a geopriv site linked from the WG charter
DanC_MSP: ah... Jonathan Rosenberg is the guy making lots of good "keep it simple" and such comments.
DanC_MSP: jr points out this is hard because it crosses layers. (problem seems to regard emergency calls, ala 911, and the problems arising from geographic location independence of voip)
DanC_MSP: chair asks speaker to repeat... speaker replies, in jest, "they're recording this in mp3; just hit playback". I think the discussion is being recorded, but I can't quite tell
DanC_MSP: lots of discussion of the scope of the WG
DanC_MSP: e.g. the emergency calling problem... trade-offs between solving exactly that problem and wider geopriv problems
DanC_MSP: hmmm... another IANA registry..
DanC_MSP: geopriv charter
DanC_MSP: wow... milestones in this year! (though still in the past, Feb 05)
DanC_MSP: discussion o e) draft-thomson-domain-auth ...
DanC_MSP: in the 62nd IETF
DanC_MSP: "new Domain Auth elt , peer with PIDF status element". "signatures are RFC3275." "XML transform..."
DanC_MSP: Jon Peterson at the mic...
DanC_MSP: geopriv@ietf.xmpp.org logs
DanC_MSP: James Winterbottom is a name on the slides
DanC_MSP: commentor at the mic says "I wrote an ID on doing this with SIP". SIP seems to be doing everything
DanC_MSP: discussing draft-thomson-domain-auth
DanC_MSP: hm... 7.1 URN Sub-Namespace Registration for urn:ietf:params:xml:ns:pidf:geopriv10:domain-auth
DanC_MSP: moving on to c) draft-winterbottom-http-location-delivery
DanC_MSP: "HTTP Enabled Location Delivery (HELD)" James Winterbottom
DanC_MSP: HTTP Enabled Location Delivery (HELD)
DanC_MSP: chair says some folks did something related but different earlier, went away, and have come back... "we have to decide what to do about HTTP"
DanC_MSP: IANA considerations (section 7): "A new DNS services (SVR) field type of LOCSERV+HTTP with a protocol type of TCP is required in order for a client-device to discover the Location Server in the access network."
DanC_MSP: JamesW said "I thought about doing this in SIP" earlier. SIP and HTTP are almost the same but different. hmm.
DanC_MSP: lots of reference to PIDF-LO... gotta figure out what that is...
DanC_MSP: Q: how can you prevent me from pretending to be you and getting your location? A: good point.
DanC_MSP: PIDF-LO references seem to be grounded in A Presence-based GEOPRIV Location Object Format
DanC_MSP: sigh... targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10
DanC_MSP: PIDF-LO is an XML syntax, specified using XML Schema
DanC_MSP: eek! "Basic Location Request... made using HTTP post"
DanC_MSP: aha! slides on the web (in ppt, zipped) via a geopriv site linked from the WG charter
DanC_MSP: ah... Jonathan Rosenberg is the guy making lots of good "keep it simple" and such comments.
DanC_MSP: jr points out this is hard because it crosses layers. (problem seems to regard emergency calls, ala 911, and the problems arising from geographic location independence of voip)
DanC_MSP: chair asks speaker to repeat... speaker replies, in jest, "they're recording this in mp3; just hit playback". I think the discussion is being recorded, but I can't quite tell
DanC_MSP: lots of discussion of the scope of the WG
DanC_MSP: e.g. the emergency calling problem... trade-offs between solving exactly that problem and wider geopriv problems
danbri: "Professor Shadbolt will demonstrate how the developing Semantic Web could provide web services for the military which might change how it operates."
danbri: I wonder if any slides are going to go online. Sounds interesting...
danbri: "For example, through developing information sets about locations, military units could access instant information about the geology, geography, customs and cultural and religious structures of a location before entering."
timbl: See also for example Semantic Web for the Military User May 2003
danbri: I wonder if any slides are going to go online. Sounds interesting...
danbri: "For example, through developing information sets about locations, military units could access instant information about the geology, geography, customs and cultural and religious structures of a location before entering."
timbl: See also for example Semantic Web for the Military User May 2003
kasei: I've just added new answers and thinking-aloud questions to the FAQs
kasei: feedback wanted
kasei: feedback wanted
dajobe: Enterprise Information Integrator (EII) 2.1 includes enhancements such as support for W3C Semantic Web standards, including OWL (Web Ontology Language) and RDF (Resource Description Framework)...