OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tm-pubsubj message

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

Subject: RE: [chairs] your input on OASIS functionality enhancements

Norman, I agree completely on all your points. And another point I would
add about URI management, and that has really worried me and that I had
pointed out at the time, is that you can upload proprietary format
documents like MS Word or PDF, but not plain HTML pages with images - at
least last time I tried, which was quite long ago. Speak about standards

After struggling for a while with the problem, I completely gave up after
getting the following answer from OASIS "Webmaster" on April 8. No comment.

"I'm wondering if I set up an images folder on the server, if you could
forward me the images, I'll place them there. That way, perhaps (I'm
hoping) that if we change the html code in that page to the absolute link
it may work." (sic)

As a general feedback, I will add that the TC I was chairing at the time
(Published Subjects) was, when we migrate to Kavi, at a critical point of
its history, about to release a long overdue first deliverable, and in deep
debate about its future roadmap. We have a very small task force, and most
of our energy during spring was to figure out how to deal with the new
system, and the release of the first deliverable was really a mess. TC
members, and people interested in its work, have kept complaining since
about the lack of visibility of documents and TC status.

Somehow, the TC has been in standby since the same period. This is
certainly a simple coincidence, and I don't want to put the responsibility
of it on the system, there are many other reasons for it that we know of.
But clearly dealing with the new system was felt by the TC more as another
unnecessary burden on the top of the pile than a help.

Bernard Vatant
Senior Consultant
Knowledge Engineering
Mondeca - www.mondeca.com

> -----Message d'origine-----
> De : Norman Walsh [mailto:ndw@nwalsh.com]
> Envoye : vendredi 9 janvier 2004 20:44
> A : karl.best@oasis-open.org
> Cc : Chairs OASIS; jamie.clark@oasis-open.org; jeff.lomas@oasis-open.org
> Objet : Re: [chairs] your input on OASIS functionality enhancements
> / "Karl F. Best" <karl.best@oasis-open.org> was heard to say:
> | Last spring we rolled out the new collaborative tools from Kavi,
> | including membership roster management, balloting, email lists,
> | document repository, action items, etc.
> I remain utterly unimpressed. I will not go so far as to say that I
> think the new system is an unmitigated disaster, but it is, IMHO, just
> barely usable.
> The system is awkward, the website is cumbersome, and I think it has
> made the OASIS site less useful not only to TC members but also to the
> general public.
>  * There are parts chairs can't edit
>  * The list of documents presented to the public is still a flat
>    list lacking the hierarchy created by the chair or secretary
>  * There's no provision for navigation within the pages of the
>    of a single TC.
> As I have said before, the most significant bug is that it is
> impossible to publish documents with predictable URIs. I consider the
> site unusable for publishing important documents until this bug is
> fixed. (It works fine for meeting minutes and other things, but I
> cannot reliably publish specifications, schemas, or other documents
> that have internal URI references.)
> For example, I just published a working draft of the XML Catalogs
> specification for the Entity Resolution TC. The HTML version of that
> specification includes URIs for the original XML sources and a PDF
> version of the document.
> While I can upload all three documents,I cannot make the links work
> because I cannot predict what the URI for the XML or PDF versions will
> be when I am generating the HTML.
> And while we're talking about URIs, the URIs that Kavi creates really
> suck:

Granted, URIs are technically opaque, but that URI doesn't even give
me a hint about what committee created it.

I'd happily go back to the days when I could have published:


Nevermind functionality *enhancements*, the system still has an
absolutely critical flaws.

                                        Be seeing you,

Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

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