Delete Phone Function

[GoogleCodeExporter]

From previous thread with Ben Kutsch

Clive: Phone Function still seems the same as Phone Description (Is there 
a clearer definition or just accept some duplication here and keep it in 
mind for later?)

Ben: Yeah, I think these two are about the same. For now we should just 
accept duplication. One thing though is function is definitely something 
short like after hours while Description could be something: "Phone 
staffed with a live person 24/7 except on Holidays. I see Description as 
much broader freer element, where function should be constrained at the 
Style level to mean common things.

Original issue reported on code.google.com by clivemjo...@gmail.com on 12 Feb 2010 at 4:36

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Isn't PhoneFunction the type of phone (Fax, Tollfree, etc) whereas Description 
can be more verbose (e.g. Gambling Addiction Hotline)?

Original comment by bleeb...@gmail.com on 13 Jan 2012 at 4:46

[GoogleCodeExporter]

The fields used in the AIRS Standards should be used in the AIRS XSD.  So, this 
is an opportunity for consistency.

Original comment by gglbwmn2...@gmail.com on 18 Jan 2012 at 4:44

[GoogleCodeExporter]

The description in that case is really the program name and would have its own 
place.

In the XSD, there is a place for a Phone Description, a Phone Type and a Phone 
Function. Page 20 of the scary XSD version of the Style Guide contains my guess 
of what it means !

Minor point, but the AIRS Standards lays out data required for a resource 
record -- it doesn't technically have to be placed within a designated field - 
though that does make it easier to search/follow

Original comment by clivemjo...@gmail.com on 18 Jan 2012 at 5:21

Attachments:

• AIRS_StyleGuide_FinalAugust2009_FullXSDVersion.doc

[GoogleCodeExporter]

Voting was in favor of making this change in 3.1.

Original comment by e...@ejahn.net on 17 Feb 2012 at 8:20

• Changed state: Accepted

[GoogleCodeExporter]

from style guide: 
PHONE DESCRIPTION

Definition

A phone description modifies a phone number. It is information that clarifies 
the purpose of the phone number, beyond what is communicated by the phone type. 
For example, it may explain that the phone number is the “administrative 
line”, the “after hours service” or the “central intake” number.

Preferred style examples

Administration
After Hours
Answering Service
Home
Hotline/Helpline
Information
Intake
Recorded Message
Talkline
Voice Mail
Work

Additional information

Generally, use Administration over Admin.  

PHONE TYPE

Definition

A phone type modifies the phone number. It is information that clarifies the 
purpose or classification of the phone number, but that applies to the 
“mechanical” type of phone into which an incoming call is connected. For 
example, the “phone type” would describe whether the number that has been 
dialed is heading to a cell phone or a fax machine.

Preferred style examples

Cell
Fax
Pager
Modem
TTY/TDD
Voice
Voice/Fax
Voice/TTY/TDD

Additional information

The logical assumption is that a call is going into a “normal” voice 
telephone unless indicated otherwise.

There may also be a need to sometimes indicate that a particular toll-free 
phone number may be in English only or Spanish only.

PHONE FUNCTION

This allows for any additional contextual information that might be required. 
For example, “Phone staffed with a live person 24/7 except on weekends and 
holidays when it is forwarded to answering service.”

Original comment by e...@ejahn.net on 17 Feb 2012 at 8:28

[GoogleCodeExporter]

I think the Style Guide needs to be changed, before we change the schema, or 
else we will make them out of sync.  

Phone Description = picklist (voice line, admin, after hours. etc.)
Phone Type = picklist (cell, fax etc.)
Phone Function = open text field with description

In my opinion, the the current Phone Function should be renamed "Phone 
Description".  The current Phone Description should be renamed to "Phone 
Function", and the current Phone Type should stay as is.  I think the problem 
originally cropped up when Function and Description were accidentally swapped 
when writing the Style Guide.  So, we should delay deleting Phone Function 
until the guide is fixed,  unless it can be fixed quickly before 3.1 comes out.

Original comment by e...@ejahn.net on 17 Feb 2012 at 8:37

• Changed state: WontFix

[GoogleCodeExporter]

Style guide changed in coordination with Clive Jones, and Phone Function and 
Phone Description titles are now switched in schema and style guide.  The 
description is now truly an open-ended description and function is now a style 
guide recommended picklist (not enforced by schema).

Original comment by e...@ejahn.net on 17 Feb 2012 at 8:58

• Changed state: Fixed

[GoogleCodeExporter]

discussed on 3/22 having an enumerated list for 4.0

Original comment by e...@ejahn.net on 22 Mar 2012 at 6:11