RPID Meeting Agenda Items

  • Examples
  • Puppetizing
  • Prefixes
  • Karst Node
  • Web Content
  • UAG

RPID Meeting Minutes

Examples

Larry created a strawman. Try some examples to actual cases to see how this would work. Two issues: 1. complexity - worked but was complicated 2. Need several instances to create a interesting (usable) environement

It is easy to confuse DTrecord with this PID kernel strawman. Two metadata schemes that dont fit together. Deal with Typed values. 16 types in strawman. To use these types they need to be documented and described in an understandable way to be used. Need records to apply these to. * Bridget will do this for a few types of data. * Robert will try with VMs on Jetstream. * Gabriele will try with Rice genomic data. * Isuru has tried this with SEED data, will discuss issues encountered on next call. * When publishing wanted to do per/day per/device in kernal. Could not fit device ID, nothing matched with strawman. At the next call we will do some comparisons to see where issues were encountered. Given this identifier, what can I do next? Filtering notion takes presedence. What are the purposes of the handle service? Low-level services, not querying directly but infrastructure. Handle service only does one this returns a handle record.

Puppetizing

Bridget had her first discussion. Description of what we're trying to do. Rob will review this consultation and we'll talk about it more before next meeting. Can be published to the DTR working group at RDA.

Karst Node

Experimental environment July before installation will be possible AWS instances will not be persistent only for experimentation We will keep a dev-instance along with prime instance

Prefixes

Use of prefixes with respect to test prefixes Clearly indicated prefixes are test prifixes Two constraints 1. the relation to prefix to handle service is 1:1 2. relationship of handles services to prifixes is 1:many 3. as long as no one mistakes these for longterm PIDs it is inconsequential Prefix with no or 1 delimiter are global while sub-prifixes with prifixes 2+ from individual service. Creating policy statement regarding prefixes.

Bridget, Rob and Isuru will send slides.