"I see a POI as a useful tool for linking or binding "things" to "locations"."
Indeed. I see that as its primary goal really - once again I like the
term physical hyperlinks (or plinks!).
I picture it basically as;
Real Life <POI> Data
The POI containing the information to locate something in the real
world and (optionally) a link to a bit of data to place there..
At least when it comes to AR this is the main use of POIs.
But does not this linking require a data element ? or at least, some
way to link to the (remore source) data being positioned?
Not sure if data element is the best name for it though.
As you say it opens a lot of other things to be added based on that,
but at its simplist its just url to...something else...no ?
On 3 May 2011 07:56, Rob Manson <roBman@mob-labs.com> wrote:
> I think this is a good point Thomas...and kind of the opposite of the
> recent discussion about "should a POI require a Location?".
>
> It's really a question about "should a POI allow MORE than a Location?"
>
> Again I would think the the Point in POI suggest no. Â I see a POI as a
> useful tool for linking or binding "things" to "locations". Â Making
> these other geometries as well as other media just "things" that are
> "related" to the POI makes it much more flexible and open ended.
>
> Otherwise are we really just re-inventing or revisiting the type of work
> started in geojson[1], etc?
>
> If yes, then there's a bunch of other things that could be added in
> based on that.
>
>
> roBman
>
> [1] http://wiki.geojson.org/GeoJSON_draft_version_6#Specification
>
>
> On Mon, 2011-05-02 at 21:38 +0200, Thomas Wrobel wrote:
>> Excellent work, that should help get the ball rolling on getting this
>> information pinned down.
>>
>> I'd have to go down the thing element by element, but I see a few
>> things that I would change.
>>
>> * If you use an object to define a georeferance , for example, you'd
>> still need the centre point defined in some other way as well....an
>> object could be used to represent a relative volume, but it doesn't
>> specify a location by itself. So I think that should be mentioned.
>> Also, it should be clear that the definition of an area by object is
>> quite different to specifying a 3d object to place at a POI (which is
>> of course the typical AR use-case).
>> Essentially I think its easy at the moment to get location information
>> and the data which it places mixed up. Â Geo-reference should be "where
>> you put something" but what you put there should be specified
>> elsewhere in the POI.
>>
>> * Unless I'm missing something, I think the document also needs a
>> element for this data to be positioned...I'd vote for simple a "data"
>> element that takes a URL and a MIME type - letting people position any
>> arbitrary data or document with the POI. For AR use this would be the
>> link to the 3D model, but it would also make it easy to link a
>> location to a webpage, or even a sound file. (making audio tours very
>> easy to make).
>> significant/worthy to be discussed?
>> Either way, great start to work from.
>>
>>
>> -Thomas Wrobel
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> I had a (very rough) Time element worked out
>> On 2 May 2011 19:59, Matt Womer <mdw@w3.org> wrote:
>> > Hi all,
>> >
>> > In the interest of getting us closer to publishing a First Public Working Draft, I've created a skeleton editor's draft that is based on materials in the wiki [1], the mailing list, the discussions we have had during calls and face-to-face meetings, and some stuff (the XML syntax in particular) that I just made up as I went along. Â There are lots of parts that are incomplete, insufficient, and probably extremely dangerous, but I think it should provide us a good framework for discussions going forward.
>> >
>> > Here it is, enjoy:
>> > Â Â Â Â http://www.w3.org/2010/POI/documents/Core/POI%20Core%20Draft.html
>> >
>> > I would ask that as we discuss this, please create new email threads for significant issues rather than just responding to this message. Â In the interest of not needlessly spamming the list, please send typos, editorial nits, etc to me directly. Â Please also cite the date on the top of the document as well.
>> >
>> > Thanks,
>> >
>> > -Matt Womer
>> > Editor pro tempore
>> >
>> > [1] In particular: http://www.w3.org/2010/POI/wiki/Core/Drafthttp://www.w3.org/2010/POI/wiki/Data_Model and http://www.w3.org/2010/POI/wiki/
>> >
>> >
>> >
>>
>>
>
>
>