Hi Sandy, I think more clarification is needed about the association among the terms, "the schema", "a schema document", and an absolute SCD. The spec defines the absolute SCD in the following way, "An absolute schema component designator identifies a particular schema component; it consists of two parts: a designator for the assembled schema (a schema designator), and a designator for a particular schema component or schema components relative (a relative schema component designator) to that assembled schema." But at the same time, it gives "http://example.org/schemas/po.xsd#xscd(/type::purchaseOrderType)" as an example for an absolute SCD. Obviously, the first URI part refers to a schema document, not to a schema but the definition mentions it to be an assembled schema. Also, you say that,
> - Differences between SCD and SCP. SCD could be absolute, with an URI to > identify the schema, and a fragment for the component(s) in that schema. > Given that there is no defined way to resolve an URI to a schema (note: not > a schema document), it'll often be difficult (and not very useful) to work > with absolute SCDs. So according to you, the URI part doesn't need to be something like 'http://example.org/schemas/po.xsd' because it has to be a URI for an assembled schema. Can you please help me clarify the correct interpretation of absolute SCD? Why do you say that there's no defined way to resolve a URI to a schema? Here, are you reffering to the capability of Xerces of resolving a URI to a schema? Thanks in advance. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
