documento generado automáticamente
Descripción global: Esquema de agente que cumple la especificación DCAT-AP 2.1.1
versión: 1.0.1
[*] Si no hay un tipo en un atributo es porque puede tener varios tipos o diferentes formatos/patrones.
Type[string]
: Esta propiedad se refiere a un tipo de agente que pone a disposición el Catálogo o Conjunto de Datos . Model: http://www.w3.org/2004/02/skos/core#Conceptaddress[object]
: La dirección postal . Model: https://schema.org/addressaddressCountry[string]
: El país. Por ejemplo, España . Model: https://schema.org/addressCountryaddressLocality[string]
: La localidad en la que se encuentra la dirección postal, y que está en la región . Model: https://schema.org/addressLocalityaddressRegion[string]
: La región en la que se encuentra la localidad, y que está en el país . Model: https://schema.org/addressRegiondistrict[string]
: Un distrito es un tipo de división administrativa que, en algunos países, gestiona el gobierno localpostOfficeBoxNumber[string]
: El número del apartado de correos para las direcciones de apartados postales. Por ejemplo, 03578 . Model: https://schema.org/postOfficeBoxNumberpostalCode[string]
: El código postal. Por ejemplo, 24004 . Model: https://schema.org/https://schema.org/postalCodestreetAddress[string]
: La dirección . Model: https://schema.org/streetAddress
areaServed[string]
: La zona geográfica en la que se presta un servicio o se ofrece un artículo . Model: https://schema.org/Textid[*]
: Identificador único de la entidadlocation[*]
: Referencia Geojson al elemento. Puede ser Point, LineString, Polygon, MultiPoint, MultiLineString o MultiPolygon.name[array]
: Esta propiedad contiene el nombre del agente. Esta propiedad se puede repetir para diferentes versiones del nombre (por ejemplo, el nombre en diferentes idiomas) . Model: dct:descriptiontype[string]
: Tipo de entidad NGSI. Tiene que ser Agente
Propiedades requeridas
id
name
type
Adaptado de DCAT-AP versión 2.1.1. El atributo type original de DCAT 2.1.1 ha sido renombrado a Type para permitir su uso con NGSI-LD.
Ordenados alfabéticamente (pulse para más detalles)
full yaml details
Agent:
description: Agent Schema meeting DCAT-AP 2.1.1 specification
properties:
Type:
description: This property refers to a type of the agent that makes the Catalogue or Dataset available
type: string
x-ngsi:
model: "http://www.w3.org/2004/02/skos/core#Concept"
type: Property
address:
description: The mailing address
properties:
addressCountry:
description: 'The country. For example, Spain'
type: string
x-ngsi:
model: https://schema.org/addressCountry
type: Property
addressLocality:
description: 'The locality in which the street address is, and which is in the region'
type: string
x-ngsi:
model: https://schema.org/addressLocality
type: Property
addressRegion:
description: 'The region in which the locality is, and which is in the country'
type: string
x-ngsi:
model: https://schema.org/addressRegion
type: Property
district:
description: 'A district is a type of administrative division that, in some countries, is managed by the local government'
type: string
x-ngsi:
type: Property
postOfficeBoxNumber:
description: 'The post office box number for PO box addresses. For example, 03578'
type: string
x-ngsi:
model: https://schema.org/postOfficeBoxNumber
type: Property
postalCode:
description: 'The postal code. For example, 24004'
type: string
x-ngsi:
model: https://schema.org/https://schema.org/postalCode
type: Property
streetAddress:
description: The street address
type: string
x-ngsi:
model: https://schema.org/streetAddress
type: Property
streetNr:
description: Number identifying a specific property on a public street
type: string
x-ngsi:
type: Property
type: object
x-ngsi:
model: https://schema.org/address
type: Property
areaServed:
description: The geographic area where a service or offered item is provided
type: string
x-ngsi:
model: https://schema.org/Text
type: Property
id:
anyOf:
- description: Identifier format of any NGSI entity
maxLength: 256
minLength: 1
pattern: ^[\w\-\.\{\}\$\+\*\[\]`|~^@!,:\\]+$
type: string
x-ngsi:
type: Property
- description: Identifier format of any NGSI entity
format: uri
type: string
x-ngsi:
type: Property
description: Unique identifier of the entity
x-ngsi:
type: Property
location:
description: 'Geojson reference to the item. It can be Point, LineString, Polygon, MultiPoint, MultiLineString or MultiPolygon'
oneOf:
- description: Geojson reference to the item. Point
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
type: number
minItems: 2
type: array
type:
enum:
- Point
type: string
required:
- type
- coordinates
title: GeoJSON Point
type: object
x-ngsi:
type: GeoProperty
- description: Geojson reference to the item. LineString
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
items:
type: number
minItems: 2
type: array
minItems: 2
type: array
type:
enum:
- LineString
type: string
required:
- type
- coordinates
title: GeoJSON LineString
type: object
x-ngsi:
type: GeoProperty
- description: Geojson reference to the item. Polygon
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
items:
items:
type: number
minItems: 2
type: array
minItems: 4
type: array
type: array
type:
enum:
- Polygon
type: string
required:
- type
- coordinates
title: GeoJSON Polygon
type: object
x-ngsi:
type: GeoProperty
- description: Geojson reference to the item. MultiPoint
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
items:
type: number
minItems: 2
type: array
type: array
type:
enum:
- MultiPoint
type: string
required:
- type
- coordinates
title: GeoJSON MultiPoint
type: object
x-ngsi:
type: GeoProperty
- description: Geojson reference to the item. MultiLineString
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
items:
items:
type: number
minItems: 2
type: array
minItems: 2
type: array
type: array
type:
enum:
- MultiLineString
type: string
required:
- type
- coordinates
title: GeoJSON MultiLineString
type: object
x-ngsi:
type: GeoProperty
- description: Geojson reference to the item. MultiLineString
properties:
bbox:
items:
type: number
minItems: 4
type: array
coordinates:
items:
items:
items:
items:
type: number
minItems: 2
type: array
minItems: 4
type: array
type: array
type: array
type:
enum:
- MultiPolygon
type: string
required:
- type
- coordinates
title: GeoJSON MultiPolygon
type: object
x-ngsi:
type: GeoProperty
x-ngsi:
type: GeoProperty
name:
description: This property contains a name of the agent. This property can be repeated for different versions of the name (e.g. the name in different languages)
items:
description: Every name in different languages
minItems: 1
type: string
x-ngsi:
type: Property
type: array
x-ngsi:
model: dct:description
type: Property
type:
description: NGSI Entity type. It has to be Agent
enum:
- Agent
type: string
x-ngsi:
type: Property
required:
- id
- type
- name
type: object
x-derived-from: ""
x-disclaimer: 'Redistribution and use in source and binary forms, with or without modification, are permitted provided that the license conditions are met. Copyleft (c) 2022 Contributors to Smart Data Models Program'
x-license-url: https://github.com/smart-data-models/dataModel.DCAT-AP/blob/master/Agent/LICENSE.md
x-model-schema: https://smart-data-models.github.io/dataModel.DCAT-AP/Agent/schema.json
x-model-tags: ""
x-version: 1.0.1
Aquí hay un ejemplo de un Agente en formato JSON-LD como key-values. Esto es compatible con NGSI-v2 cuando se utiliza options=keyValues
y devuelve los datos de contexto de una entidad individual.
show/hide example
{
"id": "urn:ngsi-ld:id:ZLHO:07918336",
"type": "Agent",
"name": [
"Agent 10",
"Agente 10"
],
"location": {
"type": "Point",
"coordinates": [
12.934074,
-149.532943
]
},
"address": {
"streetAddress": "2 Rue Mercier",
"addressLocality": "Luxembourg",
"addressRegion": "Luxembourg",
"addressCountry": "Luxembourg",
"postalCode": "2985 ",
"postOfficeBoxNumber": "",
"areaServed": "European Union"
},
"Type": "EU Publications office"
}
Aquí hay un ejemplo de un Agente en formato JSON-LD normalizado. Esto es compatible con NGSI-v2 cuando no se utilizan opciones y devuelve los datos de contexto de una entidad individual.
show/hide example
{
"id": "urn:ngsi-ld:id:ZLHO:07918336",
"type": "Agent",
"location": {
"type": "geo:json",
"value": {
"type": "Point",
"coordinates": [
12.934074,
-149.532943
]
}
},
"address": {
"type": "StructuredValue",
"value": {
"streetAddress": "2 Rue Mercier",
"addressLocality": "Luxembourg",
"addressRegion": "Luxembourg",
"addressCountry": "Luxembourg",
"postalCode": "2985 ",
"postOfficeBoxNumber": "",
"areaServed": "European Union"
}
},
"name": {
"type": "StructuredValue",
"value": [
"Agent 10",
"Agente 10"
]
},
"Type": {
"type": "Text",
"value": "EU Publications office"
}
}
Aquí hay un ejemplo de un Agente en formato JSON-LD como key-values. Esto es compatible con NGSI-LD cuando se utiliza options=keyValues
y devuelve los datos de contexto de una entidad individual.
show/hide example
{
"id": "urn:ngsi-ld:id:ZLHO:07918336",
"type": "Agent",
"address": {
"streetAddress": "2 Rue Mercier",
"addressLocality": "Luxembourg",
"addressRegion": "Luxembourg",
"addressCountry": "Luxembourg",
"postalCode": "2985 ",
"postOfficeBoxNumber": "",
"areaServed": "European Union"
},
"name": [
"Agent 10",
"Agente 10"
],
"Type": "EU Publications office",
"description": "organization the Agent 10 belongs to.",
"location": {
"type": "Point",
"coordinates": [
12.934074,
-149.532943
]
},
"@context": [
"https://raw.githubusercontent.com/smart-data-models/dataModel.DCAT-AP/master/context.jsonld"
]
}
Este es un ejemplo de un Agente en formato JSON-LD normalizado. Esto es compatible con NGSI-LD cuando no se utilizan opciones y devuelve los datos de contexto de una entidad individual.
show/hide example
{
"id": "urn:ngsi-ld:id:ZLHO:07918336",
"type": "Agent",
"address": {
"type": "Property",
"value": {
"streetAddress": "2 Rue Mercier",
"addressLocality": "Luxembourg",
"addressRegion": "Luxembourg",
"addressCountry": "Luxembourg",
"postalCode": "2985 ",
"postOfficeBoxNumber": "",
"areaServed": "European Union"
}
},
"name": {
"type": "Property",
"value": [
"Agent 10",
"Agente 10"
]
},
"Type": {
"type": "Property",
"value": "EU Publications office"
},
"location": {
"type": "GeoProperty",
"value": {
"type": "Point",
"coordinates": [
12.934074,
-149.532943
]
}
},
"@context": [
"https://raw.githubusercontent.com/smart-data-models/dataModel.DCAT-AP/master/context.jsonld"
]
}
Consulte FAQ 10 para obtener una respuesta sobre cómo tratar las unidades de magnitud.