| Key: |
OFFICE-2529
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Blocker
|
| Assignee: |
Unassigned
|
| Reporter: |
Robert Weir
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution: |
The exact way in which the content of the text:meta-field is generated from RDF metadata is unspecified.
ODF 1.2 text:meta-field is a very flexible and generic element, and we don't want to constrain what can be done with it prematurely.
This means that ODF consumers are not expected to be able to re-generate the content of arbitrary text:meta-fields; they should only re-generate those meta-fields that they know and recognize (by the describing RDF metadata) and leave the rest alone.
It may be a good idea to specify some mechanism by which field content can be generated automatically for simple cases, like e.g. querying a single value from a semantic web database, for a future version of ODF.
The exact way in which the content of the text:meta-field is generated from RDF metadata is unspecified.
ODF 1.2 text:meta-field is a very flexible and generic element, and we don't want to constrain what can be done with it prematurely.
This means that ODF consumers are not expected to be able to re-generate the content of arbitrary text:meta-fields; they should only re-generate those meta-fields that they know and recognize (by the describing RDF metadata) and leave the rest alone.
It may be a good idea to specify some mechanism by which field content can be generated automatically for simple cases, like e.g. querying a single value from a semantic web database, for a future version of ODF.
|
|
Public Comment: An analysis of the <text:meta-field> element
The commenter is under the impression that the text:meta-field is much smarter than it actually is.
The exact way in which the content of the text:meta-field is generated from RDF metadata is unspecified.
ODF 1.2 text:meta-field is a very flexible and generic element, and we don't want to constrain what can be done with it prematurely.
This means that ODF consumers are not expected to be able to re-generate the content of arbitrary text:meta-fields; they should only re-generate those meta-fields that they know and recognize (by the describing RDF metadata) and leave the rest alone.
Maybe it would be a good idea to specify some mechanism by which field content can be generated automatically for simple cases, like e.g. querying a single value from a semantic web database... but that seems more like ODF-next to me in any case.
Because there is no concrete proposal here the issue can be closed.