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.
BizTalk Orchestration Artifacts
Orchestration Port Types
Mult Part Message Type
Multi Part Message
Role Link Type
.net coding standards
BizTalk Receive Location
BizTalk Schema Specification
Functoid (Within Maps)
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]
§ Description = a document description maybe a project name or entity name or application name
§ Type of Schema: FLATFILE, EDI, XML
In addition to the “map” prefix appended to all BizTalk maps, the following naming convention should be followed:
“map” + [SourceSpec] + “To” + [DestinationSpec]
§ SourceSpec = name of source specification excluding the specification prefix “sch”
§ DestSpec = name of destination specification excluding the specification prefix “sch”