myGrid information model

1
myGrid information model

• myGrid information model team
• Chris W, Jun, Justin, Mark, Nedim, Nick, Peter L,
  Savas, Tom
• 27 Nov 2003

2
Agenda

• Introduction (Nick)
• Modelling e-Science (Peter)
• Workflow (Justin)
• DQP (Nedim)
• Service Description (Chris)
• Provenance (Mark)
• Practical Issues (Chris)
• Discussion

3
myGrid Information ModelIntroduction

• Nick Sharman
• 27 Nov 2003

4
Outline

• Model representation
• High-level organization
• Users, Groups Roles
• Collections
• Outstanding Issues

5
Model representation

• Principally as XML Schema types
• Emerging UML class diagram
• RDF Schema?
• Application-specific knowledge/metadata
• myGrid provenance?
• All myGrid attributes??

6
High-level organization
7
Use of LSID

• All resources are identified by LSIDs
• URIs are LSIDs valid RDF subjects
• Format
• URNLSIDauthoritynamespaceobjectrevision
• Authorities allocate LSIDs
• Resolvers map LSIDs to data or metadata
• Resolvers need not support both
• Data, if available, is fixed everywhere forever
• Metadata can vary between resolvers over time

8
LSID issues

• Do we need shared LSID allocation services?
• Can we support our own resolvers for public
  databases?
• Annotation service

9
Users, Groups Roles

• User identification needed
• Provenance
• Access control
• Both imply need for authentication
• Users work in groups in different roles
• Roles represent sets of access rights

10
Users, Groups and Roles
11
Collections
12
Outstanding issues

• LSID problems opportunities
• Port types
• Serialization of recursive data
• XML vs. RDF
• Modelling notifications
• Low-level transport vs. role in myGrid