Dear all,
Today, we had a videomeeting with Jane and Richard from Australia about
how to export the current content of the TeD-T platform and import it
again into the ANDS platform.
Jane and Richard will provide further SKOS documentation and examples to
Garching. We will then try to "skosify" the already existing RDF output
so that it can be imported into the ANDS services. In the near future,
the TeD-T wiki will be continued to collect new terms / definitions and
make them editable for the RDA users. The ANDS platform will then be
used for publishing stable, read-only versions of the TeD-T content.
Best regards,
Tom
--
Dr. Thomas Zastrow
Max Planck Computing and Data Facility (MPCDF)
Gießenbachstr. 2, D-85748 Garching bei München, Germany
Tel +49-89-3299-1457
http://www.mpcdf.de
Author: Jane Frazier
Date: 20 Mar, 2016
Hi Thomas,
It was lovely to meet with you last week.
The SKOS Primer can be found here: https://www.w3.org/TR/skos-primer/
and the SKOS Reference here: http://www.w3.org/TR/skos-reference/
and another guide created by our colleagues at CSIRO here in Australia:
https://www.seegrid.csiro.au/wiki/Siss/VocabularyFormalizationInSKOS
Also, 2 SKOS validators are available:
- https://www.w3.org/2004/02/skos/validation
- http://qskos.poolparty.biz/login
Here's a document that Richard wrote about PoolParty prerequisites for
importing SKOS data:
https://documentation.ands.org.au/display/DOC/PoolParty%27s+prerequisite...
Please let us know if you'd like support in mapping the DFT vocabulary
metadata to SKOS elements.
All the best,
Jane
Author: Gary Berg-Cross
Date: 21 Mar, 2016
Thanks for moving this forward and I look forward to hearing how things are
going.
Gary Berg-Cross, Ph.D.
***@***.***
*http://ontolog.cim3.net/cgi-bin/wiki.pl?GaryBergCross
*
Member, Ontolog Board of Trustees
Independent Consultant
Potomac, MD
240-426-0770
On Sun, Mar 20, 2016 at 6:44 PM, Jane Frazier <***@***.***>
wrote:
Author: Thomas Zastrow
Date: 31 Mar, 2016
Hi Jane,
Thanks for the information, I tried to find my way through and have some
questions:
a)
In SKOS, there is the definition of "container" which is exactly what I
implemented in my RDF output. Can't we use that? Whats about SKOS
"collections"?
b)
In SKOS, it seems so that "about" does not necessarily has to point to
an URL - do we need URLs for the Pool software or can it be any string?
c)
I don't really understand the "topConceptOf", "broader" and "narrower"
attributes. Can't we use them for creating our hierarchy?
Best,
Tom
Author: Jane Frazier
Date: 04 Apr, 2016
On 1 April 2016 at 00:50, ThomasZastrow
<***@***.***> wrote:
> Hi Jane,
>
> Thanks for the information, I tried to find my way through and have some
> questions:
>
> a)
> In SKOS, there is the definition of "container" which is exactly what I
> implemented in my RDF output. Can't we use that? Whats about SKOS
> "collections"?
>
I've never come across skos:Container before... only skos:Collection.
Typically, skos:Collection is used to order or identify collections of skos
concepts. skos:ConceptScheme is typically used to represent a
vocabulary/thesaurus (perhaps with a hierarchy).
>
> b)
> In SKOS, it seems so that "about" does not necessarily has to point to an
> URL - do we need URLs for the Pool software or can it be any string?
>
skos concepts use URIs ... which may or
may not resolve, depending upon the needs/capabilities of the vocab
creators/users.
vocabularies created/managed in PoolParty are automatically assigned
resolvable URIs that either use the default ANDS URI pattern (for example,
http://purl.org/au-research/vocabulary/anzsrc-for/2008/0401) or are
designated with an external URI (for example,
http://vocab.nerc.ac.uk/collection/P01/current/MDMAP014) which may or may
not resolve outside of our Linked Data API.
>
> c)
> I don't really understand the "topConceptOf", "broader" and "narrower"
> attributes. Can't we use them for creating our hierarchy?
>
Yes, these properties exist to allow hierarchy to be captured.
- skos:broader would be used to state that one concept is broader (more
general/parent of/less granular) than another
- skos:narrower would be used to state the inverse: that one concept is
narrower (more specific/child of/more granular) than another
- skos:topConceptOf would be used to state that a concept is at the top
of a hierarchy, and is a top concept in a skos:ConceptScheme
> Best,
>
> Tom
>
> Am 20.03.2016 um 23:44 schrieb Jane Frazier:
>
> Hi Thomas,
> It was lovely to meet with you last week.
>
> The SKOS Primer can be found here: https://www.w3.org/TR/skos-primer/
> and the SKOS Reference here:
> http://www.w3.org/TR/skos-reference/
> and another guide created by our colleagues at CSIRO here in Australia:
>
> https://www.seegrid.csiro.au/wiki/Siss/VocabularyFormalizationInSKOS
>
> Also, 2 SKOS validators are available:
>
> -
> https://www.w3.org/2004/02/skos/validation
> - http://qskos.poolparty.biz/login
>
> Here's a document that Richard wrote about PoolParty prerequisites for
> importing SKOS data:
>
> https://documentation.ands.org.au/display/DOC/PoolParty%27s+prerequisite...
>
> Please let us know if you'd like support in mapping the DFT vocabulary
> metadata to SKOS elements.
>
> All the best,
> Jane
>
> On 17 March 2016 at 22:29, Thomas Zastrow
<***@***.***>
> wrote:
>
>> Dear all,
>>
>> Today, we had a videomeeting with Jane and Richard from Australia about
>> how to export the current content of the TeD-T platform and import it again
>> into the ANDS platform.
>>
>> Jane and Richard will provide further SKOS documentation and examples to
>> Garching. We will then try to "skosify" the already existing RDF output so
>> that it can be imported into the ANDS services. In the near future, the
>> TeD-T wiki will be continued to collect new terms / definitions and make
>> them editable for the RDA users. The ANDS platform will then be used for
>> publishing stable, read-only versions of the TeD-T content.
>>
>> Best regards,
>>
>> Tom
>>
>> --
>> Dr. Thomas Zastrow
>> Max Planck Computing and Data Facility (MPCDF)
>> Gießenbachstr. 2, D-85748 Garching bei München, Germany
>> Tel +49-89-3299-1457
>> http://www.mpcdf.de
>>
>>
>
>
> --
> *Jane Frazier*
> Data Librarian | *Australian National Data Service*
> orcid.org/0000-0002-2374-4964
>
> Monash University, Building F, Level 6, Room 26, 900 Dandenong Road,
> Caulfield East, VIC 3145
> Postal address: ANDS Office, Monash University, F610, PO Box 197,
> Caulfield East VIC 3145
> T: +613 9905 6275 | E: <***@***.***>***@***.***
>
>
> --
> Dr. Thomas Zastrow
> Max Planck Computing and Data Facility (MPCDF)
> Gießenbachstr. 2, D-85748 Garching bei München, Germany
> Tel +49-89-3299-1457http://www.mpcdf.de
>
On 1 April 2016 at 00:50, ThomasZastrow
<***@***.***> wrote:
> Hi Jane,
>
> Thanks for the information, I tried to find my way through and have some
> questions:
>
> a)
> In SKOS, there is the definition of "container" which is exactly what I
> implemented in my RDF output. Can't we use that? Whats about SKOS
> "collections"?
>
I've never come across skos:Container before... only skos:Collection.
Typically, skos:Collection is used to order or identify collections of skos
concepts. skos:ConceptScheme is typically used to represent a
vocabulary/thesaurus (perhaps with a hierarchy).
On 1 April 2016 at 00:50, ThomasZastrow
<***@***.***> wrote:
> Hi Jane,
>
> Thanks for the information, I tried to find my way through and have some
> questions:
>
> a)
> In SKOS, there is the definition of "container" which is exactly what I
> implemented in my RDF output. Can't we use that? Whats about SKOS
> "collections"?
>
I've never come across skos:Container before... only skos:Collection.
Typically, skos:Collection is used to order or identify collections of skos
concepts. skos:ConceptScheme is typically used to represent a
vocabulary/thesaurus (perhaps with a hierarchy).
>
> b)
> In SKOS, it seems so that "about" does not necessarily has to point to an
> URL - do we need URLs for the Pool software or can it be any string?
>
skos concepts use URIs ... which may or
may not resolve, depending upon the needs/capabilities of the vocab
creators/users.
vocabularies created/managed in PoolParty are automatically assigned
resolvable URIs that either use the default ANDS URI pattern (for example,
http://purl.org/au-research/vocabulary/anzsrc-for/2008/0401) or are
designated with an external URI (for example,
http://vocab.nerc.ac.uk/collection/P01/current/MDMAP014) which may or may
not resolve outside of our Linked Data API.
On 1 April 2016 at 00:50, ThomasZastrow
<***@***.***> wrote:
> Hi Jane,
>
> Thanks for the information, I tried to find my way through and have some
> questions:
>
> a)
> In SKOS, there is the definition of "container" which is exactly what I
> implemented in my RDF output. Can't we use that? Whats about SKOS
> "collections"?
>
I've never come across skos:Container before... only skos:Collection.
Typically, skos:Collection is used to order or identify collections of skos
concepts. skos:ConceptScheme is typically used to represent a
vocabulary/thesaurus (perhaps with a hierarchy).
>
> b)
> In SKOS, it seems so that "about" does not necessarily has to point to an
> URL - do we need URLs for the Pool software or can it be any string?
>
skos concepts use URIs ... which may or
may not resolve, depending upon the needs/capabilities of the vocab
creators/users.
vocabularies created/managed in PoolParty are automatically assigned
resolvable URIs that either use the default ANDS URI pattern (for example,
http://purl.org/au-research/vocabulary/anzsrc-for/2008/0401) or are
designated with an external URI (for example,
http://vocab.nerc.ac.uk/collection/P01/current/MDMAP014) which may or may
not resolve outside of our Linked Data API.
>
> c)
> I don't really understand the "topConceptOf", "broader" and "narrower"
> attributes. Can't we use them for creating our hierarchy?
>
Yes, these properties exist to allow hierarchy to be captured.
- skos:broader would be used to state that one concept is broader (more
general/parent of/less granular) than another
- skos:narrower would be used to state the inverse: that one concept is
narrower (more specific/child of/more granular) than another
- skos:topConceptOf would be used to state that a concept is at the top
of a hierarchy, and is a top concept in a skos:ConceptScheme
Author: Thomas Zastrow
Date: 04 Apr, 2016
Dear Richard,
Thank you very much for your information. Let me summarize your mail and
pass it as a question to Gary:
Gary, in which way do you want to make use of the TeD-T import into
ANDS? What are the reasons, which functionality do you expect?
If this is clarified, then we can go on with the SKOS export. But to be
honest, I have to say that I don't have the time for diving deep into
the SKOS specification. So, it would be nice if someone can come up with
an idea how I should map the TeD-T-content (terms, definition,
hierarchy) into the SKOS world.
Best,
Tom
--
Dr. Thomas Zastrow
Max Planck Computing and Data Facility (MPCDF)
Gießenbachstr. 2, D-85748 Garching bei München, Germany
Tel +49-89-3299-1457
http://www.mpcdf.de