[OASIS Issue Tracker] Issue Comment Edited: (OFFICE-3010) 19.322grddl:transformation - 2nd paragraph - "intended to be interpreted"?

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Dennis Hamilton edited comment on OFFICE-3010 at 8/9/10 1:11 PM:
-----------------------------------------------------------------

Technically, we could omit the attribute from the ODF 1.2 schema and specification completely and let it be dealt with as a foreign attribute.

Although it would be best to deal with related matters in a separate JIRA issue, I want to make sure that I mention that I have concerns about other aspects of this attribute definition: (1) Despite what it says in the text, there is no mechanism in place for registering any particular ones, and there is no provision on the OASIS site to hold onto them.  (2) there are documents in the wild where there is a reference to the OASIS site for a transform, but the reference is not resolvable.  (the reference seems to be boilerplate that is simply provided on every ODF document that a particular implementation spits out).  In addition, I thought it was the manifest.rdf that was supposed to help us deal with this situation, rather than having someone do (signature-breaking) modifications to the content.xml file in an arbitrary way.  I can also see concerns about signing a file that has one of these in it, since it is not something the signer is like to be able to see or have knowledge of.

I note that there are related issues to this one: OFFICE-2869 and OFFICE-3011.

      was (Author: orcmid):
    Technically, we could omit the attribute from the ODF 1.2 schema and specification completely and let it be dealt with as a foreign attribute.

Although it would be best to deal with related matters in a separate JIRA issue, I want to make sure that I mention that I have concerns about other aspects of this attribute definition: (1) Despite what it says in the text, there is no mechanism in place for registering any particular ones, and there is no provision on the OASIS site to hold onto them.  (2) there are documents in the wild where there is a reference to the OASIS site for a transform, but the reference is not resolvable.  (the reference seems to be boilerplate that is simply provided on every ODF document that a particular implementation spits out).  In addition, I thought it was the manifest.rdf that was supposed to help us deal with this situation, rather than having someone do (signature-breaking) modifications to the content.xml file in an arbitrary way.  I can also see concerns about signing a file that has one of these in it, since it is not something the signer is like to be able to see or have knowledge of.
  
> 19.322 grddl:transformation - 2nd paragraph - "intended to be interpreted"? 
> ----------------------------------------------------------------------------
>
>                 Key: OFFICE-3010
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3010
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Metadata, Part 1 (Schema)
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Patrick Durusau
>            Assignee: Svante Schubert 
>             Fix For: ODF 1.2 CD 06
>
>
> The second paragraph reads: 
> "These algorithms are intended to be interpreted by consumers that do not support OpenDocument. OpenDocument consumers may interpret these algorithms."
> Why we create this algorithms really isn't at issue. Let's drop the 2nd paragraph. 

-- 
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