|
This is version 26.
It is not the current version, and thus it cannot be edited.
[Back to current version]
[Restore this version]
- Updates: Overview and Progress
- General Discussion
- Current issues
- New ideas
- Priorities
- Goals (Short-term, 6-month, 1 year)
- Bertram high-level
- requirements:
- semantic (in addition to structural) annotation of:
- services (actor) and
- datasets
- for ... discovery, WF design, ...
- prerequisites: what does this annotation langauge have?
- structural types
- array of float; list of record of (int, float, string); etc.
- e.g., relational schema type, ptolemy type
- applies both to data and "functions" (actors)
- essentially, useful for plumbing -- the level of the programmer, or data provider
- semantic type
- formal expression referencing concepts in an ontology
- to provide a high-level, conceptual of data and services
- data(set)
- informal descriptions: eml style metadata, keywords, controlled vocabularly
- formal description
- dataset ~ concept
- attribute (column) ~ concept
- fine-grained:
- query(X1, X2, ..., Xn) ~ concept expression(X1, ..., Xn)
- Xi are "tags" or variables point to substructure
- actors (services)
- overall function
- input/output signature (-> reuse framework from dataset annotation)
- Questions
- How do you require that certain things must be registered, e.g., that a lat lon point has an x and y coord
- How do you handle null values in a table ... e.g., a row doesn't have an x value
- What is the difference between an annotation langauge and a description logic
-
Back to the Annual meeting agenda
|
