You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👍 @udiedrichsen@whizkid77 – just noticed that as well while working on a node.js module.
Would be nice if this could be fixed in the 'scraper'.
Meanwhile:
I compared the results of .types with our node.js JSON and put the missing .types-comments in this gist!
You can ignore the links attribute - it contains links within the comments.
Why? [would be also a "feature request"/"enhancement" for this project]
I think there is a JSON specification for specifying schema.org - and that is JSON Schema – nice read here
For example when the comment is saying "use ISO 8601 duration format" this can be specified in JSON Schema. A discussion is here.
I am using the JSON data provided by
http://schema.rdfs.org/all.json
but for all datatypes and types are the fields comments and commtents_plain empty:
datatypes": {
"Boolean": {
"ancestors": [
"DataType"
],
"comment": "",
"comment_plain": "",
"id": "Boolean",
"instances": [
"False",
"True"
],
"label": "Boolean",
"properties": [],
"specific_properties": [],
"subtypes": [],
"supertypes": [
"DataType"
],
"url": "http://schema.org/Boolean"
},
and
"WearAction": {
"ancestors": [
"Thing",
"Action",
"ConsumeAction",
"UseAction"
],
"comment": "",
"comment_plain": "",
Would be nice, if the comments could be filled. For all properties the comment fields are ok.
Cheers,
Uli
The text was updated successfully, but these errors were encountered: