Difference between revisions of "Alternative Content Formats"

From BioDAS
Jump to: navigation, search
(Created page with 'List of alternative content formats: {| !Name||MIME type||Commands |- |das-xml||application/xml||all |- |das-json||application/json||sources,features,types |- |binary-bigwig||a…')
 
m (das-json sources)
Line 49: Line 49:
 
                     "coordinates" : [
 
                     "coordinates" : [
 
                         {
 
                         {
                             "uri"       : "http://www.dasregistry.org/dasregistry/coordsys/CS_DS108",
+
                             "uri"       : "http://www.dasregistry.org/dasregistry/coordsys/CS_DS108",
                             "label"     : "NCBIM_37,Chromosome,Mus musculus",
+
                             "label"     : "NCBIM_37,Chromosome,Mus musculus",
 
                             "authority"  : "NCBIM",
 
                             "authority"  : "NCBIM",
                             "version"   : "37",
+
                             "version"   : "37",
 
                             "source"    : "Chromosome",
 
                             "source"    : "Chromosome",
                             "taxid"     : 10090,
+
                             "taxid"     : 10090,
 
                             "test_range" : "8:1,100"
 
                             "test_range" : "8:1,100"
 
                         }
 
                         }

Revision as of 09:54, 27 March 2012

List of alternative content formats:

Name MIME type Commands
das-xml application/xml all
das-json application/json sources,features,types
binary-bigwig application/octet-stream features
binary-bigbed application/octet-stream features

das-json

This format is a native JSON encoding of the DAS data model. The design principle for this format is that the properties accurately match those in the specification, rather than the XML. Thus there are no distinctions made between elements, attributes and text content. Whilst this means that implementing a reciprocal XML-JSON conversion function must be done explicitly for each DAS command, using DAS in Javascript web applications is more natural.

Currently, the das-json format is defined for the sources, features and types commands.

das-json sources

{
    "sources" : [
        {
            "uri" : "mygenes",
            "title" : "My Genes",
            "description" : "A source that provides gene features",
            "maintainer" : {
                "email": "me@myplace.com"
            },
            "doc_href" : "http://myplace.com/info/mysource",
            "versions" : [
                {
                    "uri" : "mysource",
                    "created" : "2012-03-27T14:23:44Z",
                    "capabilities" : [
                        {
                           "type" : "das1:sources",
                           "query_uri" : "http://myplace.com/das/mygenes"
                        },
                        {
                           "type" : "das1:features",
                           "query_uri" : "http://myplace.com/das/mygenes/features"
                        }
                    ],
                    "coordinates" : [
                        {
                            "uri"        : "http://www.dasregistry.org/dasregistry/coordsys/CS_DS108",
                            "label"      : "NCBIM_37,Chromosome,Mus musculus",
                            "authority"  : "NCBIM",
                            "version"    : "37",
                            "source"     : "Chromosome",
                            "taxid"      : 10090,
                            "test_range" : "8:1,100"
                        }
                    ],
                    "properties" : [
                        {
                            "name" : "Some Key",
                            "value" : "Some Value"
                        }
                    ]
                }
            ]
        }
    ]
}