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-3653) Public Comment:PRD02 <text:a> anchor text nonsense

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

Dennis Hamilton commented on OFFICE-3653:

@Patrick, the alternatives all create ambiguity around what paragraph is being talked about.  

It turns out that the <text:a> element has paragraph-content as the pattern for *its* content.  The <text:a> element generally appears in a pattern named paragraph-content-or-hyperlink.  That makes references to some nonspecific paragraph of which the <text:a> is part rather clumsy in regard to the schema and what the schema says is paragraph-content.  

So a wording that unambiguously refers to the document content derived from the <text:a> content alone in an unambiguous way is required.  The first form of the resolution accomplishes that.  For me, the alternatives fail to maintain a clear distinction.

More Consideration:

We need to say when we mean the document text that the <text:a> element determines and not create confusion with the casual use of the word paragraph in the specification and with the specific elements beside <text:a> that have paragraph-content[-or-hyperlink] patterns, including <text:h>, <text:p>, <text:meta>, <text:meta-field>, <text:span>, <text:ruby-base>.  To add to the confusion, there is also the text-content pattern, a specific pattern of the schema that can also deliver a considerable amount of character data to a document (e.g., via a <text:section>).

Note: My concern that the "anchor" not be limited to character data is a separate matter and applies to all forms of the resolution.  That does not figure in why I prefer the first over the alternatives.  Also, note that a <text:a> can have another <text:a> (under a <text:span>) in its subsidiary paragraph-content and I suspect that isn't included in the higher-level "anchor" even though it contributes character data up into it.

> Public Comment: PRD02 <text:a> anchor text nonsense
> ---------------------------------------------------
>                 Key: OFFICE-3653
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3653
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Needs Discussion, Public Review, Text
>    Affects Versions: ODF 1.2 CD 06
>            Reporter: Robert Weir 
>            Priority: Trivial
>             Fix For: ODF 1.2 CD 07
> Copied from office-comment list
> Original author: Alex Brown <alexb@griffinbrown.co.uk> 
> Original date: 21 Dec 2010 18:11:01 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/201012/msg00066.html

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]