All very good but how shall we choose?
The virtue of XML is that with minimal
coding skills and a handful of GUI, you can create tools that do useful work
for you.
The challenge is doing it for others.
len
-----Original Message-----
From: Robin Cover
[mailto:robin@oasis-open.org]
Sent: Friday, February 03, 2012
1:09 PM
To: Costello, Roger L.;
xml-dev@lists.xml.org
Cc: Robin Cover
Subject: Re: [xml-dev] Naming
conventions for a sampling of W3C and ISO XML vocabularies
Roger, the following resources might be of interest.
Both are
(way) out of date, but provide reasonable samples for
the
1. Naming and Design Rules
Naming and Design Rules (NDR) Specifications
- ACORD Naming and Design Rules (NDR)
- Danish XML Project: OIOXML Naming and Design Rules
- EPA Exchange Network XML Design Rules and
Conventions
- Federal XML Naming and Design Rules Project
- Global Justice XML Data Model (GJXDM) Naming and
Design Rules
- Hong Kong OGCIO Interoperability Framework for
E-Government
- IRS XML Naming and Design Rules
- OAGIS Naming and Design Rules (NDR)
- OASIS LegalXML Exchange Document Methodology,
Naming, and Design Rules (MNDR) Subcommittee
- Universal Business Language (UBL) Naming and Design
Rules
- UN/CEFACT XML Naming and Design Rules Technical
Specification
- US Department of the Navy XML Naming and Design
Rules
- US National Information Exchange Model (NIEM) NDR
2. Use of Camel Case for Naming XML and
XML-Related Components
http://xml.coverpages.org/camelCase.html
On Fri, Feb 3, 2012 at 8:48 AM, Costello, Roger L.
<costello@mitre.org> wrote:
Hi
Folks,
I am sampling some standard XML vocabularies to see what naming convention they
use. Below is what I've compiled thus far. What naming convention do you use?
1. XML Schema: all elements and attributes are camel case. Examples: maxOccurs,
elementFormDefault, substitutionGroup.
2. XSLT: all elements and attributes are lower-case, dash-separated. Examples:
apply-templates, exclude-result-prefixes, analyze-string.
3. Schematron: most elements and attributes are a single, lower-case word
(e.g., assert, rule, pattern). There is an element and an attribute with
multiple words (value-of, is-a). There are two elements that use camel case
(queryBinding and defaultPhase).
Notice that Schematron isn't consistent in its naming convention. Is that a bad
thing? Is it a good thing to have a consistent naming convention?
Why does XML Schema and XSLT have different naming conventions? They are both
W3C technologies. Does the W3C not have a policy on naming markup?
/Roger
_______________________________________________________________________
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
--
Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org
Staff bio: http://www.oasis-open.org/people/staff/robin-cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783
