access:track_labeling
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
access:track_labeling [2015/11/26 00:21] mjallison [Other structural items in server] |
access:track_labeling [2015/12/01 00:45] (current) mjallison [Proposed structure] |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| ===== Other structural items in server ===== | ===== Other structural items in server ===== | ||
| - | Currently the provides generic Configuration objects and cycleline storage available to end user programs. These objects are stored using the Json standard. There should be strong consideration to extend this to track attributes. | + | Currently the provides generic Configuration objects and cycleline storage available to end user programs. These objects are stored using the [[http://www.json.org|JSON]] standard. There should be strong consideration to extend this to track attributes. |
| - | The most compatible format right now is to add JSon objects to each track, as a field called "attributes". This allows applications to store additional attributes, either track-global, or time varying (by changing field names). All deployment platforms are able to parse Json objects. | + | The most compatible format right now is to add [[http://www.json.org|JSON]] objects to each track, as a field called "attributes". This allows applications to store additional attributes, either track-global, or time varying (by changing field names). All deployment platforms are able to parse [[http://www.json.org|JSON]] objects. |
| ===== Proposed structure ===== | ===== Proposed structure ===== | ||
| Line 25: | Line 25: | ||
| Initial proposal for attributes: | Initial proposal for attributes: | ||
| - | * "com.agtek.label", string, arbitrary value. | + | * "agtek.label", string, arbitrary value. |
| - | Other attribute values can be added at a later time, provided applications retain the entire JSon object when updating tracks. Applications should ignore attribute fields which are not understood. | + | Other attribute values can be added at a later time, provided applications retain the entire [[http://www.json.org|JSON]] object when updating tracks. Applications should ignore attribute fields which are not understood. |
| ===== Support Libraries ===== | ===== Support Libraries ===== | ||
| - | The following JSon implementations are available for the listed platforms: | + | The following [[http://www.json.org|JSON]] implementations are available for the listed platforms: |
| * Android - org.json (part of runtime) | * Android - org.json (part of runtime) | ||
| * IOS - NSJsonSerialization | * IOS - NSJsonSerialization | ||
| - | * Java - org.json (part of runtime) | + | * Java - org.json (external library, available) |
| * Web - Built into most web browsers | * Web - Built into most web browsers | ||
| * Windows - Windows.Data.Json | * Windows - Windows.Data.Json | ||
access/track_labeling.1448497262.txt.gz · Last modified: 2015/11/26 00:21 by mjallison
Page Tools
