[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (OFFICE-3361) ODF 1.2 Part 17.5.19 <text:meta-field> underspecified
[ http://tools.oasis-open.org/issues/browse/OFFICE-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21563#action_21563 ]
Michael Brauer commented on OFFICE-3361:
----------------------------------------
As for "This field, appears to be some sort of <text:span> with magical powers.":
The <text:meta-field> and <text:span> elements have in common that they can include other text level content and both can appear within paragraph. But the <text:span> element is for attaching styles while the <text:meta-field> element contains some generated content. That's a semantic difference that is worth having two elements. In particular since implementations need to handle them differently. For a <text:span> element it is possible to break it in multiple elements. That is <text:span>Hello World!</text:span> is the same as <text:span>Hello </text:span><text:span>World!</text:span>. However breaking up <text:meta-field>Hello World!</text:meta-field> into <text:meta-field>Hello </text:meta-field><text:meta-field>World!</text:meta-field> obviously would result in a duplication of the content if the field content is recreated.
In general, I think rather then suggesting to delete elements or attributes we don't fully understand, we should try to clarify them in a way that they get understandable.
> ODF 1.2 Part 1 7.5.19 <text:meta-field> underspecified
> ------------------------------------------------------
>
> Key: OFFICE-3361
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-3361
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: Public Review
> Affects Versions: ODF 1.2 CD 05
> Reporter: Dennis Hamilton
> Priority: Blocker
> Fix For: ODF 1.2 CD 06
>
>
> This field, appears to be some sort of <text:span> with magical powers. However, the following critical questions are not answered:
> (0) I have no idea what it means to say "generated upon existing metadata."
> (1) In the document, Is the content already generated and is that what the mixed content of the element is? If the document is signed?
> (2) What are producers expected to deliver here if they deliver it?
> (3) What is a consumer expected to make of this when encountered? May it simply be interpreted as a supply of mixed content at the place where it is an element child"
> (4) Is the xml:id for reference to the <text-meta-field> from outside of the document (e.g., by some tool that might be used to fill in the field? How about by some tool that might want to extract it? Are there any relationships with reference to the element from elsewhere in the same XML document? Is this anything that a consumer needs to deal with in any way as part of consumption of the document as what it is?
> (5) I see nothing in the definition of <text:meta-field> that explains how it is a container for generated text and there is nothing that indicates anything special in terms of metadata. There is nothing to let us pull.
> Since RDF does not "push," it only describes and points, how is generation expected to have been accomplished?
> There is just not enough semantics to go with this to know what its field-ness is and what is based on?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]