OceanOPS Passport Book page

[pbuttigieg]

@tomlatter @MKrieger29

A placeholder issue to develop the JSON-LD/schema.org representation of the OceanOPS passport, for documentation in the ODIS Book

[tomlatter]

Hi @pbuttigieg @MKrieger29 @louatbodc , I've made some adjustments to this:

passport.json

Sorry for the size of this, I think once we agree on the core structure and classes to use, we'll be able to work on smaller subsections at a time.

• I've used Certification for the Passport root class, with its own PID seperate from platform or mission. This makes sense I think and certificationStatus will allow us to say if the passport has been approved, pending or refused.

• The passport is about an Action , the Action being an ocean observation mission. Action seems the best fit here, with result property used for the Observations DataSet, instrument for the Platform, provider for the program, potentialAction for the sensors and subjectOf for the mission's start and end operations.

• I've added the telecommunication device as a potentialAction of the platform

• And added a CreativeWork to the Passport using hasPart. It is a Log to put EventSeries for status updates history, metadata updates history and more.

The properties expressed here cover roughly half of what we would like to put in the passport, but all the main 'classes' are covered. Please let me know if this structure and my choice of classes and properties makes sense to you, and if it will work. Note that many of the identifiers have not been determined yet, we'll need to focus on that in a future step.

[pbuttigieg]

Xref https://github.com/iodepo/odis-arch/issues/68#issuecomment-2897280075

@louatbodc pinging you in relation to our drafting

[pbuttigieg]

Thanks @tomlatter this is quite clear. I think the Certification type can work well.

Does OceanOPS have an OceanExpert ID? this can help with the issuer metadata (one can use an OE identifier) and prep for its ODIS Node

[tomlatter]

Thanks @pbuttigieg , yes OceanOPS has an OceanExport ID, I can add it to the issuer like this:

"issuedBy":  {
    	"@type": "Organization",
        "name": "OceanOPS",
	"identifier": {
		"@type": "PropertyValue",
		"description": "OceanExpert ID",
		"value": "16741",
		"url": "https://oceanexpert.org/institution/16741"
	}
},