[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emix-comment] Review of emix csprd02
Point 1: In the example you gave, Marty, you cite locations. See SchemaLocation. <xs:import namespace="urn:ietf:params:xml:ns:icalendar-2.0" schemaLocation="http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csprd02/xsd/iCalendar-availability-extension.xsd"/> Curiously enough, cutting and pasting that schema location into your browser will download that schema. We also reference GML which can be downloaded the same way. GML references other schemas, which can be referenced the same way. Shortening the url will give you the directory, like http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csprd02/xsd/ A tendency of some reviewers to use archived/cached/ obsolete versions of schemas, rather than referencing the actual links, has been the primary source of reviewer issues with examples. Note: In the OASIS process, which is what we are using, all examples are illustrative only, and non-normative. Checking examples for Gotcha errors is as constructive as spell-checking. THe artifacts, from the referenced locations, are normative. If there is any disagreement, the artifacts are the specification. Thanks tc "He who fights with monsters should look to it that he himself does not become a monster, and if you stare long into an abyss, the abyss also stares into you." - Fredrich Nietzche
From: Marty Burns [mailto:burnsmarty@aol.com] All, I am beginning to review the CSPRD02 version of EMIX. In this regard, I believe the following would be immensely helpful to me and other reviewers to understand and comment on the draft. Can you please provide the following: 1) referenced schemas in file form for coordinated review – in reviewing schemas, often problems occur in referenced schemas and this cannot be worked with when they are only available by url. I think this includes: <xs:import namespace="urn:ietf:params:xml:ns:icalendar-2.0" schemaLocation="http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csprd02/xsd/iCalendar.xsd"/> <xs:import namespace="urn:ietf:params:xml:ns:icalendar-2.0" schemaLocation="http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csprd02/xsd/iCalendar-wscal-extensions.xsd"/> <xs:import namespace="urn:ietf:params:xml:ns:icalendar-2.0" schemaLocation="http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/csprd02/xsd/iCalendar-availability-extension.xsd"/> <xs:import namespace="urn:un:unece:uncefact:codelist:standard:5:ISO42173A:2010-04-07" schemaLocation="http://www.unece.org/uncefact/codelist/standard/ISO_ISO3AlphaCurrencyCode_20100407.xsd"/> <xs:import namespace="http://www.opengis.net/gml/3.2" schemaLocation="http://schemas.opengis.net/gml/3.2.1/gml.xsd"/> 2) UML Model of the standard – there are other standards in progress that want to use EMIX and are working in UML. Availability of the correct UML to the standard is essential for these adopters (I am thinking specifically ASHRAE SPC201P which is working exclusively in UML). One would expect that the UML model matches the XMLSchema to the extent this is possible due to the different paradigms of UML and XSD. However, class hierarchy, aggregation, associations, and vocabulary should transfer properly. I recognize that the “substitutionGroup” facet will not transfer, but most else will. 3) There is one example in the draft – Appendix G. Which schema can be used to validate it – emix.xsd? power-products.xsd? Is there some description of what this example is about beyond the one sentence description? It would be useful to understand how it is composed of EMIX constructs? Is there an example of the use of the other major component resource? Cheers, Marty Dr. Martin J. Burns President Hypertek Inc. 14624 Country Creek Lane North Potomac, MD 20878 p-1(301)315-9101 c-1(301)257-9101 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]