RE: [dita] Re: DITA 1.2, CD 02 submission (DITA1.2-CD02.zip) uploaded

[Eric Sirois <esirois@ca.ibm.com>]

Hi,
  
I agree with Paul.  We cannot change
the current namespace in DITA 1.x.  Doing so will make some existing
documents invalid.  That means DITA 1.2 is no longer backwards compatible.
Not in a minor release.  I understand OASIS' point of view, but there's
nothing that we can do about it until DITA 2.0.

(1) - Part of the issue is that any
DTD validated document that is stored  on disk or in memory (i.e.
XML applications that store documents in a canonical tree structure) will
have the namespace attribute expanded and stored in the document.  Since
the namespace is a fixed value in the DTD any change in value will cause
errors when the document is parsed against an updated value in the DTDs.
 It's an unfortunate by-product of using namespaces in DTD, but one
that we have to deal with.  This behavior is part of Canonical XML
specification [1].

(2) - Some applications use the ditaArch:DITAArchVersion
attribute as a way to identify that XML docs with that attribute is a DITA
doc.  Changing the namespace also so means that those applications
need to be updated (future and in-service releases).  So changing
the namespace to a different URL have ramifications on applications that
consume and support DITA.

Eric


[1] - http://www.w3.org/TR/xml-c14n

---

Eric A. Sirois
Staff Software Developer 
DB2 Universal Database - Information Development
DITA XML Schema Architect and DITA Open Toolkit Developer
IBM Canada Ltd. - Toronto Software Lab
Email: esirois@ca.ibm.com
Phone:(905) 413-2841
Blue
Pages (Internal)

"Transparency and accessibility requirements dictate that public information
and government 
transactions avoid depending on technologies that imply or impose a specific
product or 
platform on businesses or citizens" - EU on XML-based office document
formats.

From:	"Grosso, Paul" <pgrosso@ptc.com>
To:	"Mary McRae" <mary.mcrae@oasis-open.org>
Cc:	"Kristen James Eberlein" <kris@eberleinconsulting.com>, "DITA TC" <dita@lists.oasis-open.org>
Date:	06/22/2010 09:38 PM
Subject:	RE: [dita] Re: DITA 1.2, CD 02 submission (DITA1.2-CD02.zip) uploaded

---

Mary,
 
We aren't communicating.

 
I don't know what "it"
isn't the issue for you.
 
I don't know what it means
for a namespace to be at a location.
 
The DITA namespace name
is http://dita.oasis-open.org/architecture/2005/.
 That is unchangeable.
 
When someone puts a namespace
name into a browser, they are supposed to be served a namespace document.
 That is a recommendation of the W3C Technical Advisory Group headed
by Tim Berners-Lee.  I don't not want to see OASIS violate this, and
I would hope you and the other people who make OASIS policy [isn't that
supposed to be the OASIS members, i.e., us] would not want to violate this
either. 
 
So something needs to be
served when http://dita.oasis-open.org/architecture/2005/
is accessed. The easiest way to do that is to put something at http://dita.oasis-open.org/architecture/2005/index.htm.
 That something can either be the namespace document or a document
that redirects to a copy of the namespace document.
 
paul
 
From: Mary McRae [mailto:mary.mcrae@oasis-open.org]
Sent: Tuesday, 2010 June 22 21:28
To: Grosso, Paul
Cc: Kristen James Eberlein; DITA TC
Subject: Re: [dita] Re: DITA 1.2, CD 02 submission (DITA1.2-CD02.zip)
uploaded
 
Hi Paul,
 
  No, that's not the issue.
OASIS requires all namespaces to live at http://docs.oasis-open.org/ns/dita/...
or http://docs.oasis-open.org/dita/ns.
If a namespace was declared prior to the naming guidelines going into effect
(which created the explicit 'ns' in the path) then it must be at http://docs.oasis-open.org/dita/...
 It can't be at dita.oasis-open.org.
 
Mary 


 
On Jun 21, 2010, at 11:49 PM, Grosso,
Paul wrote:


Re:
 
The namespace must live on http://docs.oasis-open.org/dita
- it cannot live at the site of the focus area.
 
I assume by "namespace"
you mean the namespace document.
 
The namespace name is http://dita.oasis-open.org/architecture/2005/
 
Since the namespace document
has to be returned when one accesses the namespace name, the namespace
document (or perhaps a redirect to it) has to reside at http://dita.oasis-open.org/architecture/2005/index.htm.
 
paul
 
 
From: Mary McRae [mailto:mary.mcrae@oasis-open.org]
Sent: Monday, 2010 June 21 23:37
To: Kristen James Eberlein
Cc: DITA TC
Subject: [dita] Re: DITA 1.2, CD 02 submission (DITA1.2-CD02.zip) uploaded
 
Hi Kris,
 
  from the original list:
 
In the PDF version:

1. This Version URIs: text on the cover is fine, but the actual hypertext
links point to cd01
> The URI has been incorrectly
changed to point to the generic version rather than cd02; the URI was fine
before - it was the hypertext link that was incorrect

2. Latest Version URIs: these are generic URIs that will be used to always
access the most recent version of the spec. If you remove the cd02 subdir
from the path it will be fine. Again, make sure the actual hypertext links
are updated as well; they still point to cd01
> fixed

3. Namespace: this must be an actual hypertext link
> The namespace must live on
http://docs.oasis-open.org/dita
- it cannot live at the site of the focus area.

4. running footer: please add CD 02 to DITA v1.2
> fixed

COMMENT: Section 1.4 is great! Thank you for adding this.

5. There are some rules showing up that seem to be tied to examples and
should be removed; they appear to be tied to the heading below them.
> rules still appearing; see
pg 33 - just prior to 2.1.2.2.5

6. Each Appendix should start a new page; same styling as 1st level headings
> The section labeled 'appendices'
should be removed or turned into Appendix A.
 
NOTE: In the top section level
head, the rule should be the same purple as the headings themselves.


In the XHTML version:
(in addition to the problems above)

1. The first page doesn't have any navigation links on the bottom. Should
at least have next.
> fixed; but now all point to
generic URI rather than version-specific. must point to version-specific.

2. The footer on each of the HTML pages says CD 01
> fixed

3. The link back to the main page points to cd01
> this now incorrectly points to the generic URI rather than cd02-specific
 
In the DITA source version:
(assume the same problems with hypertext links, URIs as in PDF)
1. the main html spec file is in this directory; not sure why it's duplicated.
> fixed

In the CHM version:
(same link and URI problems as in PDF)

1. Same footer problem as XHTML
> assuming it's fixed; haven't opened up windows.
 
 
 
On Jun 21, 2010, at 8:39 AM, Kristen
James Eberlein wrote:



Mary, you can get the latest ZIP file from
the following URL:
http://www.oasis-open.org/apps/org/workgroup/dita/download.php/38368/DITA1.2-CD02.zip

All the changes that you requested have been completed.

Best,

Kris

Kristen James Eberlein
Principal consultant, Eberlein Consulting
Secretary, OASIS DITA Technical Committee
Charter member, OASIS DITA Adoption Committee
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)

-------- Original Message --------

Subject:	[dita] Groups - DITA 1.2, CD 02 submission (DITA1.2-CD02.zip) uploaded
Date:	21 Jun 2010 12:04:35 -0000
From:	kris@eberleinconsulting.com
To:	dita@lists.oasis-open.org

 
Thanks to Seth Park for his work on the weekend:
 
Changes to PDF:
* Modified footer
* Modified styling of <example>
* Appendices each start on new page
 
 -- Kristen Eberlein
 
The document revision named DITA 1.2, CD 02 submission (DITA1.2-CD02.zip)
has been submitted by Kristen Eberlein to the OASIS Darwin Information
Typing Architecture (DITA) TC document repository.  This document is
revision #3 of DITA1.2-CD01-submission.zip.
 
Document Description:
 
 
View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=38368
 
Download Document:  
http://www.oasis-open.org/committees/download.php/38368/DITA1.2-CD02.zip
 
Revision:
This document is revision #3 of DITA1.2-CD01-submission.zip.  The document
details page referenced above will show the complete revision history.
 
 
PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.
 
-OASIS Open Administration