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 Schema ValidationService


/ "David RR Webber" <david@drrw.info> was heard to say:
| Namespace I would urge should be used with extreme caution and in a
| minimilistic way.  Paradoxically CAM itself makes one single use of
| namespace to differentiate embedded attribute and predicate usage,
| that needs to be filtered separate from the rest of an XML instance itself.
| Otherwise - judicious use of XPath can easily differentiate the context
| and usage of fields in all but the most arcane syntax instances.

I'm reasonably confident that there are a lot of different viewpoints
on this issue. There's certainly a case to be made for reusing names
in multiple contexts and making sure that different contexts are
clearly identified.

| BTW - we are using this declaration pattern for the namespace which
| I would suggest is adequate - if you absolutely must have a namespace
| for your purposes:
|
|   xmlns:as="http://www.oasis-open.org/committees/cam";

If you define an XML vocabulary, you should use a namespace. OTOH, if
someone else has written a vocabulary with exactly the semantics you
need, re-use it.

As to the particular namespace pattern you've chosen, I'll point out that
ending your URI with "/" or "#" (if you have a desire to use the URI in
RDF) may have practical benefits.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

PGP signature



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