From: Denis KENZIOR <denis.kenzior@trolltech.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Proposed DTD
Date: Mon, 23 Oct 2006 10:25:51 +1000 [thread overview]
Message-ID: <200610231025.51818.denis.kenzior@trolltech.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
Marcel,
Here's the proposed DTD for SDP over XML. It closely follows the SDP profile
doc. I wasn't sure whether sequences can be empty (which makes no sense to
me), so I required at least one element in a sequence. The sizes for Text,
URLs and Sequences was dropped. It can easily be inferred from parsing the
document.
I'd like to get some feedback as to how to manage things like Record Handle,
and RFCOMM/L2Cap channels, etc. For record handle I think it is easy, just
remove that particular attribute and let the SDP server figure it out. For
RFCOMM channel, etc it is more tricky. Should we use a magic value or just
override it behind the scenes? We can always rely on the user to pick a
correct channel as well (and fail registration if they pick a channel that is
already in use)
-Denis
[-- Attachment #2: sdprecord.dtd --]
[-- Type: text/plain, Size: 998 bytes --]
<!ELEMENT SdpRecord (Attribute)*>
<!ELEMENT Attribute (Sequence|Alternate|UUID16|UUID32|UUID128|UINT8|UINT16|UINT32|UINT64|UINT128|INT8|INT16|INT32|INT64|INT128|BOOL|Text|URL|NIL)>
<!ATTLIST Attribute id CDATA #REQUIRED>
<!ELEMENT Sequence (Sequence|Alternate|UUID16|UUID32|UUID128|UINT8|UINT16|UINT32|UINT64|UINT128|INT8|INT16|INT32|INT64|INT128|BOOL|Text|URL|NIL)+>
<!ELEMENT Alternate (Sequence|Alternate|UUID16|UUID32|UUID128|UINT8|UINT16|UINT32|UINT64|UINT128|INT8|INT16|INT32|INT64|INT128|BOOL|Text|URL|NIL)+>
<!ELEMENT UUID16 (#PCDATA)>
<!ELEMENT UUID32 (#PCDATA)>
<!ELEMENT UUID128 (#PCDATA)>
<!ELEMENT UINT8 (#PCDATA)>
<!ELEMENT UINT16 (#PCDATA)>
<!ELEMENT UINT32 (#PCDATA)>
<!ELEMENT UINT64 (#PCDATA)>
<!ELEMENT UINT128 (#PCDATA)>
<!ELEMENT INT8 (#PCDATA)>
<!ELEMENT INT16 (#PCDATA)>
<!ELEMENT INT32 (#PCDATA)>
<!ELEMENT INT64 (#PCDATA)>
<!ELEMENT INT128 (#PCDATA)>
<!ELEMENT BOOL (#PCDATA)>
<!ELEMENT URL (#PCDATA)>
<!ELEMENT Text (#PCDATA)>
<!ATTLIST Text type (data|string) "string">
[-- Attachment #3: Type: text/plain, Size: 373 bytes --]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-10-23 0:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 0:25 Denis KENZIOR [this message]
2006-10-23 3:13 ` [Bluez-devel] Proposed DTD Marcel Holtmann
2006-10-23 3:59 ` Denis KENZIOR
2006-10-23 4:11 ` Marcel Holtmann
2006-10-23 4:31 ` Denis KENZIOR
2006-10-23 7:27 ` Marcel Holtmann
2006-10-24 5:47 ` Denis KENZIOR
2006-10-24 8:13 ` Marcel Holtmann
2006-10-24 6:47 ` Denis KENZIOR
2006-10-24 9:16 ` Marcel Holtmann
2006-10-24 8:09 ` Denis KENZIOR
2006-10-24 10:17 ` Marcel Holtmann
2006-10-30 13:27 ` Marcel Holtmann
2006-11-09 1:49 ` Denis KENZIOR
2006-11-10 18:09 ` Claudio Takahasi
2006-11-10 21:38 ` Claudio Takahasi
2006-11-13 1:14 ` Denis KENZIOR
2006-11-13 6:21 ` Marcel Holtmann
2006-11-13 6:37 ` Marcel Holtmann
2006-11-13 7:03 ` Denis KENZIOR
2006-11-13 7:17 ` Marcel Holtmann
2006-10-24 7:08 ` Denis KENZIOR
2006-10-24 9:13 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200610231025.51818.denis.kenzior@trolltech.com \
--to=denis.kenzior@trolltech.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox