Week-8-Update

During this week, we had an intensive discussion about the YesWorkflow Data Model vocabulary. Finally, we came to a conclusion that we should adopt the following predicates between Port, Data and Resource. <Port> yw:sends/yw:receives <Data> <Data> yw:wasReadFrom/yw:wasWrittenTo <Resource> To distinguish prospective and retrospective provenance, we used two different RDF Turtle Continue reading Week-8-Update

Prospective and Retrospective Provenance Queries: Week 7 – Fine-tuning YW Model & SPARQL queries

Hi all, It’s Linh Hoang, the intern from project 3 (again 🙂 ). Time flies! And we are reaching the last few weeks of the internship! This week, we mainly spent time for fine-tuning our YW Model. Some minor changes were made for naming convention purposes. Also documentations of the model including Continue reading Prospective and Retrospective Provenance Queries: Week 7 – Fine-tuning YW Model & SPARQL queries

Week-7-Update

The main task for this week is still updating the YesWorkflow Model Vocabulary and Structure, and modifying SPARQL queries for advanced questions. This is our GitHub repository including the Model Specification, RDF Turtle facts, and SPARQL queries: simulate_data_collection example 1. YesWorkflow SPARQL Queries For the SPARQL queries, the combined queries Continue reading Week-7-Update

Prospective and Retrospective Provenance Queries: Week 6 – Mapping YW & ProvONE model, explore RDF & SPARQL limitations

Hi everyone, It’s Linh Hoang, the intern from project 3. This week, along with our supervisors, my co-intern and I tried to finalize the YW model with our own vocabulary. We also created an UML diagram to represent the model. This is a good way for outsiders to conceptualize and understand Continue reading Prospective and Retrospective Provenance Queries: Week 6 – Mapping YW & ProvONE model, explore RDF & SPARQL limitations

Prospective and Retrospective Provenance Queries: Week 5 – YW Data Model & SPARQL queries (cont.)

Hello everyone, It’s Linh Hoang, the intern from project 3. This week, my co-intern and I continue to focus on revising our YesWorkflow Data Model with our own vocabulary. Besides that, we also created an UML diagram to represent components of the model and how they connects to each other. The diagram is Continue reading Prospective and Retrospective Provenance Queries: Week 5 – YW Data Model & SPARQL queries (cont.)

Week-5-Update

During the middle week of my intern, I continued working on improving the YesWorkflow Conceptual Model vocabulary and structure. As suggested by my primary mentor, I utilized Markdown format combined with HTML tags to create the model vocabulary documentation table to make it machine-readable. I also created another table for Continue reading Week-5-Update

Week-4-Update

During this week, I further improved the RDF model for YesWorkflow model facts. Especially, I introduced three self-defined associations (yw:isAssociatedWith, yw:filePath, yw:portType) and one class (yw:Data). These namespaces can help me to distinguish input ports, output ports and parameters, and to connect data with URI templates to corresponding ports. To Continue reading Week-4-Update

Prospective and Retrospective Provenance Queries: Week 4 – YesWorkflow Data Model

Hi everyone, I’m Linh Hoang, from project 3. This week, my co-intern and I focused on creating a YesWorkflow Data Model with our own vocabulary. Previously, we used ProvONE Data Model (which is an extension of the standard Provenance Data Model recommended by W3C) to represent items of YesWorkflow. However, Continue reading Prospective and Retrospective Provenance Queries: Week 4 – YesWorkflow Data Model