Marcel,

On Tuesday 24 October 2006 18:13, Marcel Holtmann wrote:
> Hi Denis,
>
> > Based on your feedback a new DTD specification.  Hopefully it is getting
> > closer.
>
> looks good. However the text about hex encoded is not needed. All number
> based values can be either in hex or decimal or whatever. We will use
> the standard encoding to detect it. For example if it starts with 0x
> then it is hex, otherwise it is decimal.

Yes, the encoding is only relevant for the <text[8,16,32]> fields.  The rest 
of the attributes should not have it (this is hard to express in a DTD.)

>
> I am also not sure that the encoding attribute is needed. If you wanna
> encode binary data in text elements (at the moment only HID does this)
> then you can use \000 style encoding to do so.

This does not seem to be supported by expat, unless I'm missing something.  I 
also want to expand encoding to eventually have a base64 option, for space 
saving.  

How would this work, do you mean to just recognize if a character starts with 
\0xxx - Octal
\xx - Hex?

>
> Can also provide an example XML record for a really simple serial port
> profile. This will help to see how it looks like.
>
> Anyone willing to write a really specific and simple XML parser to
> convert these XML files into sdp_record_t structures. And or course a
> function that converts this structure back to XML.

Attached is a sample of OPUSH profile.  Attached also is the code to generate 
one of these and parse one of these as well (you can use attached sdptool 
patch to play with it)

The code is still pretty raw, but it should at least get us started.

>
> Regards
>
> Marcel
>

-Denis