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

 


Help: OASIS Mailing Lists Help | MarkMail Help

chairs message

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


Subject: Re: [chairs] Specification Namespaces? Standard XML SchemaValidation Service


FWIW,

I agree with both Duane and Norm, and my original suggestion was 
meant only for specifications using W3C XML Schema, not that any 
other specifications ought to use it, nor that there should an 
agreed-upon validation mechanism for all specs. I would just like a 
minimum validation bar established. The registry seems like an 
excellent mechanism for handling namespaces, at least those that wish 
to cite schemalocation="" That happens to be my preference over the 
general urn, but like validation, getting agreement on that is also 
fraught with differences of opinion.

Ciao,
Rex

At 7:39 AM -0700 4/16/04, Duane Nickull wrote:
>Checking validity is fairly easy.  One can test schemas against 
>several on line schema validators for the more common formats or 
>simply use Xerces and test an instance against the schema for 
>validity.
>
>I would recommend that we possibly use the OASIS registry/repository 
>for storing and referencing schemas from.  It is very easy since the 
>schema location attribute can be set to a URL encoded string in the 
>form:
>
>schemaLocation="http://registry.oasis-open.org/urlInterface/getRegistryObject?id=urn:uuid:5741757c-5e1b-6f12-297a-4322096d3836";
>
>the last part being the uuid of the registry object.  This one 
>actually works (click on it, you will retrieve a copy of a company 
>record)
>
>Placing all OASIS schemas into the registry also will perform a 
>rudimentary test for well formedness since the registry interface 
>supports some content validation.  This also would allow for schema 
>reference from instances or schema imports since the registry can be 
>considered a stable, persistent store for schemas and fragments 
>thereof.
>
>Duane
>
>Karl F. Best wrote:
>
>>The TAB has considered, and recommended to the Board, a similar 
>>suggestion in regards to the quality of the specifications that are 
>>submitted to the OASIS membership for consideration as an OASIS 
>>Standard.
>>
>>So it's being considered.
>>
>>I agree with Norm that checking may be difficult...
>>
>>-Karl
>>
>>
>>Norman Walsh wrote:
>>
>>>/ Rex Brooks <rexb@starbourne.com> was heard to say:
>>>| Can we establish a standard validation service for all OASIS
>>>| specification schemata, and require validation using this validation
>>>| service for a Committee Draft (or Committee Specification if we change
>>>| it back to that formulation to avoid confusion) and for Submission of
>>>| a Committee Draft to OASIS for approval of a candidate standard?
>>>
>>>I expect not. I can imagine TCs wanting to publish schemas in exactly
>>>one of the following: SGML DTDs, XML DTDs, RELAX NG, W3C XML Schema,
>>>Schematron, and perhaps a number of other things.
>>>
>>>Naturally, I thinkj TCs should make sure that the schemas the publish
>>>are valid against the schema that defines their schema language of
>>>choice. But adding a formal process to assure this seems awfully
>>>heavyweight to me.
>>>
>>>                                         Be seeing you,
>>>                                           norm
>>>
>>
>>
>
>--
>Senior Standards Strategist
>Adobe Systems, Inc.
>http://www.adobe.com


-- 
Rex Brooks
GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth
W3Address: http://www.starbourne.com
Email: rexb@starbourne.com
Tel: 510-849-2309
Fax: By Request


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