Skip to content

Add an example of ESIP Science-On-Schema markup to the data directory. #3065

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

Merged
merged 6 commits into from
Apr 6, 2023

Conversation

nein09
Copy link
Contributor

@nein09 nein09 commented Mar 11, 2022

These are examples for scientific research data sets and data repositories taken from the guide developed by the Science-On-Schema ESIP cluster.

I'm happy to try and make up HTML / RDFA / other markup for these, but this working group has been focused on JSON-LD.

@nein09
Copy link
Contributor Author

nein09 commented Mar 14, 2022

@chrisspradling1980 are you talking about this change specifically? I removed the prov elements from the json-ld markup that I am proposing with this pull request because I thought they may be outside the scope of what the schema.org maintainers would like to see in these examples.

@chrisspradling1980
Copy link

chrisspradling1980 commented Apr 10, 2022

(#3086 (comment))
I was just do the familiarities of NLP or owl programming language that is persistent inside of GitHub. I know that there are repository containers that store chronological to numeric word cabinets. if we could just eliminate terminology that may pertain to programming language as opposed to everyday usage words that may come conflict with some of the NLP understanding I think this would help scientists and the open source community.
you have to forgive me I'm not very familiar with the terms inside GitHub. I do the best that I can but I never went to school for any of this and half the time I don't know what the heck I'm doing or what I'm reading. I'm just trying to make things easier for symbolic information extractor and biomedical technology

Copy link

@chrisspradling1980 chrisspradling1980 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks fine however, if there's any way that we could get data sets to challenge the discrepancy or to find discrepancies to include challenges which would create markup to markdown work overs. then multiple data sets can be challenged for multi language discrepancies in scientific fields and also in computer science for data sets. I hope this wouldn't be too hard or too much to ask but this is important.


MICRODATA:

<!-- An online repository that hosts scientific research data. -->
TODO

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Find and define all terminology discrepancies between all compilers, programming languages, markup, mark down, data sets and computational linguistic systems containers and or libraries as repositories for owl, RTL and xbrtl file formats.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the point of this comment?

@github-actions
Copy link

This pull request is being nudged due to inactivity.

@github-actions github-actions bot added the no-pr-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Jul 13, 2022
Copy link
Contributor

@RichardWallis RichardWallis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some fixes required after validating :

First example

  1. Misspelling of 'application' in script tag
  2. Extra comma at end of description

Second example

  1. No TYPES: definition
  2. availableChannel not a valid property for Organization type

@nein09
Copy link
Contributor Author

nein09 commented Oct 5, 2022

@RichardWallis thank you! I thought I had run it through a validator but I guess I hadn't, or at least not the right one.

@RichardWallis RichardWallis merged commit a7e9c97 into schemaorg:main Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-pr-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants