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

typo #617

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

typo #617

Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/croissant-spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -1526,7 +1526,7 @@ More generally, when a `RecordSet `is assigned a `dataType`, some or all of its
* Either the `@id` of the field has the name of the property as a suffix, e.g., a field with `@id `"cities/latitude" corresponds to the property "[sc:latitude](http://schema.org/latitude)" associated with the data type [sc:GeoCoordinates](http://schema.org/GeoCoordinates).
* Or there is an explicit mapping specified on the Field, via the property `equivalentProperty`.

When a field is mapped to a property, it can inherit the range type of that property (e.g., latitude and longitude can be or of type Text or Number). It may also specify a more restrictive type, as long as it doesn't contradict the rang of the property (e.g., require the values of latitude and longitude to be of type Float).
When a field is mapped to a property, it can inherit the range type of that property (e.g., latitude and longitude can be or of type Text or Number). It may also specify a more restrictive type, as long as it doesn't contradict the range of the property (e.g., require the values of latitude and longitude to be of type Float).

A cities `RecordSet` with fields implicitly mapped to latitude and longitude:

Expand Down
Loading