View unanswered posts | View active topics It is currently Thu Feb 21, 2019 12:48 pm

All times are UTC + 10 hours [ DST ]




Reply to topic  [ 1 post ] 
Transformation of identifiers as URLs 
Author Message
ANDS Staff
User avatar

Joined: Thu Feb 10, 2011 11:18 am
Posts: 76
Suggested schema change
All identifier values that can have a URL form (for example, handles, DOIs, purls) should be supplied, stored, displayed and exported in that format to support linked data and semantic web initiatives.
Alternatively, as a fallback position, identifiers can continue to be provided in any format but ANDS should display them as URLs in Research Data Australia if they are of the appropriate type (some identifiers may not have URL forms). This option would not require a schema change.

Problem this suggestion addresses
Identifiers such as handles, Digital Object Identifiers and purls can be provided either as strings containing the identifier component only, or as resolvable URLs. RIF-CS schema and ANDS guidelines do not address this issue consistently across all elements and in many cases the URL form is not provided or displayed in Research Data Australia.
URLs are preferable where available, both to facilitate navigation by users and to support linked data developments.
Also for discussion: what are the priorities and time frames for support of linked data? How many ANDS partners have a linked data solution underway or planned? What would be involved in supporting linked data?

Identified by
Discussion on ANDS partners email list

RIF-CS schema components affected
Key element, identifier element, location element (electronic address), citationInfo element, relatedInfo element (see example diagram below).

Impact on content providers
Dependent on implementation approach.

Pros

URLs will support linked data and semantic web uses and allow user navigation.
Resolvable URLs support the discovery function of Research Data Australia and the concept of the navigable mesh of information.

Cons
Longer strings of metadata

Technical options
Keys should not be provided as URLs even if they are handles, purls or other persistent identifiers
The current rif-cs xml schema currently supports the ability to store, display and export identifier values that have a URL form.
No schema changes would be required to implement this suggested change.
Changes would need to be made in how identifier values that have a URL form are displayed in RDA. Determining the type of the identifier value and forming the required full resolvable address (if it has not already been supplied) would do this.


Tue Jun 28, 2011 12:26 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 1 post ] 

All times are UTC + 10 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software for PTF.