I thought you might find these useful (courtesy of Aleksey Savateyev et. al.)

The table below includes prefixes/suffixes that should be used when naming BizTalk 2004 orchestration types and send and receive ports.   In addition, each prefix  must be followed by a logical object/entity name.  For the object name, follow these guidelines:

§         Spell out all words used in the name.  Do not abbreviate unless the object name becomes long.

§         Avoid the use of underscores within object names.

§         Object names shall be in standard “Hungarian” (upper and lower) case.

§         No spaces are allowed in object names.

 Schema/Document Definition Naming Convention

In addition to the “sch” prefix that is appended to all BizTalk specifications and document definitions, the following convention should be followed:

“sch” + [Description] + [Type of Schema]

where:

§         Description = a document description maybe a project name or entity name or application name

§         Type of Schema: FLATFILE, EDI, XML

 Map Naming Conventions

In addition to the “map” prefix appended to all BizTalk maps, the following naming convention should be followed:

“map”  + [SourceSpec] + “To” + [DestinationSpec]

where:

§         SourceSpec = name of source specification excluding the specification prefix “sch”

§         DestSpec = name of destination specification excluding the specification prefix “sch”