- From: Marian, Radu <radu.marian@baml.com>
- Date: Fri, 03 May 2013 20:38:32 +0000
- To: "'Linked JSON'" <public-linked-json@w3.org>
- Message-id: <8EB326E198A85A409CDBB4297857CACB9F5F7C@smtp_mail.bankofamerica.com>
Dear JSON-LD Community,
I am new to JSON-LD but trying (hard) to make sense out of it. I have the following ontology model:
https://www.oasis-open.org/committees/download.php/49053/entitlement.ontology.png
Below is how I represent the syntax of Role - pretty much following the Role to Task to Resource and Action relationships. I may be doing something wrong.... Do I need to use @type instead? My other question is that I would like to create a Role instance json-ld but struggling how would I express it.... Roles do not have a meaning instead they inherit the meaning from Task (i.e. use Tasks description to provide a Role description).
{
"@context": {
"@vocab": "http://access.control.vocab.example.org",
"ctid": "http://concept.type.identifier.example.org",
"Role": {
"@id": "ctid:3003",
"enablesExecutionOf": {
"@id": "ctid:7003",
"Task": {
"@id": "ctid:3006",
"accesses": {
"@id": "ctid:7005",
"Business Resource": {
"@id": "ctid:3007"
}
},
"performs": {
"@id": "ctid:7006",
"Action": {
"@id": "ctid:3008"
}
},
"inContext": {
"@id": "ctid:7007",
"Business Context": {
"@id": "ctid:3009"
}
},
"implementedBy": {
"@id": "ctid:7008",
"Application": {
"@id": "ctid:3010"
}
}
},
"constrainedBy": {
"@id": "ctid:7013",
"Policy": {
"@id": "ctid:3005"
}
}
}
}
}
}
Radu Marian, MSCS, SCEA, CISSP
Bank of America - Charlotte, NC
VP, Architect 2, Enterprise Security Architecture
Business phone number: (704) 628-6874
an Enterprise without Ontology is like a country without a map.
----------------------------------------------------------------------
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message.
Received on Friday, 3 May 2013 20:39:04 UTC