OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ISSUE 162: XML schema type for @package of JavaImport/JavaExport is toorestrictive


http://www.osoa.org/jira/browse/JAVA-162

Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com

Inactive hide details for Raymond Feng---05/08/2009 05:16:20 PM---TARGET: Service Component Architecture Java Component ImplemeRaymond Feng---05/08/2009 05:16:20 PM---TARGET: Service Component Architecture Java Component Implementation Specification Version 1.1, Com


From:

Raymond Feng/Burlingame/IBM@IBMUS

To:

sca-j@lists.oasis-open.org

Date:

05/08/2009 05:16 PM

Subject:

[sca-j] [NEW ISSUE] XML schema type for @package of JavaImport/JavaExport is too restrictive





TARGET: Service Component Architecture Java Component Implementation Specification Version 1.1, Committee Draft 01/Public Review Draft 01

DESCRIPTION:

The non-normative description of the text has "xs:string" for the package attribute: <import.java package="xs:string" location="xs:anyURI"?/>. But the XSD uses xs:NCName: <attribute name="package" type="NCName" use="required"/>.

As we use the OSGi-like package import/export with directives, NCName is too restrictive. For example, [] or : is not valid for NCName.

PROPOSAL:
Use xsd:string for the package attribute.

Thanks,
Raymond



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]