diff --git a/guides/DataRepository.md b/guides/DataRepository.md index b47d55d..eac3908 100644 --- a/guides/DataRepository.md +++ b/guides/DataRepository.md @@ -15,13 +15,11 @@ [![Repository - Overview](/assets/diagrams/repository/repository-overview.svg "Repository - Overview")](#) -In schema.org, we model a repository as both an [schema:ResearchProject](https://schema.org/ResearchProject), a sub-class of an Organization, and a [schema:Service](https://schema.org/Service). This double-typing gives us the most flexibility in describing the characteristics of the organization providing the service and the services offered by the organization. +In schema.org, we model a repository as both an [schema:ResearchProject](https://schema.org/ResearchProject), a sub-class of an Organization, and a [schema:Service](https://schema.org/Service). This double-typing gives us the most flexibility in describing the characteristics of the organization providing the service and the services offered by the organization.
{ - "@context": { - "@vocab": "https://schema.org/" - }, + "@context": "https://schema.org/", "@type": ["Service", "ResearchProject"], "legalName": "Sample Data Repository Office", "name": "SDRO" @@ -44,9 +42,7 @@ The other fields you can use to describe the Organziation and the Service are:{ - "@context": { - "@vocab": "https://schema.org/" - }, + "@context": "https://schema.org/", "@type": ["Service", "ResearchProject"], "legalName": "Sample Data Repository Office", "name": "SDRO", @@ -69,9 +65,7 @@ The other fields you can use to describe the Organziation and the Service are: If you are using the "@id" attribute for your Repository, and the provider of the repository's services is the same Organziation, you can specify the [schema:provider](https://schema.org/provider) of the [schema:Service](https://schema.org/Service) in this way:{ - "@context": { - "@vocab": "https://schema.org/" - }, + "@context": "https://schema.org/", "@type": ["Service", "ResearchProject"], "@id": "https://www.sample-data-repository.org", "legalName": "Sample Data Repository Office", @@ -92,9 +86,7 @@ However, if your repository has a situation where multiple organizations act as{ - "@context": { - "@vocab": "https://schema.org/" - }, + "@context": "https://schema.org/", "@type": ["Service", "ResearchProject"], "legalName": "Sample Data Repository Office", "name": "SDRO", @@ -125,9 +117,7 @@ Adding additional fields of [schema:ResearchProject](https://schema.org/Research{ - "@context": { - "@vocab": "https://schema.org/" - }, + "@context": "https://schema.org/", "@type": ["Service", "ResearchProject"], "legalName": "Sample Data Repository Office", "name": "SDRO", @@ -167,9 +157,7 @@ If this ResearchProject, or Organization, has a parent entity such as a college,{ - "@context": { - "@vocab": "https://schema.org/" - }, + "@context": "https://schema.org/", "@type": ["Service", "ResearchProject"], "legalName": "Sample Data Repository Office", "name": "SDRO", @@ -212,9 +200,7 @@ Some organizations may have a persistent identifier (DOI) assigned to their orga{ - "@context": { - "@vocab": "https://schema.org/" - }, + "@context": "https://schema.org/", "@type": ["Service", "ResearchProject"], "legalName": "Sample Data Repository Office", "name": "SDRO", @@ -249,9 +235,7 @@ To describe the funding source of a repository, you use the [schema:funder](http{ - "@context": { - "@vocab": "https://schema.org/" - }, + "@context": "https://schema.org/", "@type": ["Service", "ResearchProject"], "legalName": "Sample Data Repository Office", "name": "SDRO", @@ -333,9 +317,7 @@ For repositories might offer services for accessing data as opposed to directly{ - "@context": { - "@vocab": "https://schema.org/" - }, + "@context": "https://schema.org/", "@type": ["Service", "ResearchProject"], "legalName": "Sample Data Repository Office", "name": "SDRO", @@ -377,9 +359,7 @@ If your repository has a concept of a data collection, some grouping of a number{ - "@context": { - "@vocab": "https://schema.org/" - }, + "@context": "https://schema.org/", "@type": ["Service", "ResearchProject"], "legalName": "Sample Data Repository Office", "name": "SDRO", @@ -427,11 +407,13 @@ The SWEET ontology defines a number of science disciplines and a repository coul{ - "@context": { - "@vocab": "https://schema.org/", - "sweet-rel": "http://sweetontology.net/rela/", - "sweet-kd": "http://sweetontology.net/humanKnowledgeDomain/" - }, + "@context": [ + "https://schema.org/", + { + "sweet-rel": "http://sweetontology.net/rela/", + "sweet-kd": "http://sweetontology.net/humanKnowledgeDomain/" + } + ], "@type": ["Service", "ResearchProject"], "legalName": "Sample Data Repository Office", "name": "SDRO",