cdash to rdf 31 may 2013 phuse emerging technologies semantic technologies wg

12
CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

Upload: norma-cameron

Post on 18-Jan-2016

218 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

CDASH TO RDF

31 May 2013

PhUSE Emerging TechnologiesSemantic Technologies WG

Page 2: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

Agenda

• Introductions

• Goals (Frederik)

• CDASH – An Overview (Rhonda, Gary)

• Source Control (Geoff)

Page 3: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

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)

Page 4: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

CDASH – AN OVERVIEW

Page 5: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

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

Page 6: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

A BRANCHING MODEL

Page 7: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

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)

Page 8: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

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

Page 9: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

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

Page 10: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

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

Page 11: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

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?

Page 12: CDASH TO RDF 31 May 2013 PhUSE Emerging Technologies Semantic Technologies WG

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