Re: [ubl] Proposed addition to 2.1 documented constraints - no schema location hints

[JAVEST by Roberto Cisternino <roberto@javest.com>]

Ok,
I am not aware of the requirement to use RELAX-NG, however the W3C XML Schema is a normative syntax for UBL.

Are we going to provide other normative syntaxes ?

---
G. Ken Holman ha scritto:

7.0.1.0.2.20091015161719.02700a68@wheresmymailserver.com" type="cite">At 2009-10-15 21:07 +0100, Stephen Green wrote:

Just reading Roberto's comments and I think I
agree but would go further: the implementations
of XML are really responsible for ensuring they
can handle the essentials of modern XML
technology like schemaLocation and multiple
prefixes and namespaces.

But schemaLocation isn't part of XML while the other parts are.

then why worry about what is a core feature of XML?
The use of schemaLocation is pretty much the usual
use of XML

I wholeheartedly disagree.  It is presumptive vocabulary outside of the reserved XML namespace.  Your line of reasoning makes it a hidden facet of the UBL vocabulary that would need to be accommodated explicitly in a RELAX-NG schema when it has a role no more important than a processing instruction, yet it is far more intrusive than a processing instruction.

whereas requiring the prevention of empty
elements is, I think, rather an obscure use of XML.

Fine.

But xsi:schemaLocation is W3C Schema baggage that doesn't belong in an XML *interchange* document:

Also processing instructions... but all of these hints are just to retrieve an XSD or a Stylesheet.

I am pretty sure that many software apply the XSI information automatically, so I think we should take care of this possible issue.

7.0.1.0.2.20091015161719.02700a68@wheresmymailserver.com" type="cite">
At 2009-10-15 12:55 -0400, I wrote:

> Having chosen the W3C Schema syntax to express the semantics of the document
> constraints has brought this in along as baggage ... if one were to create,
> say, a RELAX-NG model of the UBL schemas, that model would necessarily need
> to include in it a declaration of an optional xsi:schemaLocation to
> accommodate that it is implicitly allowed by our choice of schema
> expression.

It may be just fine for a document reserved for use within a particular system where such a hint is useful for that system.

But I sincerely believe platform dependencies have no role in an interchange document and can only introduce problems for recipients.

I agree it is not related to the interchange of data, but within simple systems where a sophisticated xml catalog resolver is not available the xsi schemaLocation could provide precious information expecially for instances where the namespace URI do not provide full information about the XML Schema version/customization/profile.

Instead, a simple system could be resolving the XML Schema location internally by just retrieving the schema name from the xsi:schemaLocation.    In fact the schema name could be the original name used for that kind of customization or profile.

So if the schema name is "UBL-Invoice-2.0-Watusi-Tall-1.0.xsd"  the receiver could match this file locally on their system using just the name and ignoring the original path of the sender.

I know this seems to be stupid or crazy, but implementations are very similar to my example around the world... :)

Hope this helps

Ciao!

7.0.1.0.2.20091015161719.02700a68@wheresmymailserver.com" type="cite">
But if the committee feels this isn't something we need to worry about, then my task of bringing the subject up for discussion is satisfied.

Thanks!

. . . . . . . . . . Ken

--
Upcoming: hands-on code list, UBL, XSLT, XQuery and XSL-FO classes
in Copenhagen Denmark and Washington DC USA, October/November 2009
Interested in other classes?  http://www.CraneSoftwrights.com/o/i/
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
Video lesson:    http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
Video overview:  http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

Nessun virus nel messaggio in arrivo.
Controllato da AVG - www.avg.com 
Versione: 8.5.421 / Database dei virus: 270.14.20/2440 -  Data di rilascio: 10/16/09 06:32:00

  

--

JAVEST by Roberto Cisternino

* Document Engineering Services Ltd. - Alliance Member * UBL Italian Localization SubCommittee (ITLSC), co-Chair * UBL Online Community editorial board member (ubl.xml.org) * Italian UBL Advisor

Roberto Cisternino

mobile: +39 328 2148123
skype: roberto.cisternino.ubl-itlsc
[UBL Technical Committee]	http://www.oasis-open.org/committees/ubl
[UBL Online Community]	http://ubl.xml.org
[UBL International Conferences]	http://www.ublconference.org
[UBL Italian Localization Subcommittee]	http://www.oasis-open.org/committees/ubl-itlsc
[Iniziativa divulgativa UBL Italia]	http://www.ubl-italia.org

PPlease consider the environment before printing this email.