OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (OFFICE-2932) 7.5.19<text:meta-field> "acts as a wrapper"? - how about - "is a container for" ?

    [ http://tools.oasis-open.org/issues/browse/OFFICE-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19526#action_19526 ] 

Dennis Hamilton commented on OFFICE-2932:

Since the mixed content is already there, I would say "is a container of".  I am not so sure about the subsequent "generated upon existing metadata."  "generated upon" baffles me.

Considering that there can be any paragraph content (so this is very much like a <text:span>), I don't understand the description of the style:data-style-name for <text:meta-field>.  It seems far too limiting and it is not clear what ""number" it is that  the style might apply to.

It seems that what this element accomplishes, beside having the peculiar style:data-style-name attribute, is attaching an xml:id to the element.  Since this is for an incoming reference (via IDREF or via a #fragment-id in a URI), I also don't quite know what to make out of the xml:id serving "to attach (link) the metadata used to generate the content of a <text:meta-field> element."  It seems to me that the metadata that is somehow the basis for this element's mixed content can link here, but this element has no provision for linking there.

Off-hand, it seems easier to have this be the subject of meta-data rather than derived from meta-data in some way.  Either way, this is a challenge for a producer, who must be able to provide an XML-document-unique xml:id that can be used in a subject or object triple of one or more RDF assertions somewhere else in the package.

My mind runs away from any speculation concerning the different cases where tracked changes must capture all or part of one of these elements.

I'd make an issue about all of this if I could figure out what to call it.

> 7.5.19 <text:meta-field> "acts as a wrapper"? - how about - "is a container for" ?
> ----------------------------------------------------------------------------------
>                 Key: OFFICE-2932
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2932
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.2 Part 1 CD 5
>            Reporter: Patrick Durusau
>            Assignee: Patrick Durusau
>            Priority: Minor
>             Fix For: ODF 1.2 Part 1 CD 5
> 7.5.19 <text:meta-field> "acts as a wrapper"? - how about - "is a container for" ?

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]