Media Types review for application/simple-filter+xml
hisham.khartabil at telio.no (Hisham Khartabil) Thu, 27 January 2005 15:03 UTC
From: "hisham.khartabil at telio.no"
Date: Thu, 27 Jan 2005 15:03:31 +0000
Subject: Media Types review for application/simple-filter+xml
In-Reply-To: <20050127131018.QAYU1713.lakermmtao09.cox.net@A31P>
References: <20050127131018.QAYU1713.lakermmtao09.cox.net@A31P>
Message-ID: <323D8A96-706C-11D9-949B-000D93C60BA0@telio.no>
X-Date: Thu Jan 27 15:03:31 2005
On Jan 27, 2005, at 2:12 PM, Scott Hollenbeck wrote: > Two comments. The first is on the namespace registration template > found in > section 8.2. It says: > > "This section registers a new XML namespace, as per guidelines in URN > document [4]." [4] is: > > [4] Mealling, M., "The IETF XML Registry", RFC 3688, January 2004. > > There are two problems with the above. > > 1. 3688 isn't really a URN document. It describes procedures to > register > URNs, but it is better described as the "IETF XML Registry". Ok. > > 2. Section 3.2 of 3688 describes what gets registered when registering > an > XML namespace. It says "XML Namespaces ... are named by a URI. They > have > no real, machine-parsable representation". Yet the template includes a > chunk of XML to be registered. It's not needed, so why is it > included? All > that needs to be registered is the > urn:ietf:params:xml:ns:simple-filter URN. That's how I've seen it done. Check out http://www.ietf.org/rfc/rfc3858.txt and http://www.ietf.org/internet-drafts/draft-ietf-simple-iscomposing -03.txt (in author's 48 hours) > > Second comment: the schema in section 6 includes several elements and > attributes that allow extensibility, including "<xs:anyAttribute > namespace="##other" processContents="lax"/>" and "<xs:any > namespace="##other" processContents="lax" minOccurs="0" > maxOccurs="unbounded"/>". I don't see any text in the document > describing > just how these extension elements and attributes are supposed to be > used, > though. You really should add some text to describe the extensibility > framework. What's allowed? What isn't? What needs to be done to > avoid > namespace collisions and version conflicts? Will add some text. Thanks, Hisham > > -Scott- > >> -----Original Message----- >> From: Hisham Khartabil [mailto:hisham.khartabil@telio.no] >> Sent: Wednesday, January 26, 2005 9:21 AM >> To: ietf-types@alvestrand.no >> Cc: Ted Hardie; Robert Sparks >> Subject: Media Types review for application/simple-filter+xml >> >> The SIMPLE Working Group requests a Media Type review for the >> following new type: >> >> - application/simple-filter+xml >> >> This is intended for the IETF tree, and specified in section >> 8.1 of >> http://www.ietf.org/internet-drafts/draft-ietf-simple-filter-format >> -04.txt >> >> Thanks, >> Hisham Khartabil >> SIMPLE WG Co-chair >
- Media Types review for application/simple-filter+… Scott Hollenbeck
- Media Types review for application/simple-filter+… Hisham Khartabil
- Media Types review for application/simple-filter+… Hisham Khartabil