| ... | ... | @@ -22,18 +22,6 @@ Here is an example of our API : |
|
|
|
"get_full_name": "rdfs:label"
|
|
|
|
}
|
|
|
|
],
|
|
|
|
"permissions": [
|
|
|
|
{
|
|
|
|
"mode": {
|
|
|
|
"@type": "view"
|
|
|
|
}
|
|
|
|
},
|
|
|
|
{
|
|
|
|
"mode": {
|
|
|
|
"@type": "change"
|
|
|
|
}
|
|
|
|
}
|
|
|
|
]
|
|
|
|
}
|
|
|
|
```
|
|
|
|
# Looks like a simple JSON but it's more
|
| ... | ... | @@ -95,10 +83,19 @@ account | accountName | accountServiceHomepage | age | aimChatID | based_near | |
|
|
|
|
|
|
|
Now we can describe a user for every machines in the world using a universal language :)
|
|
|
|
|
|
|
|
# Why JsonLD is awesome ?
|
|
|
|
|
|
|
|
A document structured in RDF is a set of triplets.
|
|
|
|
|
|
|
|
An RDF triplet is an association (subject, predicate, object) :
|
|
|
|
|
|
|
|
* the "subject" represents the resource to be described;
|
|
|
|
* the "predicate" represents a type of property applicable to this resource;
|
|
|
|
* the "object" represents a data or another resource: it is the value of the property.
|
|
|
|
|
|
|
|
But in today life, we use to structure datas in in a file, directory, inventory logic and not in linked triplets. It's quickly a mess to apprehend.
|
|
|
|
|
|
|
|
JsonLD allow us to us Linked Datas in a very intuitive way.
|
|
|
|
|
|
|
|
|
|
|
|
The page is still in process and constructed in french.
|
|
|
|
You can participate to [the review](https://docs.google.com/document/d/1l70VbMxgGPAVuyT9_MtxLHhnELBE__hl40gE7AaJvk8/edit?usp=sharing)
|
|
|
|
|
