RE: [xml-dev] Data model vocabulary

[William Velasquez <wvelasquez@visiontecnologica.com>]

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
>