This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Datatypes R2 Issue 17"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
== Introduction == | == Introduction == | ||
| + | Very often ED content comes from a file that has a name, | ||
| + | or some other source where there is some text that | ||
| + | describes the content - for when it will eventually | ||
| + | be a file name. | ||
| − | + | This name is a useful thing for applications - they | |
| + | can use it when they do move the content into a filename, | ||
| + | or display the name in preference to the content sometimes. | ||
| + | |||
| + | |||
| + | backward compatible: yes | ||
== Discussion == | == Discussion == | ||
| + | We can simply add title:ST to the abstract and add it | ||
| + | as an attribute in the XML ITS. | ||
| + | |||
| + | == Status == | ||
| + | |||
| + | Proposed. | ||
== Links == | == Links == | ||
Back to [[Data Types R2 issues]] | Back to [[Data Types R2 issues]] | ||
Revision as of 17:10, 3 May 2007
Contents
Data Types Issue 17: Add title or filename to ED
Introduction
Very often ED content comes from a file that has a name, or some other source where there is some text that describes the content - for when it will eventually be a file name.
This name is a useful thing for applications - they can use it when they do move the content into a filename, or display the name in preference to the content sometimes.
backward compatible: yes
Discussion
We can simply add title:ST to the abstract and add it as an attribute in the XML ITS.
Status
Proposed.
Links
Back to Data Types R2 issues
