[auscope-geosciml] GeoSciML vocabulary http URIs dereferencing old URIs and encoding errors in skos vocabularies

Ebner, Marcus Marcus.Ebner at geologie.ac.at
Tue Feb 28 05:20:21 EST 2012


Steve,

its  good to know that the old URIs will continue to dereference this saves me some work! Concerning the encoding of the ConceptSchemes your guess was correct. It seems that the skos:concept triple was indeed created during the processing of the data.  The ConceptSchemes are thus encoded correctly. Sorry for causing inconvenience!

One small last thing:
 In the definition for "reverse" ( http://resource.geosciml.org/classifier/cgi/faultmovementsense/0008 ) in faultmovementsense vocab the hanging wall should be moved up...

Please let me know when the SPARQL Endpoint is available...

Marcus

-----Ursprüngliche Nachricht-----
Von: auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope-geosciml-bounces at lists.arcs.org.au] Im Auftrag von auscope-geosciml-request at lists.arcs.org.au
Gesendet: Montag, 27. Februar 2012 23:36
An: auscope-geosciml at lists.arcs.org.au
Betreff: auscope-geosciml Digest, Vol 35, Issue 37

Send auscope-geosciml mailing list submissions to
	auscope-geosciml at lists.arcs.org.au

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.arcs.org.au/cgi-bin/mailman/listinfo/auscope-geosciml
or, via email, send a message with subject or body 'help' to
	auscope-geosciml-request at lists.arcs.org.au

You can reach the person managing the list at
	auscope-geosciml-owner at lists.arcs.org.au

When replying, please edit your Subject line so it is more specific than "Re: Contents of auscope-geosciml digest..."


Today's Topics:

   1. Re: GeoSciML vocabulary http URIs dereferencing	old URIs and
      encoding errors in skos vocabularies (Stephen M Richard)
   2. Re: A Geoscience, Minerals and Petroleum Thesaurus
      [SEC=UNCLASSIFIED] (Oliver.Raymond at ga.gov.au)


----------------------------------------------------------------------

Message: 1
Date: Mon, 27 Feb 2012 12:48:45 -0700
From: "Stephen M Richard" <steve.richard at azgs.az.gov>
To: <auscope-geosciml at lists.arcs.org.au>
Subject: Re: [auscope-geosciml] GeoSciML vocabulary http URIs
	dereferencing	old URIs and encoding errors in skos vocabularies
Message-ID: <013401ccf588$d24534d0$76cf9e70$@azgs.az.gov>
Content-Type: text/plain;	charset="iso-8859-1"

Marcus--
Yes the existing URI's will continue to dereference, as you point out there are systems using them that we don't want to break. The vocabulary document with the new URI's also includes skos:ExactMatch relations between the new and old URIs for the same concepts. 

Thanks for noting the issue with the ConceptSchemeID triple. 
ConceptScheme is defined thus in the xml/rdf:
<owl:Class rdf:about="&skos;ConceptScheme">
        <rdfs:subClassOf rdf:resource="&owl;Thing"/>
    </owl:Class>
   And thus in the new Turtle versions c defined thus:
skos:ConceptScheme rdf:type owl:Class ;      
       rdfs:subClassOf owl:Thing .

I can't find ConceptSchemeID in the files in subversion repository (https://www.seegrid.csiro.au/subversion/CGI_CDTGVocabulary/tags/SKOSVocabul
aries) or in the xml/rdf files (spot checking files from http://resource.geosciml.org/201012RDF/.  My guess is that ConceptSchemeID may be added to the vocabularies somewhere in your processing workflow?  It is indeed inconsistent with the triples listed.


Fixed the vein problem

Hmm, the capitalization will have to get fixed in the 201202 versions...

Auscope is setting up a sparql endpoint, it was working last week (try
http://resource.geosciml.org/classifier/cgi/eventenvironment/0008) , but they're doing some development work and it doesn't seem to be up today.

steve

Stephen M. Richard
Arizona Geological Survey
416 W. Congress St., #100
Tucson, Arizona, 85701   USA
phone: 520 209-4127
AZGS Main: (520) 770-3500.  FAX: (520) 770-3505
email: steve.richard at azgs.az.gov

> -----Original Message-----
> From: auscope-geosciml-bounces at lists.arcs.org.au 
> [mailto:auscope-geosciml- bounces at lists.arcs.org.au] On Behalf Of 
> Ebner, Marcus
> Sent: Monday, February 27, 2012 3:56 AM
> To: auscope-geosciml at lists.arcs.org.au
> Subject: Re: [auscope-geosciml] GeoSciML vocabulary http URIs
dereferencing
> old URIs and encoding errors in skos vocabularies
> 
> Dear GeoSciML concept definition task group,
> 
> I am glad to see that you have come to a decision regarding the new 
> (and hopefully persistent) URI scheme for the CGI vocabulary. Will the 
> GeoSciML Server http://auscope-services-test.arrc.csiro.au/ that hosts 
> the
vocabulary be
> able to dereference (or redirect) the old URIs to the new cool ones? 
> Since
the
> old URIs are around for more than 2 years this would make sense (and 
> would save me some work). In addition the authors of the INSPIRE data
specification
> (Geology & Mineral Resources) make heavy use of CGI vocabularies 
> although they currently ignore the identifier management or at least 
> factor it
out.... It
> would thus be very useful in terms of INSPIRE?
> 
> Apart from that I suggest that the development of the new version of 
> the vocabularies could be used to get rid of some encoding errors  I 
> have encountered while working with the currently available vocabularies:
> 1)
> I have found that all ConceptSchemes have the following triples...
> ConceptSchemeID	 http://www.w3.org/1999/02/22-rdf-syntax-ns#type
> 	http://www.w3.org/2004/02/skos/core#ConceptScheme
> ConceptSchemeID	 http://www.w3.org/1999/02/22-rdf-syntax-ns#type
> 	http://www.w3.org/2004/02/skos/core#Concept
> 
> According the the Skos reference (see section 4.4 in 
> http://www.w3.org/TR/2008/WD-skos-reference-20080125/#concept-schemes
> ) the classes Concept and ConceptScheme are DISJOINT!
> 
> 2)
> In the geologic unit morphology vocabulary Sigmoidal vein and  vein 
> shape
are in
> a circular loop (i.e. they are broader and narrower concepts of each
other) !!!
> 
> 3)
> The capitalization in the labels (especially for the concept schemes) 
> is
not
> consistent
> e.g. 	CGI Simple Lithology Categories
> 	CGI Lineation type categories
> 	CGI Alteration type Categories
> 	CGI Mapped Feature Observation Method terms
> 	...
> The following concept schemes lack  "CGI" in the prefLabel (and are
sometimes
> in CamelBack notation)
> 	CompositionCategory
> 	ContactType
> 	EventEnvironment
> 	Fault Type Categories
> 	FoliationType
> 	Metamorphic facies categories
> 	Structure measurement convention code vocabulary
> 
> 
> 
> I suggest providing future vocabulary via a public sparql endpoint. 
> This
would be
> very useful distribute your vocabularies to a technical audience
(developer)  in
> addition encoding errors can be tracked down easily.
> 
> 
> Cheers,
> 
> Marcus
> 
> 
> --
> Dr. Marcus Ebner
> Fachabteilung Geoinformation - Department of Geoinformation 
> Geologische Bundesanstalt - Geological Survey of Austria Neulinggasse 
> 38, A-1030
Vienna,
> AUSTRIA
> Phone:  +43-1-712 56 74 414  FAX: +43-1-712 56 74 56
> email: marcus.ebner at geologie.ac.at
> web: www.geologie.ac.at
> 
> 
> 
> 
> 
> -----Urspr?ngliche Nachricht-----
> Von: auscope-geosciml-bounces at lists.arcs.org.au 
> [mailto:auscope-geosciml- bounces at lists.arcs.org.au] Im Auftrag von 
> auscope-geosciml- request at lists.arcs.org.au
> Gesendet: Montag, 27. Februar 2012 01:58
> An: auscope-geosciml at lists.arcs.org.au
> Betreff: auscope-geosciml Digest, Vol 35, Issue 34
> 
> Send auscope-geosciml mailing list submissions to
> 	auscope-geosciml at lists.arcs.org.au
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.arcs.org.au/cgi-bin/mailman/listinfo/auscope-geosciml
> or, via email, send a message with subject or body 'help' to
> 	auscope-geosciml-request at lists.arcs.org.au
> 
> You can reach the person managing the list at
> 	auscope-geosciml-owner at lists.arcs.org.au
> 
> When replying, please edit your Subject line so it is more specific 
> than
"Re:
> Contents of auscope-geosciml digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: GeoSciML vocabulary http URIs (Simon.Cox at csiro.au)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 27 Feb 2012 08:58:14 +0800
> From: <Simon.Cox at csiro.au>
> To: <auscope-geosciml at lists.arcs.org.au>,
> 	<alistair.bh.ritchie at gmail.com>,
> 	<Joachim.Gersemann at bgr.de>,
> 	<reh at bgs.ac.uk>, <Jan.Jellema at tno.nl>,
> 	<luca.olivetta at isprambiente.it>, <Maija.Pennanen at gtk.fi>,
> 	<snt at agiweb.org>, <y.filkin at mail.ru>
> Subject: Re: [auscope-geosciml] GeoSciML vocabulary http URIs
> Message-ID:
> 	<5D27281509882544A841804E4EBA914C3AA96DA919 at EXWA-
> MBX01.nexus.csiro.au>
> Content-Type: text/plain; charset="utf-8"
> 
> Steve ?
> 
> While I?m strongly in favour of memorable URIs, I don?t think it is
imperative
> that the URI itself be searchable.
> 
> Simon
> 
> From: auscope-geosciml-bounces at lists.arcs.org.au 
> [mailto:auscope-geosciml- bounces at lists.arcs.org.au] On Behalf Of 
> Stephen M Richard
> Sent: Saturday, 25 February 2012 2:28 AM
> To: 'Alistair Ritchie'; auscope-geosciml at lists.arcs.org.au; Gersemann,
Joachim;
> Heaven, Rachel E; Jellema, J. (Jan); Luca Olivetta; 
> Maija.Pennanen at gtk.fi; Sharon Tahirkheli; Yuri Filkin
> Subject: Re: [auscope-geosciml] GeoSciML vocabulary http URIs
> 
> We are in the process of generating a new set of SKOS vocabularies 
> that
use all
> text-based tokens, e.g.
> http://resource.geosciml.org/classifier/cgi/lithology/0260
> will map to
>
http://resource.geosciml.org/classifier/cgi/lithology/tuff_breccia_agglomera
te
> _or_pyroclastic_breccia
> 
> BUT there is a question as to what would be the best form of
concept-specific
> token string. Here are the options (using the above example
> Lower camel case:    tuffBrecciaAgglomerateOrPyroclasticBreccia
> Upper camel case:  TuffBrecciaAgglomerateOrPyroclasticBreccia
> All lower case: tuffbrecciaagglomerateorpyroclasticbreccia
> Underscores: tuff_breccia_agglomerate_or_pyroclastic_breccia
> Hyphens: tuff-breccia-agglomerate-or-pyroclastic-breccia
> 
> Strings containing underscores are treated as a single, continuous 
> sting,
while
> those containing hyphens as treated as being separated into words at 
> each hyphen. Thus a web search for tuff would likely find
>
http://resource.geosciml.org/classifier/cgi/lithology/tuff-breccia-agglomera
te-
> or-pyroclastic-breccia, but not any of the other schemes.
> 
> Currently I?ve been converting using the underscore scheme (see 
> rdf/turtle
docs
> at
> https://www.seegrid.csiro.au/subversion/CGI_CDTGVocabulary/trunk/Vocab
> ula ry201202), so easiest thing is to stick to that. Speak up now if 
> you have
any
> opinions or tech reasons for favoring one of the other approaches.
> 
> Thanks
> steve
> 
> 
> Stephen M. Richard
> Arizona Geological Survey
> 416 W. Congress St., #100
> Tucson, Arizona, 85701   USA
> phone: 520 209-4127
> AZGS Main: (520) 770-3500.  FAX: (520) 770-3505
> email: steve.richard at azgs.az.gov
> 
> From: Alistair Ritchie [mailto:alistair.bh.ritchie at gmail.com]
> Sent: Thursday, February 23, 2012 6:12 PM
> To: Stephen M Richard
> Subject: Re: GeoSciML vocabulary http URIs
> 
> Hi Steve,
> 
> First up: glad you've made the shift to Turtle, it's an awful lot 
> easier
to cope with
> than RDF/XML.
> 
> I've become agnostic about underscores as separators - in large part
because
> TopBraid Composer/EVN is bullying me into accepting them. For a while 
> I
liked
> the idea of pluses ('+') for spaces in the URI - after all, it is the
space escape char
> so it means space - before realising that makes them an invalid part 
> of a QName. Bit of a problem in the RDF space.
> 
> The next (only other?) thing I assume we need to be mindful of is 
> whether
we
> want a search engine to find words in a URI - a search on 'igneous rock'
finds a
> resource containing the string
> 'http://resource.example.org/classifier/abhr/igneous-rock.' This seems 
> to
be an
> advantage of the memorable-ness of cool URIs. If we do, then the 
> general underscore vs hyphen debate becomes important. Strings 
> containing underscores are treated as a single, continuous sting, 
> while those
containing
> hyphens as treated as being separated at each hyphen.
> 
> Although this isn't unambigous:
> barium-bearing carbonate chemistry ->
> http://resource.geosciml.org/classifier/cgi/compositioncategory/barium
> -
> bearing-carbonate-chemistry
> 
> This means I've a slight preference for hyphens,and have favoured them 
> in
my
> feature IDs, but but using underscores as per the original URN 
> convention
we
> can compare the tokens in the URIs with the URNs.
> 
> There is CamelCase as well, which Simon used for the age intervals. If
we're
> going to have a single string, that seems best from a human-readable 
> perspective.
> 
> This is a bit of a ramble ... is the ability to match URIs to phrases
important? If
> not - I'd stick with the URNs.
> 
> Cheers,
> Alistair
> 
> "XML is like violence. If it doesn't solve the problem, use more." -
Unknown
> 
> On 24 February 2012 12:34, Stephen M Richard 
> <steve.richard at azgs.az.gov<mailto:steve.richard at azgs.az.gov>> wrote:
> HI?glad someone else has some time to put in this. If you look in the
> CGI_CDTGVocabulary/trunk/Vocabulary201202 subversion directory 
> (https://www.seegrid.csiro.au/subversion/CGI_CDTGVocabulary/trunk/Voca
> bul
> ary201202) you?ll see a number of vocabs I?ve converted to the 
> word-based final token (cool???) URI?s. Only difference is mine have 
> underscores
between
> words (?_?). I just used the same text we had in the URNs in our first
iteration.
> 
> I also switched to Turtle notation for the SKOS; it?s easier to 
> manipulate
in a text
> editor. I attached the python script I use to do the replacements, and 
> a
mapping
> file that the python uses. It replaces everything in the second column
with
> what?s in the first column.
> I?ve converted all the files, but there?s a one more pass required to
check the
> ttl, update the historyNote, and check for other assorted errors. I?ll
commit all
> the files if you might be able to do the final check. I?m using Prot?g?
still for this
> kind of editing. I?m agnostic about the underscores in the
concept-specific
> tokens. They could be eliminated with some global search and replace, 
> or running the python replaceIDs routine again?
> 
> What do you think?
> steve
> 
> 
> Stephen M. Richard
> Arizona Geological Survey
> 416 W. Congress St., #100
> Tucson, Arizona, 85701   USA
> phone: 520 209-4127<tel:520%20209-4127> AZGS Main: (520) 
> 770-3500<tel:%28520%29%20770-3500>.  FAX: (520) 770- 
> 3505<tel:%28520%29%20770-3505>
> email: steve.richard at azgs.az.gov<mailto:steve.richard at azgs.az.gov>
> 
> From: Alistair Ritchie
>
[mailto:alistair.bh.ritchie at gmail.com<mailto:alistair.bh.ritchie at gmail.com>]
> Sent: Thursday, February 23, 2012 1:20 AM
> To: Steve Richard
> Cc: Simon Cox
> Subject: GeoSciML vocabualry http URIs
> 
> Hi Steve
> 
> With the recent decsion to make the GeoSciML vocabulary http URIs cool
again,
> I've tried to make sure that the reference dataset is cool as well (if 
> it
is, it'll be
> the first I've ever done anything cool).
> 
> Based on the format of relationship type vocabulary URIs you 
> circulated
recently
> I took a stab at providing new URIs according that template (from what 
> I
can
> tell: all lower case, no seperators, hyphens remain - eg
'continental-crustal').
> 
> Would you mind casting you eyes over the following list of URIs and 
> tell
me
> whether or not I got it right. I'd like to make sure that the 
> reference DB
conatins
> valid content with identifiers that can be derferenced.
> 
> Pretty sure I've got the ages right - straight from the new ontology.
> 
> Thanks,
> Alistair
> 
> /*/gsml:samplingFrame
> "http://resource.geosciml.org/feature/cgi/EarthNaturalSurface"
> 
> /gsml:MappedFeature/gsml:observationMethod
> "direct
>
observation";"http://resource.geosciml.org/classifier/cgi/mappedfeatureobser
v
> ationmethod/directobservation"
> "inferred by indirect
>
methods";"http://resource.geosciml.org/classifier/cgi/mappedfeatureobservati
> onmethod/inferredbyindirectmethods"
> "inferred radiometric
>
survey";"http://resource.geosciml.org/classifier/cgi/mappedfeatureobservatio
n
> method/inferredradiometricsurvey"
> "observed elevation
>
data";"http://resource.geosciml.org/classifier/cgi/mappedfeatureobservationm
> ethod/observedelevationdata"
>
"compilation";"http://resource.geosciml.org/classifier/cgi/mappedfeatureobse
r
> vationmethod/compilation"
> "observed aerial
>
imagery";"http://resource.geosciml.org/classifier/cgi/mappedfeatureobservati
o
> nmethod/observedaerialimagery"
> 
> gsmler:lithology
> "anthropogenic
>
material";"http://resource.geosciml.org/classifier/cgi/lithology/anthropogen
ic
> material"
> "ash tuff, lapillistone, and lapilli
>
tuff";"http://resource.geosciml.org/classifier/cgi/lithology/ashtufflapillis
tonean
> dlapillituff"
> "basalt";"http://resource.geosciml.org/classifier/cgi/lithology/basalt"
> "breccia";"http://resource.geosciml.org/classifier/cgi/lithology/breccia"
> "clay";"http://resource.geosciml.org/classifier/cgi/lithology/clay"
>
"conglomerate";"http://resource.geosciml.org/classifier/cgi/lithology/conglo
m
> erate"
>
"diamictite";"http://resource.geosciml.org/classifier/cgi/lithology/diamicti
te"
> "dolomitic or magnesian sedimentary
>
rock";"http://resource.geosciml.org/classifier/cgi/lithology/dolomiticormagn
esi
> ansedimentaryrock"
> "fine grained igneous
>
rock";"http://resource.geosciml.org/classifier/cgi/lithology/finegrainedigne
ousr
> ock"
> "granite";"http://resource.geosciml.org/classifier/cgi/lithology/granite"
>
"granodiorite";"http://resource.geosciml.org/classifier/cgi/lithology/granod
iori
> te"
> "gravel";"http://resource.geosciml.org/classifier/cgi/lithology/gravel"
>
"hornfels";"http://resource.geosciml.org/classifier/cgi/lithology/hornfels"
> "metamorphic
>
rock";"http://resource.geosciml.org/classifier/cgi/lithology/metamorphicrock
"
> "mud";"http://resource.geosciml.org/classifier/cgi/lithology/mud"
>
"mudstone";"http://resource.geosciml.org/classifier/cgi/lithology/mudstone"
> "peat";"http://resource.geosciml.org/classifier/cgi/lithology/peat"
> "phaneritic igneous
>
rock";"http://resource.geosciml.org/classifier/cgi/lithology/phaneriticigneo
usro
> ck"
> "pyroclastic
>
material";"http://resource.geosciml.org/classifier/cgi/lithology/pyroclastic
mate
> rial"
> "sand";"http://resource.geosciml.org/classifier/cgi/lithology/sand"
>
"sandstone";"http://resource.geosciml.org/classifier/cgi/lithology/sandstone
"
> "sedimentary
>
material";"http://resource.geosciml.org/classifier/cgi/lithology/sedimentary
ma
> terial"
> "shale";"http://resource.geosciml.org/classifier/cgi/lithology/shale"
> "silt";"http://resource.geosciml.org/classifier/cgi/lithology/silt"
> "tholeiitic
> basalt";"http://resource.geosciml.org/classifier/cgi/lithology/tholeii
> tic
basalt"
> 
> gsmler:consoldiationDegree
>
"consolidated";"http://resource.geosciml.org/classifier/cgi/consolidationdeg
re
> e/consolidated"
>
"indurated";"http://resource.geosciml.org/classifier/cgi/consolidationdegree
/in
> durated"
>
"unconsolidated";"http://resource.geosciml.org/classifier/cgi/consolidationd
eg
> ree/unconsolidated"
> "unconsolidated,
>
loose";"http://resource.geosciml.org/classifier/cgi/consolidationdegree/unco
ns
> olidatedloose"
> 
> gsmlga:eventEnvironment
> "coastal plain
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/coast
al
> plainsetting"
> "contact metamorphic
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/conta
ct
> metamorphicsetting"
> "continental-crustal
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/conti
ne
> ntal-crustalsetting"
> "continental shelf
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/conti
ne
> ntalshelfsetting"
> "eruption centre
> environment";"http://www.opengis.net/def/nil/OGC/0/template"
> "floodplain
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/flood
pl
> ainsetting"
> "glacier related
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/glaci
err
> elatedsetting"
> "lacustrine
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/lacus
tri
> nesetting"
> "middle continental crust
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/middl
ec
> ontinentalcrustsetting"
> "playa
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/playa
se
> tting"
> "river channel
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/river
cha
> nnelsetting"
> "shoreline
>
settings";"http://resource.geosciml.org/classifier/cgi/eventenvironment/shor
eli
> nesettings"
> "submarine fan
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/subma
ri
> nefansetting"
> "swamp or marsh
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/swamp
> ormarshsetting"
> "terrestrial
>
setting";"http://resource.geosciml.org/classifier/cgi/eventenvironment/terre
stri
> alsetting"
> 
> gsmlga:eventProcess
> "contact
>
metamorphism";"http://resource.geosciml.org/classifier/cgi/eventprocess/cont
> actmetamorphism"
>
"deposition";"http://resource.geosciml.org/classifier/cgi/eventprocess/depos
iti
> on"
> "deposition from moving
>
fluid";"http://resource.geosciml.org/classifier/cgi/eventprocess/depositionf
rom
> movingfluid"
>
"eruption";"http://resource.geosciml.org/classifier/cgi/eventprocess/eruptio
n"
>
"intrusion";"http://resource.geosciml.org/classifier/cgi/eventprocess/intrus
ion"
> "mass
>
wasting";"http://resource.geosciml.org/classifier/cgi/eventprocess/masswasti
n
> g"
> "material transport and
>
deposition";"http://resource.geosciml.org/classifier/cgi/eventprocess/materi
alt
> ransportanddeposition"
> "mechanical
>
deposition";"http://resource.geosciml.org/classifier/cgi/eventprocess/mechan
i
> caldeposition"
> "turbidity current
>
deposition";"http://resource.geosciml.org/classifier/cgi/eventprocess/turbid
ityc
> urrentdeposition"
> "wind
>
erosion";"http://resource.geosciml.org/classifier/cgi/eventprocess/winderosi
on
> "
> 
> gsmlgs:contactType
> "conformable
>
contact";"http://resource.geosciml.org/classifier/cgi/contacttype/conformabl
e
> contact"
>
"contact";"http://resource.geosciml.org/classifier/cgi/contacttype/contact"
> "disconformable
>
contact";"http://resource.geosciml.org/classifier/cgi/contacttype/disconform
a
> blecontact"
> "faulted
>
contact";"http://resource.geosciml.org/classifier/cgi/contacttype/faultedcon
ta
> ct"
> "igneous intrusive
>
contact";"http://resource.geosciml.org/classifier/cgi/contacttype/igneousint
rus
> ivecontact"
> "nonconformable
>
contact";"http://resource.geosciml.org/classifier/cgi/contacttype/nonconform
> ablecontact"
> "unconformable
>
contact";"http://resource.geosciml.org/classifier/cgi/contacttype/unconforma
b
> lecontact"
> "unknown";"http://www.opengis.net/def/nil/OGC/0/unknown"
> 
> gsmlgu:CompositionPart/gsmlgu:role
> "concretions";"http://resource.geosciml.org/classifier/cgi/role/template"
> "dominant
> component";"http://resource.geosciml.org/classifier/cgi/role/template"
> "dykes";"http://resource.geosciml.org/classifier/cgi/role/template"
> "interbedded
> component";"http://resource.geosciml.org/classifier/cgi/role/template"
> "layers";"http://resource.geosciml.org/classifier/cgi/role/template"
> "major
component";"http://resource.geosciml.org/classifier/cgi/role/template"
> "sole
component";"http://resource.geosciml.org/classifier/cgi/role/template"
> 
> gsmlgu:GeologicUnit/gsmlgu:geologicUnitType
> "biostratigraphic
>
unit";"http://resource.geosciml.org/classifier/cgi/geologicunitrank/biostrat
igra
> phicunit"
> "geologic
>
unit";"http://resource.geosciml.org/classifier/cgi/geologicunitrank/geologic
unit
> "
> "lithodemic
>
unit";"http://resource.geosciml.org/classifier/cgi/geologicunitrank/lithodem
icu
> nit"
> "lithostratigraphic
>
unit";"http://resource.geosciml.org/classifier/cgi/geologicunitrank/lithostr
atigr
> aphicunit"
> 
> 
> gsmlgu:GeologicUnit/gsmlgu:rank
>
"formation";"http://resource.geosciml.org/classifier/cgi/stratigraphicrank/f
orm
> ation"
>
"lithodeme";"http://resource.geosciml.org/classifier/cgi/stratigraphicrank/l
itho
> deme"
>
"subgroup";"http://resource.geosciml.org/classifier/cgi/stratigraphicrank/su
bgr
> oup"
> 
> 
> "XML is like violence. If it doesn't solve the problem, use more." -
Unknown
> 
> 
> -------------- next part -------------- An HTML attachment was 
> scrubbed...
> URL: <http://lists.arcs.org.au/pipermail/auscope-
> geosciml/attachments/20120227/06b427af/attachment.html>
> 
> ------------------------------
> 
> _______________________________________________
> auscope-geosciml mailing list
> auscope-geosciml at lists.arcs.org.au
> http://lists.arcs.org.au/cgi-bin/mailman/listinfo/auscope-geosciml
> 
> 
> End of auscope-geosciml Digest, Vol 35, Issue 34
> ************************************************
> _______________________________________________
> auscope-geosciml mailing list
> auscope-geosciml at lists.arcs.org.au
> http://lists.arcs.org.au/cgi-bin/mailman/listinfo/auscope-geosciml



------------------------------

Message: 2
Date: Tue, 28 Feb 2012 09:35:43 +1100
From: <Oliver.Raymond at ga.gov.au>
To: <auscope-geosciml at lists.arcs.org.au>
Subject: Re: [auscope-geosciml] A Geoscience, Minerals and Petroleum
	Thesaurus [SEC=UNCLASSIFIED]
Message-ID:
	<64596720D115484A9F1C2DC2D4CB00217372C02A58 at EXCCR01.agso.gov.au>
Content-Type: text/plain; charset="utf-8"

It is one and the same.  AMF recently handed over the custodianship of it to GSWA.

Cheers,
Ollie

-----Original Message-----
From: auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope-geosciml-bounces at lists.arcs.org.au] On Behalf Of Passmore, James H.
Sent: Tuesday, February 28, 2012 2:23 AM
To: auscope-geosciml at lists.arcs.org.au
Subject: Re: [auscope-geosciml] A Geoscience, Minerals and Petroleum Thesaurus [SEC=UNCLASSIFIED]

It looks very much like the AMF based thesaurus we have at BGS

http://gempet.dmp.wa.gov.au/GemPet/Home/SelectTerm/1727

http://gempet.dmp.wa.gov.au/GemPet/Home/SelectTerm/2527



James

James Passmore
GIS and WWW Specialist
Information Systems and Infrastructure,
British Geological Survey,
http://www.bgs.ac.uk/

+44 (0)115 936 3125


> -----Original Message-----
> From: auscope-geosciml-bounces at lists.arcs.org.au [mailto:auscope- 
> geosciml-bounces at lists.arcs.org.au] On Behalf Of 
> Oliver.Raymond at ga.gov.au
> Sent: Monday, February 27, 2012 3:55 AM
> To: auscope-geosciml at lists.arcs.org.au
> Subject: [auscope-geosciml] A Geoscience, Minerals and Petroleum 
> Thesaurus [SEC=UNCLASSIFIED]
> 
> Hi all,
> 
> 
> 
> Here?s something that may interest the vocabulary enthusiasts among 
> you
> - a Geoscience, Minerals and Petroleum Thesaurus currently maintained 
> by the Geological Survey of Western Australia.  It doesn?t contain 
> concept descriptions as far as I can tell, but it is maintained as a 
> fully relational ontology of terms covering a very large number of 
> fields of pure and applied geoscience, including geology, mining, 
> metallurgy, geochemistry, geostatistics, mineral processing, materials 
> handling, mining transport, mining economics, etc, etc, etc.
> 
> 
> 
> http://gempet.dmp.wa.gov.au/GemPet 
> <http://gempet.dmp.wa.gov.au/GemPet>
> 
> 
> 
> Cheers,
> 
> Ollie
> 
> 
> 
> PS.  They haven?t used cool URI?s  ;)
> 
> 
> 
> ______________________________________________________________________
> _
> 
> 
> 
> Ollie Raymond
> 
> 
> 
> Section Leader
> 
> National Geological Maps and Data Standards Section
> <http://www.ga.gov.au/minerals/projects/current-projects/geological-
> maps-standards.html>
> 
> Geoscience Australia
> 
> 
> 
> Interoperability Working Group
> <https://www.seegrid.csiro.au/wiki/bin/view/CGIModel/InteroperabilityW
> G
> >
> 
> IUGS Commission for the Management and Application of Geoscience 
> Information
> 
> 
> 
> Address: GPO Box 378, Canberra, ACT, 2601, Australia | ABN: 80 091 799
> 039
> 
> Ph: +61 2 62499575 | Fax: +61 2 62499917 | Email:
> oliver.raymond at ga.gov.au <mailto:oliver.raymond at ga.gov.au>  | Google 
> Map 
> <http://maps.google.com/maps?f=q&hl=en&geocode=&q=canberra+australia&i
> e
> =UTF8&ll=-
> 35.344028,149.158362&spn=0.007684,0.016404&t=h&z=17&iwloc=addr&om=1>
> 
> ______________________________________________________________________
> _
> 
> 
> 
> --- This message was created with 100% recycled electrons ---
> 
> 


--
This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.

------------------------------

_______________________________________________
auscope-geosciml mailing list
auscope-geosciml at lists.arcs.org.au
http://lists.arcs.org.au/cgi-bin/mailman/listinfo/auscope-geosciml


End of auscope-geosciml Digest, Vol 35, Issue 37
************************************************



More information about the GeoSciML mailing list