RE: [xml-dev] Data model vocabulary

["Lists DMS" <lists@d-m-s.co.nz>]

Thank you Bill for sharing your conclusions.

Open formats have the obvious advantages, but depending on the context also
some disadvantages.

The main reasons for MXV's model format not being open:
- provide an *enterprise* vocabulary/XML schema design solution
- utilise COTS modelling tool features
  (for example visual diagramming, concurrent modelling, versioning and
impact analysis, import/export for the vocabulary AND XML schema models
- validate the XML document schema design against the vocabulary at schema
design time
  (for example, allow a BirthDate element only being nested under a Person
element, because the BirthDate is an attribute of the Person class in the
UML vocabulary.)
- embed context-sensitive business definitions in XML schema sourced from
latest vocabulary version at schema generation time
  (for example, the business definition of StartDate of an
EmploymentContract differs from StartDate of a Project, yet they use the
same Common Basic Component cbc:StartDate which does not have a
context-sensitive business definition itself)

Open vocabulary model formats commonly require iterative steps to convert
the open model versions into *complete* XML schemas. This works fine for a
single business domain and its release cycles where all its schemas are
pre-defined and published at once. UBL and its schema generation tools are a
good example for that.
For multiple business domains with independent release cycles, publishing
all schemas at once is not feasible. Neither is it feasible to define all
document schemas for all domains before generating the library schemas. The
schema design process for concurrent projects sharing the same enterprise
vocabulary needs more flexibility. In particular, designing a new "within
bounds" document schema after the library schemas have been finalised must
be possible. This however calls for a tighter real-time integration and
validation of the document schema design/generation with the vocabulary
model. The UML model format appears best to enable this real-time
integration to make MXV an enterprise vocabulary solution. At the price of a
static vocabulary model format of course.

Hope this helps.

Juerg


> -----Original Message-----
> From: William Velasquez [mailto:wvelasquez@visiontecnologica.com]
> Sent: Wednesday, 11 June 2014 3:00 a.m.
> To: xml-dev@lists.xml.org
> Subject: RE: [xml-dev] Data model vocabulary
> 
> Thank you for all your suggestions. I found them very insightful.
> 
> Just to share short conclusions:
> - Annotations on XML Schema: The simplest path and for sure is the path
> we'll take. It'd be nice if we use an standard for annotations.
> - AML: Sorry it's not XML, but very interesting for new projects.
> - MXV: What this product does is what we are trying to do, but our models
> are already built on XML Schemas, so there is little return for the
> investment required at this point. Why not making its model format open?
> You could still sell the tools.
> 
> 
> Again, thank you for sharing
> 
> 
> - Bill
> -----Mensaje original-----
> De: George Cristian Bina [mailto:george@oxygenxml.com] Enviado el: martes,
> 10 de junio de 2014 12:33 a. m.
> Para: William Velasquez; xml-dev@lists.xml.org
> Asunto: Re: [xml-dev] Data model vocabulary
> 
> Hi William,
> 
> The easiest thing to do is to just bring whatever additional data you have
> as annotations in your schemas.
> 
> Best Regards,
> George
> --
> George Cristian Bina
> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
> 
> On 6/10/14, 12:54 AM, William Velasquez wrote:
> > Hi,
> >
> > Currently my company is working on the creation of one application to
> navigate a data model currently represented as XML Schemas (a lot of them)
> and external Spreadsheets to keep its Data Dictionary in various
> languages.
> >
> > The first step we want to take, is to create unified Data Model files
> that combine the information stored in the schemas and the spreadsheets,
> and then create an application, using XML technologies, to allow the user
> navigate this model in multiple languages.
> >
> > Before spending a lot of time creating our own vocabulary and converting
> the XML schemas to it, I want to know if such vocabulary already exists.
> >
> > This is the requirements list:
> > - Must be an XML vocabulary
> > - Must Support standard XML Schema constraints: data types, cardinality,
> etc.
> > - Should Support for XPath validation (assertions) like Schematron,
> > RelaxNG
> > - Must be convertible from/to XML Schema
> > - Must support human-readable definitions of every element in various
> languages.
> > - Should be extensible to support custom properties for every element
> > - Desirable: support for modeling graphs (no just trees of data).
> >
> > Somebody here could recommend an XML vocabulary for this task?
> >
> > Is better to create a new vocabulary that supersedes XML Schema? Will it
> be useful for some of you?
> >
> > Thank you for sharing your wisdom,
> >
> >
> >
> > William David Velásquez
> > Director de Investigación y Desarrollo Visión Tecnológica S.A.S.
> > www.visiontecnologica.com
> > Tel (57 4) 444 7292
> > Movil (57) 311 709 8421
> > Follow me @williamda
> >
> >
> >
> >
> >
> > ______________________________________________________________________
> > _
> >
> > 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
> >
> 
> _______________________________________________________________________
> 
> 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