Giter Site home page Giter Site logo

Comments (3)

peterlubrich avatar peterlubrich commented on June 25, 2024

Regarding "I do no understand...":
We will refine the usage note as follows:
"This property refers to a data schema associated with the applied data model, see property mobilitydcatap:dataModel."

Regarding 1:
You propose to change the range of this property from "rdfs:Resource" to "dcat:Distribution".
If we do so, the schema information would need to include any mandatory properties from the class "dcat:Distribution", see:
https://mobilitydcat-ap.github.io/mobilityDCAT-AP/drafts/latest/#properties-for-distribution

This would unnecessarily explode the payload: For example, the property "mobilitydcatap:dataModel" would need to be noted again, which is equal to "mobilitydcatap:dataModel" of the original distribution.
I propose to keep the generic range "rdfs:Resource".

Regarding 2:
If we keep the range "rdfs:Resource" (see above), the NAP system can decide how to reference the schema. It might be a URL to a NAP-internal catalogue of schemas, a URL to an individual schema (that is provided by the metadata publisher), or a URL to an external catalogue of schemas (like on the datex2.eu page). I will add this as a usage note.

I propose NOT to not include any additional properties for mobilityDCAT-AP1.0. We have only a few days until the publication, and property additions would involve another review round. However, let's think about refinements of our format-related properties (which may be expressed as formal sub-properties) for mobilityDCAT-AP2.0.

from mobilitydcat-ap.

keesnieuwstad avatar keesnieuwstad commented on June 25, 2024

Thanks for the proposals.

I was not aware that there are (only) a few days left until the release of version 1.0. So, it's nice that the usage note of 1 and 2 can still be adjusted.

To see later whether it is desirable to further develop format-related properties, looks like a sensible route to me.

from mobilitydcat-ap.

peterlubrich avatar peterlubrich commented on June 25, 2024

I resolved this while resolving this issue:
#12
See point 2.
-> There is a dedicated new class "Mobility Data Standard", with a property "Schema".
-> The range of "Schema" is kept with "rdfs:Resource", for the reasons above.
-> The usage of "Schema" has been concretised, with the options how to describe a schema described above.

from mobilitydcat-ap.

Related Issues (19)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.