openstack/pycadf
Code Issues Proposed changes

Additional doc clean up

Browse Source 
1) Added code-block headers to the JSON examples
2) Formatted the JSON examples
3) Replaced a few instances of double-byte characters with more
   their usual counter parts ("-" and "'"), these normally originate
   from the openstack wiki for some reason.

Change-Id: I2ca1dbfc5bdf1c50da466b290a6460a42f1b885a
This commit is contained in:
Steve Martinelli
2015-02-17 00:10:10 -05:00
parent 1613013277
commit 6c1ee2e583
11 changed files with 299 additions and 240 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
doc/source/specification/attachments.rst
View File

@@ -20,9 +20,9 @@
============
An attachment is a container for data or "content" that may follow any
structure – from an atomic type to a complex hierarchy. However, it is
desirable for processing and interoperability that the type – or
structure – of the content be identified by a simple value. To this end the
structure - from an atomic type to a complex hierarchy. However, it is
desirable for processing and interoperability that the type - or
structure - of the content be identified by a simple value. To this end the
attachment also contains a "content type", i.e., a URI that identifies the
kind of content.
@@ -40,19 +40,19 @@ contentType xs:string Yes An optional name that can be used to provide an i
Serialisation
=============
json::
.. code-block:: javascript
{
...,
"attachments": [
{
"content": "xs:any",
"contentType": "xs:anyURI"
},
{
"content": "xs:any",
"contentType": "xs:anyURI"
"typeURI": "http://schemas.dmtf.org/cloud/audit/1.0/event",
...,
"attachments": [
{
"content": "xs:any",
"contentType": "xs:anyURI"
},
{
"content": "xs:any",
"contentType": "xs:anyURI"
}
]
}
]
}