OpenDocument Proposal - Revision history

VonHalenbach: Reverted edits by Yg6Q7h (Talk); changed back to last version by Colin Marquardt

2007-06-08T11:04:44Z

Reverted edits by Yg6Q7h (Talk); changed back to last version by Colin Marquardt

← Older revision		Revision as of 11:04, 8 June 2007
Line 28:		Line 28:
	No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.		No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.

	Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to		Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to & differ from SVG. For example, this helps in changing any existing implementations of that part of the standard to use a more SVG-friendly replacement. See [[OpenDocument SVG correspondence]].

Yg6Q7h at 05:15, 6 June 2007

2007-06-06T05:15:01Z

← Older revision		Revision as of 05:15, 6 June 2007
Line 28:		Line 28:
	No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.		No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.

	Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to & differ from SVG. For example, this helps in changing any existing implementations of that part of the standard to use a more SVG-friendly replacement. See [[OpenDocument SVG correspondence]].		Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to

Colin Marquardt: Reverted edits by Ns4Sso (Talk); changed back to last version by Bbb

2007-06-05T16:00:33Z

Reverted edits by Ns4Sso (Talk); changed back to last version by Bbb

← Older revision		Revision as of 16:00, 5 June 2007
Line 28:		Line 28:
	No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.		No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.

	Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to		Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to & differ from SVG. For example, this helps in changing any existing implementations of that part of the standard to use a more SVG-friendly replacement. See [[OpenDocument SVG correspondence]].

Ns4Sso at 15:42, 5 June 2007

2007-06-05T15:42:23Z

← Older revision		Revision as of 15:42, 5 June 2007
Line 28:		Line 28:
	No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.		No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.

	Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to & differ from SVG. For example, this helps in changing any existing implementations of that part of the standard to use a more SVG-friendly replacement. See [[OpenDocument SVG correspondence]].		Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to

Bbb: rv delete

2007-04-10T18:28:09Z

rv delete

← Older revision		Revision as of 18:28, 10 April 2007
Line 28:		Line 28:
	No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.		No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.

	Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to		Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to & differ from SVG. For example, this helps in changing any existing implementations of that part of the standard to use a more SVG-friendly replacement. See [[OpenDocument SVG correspondence]].

OcmFis at 17:05, 10 April 2007

2007-04-10T17:05:55Z

← Older revision		Revision as of 17:05, 10 April 2007
Line 28:		Line 28:
	No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.		No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.

	Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to & differ from SVG. For example, this helps in changing any existing implementations of that part of the standard to use a more SVG-friendly replacement. See [[OpenDocument SVG correspondence]].		Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to

Conversion script: link fix

2006-01-22T02:33:23Z

link fix

← Older revision		Revision as of 02:33, 22 January 2006
Line 1:		Line 1:
	OpenDocument is a proposed standard office-type document format for use in the EU etc.; see http://www.groklaw.net/article.php?story=20050130002908154 for more detail.		[[OpenDocument]] is a proposed standard office-type document format for use in the EU etc.; see http://www.groklaw.net/article.php?story=20050130002908154 for more detail.

	Currently it has its own custom format for graphics elements, similar to OpenOffice.org's Draw format, and also somewhat similar to SVG in some areas.		Currently it has its own custom format for graphics elements, similar to [[OpenOffice]].org's Draw format, and also somewhat similar to SVG in some areas.

	Clearly it would be good both for SVG, Inkscape, and the success of the OpenDocument standard, if OpenDocument were to use SVG to the extent possible, such that any SVG-compliant renderer could render the <svg> parts of the document.		Clearly it would be good both for SVG, Inkscape, and the success of the [[OpenDocument]] standard, if [[OpenDocument]] were to use SVG to the extent possible, such that any SVG-compliant renderer could render the <svg> parts of the document.

	(See also the inkscape-devel mailing list, subject "filter for inkscape and OpenDocument".)		(See also the inkscape-devel mailing list, subject "filter for inkscape and [[OpenDocument]]".)

	The current OpenDocument specification is available at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office .		The current [[OpenDocument]] specification is available at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office .

	To send comments, either click the "Send a comment" button on the above-referenced web-page, or use the office-comment@lists.oasis-open.org mailing list. Subscribe by sending the word "subscribe" in the body of mail to office-comment-request@lists.oasis-open.org.		To send comments, either click the "Send a comment" button on the above-referenced web-page, or use the office-comment@lists.oasis-open.org mailing list. Subscribe by sending the word "subscribe" in the body of mail to office-comment-request@lists.oasis-open.org.
Line 28:		Line 28:
	No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.		No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.

	Something that may be helpful in getting greater SVG interoperability in the OpenDocument standard is to document what bits of the OpenDocument specification correspond to & differ from SVG. For example, this helps in changing any existing implementations of that part of the standard to use a more SVG-friendly replacement. See [[OpenDocument SVG correspondence]].		Something that may be helpful in getting greater SVG interoperability in the [[OpenDocument]] standard is to document what bits of the [[OpenDocument]] specification correspond to & differ from SVG. For example, this helps in changing any existing implementations of that part of the standard to use a more SVG-friendly replacement. See [[OpenDocument SVG correspondence]].

PeterMoulder: * archives of mailing list discussion

2005-02-01T00:24:28Z

* archives of mailing list discussion

← Older revision		Revision as of 00:24, 1 February 2005
Line 9:		Line 9:
	The current OpenDocument specification is available at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office .		The current OpenDocument specification is available at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office .

	~~The discussion~~ list ~~for committee members is~~ office@lists.oasis-open.org~~, though I don't yet know how to see archives of this list~~.		To send comments, either click the "Send a comment" button on the above-referenced web-page, or use the office-comment@lists.oasis-open.org mailing list. Subscribe by sending the word "subscribe" in the body of mail to office-comment-request@lists.oasis-open.org.

	~~To send comments, either click the "Send a comment" button on the above-referenced web-page, or use the office-comment@~~lists.oasis-open.org ~~mailing list. Subscribe by sending the word "subscribe" in the body of mail to~~ office-~~comment-request@~~lists.oasis-open.org.		Archives are at http://lists.oasis-open.org/archives/office-comments/ ; similarly, archives of discussions between committee members are at http://lists.oasis-open.org/archives/office/ .

	From Daniel Carrera:		From Daniel Carrera:

PeterMoulder: * Refer to new page OpenDocument SVG correspondence.

2005-02-01T00:19:56Z

* Refer to new page OpenDocument SVG correspondence.

← Older revision		Revision as of 00:19, 1 February 2005
Line 25:		Line 25:
	time to raise a concern is right now. Send them a comment.		time to raise a concern is right now. Send them a comment.
	</blockquote>		</blockquote>

			No-one has yet done so; please edit this wiki page to indicate your progress in seeing/joining this discussion.

			Something that may be helpful in getting greater SVG interoperability in the OpenDocument standard is to document what bits of the OpenDocument specification correspond to & differ from SVG. For example, this helps in changing any existing implementations of that part of the standard to use a more SVG-friendly replacement. See [[OpenDocument SVG correspondence]].

PeterMoulder: * Supply info on how to subscribe

2005-01-31T23:53:06Z

* Supply info on how to subscribe

← Older revision		Revision as of 23:53, 31 January 2005
Line 1:		Line 1:
	OpenDocument is a proposed standard office-type document format; see http://www.groklaw.net/article.php?story=20050130002908154 for ~~its proposed use etc~~.		OpenDocument is a proposed standard office-type document format for use in the EU etc.; see http://www.groklaw.net/article.php?story=20050130002908154 for more detail.

	Currently it has its own custom format for graphics elements, similar to OpenOffice.org's Draw format, and also somewhat similar to SVG in some areas.		Currently it has its own custom format for graphics elements, similar to OpenOffice.org's Draw format, and also somewhat similar to SVG in some areas.

	Clearly it would be good both for SVG, Inkscape, and the success of the OpenDocument standard, if OpenDocument were to use SVG to the extent possible, such that any SVG-compliant renderer could render the <svg> parts of the document.		Clearly it would be good both for SVG, Inkscape, and the success of the OpenDocument standard, if OpenDocument were to use SVG to the extent possible, such that any SVG-compliant renderer could render the <svg> parts of the document.

			(See also the inkscape-devel mailing list, subject "filter for inkscape and OpenDocument".)

	The current OpenDocument specification is available at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office .		The current OpenDocument specification is available at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office .

	~~At the end of its first page~~, ~~you can see~~ how to ~~submit~~ comments. ~~(See also the inkscape~~-~~devel~~ mailing list~~, subject~~ "~~filter for inkscape and OpenDocument~~".)		The discussion list for committee members is office@lists.oasis-open.org, though I don't yet know how to see archives of this list.

			To send comments, either click the "Send a comment" button on the above-referenced web-page, or use the office-comment@lists.oasis-open.org mailing list. Subscribe by sending the word "subscribe" in the body of mail to office-comment-request@lists.oasis-open.org.

	From Daniel Carrera:		From Daniel Carrera:

	<blockquote>		<blockquote>
	~~You can leave a comment (click on "Send a comment"), join the TC, or~~
	~~simply just join their mailing list and participate in the discussion. The~~
	~~list is office@lists.oasis-open.org but I can't figure out how to~~
	~~subscribe. I know you don't have to be a TC member to participate, as I~~
	~~know of other people who aren't members and still contribute there.~~

	It is very important to get representation in the OASIS TC from multiple		It is very important to get representation in the OASIS TC from multiple
	interested parties. The goal is to make a format acceptable to everyone,		interested parties. The goal is to make a format acceptable to everyone,