JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for STARDEV Archives


STARDEV Archives

STARDEV Archives


STARDEV@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

STARDEV Home

STARDEV Home

STARDEV  August 2006

STARDEV August 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: UTYPEs

From:

Norman Gray <[log in to unmask]>

Reply-To:

Starlink development <[log in to unmask]>

Date:

Mon, 14 Aug 2006 16:49:48 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (177 lines)

David and others, hello.

[this is a long un', but it's worth it -- promise]

On 2006 Aug 7 , at 10.29, David Berry wrote:

> On Wed, 2 Aug 2006, Norman Gray wrote:
>
>> Mark,
>>
>> On 2006 Aug 2 , at 12.32, Norman Gray wrote:
>>
>>>>>> think about whether you
>>>>>> need to perform unit conversions for the quantity that you've
>>>>>> identified to mean what you think it means...
>
> Sounds to me like some standard library for handling all this system
> conversion, units conversion, searching, etc,  stuff is needed :-)

Ah, but _that_ we've already got.  What we don't have is something  
_generic_ for what I shall suddenly decide to call semantic conversion.

Until now!  Herewith the demo premiere (I plan to talk about this at  
the Strasbourg VOTech meeting, and I hope at the IVOA, but I'll run  
it past youse first).

>> I meant to add that unit conversions wouldn't be addressed by any
>> sort of solution I'm talking about, but they're rather separate
>> anyway, since unit specifications address how the value is
>> represented -- and thus are to some extent syntactic -- rather than
>> what it is.  No?
>
> In that sense a velocity (say) is a velocity is a velocity, and *all*
> metadata describing it is syntactic, not just the units.
>
> To say "velocity A and B are the same, but just measured in different
> units" seems to me to be no different to saying "velocity A and B are
> the same but just measured in different rest frames". In both cases, A
> and B are representations of the same physical phenomenon. So I can't
> immediately see any reason for treating units differently to any other
> item of metadata. They are all needed if you want to be able to  
> compare
> two values.

You're really pining for the good old Quantity discussion, aren't you?

I think that fundamentally, in the abstract, you're right, and that  
units are as much a part of the meaning of a velocity (say) as  
anything else.  However I think they are practically distinct, and I  
have just now come across what I believe to be a good illustration of  
why.

But first the demo (I'm on the edge of my seat -- I don't know about  
you).



I'm working on the utype-to-utype-to-ucd mappings I was talking about  
a week or so ago, and I'm using the USNO-B catalogue at ROE as a test  
case, simply because it was handy.  That resource has an IVO-ID of  
<ivo://roe.ac.uk/DSA_USNOB/TDB>, and has a set of column descriptions  
which includes

<column>
<name>ra</name>
<description>J2000 Celestial Right Ascension</description>
<datatype>datatype='float'</datatype>
<ucd>POS_EQ_RA_MAIN</ucd>
<unit>deg</unit>
</column>

(this is a type defined by <http://www.ivoa.net/xml/VODataService/ 
v0.5>, and yes, that <datatype> does look a bit odd...).

So, there's implicitly a UTYPE <ivo://roe.ac.uk/DSA_USNOB/TDB#ra>,  
which is a subclass of <http://cdsweb.u-strasbg.fr/UCD/ 
old#POS_EQ_RA_MAIN>.  That is, I can convert the VODataService  
information to RDF.

 From the UCD1 to UCD1+ mappings, I can get that POS_EQ_RA_MAIN is a  
subclass of (well, was mapped to) pos.eq.ra;meta.main.  I can  
generate RDF from that, too.

We might also decide that there is a set of types which is of  
interest to us, or a community we're part of, and that:

@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix x: <http://example.edu/utypes#>.
x:ra a rdfs:Class.
<ivo://roe.ac.uk/DSA_USNOB/TDB#ra> rdfs:subClassOf x:ra.

(that's RDF, in the form of `Notation3', and says that <...#ra> is a  
subclass of the concept <http://example.edu/utypes#ra>, so that the  
USNO-B RA is a more specific type of RA than the one we've defined  
and documented at that URL).

So we load those different bits of information into the reasoner, and  
then query it:

% cat query.rq
prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>
select ?t
where {
     <ivo://roe.ac.uk/DSA_USNOB/TDB#ra> rdfs:subClassOf ?t
}
%

(that's SPARQL, and is a broadly SQL-like query language for RDF).   
So we POST the query to the reasoning service:

% curl --data-binary @query.rq \
     --header 'Accept: text/csv' \
     --header 'Content-Type: application/sparql-query' \
     http://localhost:8080/quaestor/kb/ucd
t
http://example.edu/utypes#ra
http://cdsweb.u-strasbg.fr/UCD/old#POS_EQ_RA_MAIN
ivo://roe.ac.uk/DSA_USNOB/TDB#ra
http://www.w3.org/2000/01/rdf-schema#Resource
http://cdsweb.u-strasbg.fr/UCD/words#pos.eq.ra;meta.main
%

(obviously, you could dereference that URL from any code, and if  
you're prepared to URL-encode the query, you can GET it as well).   
So, that gives you a list of all the things that the USNO-B 'ra'  
column is a subclass of.  Our software has presumably been written so  
that it already knows what a <http://example.edu/utypes#ra> is  
(that's why we added the extra mapping information); but if not,  
it'll know what the pos.eq.ra;meta.main UCD is.

Thus, we've gathered together information from a variety of loosely  
cooperating sources:

* the ROE folk declared that the USNO 'ra' column
   was a particular old-style UCD, but they haven't updated it;
* there's a fixed mapping of old-style to new-style UCDs;
* you added the mapping to <http://example.edu/utype#ra> yourself,
   for your own purposes.  Perhaps you had to work it
   out from hard-to-find documentation, or perhaps
   the example.edu namespace is a discipline-specific
   standard, or an IVOA one.

Then we queried it with a very simple expression, getting output from  
which it's easy to extract the information we want.  It means all the  
various actors here can remain fairly loosely coupled, and the  
software reading this can operate at whatever level of generality it  
needs to.



The link to units (getting back to that, David) is that when  
assembling and using this information, I really couldn't see a place  
for the units information which is in the VODataService element  
above.  The statement "USNO-B's 'ra' column is a type of pos.eq.ra"  
is true independently of units.  Once I've established just what this  
USNO-B column is supposed to be (aha, an RA!), then I'm going to have  
to discover what units the data there has, in order to actually read  
it.  So yes, a complete description of the numbers in that column  
requires unit information, but that description can be usefully  
decomposed/factored into orthogonal components, namely the semantic  
information (which I'm taking to mean "column 'ra' is a pos.eq.ra")  
and the unit information.  That's not a principled factorisation, but  
a practical one.

So, what does all that sound like?

See you,

Norman


-- 
------------------------------------------------------------------------ 
----
Norman Gray  /  http://nxg.me.uk
eurovotech.org  /  University of Leicester, UK

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

July 2019
June 2019
February 2019
January 2019
December 2018
November 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
December 2017
October 2017
August 2017
July 2017
May 2017
April 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
October 2015
September 2015
August 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
2004
April 2003
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager