Re: [xml-dev] Should one adopt the tag naming convention of anexisting X

Do whatever balances consistency and existing local practice to minimise mental gear-changing. �From the perspective of that gear-changing, naming is only one issue (a large one, but only one) and local practice may conflict with external recommendations. �You need to consider structural naming issues (hyphens, camel case etc), schema stylistic issues (optionality, indications of list length) and local terminology (simple words like order, list, part, etc may mean different things in different parts of the user community). �All of these things impact on the user experience of interacting with the vocabulary. The naming convention is only one of these. �

Greg

On Sat, Feb 4, 2012 at 6:14 AM, Costello, Roger L. <costello@mitre.org> wrote:

Hi Folks,

I am about to create an XML vocabulary.

My XML vocabulary will leverage (reuse) three existing, mature XML vocabularies.

So my XML instances will consist of tags that I created and tags from the existing, mature XML vocabularies.

For the tags that I create, what tag naming convention should I use?

Here are two possibilities:

1. I will create a my own tag naming convention, independent of the XML vocabularies that I will use.

2. I will adopt the tag naming convention of one of the XML vocabularies that I will use. (Which one?)

What do you recommend?

What are the tradeoffs?

/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