[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Not quite an I-D announcement
I misremembered the date for the IETF Internet-Drafts cutoff (this morning, 9am EST), so managed to write a trio of initial XPointer scheme drafts that now can't be published through the Internet-Draft process until November 22 or thereabouts. These documents specify schemes for use in XPointer-based fragment identifiers. These schemes, like other XPointer Framework schemes, are designed primarily for use with the XML Media Types defined in RFC 3023, to identify locations within a given XML representation of a resource. If anyone would like to make comments on the initial versions of these documents prior to their submission as Internet-Drafts, I'd be happy to hear them. In many ways, this makes more sense than having a single person publish initial Internet Drafts anyway, and many of these ideas emerged from various xml-dev discussions. The three not-quite drafts are: -------------------------------------- The XPointer xinclude1() Scheme http://simonstl.com/ietf/draft-stlaurent-xinclude-frag-00.html The xinclude() scheme notifies an XPointer processor whether the creator of the XPointer intended for XInclude 1.0 processing to take place. -------------------------------------- The XPointer xmlns-local() Scheme http://simonstl.com/ietf/draft-stlaurent-xmlns-local-frag-00.html The xmlns-local() scheme notifies an XPointer processor that it should include all of the namespace binding context defined for the element containing the XPointer in the namespace binding context for the XPointer. -------------------------------------- The XPointer content-type() Scheme http://simonstl.com/ietf/draft-stlaurent-content-type-frag-00.html The content-type() scheme notifies an XPointer processor whether the creator of the XPointer intended for a particular pointer part to apply to a resource representation which uses a particular MIME content type identifier. --------------------------------------- All three of these drafts are designed primarily to ask questions rather than provide conclusive answers in any event, so limbo may be an appropriate status. I consider all of these completely experimental at this stage, but it seems worth publishing them now, while the work on RFC 2396 revision is just getting started and as XPointer work winds down. ------------- Simon St.Laurent - SSL is my TLA http://simonstl.com may be my URI http://monasticxml.org may be my ascetic URI urn:oid:1.3.6.1.4.1.6320 is another possibility altogether
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|