Cool Tools for Easy Rich Collections Descriptions - Vocab Service API
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Australian National Data Service (ANDS)
A spotlight on the ANDS Developer Tool Box - Vocabulary Service API The Vocabulary Service API allows developers to integrate with the ANDS Vocabulary service using HTTP and a variety of data representations (including XML, JSON and RDF). This short video will give you a brief overview of the API and some of its practical use cases.
 Thanks everybody for turning up. George Ben here, business analyst in the services team. The Vocabulary Service API, this is what's sitting behind the vocabulary widget and basically it allows users to sort of interrogate the published vocabularies that we have. Again the ANZ, SSRC, FOA, the ANZ, SSRC SEO and RibCS 1.5 vocabularies. The data that can be pulled out of the vocabs themselves can be pulled back in a variety of formats. So we've got the XML, the JSON, the RDF. So that sort of is available to different developers. Again in the same way that we've used it in the widget you can use it to populate picklists and menus in data capture tools, in web pages and things like that. Users can use it to search and resolve terminologies. So they may just know the term itself and they want to look to see if it's actually a published and recognised terminology in ANZ, SSRC or other vocabularies going forward. And the vocabularies that we've published obviously have common and globally resolvable identifiers that resolve to a description of concepts. So going forward as we get more and more vocabularies people will be able to refer to them by these resolvable identifiers. So again just the address, research.at australia.ans.org.au for slash developers. The web services themselves, they're not as pretty because there's no real fancy front into them. There are little explanation diagrams for each, I think nearly all of the services that we have just showing sort of how they work. In much the same way as the widgets we have tables containing all the parameters that could be passed to the services themselves. And again developers will understand that and if they don't they can get in contact via the community forum. There's a couple in some of the services they're a little bit tricky. There's sort of some sort of FAQs or common questions about the services just to help out. And a couple of example uses of working service calls. And that's pretty much all I've got.
 Thanks everybody for turning up.  George Ben here, business analyst in the services team.  The Vocabulary Service API, this is what's sitting behind the vocabulary widget  and basically it allows users to sort of interrogate the published vocabularies that we have.  Again the ANZ, SSRC, FOA, the ANZ, SSRC SEO and RibCS 1.5 vocabularies.  The data that can be pulled out of the vocabs themselves can be pulled back in a variety  of formats. So we've got the XML, the JSON, the RDF. So that sort of is available to different  developers. Again in the same way that we've used it in the widget you can use it to populate  picklists and menus in data capture tools, in web pages and things like that.  Users can use it to search and resolve terminologies. So they may just know the term itself and they  want to look to see if it's actually a published and recognised terminology in ANZ, SSRC or other  vocabularies going forward. And the vocabularies that we've published obviously have common and  globally resolvable identifiers that resolve to a description of concepts. So going forward as we  get more and more vocabularies people will be able to refer to them by these resolvable identifiers.  So again just the address, research.at australia.ans.org.au for slash developers.  The web services themselves, they're not as pretty because there's no real fancy front into them.  There are little explanation diagrams for each, I think nearly all of the services that we have  just showing sort of how they work. In much the same way as the widgets we have tables containing  all the parameters that could be passed to the services themselves. And again developers will  understand that and if they don't they can get in contact via the community forum. There's a  couple in some of the services they're a little bit tricky. There's sort of some sort of FAQs  or common questions about the services just to help out. And a couple of example uses of working  service calls. And that's pretty much all I've got.
Vocab_Service_API_-_Cool_Tools_in_the_developers_toolbox_EbEaU5vpz5A_3_0_2267.png Vocab_Service_API_-_Cool_Tools_in_the_developers_toolbox_EbEaU5vpz5A_3_2268_3107.png Vocab_Service_API_-_Cool_Tools_in_the_developers_toolbox_EbEaU5vpz5A_3_3108_3342.png