WITSML Technical Team

1
WITSML Technical Team

• Tuesday 10 May
• Enumeration list discussions
• Standard formatting. Activity list
• Minor corrections to schema
• Sequence numbers in subscribe/publish
• Subscriptions should only be for single objects?
• Keep ability for multiple objects in a
  subscription easier to manage.

2
WITSML Technical Team

• Tuesday 10 May - Wednesday 11 May
• Well/WellLog object discussions
• Multiple start and end index elements, add uom to
  depths
• Align log and wellLog objects
• Base64 does not contain commas so can go in a
  comma separated list. Use space separation for
  array elements. All data types can be used in a
  regular ltdatagt element.
• ltdatagt123.4,4.56,23 21 34 45,A34DCB22C112,12.7ltdat
  agt
• ltdatagt element should be unlimited length

3
WITSML Technical Team

• Wednesday 11 May
• Unique identifiers for adding data to a server.
• Can we return the uid string from AddToStore? Use
  the existing suppMsgOut parameter to deliver the
  uid of the main object.
• Mega-discussion on API schema versioning
• Remove version from namespace and replace with an
  attribute for version?
• WSDL version is independent of API document
  version and API schema version
• Need to investigate use of 130 in WSDL namespace
• Trajectory stations to be able to handle planned
  vs actual
• Submit to a sub-group for analysis

4
WITSML Technical Team

• Wednesday 11 May
• Including binary or other sub-objects inside
  WITSML objects
• Need a group to investigate further
• Log data delivery issues. Runs, curves/log etc.
• Start discussions w/other service companies on
  WITSMLTT site.
• Add mandatory sequence number to Tubular
  Component

5
WITSML Technical Team

• Wednesday 11 May
• Version compatibility
• Schemas must be convertible to enable backward
  compatibility
• Can add enumerations, objects, attributes,
  members to unions
• New servers should be backward compatible with
  older clients
• New clients should be backward compatible with
  old servers
• Emphasis is on new software (server or client) to
  be backward compatible
• Produce v1.2 v1.3 mapping table for each object
  (POSC)
• Server Profile Discussions