RE: [office] Re: Custom Slide Shows: presentation:page-ids is unnecessary

["Dennis E. Hamilton" <dennis.hamilton@acm.org>]

Thorsten,

A brief follow-up (and I forgot to attract Christian's attention to this discussion). 

I think we can do 3.1-3.2 immediately in the draft for ODF 1.2 part 1.

The 3.3 comment is an independent matter and we need to look at it a bit more closely in terms of all the places where we might do that in having NCName (but not ID) type where we seem to use string type very heavily now.  The implications of deprecation have to be looked at more closely.

 - Dennis

-----Original Message-----
From: Thorsten Zachmann [mailto:t.zachmann@zagge.de] 
http://lists.oasis-open.org/archives/office/200812/msg00117.html
Sent: Saturday, December 13, 2008 03:42
To: ODF TC List
Cc: dennis.hamilton@acm.org; 'David Faure'
Subject: [office] Re: Custom Slide Shows: presentation:page-ids is unnecessary

Dear Dennis and TC members,

thanks for the detailed explanation. It had quite some interesting things in 
it I did not know.

http://lists.oasis-open.org/archives/office/200812/msg00102.html
> 3. WAYS TO TIGHTEN THE SPECIFICATION FURTHER IN ODF 1.2.
>
> 3.1 In section 18.334.19 <draw:page> use of draw:name attribute, add the
> sentence: "Note that for the <draw:page> to be referenced from a
> presentation:pages attribute, the draw:name attribute must be present."
>
> (We can leave it to implementations how that is assured if an user hasn't
> provided the value (yet).)
>
> 3.2 Bonus points: Delete the unnecessary source of confusion, "If not
> present, an application may generate a unique name."  (Applications may do
> all sorts of wonderful things.  This statement is not needed to enable that
> and it has apparently provoked poor solutions.)
>
> 3.3 In the schema for the draw:name attribute of <draw:page>, the value
> should probably be of type NCName, not string.  To accomplish this, it is
> probably best to deprecate string and specify that NCName is recommended
> whenever a new draw:name is created in an ODF 1.2 document, especially
> since <svg:title> and <svg:desc> are now available.  (Implementation
> observation, not for the spec: The same can be done when making a
> down-level document, but non-NCName strings should be preserved when
> working with a down-level input that is to stay down-level.)

I'm all for dropping the proposal when the above will be incoperated into ODF 
1.2. As Dennis has pointed out we already have what we need and it is easier 
for backward compatibility.

Thorsten

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php