RE: [xml-dev] To namespace or not to Namespace ....

[w3c@drrw.info]

David,

Do you happen to have the data model available for the SQL database?

Most common SQL DBs will export this as an XSD.  That tends to be not very usable - but - there is good news!

The latest CAM v1.8 toolkit can be used to read in the SQL XSD - (use the asterix * mode in the complexType selection in CAM import template from XSD menu).

Then under Tools menu you will find a very cool renamer tool.   Run that - then load the resulting CXF file - save it as a template - then go to Files / Export / XSD from template - and it will write the refactored XSD schema back out for you.

Better yet - use Tools / Create dictionary - and make a canonical XML dictionary of your components.

Now back to namespaces - I would not use them personally unless forced - they introduce little but complexity and issues - but if you choose to use them - the renamer tool above lets you insert namespace of your choice.

Next you can also use the dictionary you just created - with the CAM blueprint approach to automatically build schema for you from components.

More information on how the CAM methodology can accelerate your information exchange development through the application of XML component dictionaries and blueprints can be found at the OASIS web site:

http://www.oasis-open.org/committees/document.php?document_id=36146

Enjoy, DW

-------- Original Message --------
Subject: [xml-dev] To namespace or not to Namespace ....
From: David <dlee@calldei.com>
Date: Mon, April 05, 2010 6:56 pm
To: xml-dev@lists.xml.org

I'm embarking on a project to create a schema (or more likely a
collection of schema(i?) ) to model a dataset.
This data is currently represented in a relational database as
semi-normalized in about 20 tables.
The underlying data is prety complex, but not in terms of
attributes/elements but rather some hidden 'business knowledge' which is
implied by
fields with coded values and things like shared "string pools".

The end result of this schema will be to be able to re-represent this
data as XML for mainly internal use, although may be published in some
form in the future
(only to partners, not the general public).

This is one of a handful of content sets that are already in XML or are
already translated to XML, its the 'last dog' of enterprise business
data to be translated to XML.

Up until now we've never used namespaces. We've been blissfully
unaffected by not using namespaces. XQuery and XSLT and pure Java
programs have had no problem with having no namespaces. The data is
typically in "silos" and while sometimes referenced together, is not of
the "module" sort intended to be embedded in other XML documents, but
rather fully standalone data (which may reference each other with loose
couplings).

I think I know the main reasons to use namespaces, and tons of reasons
to not to ...
Equally confused by Balisage's opening talk last year that (pardon the
paraphrase)
"Best Practices for XML"
1) "Always use Namespaces:"
N) "Never use Namespaces" ...

So whats a poor XML geek to do ?

Any *practical* suggestions ?


--
-------------------------
David A. Lee
dlee@calldei.com
http://www.calldei.com
http://www.xmlsh.org


_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php