Include levels of privacy of properties in their description

The privacy of the data contained in a property has been under discussion for the documentation of any property.

Now there is a first version on how to implement it.

The contribution manual has been updated for this possibility. See the specific slide about it.

Privacy clause: Privacy:’[high/medium/low]

Describes if the property has any kind of information related with personal data. Current options:

  • No clause: (default) this property does not contain personal data
  • Privacy:’high’: Those properties that refer to data on ideology, union affiliation, religion, beliefs, racial origin, health or sexual life.
  • Privacy:’medium’. Those properties related to the provision of financial solvency and credit services of people and those that contain definition of characteristics or personality and that allow evaluating certain aspects of personality or behavior of people.
  • Privacy:’low’.  Those properties that contains personal data different from the rest of types.

Example:

“refUserDevice” :{

“description”: “Property. Model:’http://schema.org/Text’. Privacy:’low’. An object representing the current device used by the User.”.

 

Instructions to be listed as a data model adopter of Smart Data Models

It has been updated the format of the list of adopters of the data models (formerly were CURRENT-ADOPTERS.md markdown files), now in it is rename into ADOPTERS.yaml based on this yaml template which allows an automatic processing. (Further announcements could be included in a future).

Further instructions in the page Data Models Adopters how to located in the menu option Data models -> Data Models Adopters How to

Improved the database of properties

The database for the searching on data models, properties and their descriptions has been expanded to allow filtering also by :

  • NGSI type (one of Property, Relationship or Geoproperty)
  • data type (string, number, boolean, array, object, etc)

Additionally, it has been updated containing more than 11.000 items

Accessible from the front page in this widget (Structured check)

You can export the results

New data models for Ports. BoatPlacesAvailable and SeaportFacilities

There are two new data models BoatPlacesAvailable and SeaportFacilities.

BoatPlacesAvailable . The purpose of the data model is to provide information on the availability of mooring rings for boats in the port by category. The information received relates only to pleasure boats and excludes commercial and passenger transport boats. The information on the Spot categories for boats is taken from the ISO 8666 standard.

SeaportFacilities. The Data Model is intended to provide information about ports that can accommodate pleasure craft, commerce or passenger transport. It permits to represent the parameters of each port, its location, its mooring capacities and the free or paid services associated with it provided directly by the port or by professionals working on or near the port“.

Located in the Subject Ports

New data model for Ports. SeaportsFacilities

There is a new data model SeaportsFacilities. The Data Model is intended to provide information about ports that can accommodate pleasure craft, commerce or passenger transport. It permits to represent the parameters of each port, its location, its mooring capacities and the free or paid services associated with it provided directly by the port or by professionals working on or near the port.

Located in the Ports Subject.

New data model for Ports. BoatAuthorized

There is a new data model BoatAuthorized. The data model is intended to provide information on the boats authorized to operate within the port according to the ISO 8666 standard for Boat Category.

This repository is created by the type of category of the boat (pleasure craft, trade, passengers, …). For each type of category, a list of optional subtypes of a category can be associated.

Located in the Ports Subject.

Specifications in languages in the readme of the data models

Now you can see the links to the specification in two languages, Spanish y French in the README.md of every data models. German and Japanese are in the queue.

See here an example

 

All specifications updated

All the specifications (the text descriptions of the data model located in the /doc directory of each daat model) for the different domains and languages (currently French and Spanish besides English) have been updated to the new format. See an example in Spanish and French.

All of them are generated automatically from the json schema (which is the unique source of truth for the data model)

The contribution manual explains further details.

Raise an issue for any point you find in the new format.