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: Re: [office] form:enctype


Warren,

Warren Turkal wrote:
> We really need an issue tracker for all these issues. Does the OASIS
> system provide one? If not, would it be useful to setup a
> code.google.com (or somewhere else) project and use it's issue
> tracker?
>
>   
Yes, well, we have notice the need before. ;-)

Two problems:

1) There aren't any good but inexpensive systems for tracking changes in 
large text documents. Yes, ArborText (whatever their current moniker) 
and 3B2 (a $20K per seat SGML editing system) are reported to have that 
sort of abilities but both are fighter pilot sort of software. Either 
you are very, very good, or you would be better off with a Big Chief 
Indian Writing Tablet and some file folders.

2) Someone has to maintain the bug tracking system, whatever it is. And 
as Rob noted recently, none of us are project managers. ;-)

Actually there is a third problem.

With code it certainly is possible to "fix" some portion of the code and 
so long as you don't visit anything that feeds into that part of the 
code, you are relatively safe in assuming that it is correct. (And you 
can have test suites to make sure.)

That is probably true as a matter of theory for markup standards but I 
think it is a very dangerous assumption to make. I am iterating over the 
text about once a week in detail and I am still finding nuances that we 
all simply missed on other passes. To simply say some section is 
"correct" is to invite the discovery (always the day *after* 
publication) that we said that we *don't* use hyperlinks or something 
equally absurd.

Let me put it to you this way, I would much rather spend the time now to 
produce a very clean text than to have to spend years answering defect 
reports in ISO. Personally I want to see if we can bootstrap on top of 
ODF 1.2 to leap to ODF 2.0. It may be a version too far but assuming we 
do our job right on 1.2, it may just be doable. Fairly radical stuff 
lurking out there for 2.0. Cutting away a lot of cruft, consolidating 
structures to reduce the number of specialized implementation 
strategies, full incorporation of a number of other standards, etc. 
(Strictly my personal view but I think we are just now on the edge of an 
evolving notion of documents that will finally deliver to the local web 
browser/desktop the promise of markup that was made 20+ years ago.)

Hope you are having a great day!

Patrick
> wt
>
> On Wed, Apr 30, 2008 at 5:17 AM, Patrick Durusau <patrick@durusau.net> wrote:
>   
>> Greetings!
>>
>>  Well, form:enctype doesn't strike me as good naming but the other issue is:
>>
>>
>>     
>>> The default value of this attribute is
>>>       
>> |application/x-www-form-urlencoded|. Other suitable MIME types are also
>> acceptable.
>>     
>>>       
>>  We say "Other suitable MIME types are also acceptable." ???
>>
>>  Actually the HTML 4.0 reference resolves to a definition of the two MIME
>> types that can be specified for forms in HTML 4.0 and a note saying that the
>> behavior of other MIME types is undefined.
>>
>>  I think we should define the MIME types we are going to accept for forms.
>> Leaving it open is just inviting a lack on interoperability.
>>
>>  Hope everyone is having a great day!
>>
>>  Patrick
>>
>>  --
>>  Patrick Durusau
>>  patrick@durusau.net
>>  Chair, V1 - US TAG to JTC 1/SC 34
>>  Convener, JTC 1/SC 34/WG 3 (Topic Maps)
>>  Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
>>  Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
>>
>>
>>
>>  ---------------------------------------------------------------------
>>  To unsubscribe from this mail list, you must leave the OASIS TC that
>>  generates this mail.  You may a link to this group and all your TCs in
>> OASIS
>>  at:
>>  https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>>     
>
>   

-- 
Patrick Durusau
patrick@durusau.net
Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]