Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

targeted examples of semantic annotation #314

Closed
mobb opened this issue Oct 8, 2018 · 9 comments
Closed

targeted examples of semantic annotation #314

mobb opened this issue Oct 8, 2018 · 9 comments
Assignees
Milestone

Comments

@mobb
Copy link
Contributor

mobb commented Oct 8, 2018

LTER IMC asked for 2 kinds of examples that include annotations to recommended vocabularies.

  • complete (EML record, as completely annotated as possible)
  • XML fragments (easy to include in docs and BPs)
@amoeba
Copy link
Contributor

amoeba commented Oct 8, 2018

Hey @mobb I saw the needs-review label on this so I thought I'd hop in.

By annotations, I assume you mean semantic annotation ala EML 2.2? What would a complete / completely annotated record look like? Or do you just mean a complete/valid EML doc? Either way, I think having a full EML 2.2 record as well as fragments is a great idea.

Folks have been working hard on carbon cycling / ECSO annotations so those'd be easy to get examples from. Though we generally stick to ecological examples with EML, I wonder if this wouldn't be a bad place to push EML a bit beyond ecology and have some geographic annotation examples (e.g. GAZ), or maybe look at how we'd annotate something from BCO-DMO (cruises, instruments, etc.).

@mobb
Copy link
Contributor Author

mobb commented Oct 9, 2018

thanks @amoeba. this was a hot topic at the LTER meeting last week; the sites are gung-ho. but need some recommendations and examples.
Probably ECSO (complete measurements) are a good start at the attrib level, but the other locations need to be shown pretty quickly too (dataset-level, entity-level), which would most likely ref different vocabs. There was a lot of talk about keywords (and that dataset-level annotations could supplant keywords) -- eg, do we need both? Probably we will want to phase this in, and outline a bunch of sub-tasks.

@amoeba
Copy link
Contributor

amoeba commented Oct 9, 2018

Dataset-level annotations do kind of amount to dataset-level keywords, huh? Except more formal which is cool. We probably want to make it really clear for people when to do one or the other, or when to mix-and-match.

Are you planning on taking a first attempt at this?

@mobb
Copy link
Contributor Author

mobb commented Oct 9, 2018

I think task 1 is to figure out the characteristics of a "reliable vocabulary". then use those to come up with a list of candidate vocabs. EML-based repos will have to figure out how to deal with each one of these.

@mbjones
Copy link
Member

mbjones commented Nov 21, 2018

TODO:

  • clean up examples, and add a MeasurementType example in eml-sample.xml
  • decide whether to eliminate eml-semantics.xml, or expand it

@stevenchong
Copy link
Contributor

I can add in a MeasurementType example to the eml-sample.xml doc

@stevenchong stevenchong self-assigned this Nov 28, 2018
@mbjones mbjones added this to the EML2.2.0 milestone Apr 16, 2019
@mbjones
Copy link
Member

mbjones commented Aug 18, 2019

@stevenchong @mobb Are these examples now complete in the primer document?

@stevenchong
Copy link
Contributor

stevenchong commented Aug 18, 2019 via email

@mbjones
Copy link
Member

mbjones commented Aug 18, 2019

Great, thanks. Then I am closing this issue. But I'm leaving #320 open for final review (I think I saw a few notes to self in there still).

@mbjones mbjones closed this as completed Aug 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants