get the facts: Ship XML or HTML? That is the question.

Jerome Gotangco jgotangco at gmail.com
Mon Jun 20 07:16:19 UTC 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Having said all this. Let's me now put technical issues aside and address why 
> I feel that a technical board should not be invoked in making the choice to 
> ship HTML. Although I do ask that one not forget the technical explanations I 
> have provided and that the artifacts presented also be kept in mind.

I tend to subscribe to the idea of invoking the technical board to
declare the unilateral decision of the team to ship in HTML rather than
XML for obvious technical and historical reasons. We are, after all, a
community-driven project. Mark said in a chat, that they cannot impose
on us something that would  be detrimental to a community-driven team,
but they can provide at least, direction. Of course, we can influence
that direction with our technical recommendations.


> My primary problem with invoking a technical board is that while I have 
> provided convincing technically founded arguments to justify my reasoning for 
> creating desktop-neutral source formats and shipping HTML in order to ensure 
> maximum interoperability between desktop environments and user agents, I have 
> yet to receive an apposing argument of the same nature. As this is the case, 
> I feel that no evidence has been present for me to reconsider my position 
> prior to invoking a technical board hearing. Since an opposing argument has 
> not been presented, I feel that the technical board has nothing to compare 
> and therefore no basis on which to make an educated decision between XML and 
> HTML.

Like I said, we invoke the TB to declare our position on this matter,
and not request for a decision that will probably disappoint the team
members.

> In closing I would like to make the following points:
> 
> 1.My proposal is not without history or consultation with the community. I 
> have therefore not made a unilateral decision.

This has been a unilateral decision of both past and present teams, as
seen in majority of meeting minutes and chat transcripts.

> Understanding of these terms and points is important and I believe will go a 
> long way to dispelling part of the current confusion.

Also, current subscribers to the ubuntu-doc list can refer to past
meeting minutes for the issues with regards to XML vs. HTML packaging:

https://wiki.ubuntu.com/DocumentationTeamMeetingSummary2
https://wiki.ubuntu.com/DocumentationTeamMeetingSummary


Jerome Gotangco


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCtm1CuJQObal7aaARAkKEAKCw0M6KF53/dstcE0IiTHl7ZCdOWACgkdUV
p6vk2klSVHd/r+0viET6ah0=
=NQRS
-----END PGP SIGNATURE-----




More information about the ubuntu-doc mailing list