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-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=21840#action_21840 ] 

Andreas Guelzow  commented on OFFICE-3361:

"The mixed content of this element should be generated from the metadata source." still doesn't mean anything to me, which considering "The source of the metadata and the means of generation of the mixed content is implementation-dependent." Probably isn't surprising.

Unless we say how this information is generated and from what, why are we talking about its content at all. Why aren't we just saying:
"The <text:meta-field> element represents arbitrary implementation-dependent content."

Since the content is implementation-dependent, I think there is little point in saying that the content might change. Only the implementation that created the content can work with it anyways.

> 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: Metadata, Needs Discussion, Public Review, Text
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Patrick Durusau
>            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]