Difference between revisions of "DAS1.6"
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [http://www.biodas.org/documents/spec-1.6.html DAS 1.6] | + | DAS 1.6 is, as of 19th October 2010, the latest official version of DAS. The specification document is found here: |
| + | [http://www.biodas.org/documents/spec-1.6.html DAS 1.6 specification] | ||
The DAS specification is a technical document but with some effort should hopefully be readable and understandable by people without a deep understanding of broader technical issues and other system architectures. That is, it makes only basic assumptions. | The DAS specification is a technical document but with some effort should hopefully be readable and understandable by people without a deep understanding of broader technical issues and other system architectures. That is, it makes only basic assumptions. | ||
| Line 9: | Line 10: | ||
* better reflect how DAS is being used in the community today | * better reflect how DAS is being used in the community today | ||
* better reflect the use of DAS beyond the genome-centric arena (protein sequences and structures) | * better reflect the use of DAS beyond the genome-centric arena (protein sequences and structures) | ||
| − | * ratify commands from the [http://www.dasregistry.org/spec_1.53E.jsp 1.53E spec] | + | * ratify commands from the [http://www.dasregistry.org/spec_1.53E.jsp 1.53E extended spec] |
* introduce some ideas inspired by DAS/2 | * introduce some ideas inspired by DAS/2 | ||
* formally introduce the DAS registry | * formally introduce the DAS registry | ||
* migrate from the use of DTDs for describing the XML formats to RelaxNG | * migrate from the use of DTDs for describing the XML formats to RelaxNG | ||
| + | |||
| + | The list of changes is listed here: [[DAS 1.6 Changes]]. | ||
| + | |||
| + | ==Compatibility== | ||
| + | |||
| + | Software developers wanting to know more about supporting or migrating between different versions of the specification may wish to consult the [[DAS 1.6 Migration]] page. | ||
| + | |||
| + | ==Extensions== | ||
| + | |||
| + | Several extensions to the 1.6 are proposed by community members. See the [[DAS1.6E]] page for more details. | ||
==Development== | ==Development== | ||
| Line 24: | Line 35: | ||
* [http://www.ebi.ac.uk/~aj/1.6_draft6/documents/spec.html Draft 6] | * [http://www.ebi.ac.uk/~aj/1.6_draft6/documents/spec.html Draft 6] | ||
* [http://www.ebi.ac.uk/~aj/1.6_draft7/documents/spec.html Draft 7] | * [http://www.ebi.ac.uk/~aj/1.6_draft7/documents/spec.html Draft 7] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Links== | ==Links== | ||
[[DAS 1.6 in Dazzle]] | [[DAS 1.6 in Dazzle]] | ||
Latest revision as of 17:26, 1 November 2010
DAS 1.6 is, as of 19th October 2010, the latest official version of DAS. The specification document is found here: DAS 1.6 specification
The DAS specification is a technical document but with some effort should hopefully be readable and understandable by people without a deep understanding of broader technical issues and other system architectures. That is, it makes only basic assumptions.
Purpose
It is the first official version published in several years, and aims to:
- clarify ambiguities in the previous DAS specification
- better reflect how DAS is being used in the community today
- better reflect the use of DAS beyond the genome-centric arena (protein sequences and structures)
- ratify commands from the 1.53E extended spec
- introduce some ideas inspired by DAS/2
- formally introduce the DAS registry
- migrate from the use of DTDs for describing the XML formats to RelaxNG
The list of changes is listed here: DAS 1.6 Changes.
Compatibility
Software developers wanting to know more about supporting or migrating between different versions of the specification may wish to consult the DAS 1.6 Migration page.
Extensions
Several extensions to the 1.6 are proposed by community members. See the DAS1.6E page for more details.
Development
The specification was developed as a community collaboration via progression through a number of drafts:
