huberrob

@rebeccaringuette , this is exactly the use case [PIDINST](https://www.rd-alliance.org/groups/persistent-identification-instruments-wg/members/all-members/) are designed for and we would like to see a possible solution on how to expose this information using schema.org

> ``` > { > "@context": { > "@vocab": "https://schema.org/", > }, > "@id": "https://doi.org/10.concept/doi", > "@type": "Dataset", > .... > "measurementTechnique": [ > {"@type": "DefinedTerm", > "identifier": "spase://SMWG/Instrument/MMS/4/FIELDS/FGM", >...

> schema:instrument If we could use schema:instrument this would be great but this would require to create a _sdo:Action_ (e.g. _sdo:CreateAction_) which then refers to the dataset created via _sdo:result_...

@rebeccaringuette I would rather expect this is in a DCAT graph. I fear in a schema.org graph the prov:wasGeneratedBy should not be used unless your instance of a schema:Dataset is...

Just a quick first comment: only the https://raw.githubusercontent.com style URLs are pointing to JSON content, URLs without the 'raw' subdomain are delivering HTML content in which JSON is displayed in...

True, at least F-UJI would follow the describedby links to locate the metadata.

Maybe you could replace the **fileFormat** values with correct mime types? Not sure how this is handles in RO-Ctate namespace butaAs far as I know fileFormat is replaced in schema.org...

OK sounds great, it should be no problem to pack several Datasets in one ro-crate, but F-UJI will evaluate the root(the crate which is of type CreativeWork) not each individual...

Just a quick note that part of the JSO-LD confusion happened on Github hosted JSON-LD/ro-crate pages which actually do deliver the JSON via the raw.githubusercontent.com URL see: #542 https://raw.githubusercontent.com/arms-mbon/data_release_001/main/ro-crate-metadata.json vs...

Dear Katrina, I think the main problem is that the 848 XML is a EML variant from GBIF and is including some metadata within GBIF specific fields. This part starts...