RE: Potential impact of registry project on schema guidelines

["Paul Spencer" <paul.spencer@boynings.co.uk>]

I agree. This was written by Carl Mattocks, based on the US Federal
Guidelines. There are two other sections that I also don't think relate to
the design of a registry, but rather to its use. I did not want to delete
any of Carl's document without discussion, so I added that these sections
are advisory only. It certainly does not affect the registry design. Thanks
for starting the discussion.

My own view is that these sections would belong in an eGov Naming and Design
Rules document, rather than in a document relating to the registry.

I have copied this to Carl and to the mailing list so that others have a
chance to join in.

Regards

Paul

> -----Original Message-----
> From: Ann Wrightson [mailto:ann.wrightson@csw.co.uk]
> Sent: 08 July 2004 08:40
> To: maewyn.cumming@cabinet-office.gsi.gov.uk; 'Anna Harvey'
> Cc: 'Paul Spencer'
> Subject: Potential impact of registry project on schema guidelines
>
>
> Maewyn, Anna,
>
> The following extract from Paul's recent document has strong potential
> impact on the GovTalk Schema Guidelines (even though it is non-normative).
> The plus side is compatibility with ebXML/UBL work and a consistent
> approach. However, in the current egov context I have doubts about the
> wisdom of insisting that datatypes have formal rather than
> business-domain-driven names, simply since it might form one more
> barrier to
> adoption.
>
> Quote:
>
> 2.8 Schema XML Component Name
> This section provides guidance on use of the registry, and is
> non-normative.
> To maximize understanding and facilitate automated analysis of schema
> components during harmonization efforts the selection of XML
> component names
> MUST be a thoughtful process involving business, functional, data
> and system
> subject matter experts. Use of ISO 11179 conventions is encouraged. For
> instance, XML components MAY be named after ISO 11179 data element names:
> XML Elements SHOULD be named after ISO 11179 data element definitions when
> business terms do not exist. XML Attributes SHOULD be named after
> ISO 11179
> data elements. XML Schema data types MUST be named after ISO 11179 data
> elements.
> Specifically,  ISO 11179 part 5 provides a standard for creating data
> elements. This standard employs a dot notation and white space to separate
> the various parts of the element and multiple words in a part
> respectively.
> In order to meet XML requirements for component naming, the ISO 11179 name
> must be converted to a Name Token. The ISO 11179 part 5 standard
> provides a
> way to precisely create a data element definition and name. Using or
> referencing this name in a schema provides analysts with a better
> understanding of XML component semantics, while using business terms as
> element names improves readability.
>
> Regards,
>
> Ann W.
>
> ***********************************************
> CSW Group Ltd
> 4240 Nash Court
> Oxford Business Park South
> Oxford
> OX4 2RU
> Tel: +44/0 1865 337400  Fax: +44/0 1865 337433
> Web: <http://www.csw.co.uk>
>
> Legal Disclaimer: <http://www.csw.co.uk/disclaimer.htm>
> ***********************************************
> CSW's XML Summer School 25th-30th July 2004 Wadham College, Oxford Further
> information: http://www.xmlsummerschool.com
> ***********************************************
>
>