- From: Henning Schulzrinne <hgs@cs.columbia.edu>
- Date: Wed, 18 Aug 2010 09:45:30 -0400
- To: 전종홍 <hollobit@etri.re.kr>
- Cc: "Matt Womer" <mdw@w3.org>, <public-poiwg@w3.org>
> - Physical Object Identifier : (maybe Recommendations)
> : it's a URI scheme. and it's a unified identifier (and markup) for any physical object in augmented environment(product, person, location ...)
> Poi:UPC.<upcnumber>
> Poi:Geo.<lat>,<lon>[,<alt>][;u=<uncertainty>]
> Poi:tel.<phonenumber>
> Poi:doi.<publishernumber>/<suffix>
> Poi:ufid.<ufid number>
> Poi:epc.<epc code>
> Poi:ean.<ean code>
> Poi:isbn.<isbn number>
> ...
We already have geo URI (see RFC 5870) and tel URIs (RFC 3996), so it seems unwise to duplicate them.
I admit that I'm having a hard time wrapping my head around the POI description idea. In its most general form, this could include a complete map of the US, with all mark-up, duplicating a full GIS system (see OpenGIS). I suspect we don't want to go there. To have a chance to succeed, a much more narrow first version seems more likely to actually see implementation. There has been significant work in the IETF GEOPRIV WG on describing 2d/3d polygons, among other simple shapes (arc band, circle, ....), as a subset of the OpenGIS effort, which might well hit the 90%-of-likely-usecases mark. Similarly, we don't want to re-invent vCal for a full calendaring description ("A concert occurs here every Tuesday, except on the 5th Tuesday of the month and during the month of July").
To see if we're on the roughly same page, here's a mockup of something I see as plausible (without worrying about precise date formats and the like):
<expires>May 17, 2011</expires>
<when>vCal string [not applicable for the park example]</when>
<where>a 2D polygon</where>
<what>urn:poi:park</what>
<details>Central Park, Manhattan</details>
Henning
Received on Wednesday, 18 August 2010 13:46:04 UTC