Skip to content
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

Extend schemas for Dataset and DataService from 2.1.1 to 3.0.0 #9

Open
wants to merge 35 commits into
base: master
Choose a base branch
from

Conversation

flopezag
Copy link
Contributor

  • Aligned to 3.0.0
  • Correct some issues with the specification of DCAT-AP to transform links to Relationship
  • Fix the license values available
  • Update notes.yaml and README.md

Copy link
Contributor

@albertoabellagarcia albertoabellagarcia left a comment

Choose a reason for hiding this comment

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

Feernando. please check the comments sent internally

@bobeal
Copy link

bobeal commented Oct 23, 2024

Hi,

What's the status of this PR? May I help in some way (since I'm working on this with @flopezag in the WATERVERSE project)?

Copy link
Contributor

@albertoabellagarcia albertoabellagarcia left a comment

Choose a reason for hiding this comment

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

Please attend the changes requested and pass the validator

]
}
"accessRights": {
"type": "Property",
Copy link
Contributor

Choose a reason for hiding this comment

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

example-normalized.json is the NGSIv2 normalized, therefore this payload is wrong. Why change the good one?

"type": "Property",
"value": [
{
"type": "ContactPoint",
Copy link
Contributor

Choose a reason for hiding this comment

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

I doubt that this is right.

Copy link

Choose a reason for hiding this comment

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

in NGSI-LD, a value can be a JSON array, so this will work. But it would be better represented using a JsonProperty instead of a Property.

Copy link
Contributor

Choose a reason for hiding this comment

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

ok, I have to implement this jsonProperty in the testing process as well

notesFooter:
# CHANGELOG DCAT-AP <img align="right" src="/semic-icon-small.png" alt="SEMIC Core Vocabulary" />
Copy link
Contributor

Choose a reason for hiding this comment

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

comments are not allowed

"description": "Property. Model:'http://www.w3.org/ns/dcat#contactPoint'. Contact information that can be used for sending comments about the Data Service. Cardinality: 0..n.",
"items": {
"type": "object",
"description": "Property. Model:'https://www.w3.org/ns/dcat#contactPoint'. Relevant contact information for the cataloged resource. Use of vCard is recommended (https://www.w3.org/TR/vcard-rdf/#d4e1819)."
Copy link
Contributor

Choose a reason for hiding this comment

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

Where are the properties of this object defined?

Copy link
Contributor

Choose a reason for hiding this comment

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

"properties": {
"email": {
"type": "string",
"description": "Property. To specify the electronic mail address for communication with the object the vCard represents"
"format": "email"
}
}}

],
"accrualPeriodicity": "weekly",
"geolocation": "True",
Copy link
Contributor

Choose a reason for hiding this comment

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

Boolean?


notesMiddle:

notesFooter:
# CHANGELOG DCAT-AP <img align="right" src="/semic-icon-small.png" alt="SEMIC Core Vocabulary" />
Copy link
Contributor

Choose a reason for hiding this comment

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

not allowed comments of this type

"geolocation": {
"type": "string",
"description": "Property. Model:'https://schema.org/Boolean'. Defines if the data stream has geolocation (coordinates) in any of its attributes.",
"enum": ["True", "False"]
Copy link
Contributor

Choose a reason for hiding this comment

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

These are strings not booleans

"type": "Property",
"value": [
{
"type": "ContactPoint",
Copy link

Choose a reason for hiding this comment

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

in NGSI-LD, a value can be a JSON array, so this will work. But it would be better represented using a JsonProperty instead of a Property.

"value": "https://raw.githubusercontent.com/smart-data-models/dataModel.DCAT-AP/refs/heads/master/DataService/schema.json"
},
"@context": [
"https://raw.githubusercontent.com/smart-data-models/dataModel.DCAT-AP/master/context.jsonld"
Copy link

Choose a reason for hiding this comment

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

better use https://smart-data-models.github.io/dataModel.DCAT-AP/context.jsonld (files served from raw.githubusercontent.com have a text/plain content type, which is invalid as per the JSON-LD specification)

Copy link
Contributor

Choose a reason for hiding this comment

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

ok, no problem

"type": "Property",
"value": "two years"
"value": "True"
},
"hasVersion": {
"type": "Property",
Copy link

Choose a reason for hiding this comment

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

Relationship since it seems to target entities?

"",
""
"urn:ngsi-ld:Dataset:id:ASDF:68185655",
"urn:ngsi-ld:Dataset:id:ASDF:78185655"
]
},
"identifier": {
"type": "Property",
Copy link

Choose a reason for hiding this comment

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

Relationship since it seems to target entities?

"qualifiedAttribution": {
"type": "Property",
"value": [
""
"Central born manage evidence data. Answer doctor visit ready physical fact. Quite allow however certain lose heart.",
"Home interesting range ever. Magazine the instead particularly. Late have collection."
]
},
"qualifiedRelation": {
"type": "Property",
Copy link

Choose a reason for hiding this comment

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

Relationship since it seems to target entities?

"fi": "Euroopan avoimen datan portaalin tietopalvelu"
}
},
"validationSchema": "https://raw.githubusercontent.com/smart-data-models/dataModel.DCAT-AP/refs/heads/master/DataService/schema.json",
"@context": [
Copy link
Contributor

Choose a reason for hiding this comment

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

better use https://smart-data-models.github.io/dataModel.DCAT-AP/context.jsonld (files served from raw.githubusercontent.com have a text/plain content type, which is invalid as per the JSON-LD specification)

Copy link
Contributor

@albertoabellagarcia albertoabellagarcia left a comment

Choose a reason for hiding this comment

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

I have sent you the comment directly there are a couple of issues on both data models dataservice and dataservicerun

Copy link
Contributor

@albertoabellagarcia albertoabellagarcia left a comment

Choose a reason for hiding this comment

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

Now we have to test if our testing process can deal with languageproperties

@flopezag
Copy link
Contributor Author

Now we have to test if our testing process can deal with languageproperties

I suggest checking it in the new service deployed on fair-services.lab.fiware.org for DataService and Dataset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants