W3C home > Mailing lists > Public > public-egov-ig@w3.org > August 2012

Re: University of Oxford/ usecase

From: Paola Di Maio <paola.dimaio@gmail.com>
Date: Fri, 24 Aug 2012 11:52:07 +0100
Message-ID: <CAMXe=Sohvq9wqnUYcC=Z4ASJ21RX_s4QgWF0PeCX=6wpooTOTg@mail.gmail.com>
To: Gannon Dick <gannon_dick@yahoo.com>
Cc: "eGov IG (Public)" <public-egov-ig@w3.org>
Thank you v much Gannon

for picking up the challenge of use cases-

I am not the geekest, but i do have some appreciation for technical beauty

the dataset you cooked up is elegant :-)

btw- is there a way to verify that the aggregated set is
'true'  (with 40 odds count one could check manually but a way to tell
that the meshup is not spitting up false result would be of
reassurance)

Yet  as you probably gather my point is that
socio-technical beauty implies the dataset to correspond to at least
one use case, or similar would like to know question

that we cannot see the use case for the data set does not mean that
there isnt one btw- maybe it will turn out useful in some unexpected
way (alien attack?)

:-)

cheers


PDM


PDM



On Tue, Aug 21, 2012 at 10:53 PM, Gannon Dick <gannon_dick@yahoo.com> wrote:
> Seems to me the most pressing problem for Policy Maker Worker Bees is
> translating anecdotal information (mash-ups) into "Normal Distributions" to
> present to their Boss.  The model I've come up with is a blending of
> Mash-ups, Statistics and RDF (Collections).  I hope to make it as easy as
> possible to switch between the vocabularies.  I think that the most pressing
> problem for Policy Makers themselves is the measurement of inequality, and
> for that, you count rooftops because Normal Distributions mix a lot better
> than they un-mix.  To measure inequality, one need only be able to separate
> an "Above Average" Class from a "Below Average" Class, and have the Normal
> Distribution for those Classes.  Mash-ups do this effortlessly, Probability
> Statistics is incapable, and breaks down with uncertainty in the data
> source.
>
> About the Model ... the geo namespace
> http://www.w3.org/2003/01/geo/wgs84_pos# defines
> altitude    [alt]    The WGS84 altitude of a SpatialThing (decimal meters
> above the local reference ellipsoid).
>
> All the Organizations, like the University of Oxford in my Model have
> circular view ports (I translate the "Place" to the center of a circle).  A
> Circle is a degenerate Ellipse.  The difference, for counting rooftops, is
> that the use of a circle instead of an ellipse means that you cannot
> abstractly land and look in the side window.  I consider that degenerate :-P
>
> --Gannon
>
>
>
> ________________________________
> From: Paola Di Maio <paola.dimaio@gmail.com>
> To: Gannon Dick <gannon_dick@yahoo.com>
> Cc: eGov IG (Public) <public-egov-ig@w3.org>
> Sent: Sunday, August 19, 2012 7:50 AM
> Subject: University of Oxford/ usecase
>
> Hello Gannon
>
> Thanks a lot for cooking up a recipe to count rooftps, brings a nice
> socio technical view -  and thanks for sharing the method
>
> from where I come from (the pragmatic world), looks still a bit of a
> theoretical exercise in the sense that I  find it hard to think how to
> use this neat info you pull up
>
> Could you please help define some use case for this kind of info
>
> I mean, what can i learn from this view of this data?
>
> exercise:
>
> what can I do with the knowledge I gather
>
> assume
> a)
> b) resident
> c)  public administrator planning for urbanpolicy
> d) any other
>
> :-)
>
>
> P
>
>
>
>
>
>
>> The University of Oxford makes a dandy test bed for Socio-Technical
>> Systems.
>> These are systems which count rooftops and households rather than
>> individuals in a population.
>>
>> There are three types of institutions at Oxford: Colleges, Graduate Only
>> Colleges, and Halls.  Each, 44 in all, have been founded over the last
>> centuries, and the founding dates are available.  No simple RDF List can
>> capture this, however 4 Lists can - three Types + ANY.  The problem, for
>> RDF
>> and SKOS, is the processing of the "first" and "rest".  The model used is
>> the "Standard Model" of Particle Physics - unit sized hard boxes. Much
>> better is a unit sized circle (diameter=2u). This truncates much of the
>> unexplainable combinatorial "fine structure" in the model  which you
>> visualize as gaps in the data.  You see fine structure shadows everywhere.
>> The situation can be compared to a Physician looking at a catalog of
>> thousands of MRI's to find a broken leg when he/she simply needs to look
>> at
>> an MRI of your leg.
>>
>> Anyway, a listing of the data is here[1].  The data base and many
>> supporting files are here[2]. If you load your own, you'll need root
>> privileges to load the Stored Procedures (Space and Time).
>>
>> And last but not least, not to be outdone by the BBC's Olympic Medals and
>> Dr. Brand Niemann
>> ... A mashup of Oxford University Colleges & Halls in time:
>> http://www.rustprivacy.org/2012/roadmap/oxford-university-area-map.pdf
>>
>> When I said I was going to count rooftops, I meant it :-)
>>
>> --Gannon
>>
>> [1]  http://www.rustprivacy.org/2012/roadmap/oxford_sp.txt
>> [2] http://www.rustprivacy.org/2012/roadmap/Oxford.zip
>>
>
>
>
Received on Friday, 24 August 2012 10:52:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 24 August 2012 10:52:36 GMT