On 30/11/06, Caroline Maynard <[EMAIL PROTECTED]> wrote:
On 29/11/06, Pete Robbins <[EMAIL PROTECTED]> wrote: > > > This was introduced when opentype support was added. Is it needed? Don't > know. What do you expect to be returned when you try to get the type of > <entry>?? > I've considered your question, and I can't see a valid alternative. I don't intend to surface it through the PHP APIs, because we can exploit dynamic typing there, but I'll go and fix up all my big switches to handle the OpenDataObjectType case.
That's the conclusion I came to as well though this may mean that there is a hole in the spec here. There is another aspect to this - when the document containing the open
content is written out or serialized, it contains a lot of xsi:type="OpenDataObject" attributes. I can't see any use for these, and they look fussy and complicated. Do you agree they can and should be eliminated? If so I'll raise a JIRA.
Yes, there should be no need for them. Example input (where all the types are open):
<content type="xhtml" xml:lang="en" xml:base="http://diveintomark.org/";><http://diveintomark.org/> <div xmlns="http://www.w3.org/1999/xhtml";> <http://www.w3.org/1999/xhtml> <p> <i>[Update: The Atom draft is finished.]</i> </p> <div class="myclass"> <p>Hello</p> </div> </div> </content> example output: <content type="xhtml" lang="en" base=" http://diveintomark.org/";><lang>en</lang><base>http://diveintomark.org/ </base><http://diveintomark.org/> <div xsi:type="OpenDataObject"> <p xsi:type="OpenDataObject"> <i xsi:type="OpenDataObject">[Update: The Atom draft is finished.]</i> </p> <div xsi:type="OpenDataObject" class="myclass"> <class>myclass</class> <p xsi:type="OpenDataObject">Hello</p> </div> </div> </content> You'll no doubt notice a second problem with the output :-). I'll be raising a JIRA for that one too.
Ah a test!! Would it be that classs is serialized as both an attribute and an element?? --
Caroline
-- Pete
