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: meta data proposal: <text:meta> vs. <text:meta-field>, etc.


I'm currently preparing a schema that contains the schema fragments for 
the proposals we approved since draft6.

While doing so, I found the following definition in the metadata proposal:

<define name="text-meta-attlist" combine="interleave">
	 	<ref name="xml-id">

It seems it shall attach an xml:id attribute to an <text:meta> element, 
but there is no such element. There is only a <text:meta-field> element.

I'm further wondering whether the following two definitions are 

<define name="draw-a-attlist" combine="interleave">
	 	<ref name="xml-id">

<define name="draw-image-attlist" combine="interleave">
	 	<ref name="xml-id">

The <draw:a> element always contains a drawing shape, which itself has 
an xml:id attribute. So, allowing an xml:id for the <draw:a> means that 
one can assign different metadata to the hyperlink that is bound to a 
drawing shape than to shape itself.

A similar situation exist for <draw:image>. It is always included in a 
<draw:frame>, which gets an xml:id, too.


Michael Brauer, Technical Architect Software Engineering
Sun Microsystems GmbH             Nagelsweg 55
D-20097 Hamburg, Germany          michael.brauer@sun.com
http://sun.com/staroffice         +49 40 23646 500

Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1,
	   D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering

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