Comments (7)
from dm-usecases.
gilleslandais wrote:
In DatasetDM, I didn't see a clear distinction between creator/author .. Markus do you have an example of this serialization in your output?
msdemlei wrote:
No. But now that you mention it, what might actually be smart is sync VOResource's "implicit" (there's no VO-DML (yet?)) data model with Dataset dm and friends. I'm not 100% sure I'd like to see a lot of VOResource in instance documents (as usual: What should clients do with it?), and we'd have to think about whether there ought to be a single "resource" DM or whether some of the types could become DMs of their own. But whatever the result of these considerations: if DM deals with Registry content, we should make sure there are no unnecessary inconsistencies.
The DatasetDM does map its content to the Resource Metadata elements.. so is in a sense, actualizing the 'implicit' model, and is VO-DML compliant.
As for creator/author.. what distinction are you looking for?
- dm:Creator == entity responsible for the creation of the Dataset (under DataID)
- dm:Contributor == other entities involved in the creation of the Dataset (under DataID)
- dm:Publisher == entity making the Dataset available (under Curation)
I think 'author' implies the Dataset is a paper or some sort, rather than a Photometric Filter or LightCurve.
I've also been curious to see how Provenance will get conveyed in the context of Datasets.
In the older models (Spectrum, Characterization, ObsCore) there is, if I recall, a Provenance placeholder node in the Observation/Dataset metadata area. I expect there is a distinction between identifying the Agents/Entities involved in THIS dataset (part of DatasetMetadata), vs identifying the HISTORY of the Dataset ( Activity which created it, progenitors, etc ).
I would like to add an other concise provenance output in the VOTable (for "naive" client)
Do you mean outside of the Annotation syntax? similar to a COOSYS/TIMESYS element directly in VOTable.
from dm-usecases.
Ok for the datasetDM - in VizieR context, CDS is the publisher (Curator) and the author is the Creator (including the biblio reference in the same DataID) - so it could be added in AssocDataDock.
But you are true , a including (refCode, author, year) is something that I prefer !
For measures it is may be more complicate -
In vizier the photometry filter characteristics is not a part of the original data (it could - but often it is added by CDS who assigned a filter or a similar filter for magnitude columns) - if VizieR provides the photometry characteristics, it is important to specify the origin. ProvDM is adapted for that, but the parsing is may be a little discouraging for clients..
So may be a simple way could be just a comment ?.. in that case is it better to put the (origin) comment on Mango:Parameter.comment or on Mango:stcextend.Photometry ?
from dm-usecases.
from dm-usecases.
If the purpose of the embedded Prov is just to say whether a filter has been added by the CDS, we could consider doing things in a simpler way.
As PhotFilter still has to be wrapped into MANGO, we can add a field telling the filter origin. This is somehow similar to the reduction status Mango had at the beginning (raw, calibrated..). This value could be carried either by an enum or a vocabulary.
from dm-usecases.
from dm-usecases.
from dm-usecases.
Related Issues (19)
- Linking Uses cases to astronomical projects HOT 1
- Native Frame case: example file mixup in GLON|GLAT spec HOT 1
- Column Groups: Question on coordinate systems involved HOT 5
- Proper motions: modeling HOT 7
- What is that dependant axes HOT 52
- Using UCD in models HOT 16
- MANGO Annotation Scope HOT 20
- 4xmm_lite.xml is invalid HOT 4
- VODML Mapping vs ModelInstanceInVot HOT 27
- Impact on the model change HOT 33
- update of the contribution table HOT 1
- Where to put this example? HOT 1
- Baseline use cases HOT 38
- MANGO model HOT 5
- Role of the roles HOT 7
- MeasCoords enhancement
- Have human-readable labels on instances that may need UI choices HOT 1
- Using intergrated models HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dm-usecases.