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-702) Public Comment:OpenDocument 1.2v7-02: 1.3 Namespaces

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

Dennis Hamilton commented on OFFICE-702:

In reviewing this issue and the extensive changes to resolve it, I have made the following refinements to arrive at the proposed resolution:

The resolution corrects the occasions where prefixes are confused with the namespaces bound to them.

The resolution adjusts for the fact that according to [xml-names] the prefix has no colon in it or after it.  The prefix is separated from the local name by a ":" but the ":" is not part of the prefix.  Since we are using prefixes in other than namespacedToken attribute values, the occurrence of a separating ":" needs to be made explicit.  I did that where needed.

Here are specific differences:

2.2.1 - not included.  The term "Dublin Core namespace" is ambiguous, since it is a term of art in the Dublin Core work having nothing to do with XML namespaces.   This section should be treated separately with a separate JIRA issue.

17.3.19 I redid namespacedToken to be defined to use QNames, not just PrefixedName forms.  This seemed to be consistent with the actual usages.

18.31 I restated this to make sense to me.  It might not be what is the actual case.

18.88.3 There needs to be a default case when no prefix is included in the namespacedToken, or it should be indicated that a PrefixedName must be the value.

18.149 There is a question about what is the default namespace here too.  Also, what it means to say "can be used" here needs to be addressed in a separate issue.

18.432 (not 18.433 - I think the numbering must be changed in a draft that we haven't seen yet - I am using cd03).  This section makes no sense and it should be resolved by something that does.  I didn't include it.

18.470 (or 471 on style:condition): I could not figure out where this goes and even why it is being added.  I didn't include this change.

18.584 table:algorithm.  I rewrote this a bit.

18.599 table:condition - I couldn't figure out how to introduce namespace prefixes in this and have it make sense.  Needs to be dealt with separately.

18.638 table:expression - I couldn't figure out where the suggested addition fits and how to have it make sense there.

18.645 and 18.808 I used a common way of saying that the formula comes after the prefix and ":" that should be there, but it still seems a little too recursive.  Also, there might be a more emphatic way to say that the prefix and ":" are optional, the formula isn't.  I didn't do anything about that, or how we make sure that there is no ambiguity with a prefix being omitted but the formula beginning with a name followed by a ":" as part of the formula, not as a prefix and its separator.

> Public Comment: OpenDocument 1.2v7-02: 1.3 Namespaces
> -----------------------------------------------------
>                 Key: OFFICE-702
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-702
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Conformance
>    Affects Versions: ODF 1.2
>         Environment: This proposal applies to ODF 1.2 Part 1.  The resolution is stated in terms of the sections in ODF 1.2 Part 1 cd03.
>            Reporter: Robert Weir 
>            Assignee: Dennis Hamilton
>            Priority: Blocker
>             Fix For: ODF 1.2
> Copied from office-comment list
> Original author: "Dennis E. Hamilton" <dennis.hamilton@acm.org> 
> Original date: 18 May 2008 06:41:47 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/200805/msg00029.html
> This issue is taken as applying specifically to the situations where the prefix of a qualified name and an independently used prefix is spoken of as being the namespace name, rather than being bound to the namespace (name) by a namespace declaration.

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]