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


Help: OASIS Mailing Lists Help | MarkMail Help

opendocument-users message

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

Subject: RE: [opendocument-users] Implementor notes

Hi Dennis,

I didn't forget about your hard work on the wiki ;-)

The reason I suggested xhtml and atom for the implementation notes
is that the wiki is read-only for non OIC members. It sure is a great place
to summarize the issues found and analyzing the spec, absolutely.

But I'm not sure if it still scales if we have to maintain the links to notes
(perhaps in several languages) and bug tracks of various products, as well
as general remarks etc. Or maybe that's just me dreaming of a perfect
world again :-)

Anyway, regardless of all this, I think we can all agree that having a spec
published XHTML opens new opportunities :-)


(it would be great if _all_ standards were made available as XHTML with
anchors to relevant parts)

From: Dennis E. Hamilton [dennis.hamilton@acm.org]
Sent: Thursday, June 18, 2009 12:50 AM
To: 'Sander Marechal'; Hanssens Bart
Cc: opendocument-users@lists.oasis-open.org
Subject: RE: [opendocument-users] Implementor notes

Sander, some additional information related to this thread:

 1. Something like this is being done on the OIC TC by putting the ODF 1.1
specification up on a Wiki.  Some initial fragments can be seen at
<http://wiki.oasis-open.org/oic/SpecAnalysis>.  The design is intended to
support linking to separate annotation pages that address matters of concern
to the ODF Interoperability and Conformance (OIC) TC.

 2. It seems to me that the reorganization undertaken in ODF 1.2 Part 1 is
so massive that it is unlikely to be able to preserve the structure
(relative URLs and fragment IDs).  In particular, attributes are no longer
described in-line with the elements that have them and there are no schema
fragments in the ODF 1.2 Part 1 text.  (The Wiki is HTML 4.01, according to
the link on the bottom of every page.)

 3. Although the OIC ODF 1.1 anchors are systematic, I would not claim them
to be easily predictable.  The good news is that every section, paragraph,
un-numbered subsection, list item, image, and schema fragment has a
permalink that can be used to make a cross-reference to that content when
commenting, making web-organized implementation notes, etc.  (I had my eye
on that specific application when I experimented with ways to move ODF 1.1
to the OIC Wiki.)

 4. When there is a stable-enough 1.2 specification, there might be ways to
cross-reference between the on-line 1.1 and an on-line 1.2 so that one can
trace the treatment of a feature in one to its treatment in the other.  It
feels too soon to start anything like that.

-----Original Message-----
From: Sander Marechal [mailto:s.marechal@jejik.com]
Sent: Wednesday, June 17, 2009 15:23
To: Hanssens Bart
Cc: opendocument-users@lists.oasis-open.org
Subject: Re: [opendocument-users] Implementor notes

Hanssens Bart wrote:
> Well, if OASIS publishes an XHTML version of the spec, with predictable
> anchors for every numbered section, every implementer could publish
> an Atom stream with a link to that particular section.

Yes, that is an excellent suggestion IMHO. Could the ODF interop TC help
with this? It seems like a very practical thing that doesn't add much
value to the standard by itself but which could really help developers
with interop.

Bonus points if the anchors are persistent over different ODF versions
when a certain element or section hasn't changed in the spec.

Sander Marechal

To unsubscribe, e-mail: opendocument-users-unsubscribe@lists.oasis-open.org
For additional commands, e-mail:

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