- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 12 Jun 2007 18:10:08 +0000
- To: public-sml@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4632 Summary: Use of IRIs Product: SML Version: unspecified Platform: PC URL: http://dev.w3.org/cvsweb/~checkout~/2007/xml/sml/build/s ml.html?content-type=text/html;%20charset=utf- 8#URI_Scheme OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Core+Interchange Format AssignedTo: cmsmcq@w3.org ReportedBy: plh@w3.org QAContact: public-sml@w3.org The current specification only talks about using URIs and doesn't say anything about IRIs. The WSDL 2.0 specification went through that debate already, so I suggest to follow their path: [[ This specification uses the XML Schema type xs:anyURI (see [XML Schema: Datatypes]). It is defined so that xs:anyURI values are essentially IRIs (see [IETF RFC 3987]). The conversion from xs:anyURI values to an actual URI is via an escaping procedure defined by (see [XLink 1.0]), which is identical in most respects to IRI Section 3.1 (see [IETF RFC 3987]). For interoperability, WSDL authors are advised to avoid the US-ASCII characters: "<", ">", '"', space, "{", "}", "|", "\", "^", and "`", which are allowed by the xs:anyURI type, but disallowed in IRIs. ]] http://www.w3.org/TR/2007/PR-wsdl20-20070523/#xmlSchemaAnyURI I would also proposed to change the name of the element from sml:uri to sml:address or something equivalent.
Received on Tuesday, 12 June 2007 18:10:10 UTC