Document:
HAVE 2.1.6 (Service Type changes)

Draft (A preliminary unapproved sketch, outline, or version.)

Details

Submitted By Mr. Darrell O'Donnell on 2012-05-08 6:56 pm UTC

Publication Type

None at this time.

Group / Folder

EM HAVE SC / Standards

Modified by

Not modified.

Copy

This document is not a copy.

Technical Contact

None at this time.

Download Count

75

Download Agreement

None at this time.

Description

for discussion at today's EM HAVE SC meeting.

The big change here is with ServicesType. I have attempted to create a way to support HAVE 1.0/HAVBED services listing while creating an extensible version as well. This effort is by no means complete. I need someone a bit more XML savvy on this one to assist.

I would like to create an example of the ServiceListItem that I created which has all of the HAVE/HAvBED services listed to show how the ExtensibleServicesList would work - that could negate the need for the HAVE1Services element totally.

STYLE QUESTIONS:
ATTRIBUTE vs. ELEMENT - I used some attributes and I am guessing that generally speaking HAVE should use elements - is this a formal decision or has it just evolved?

ID and IDREF - I haven't noticed any usage of ID/IDREF datatypes. Is this a general approach - I know that some groups don't much like them?