Dev:Common Concepts: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
* [[CO:outsourcing | Using content libraries]] and fully validating without any error or warning messages | * [[CO:outsourcing | Using content libraries]] and fully validating without any error or warning messages | ||
* [[CO:changes | Changes]] sorted by released versions | * [[CO:changes | Changes]] sorted by released versions | ||
* [[CO:Codelists]] | |||
Revision as of 16:18, 13 March 2017
Common concepts to all railML® schemas
Common is a pseudo subschema to cover general aspects or aspects interfering different subschemas. Some general concepts about handling railML files are summerized on the following wiki-sites:
- Conventions for railML files (file name extensions, compressed files, and other)
- Handling identities (id values)
- Local versus web-based validation (XML catalogs and XML namespaces)
- Versioning policy (version numbers, versioned XML namespaces)
- Officially released versus developer version (Homepage, Subversion)
- Discussed versus agreed features (Newsgroup, Trac Tickets)
- XML Syntax issues (Attribute delimiters, Character references)
- Using "xs:any" elements, "anyAttribute"s and "other:anything" enumeration values for enhancing the railML files with your special needs
- Using content libraries and fully validating without any error or warning messages
- Changes sorted by released versions
- CO:Codelists