Date post: | 18-Jan-2016 |
Category: |
Documents |
Upload: | norma-cameron |
View: | 216 times |
Download: | 0 times |
CDASH TO RDF
31 May 2013
PhUSE Emerging TechnologiesSemantic Technologies WG
Agenda
• Introductions
• Goals (Frederik)
• CDASH – An Overview (Rhonda, Gary)
• Source Control (Geoff)
Project Goals
• Model and Publish CDASH 1.1 in RDF• Scoping:
– What needs to be included into the CDASH RDF Model?– Other models: (Ex: BRIDG)
CDASH – AN OVERVIEW
SOURCE CONTROL
• Source control gives you security– Ability to rewind – Who did what, when?
• High level concepts– Repository – a source controlled location (eg folder)– Commit – writing a version to the repository– Tag – collecting certain versions of all files under a
symbolic name– Branch – Split of repository for development in parallel– Merge – coercing the versions of one branch into
another
A BRANCHING MODEL
LOCAL AND REMOTE
• You can maintain a repository under source control in two ways– Clone or copy a source controlled repository from a remote
location to your machine (get the source + history)– Initialize a local project with source control
• When you clone a remote repository, you need to commit your changes to the remote so others can see it (a push)– They can merge your changes into their local copy (a pull)
BRANCHING
• In general, you branch to add something new– Example: Addition of new domain– Branch for new domain, e.g. feature/domain_vs– Commit changes to branch– Push branch to remote– Reviewer reviews changes, makes comments– Developer replies to comments, makes changes,
resubmits– Reviewer merges branch into development branch
DEVELOPMENT PROCESS
• Following Frederik’s example– Develop a cdash-1-1-schema.rdf document (Top
Braid/Protégé)• Review by Team• Feed any meta-model-schema changes/proposals back to
Steering committee for approval (coordinate semantics across the groups)
– Suggest the schema is developed collaboratively• Process the CDASH specifications looking for ‘predicates’• Edit the schema in the teleconferences
CONTENT DEVELOPMENT
• Development of Content (cdash-1-1.rdf)–Create a spreadsheet with column headers
matching the predicates (Excel/Google Docs)–Populate the spreadsheet (Excel/Google
Docs)–Convert the spreadsheet to RDF (Top Braid) cdash-1-1.rdf
–Commit to repository on branch–Review
DEVELOPMENT - Logistics
• Logistically (Content)–Don’t want multiple versions of spreadsheets
floating about–Want people to be able to modify in parallel–Google Docs?–Spreadsheet in Source Control?
NEXT STEPS
• Read the CDASH Specification
• Review the CDASH Excel Spread sheet against the Standard Document
• Collate all the semantic terms that we might want to model