eNOAD
 
 
 

UPDATED: NOAD Schema 3.3 AnnouncementIndicator

10/30/2013 - 7 Years Ago

As part of ongoing efforts to enhance maritime domain awareness, we continue to improve handling of essential data contained within Notices of Arrival and Departure (NOAD).  On Tuesday, 26 November 2013, an updated NOAD schema will be released that incorporates improvements in consolidated longshore data reporting.  Also, beginning that date, submissions containing invalid or otherwise erroneous longshore activity data will be rejected, necessitating correction and resubmission.  When NOAD Schema 3.3 is released on 26 November 2013, NOAD Schema 3.1 and older versions will no longer be supported.



You will find a DRAFT copy of Schema 3.3 in Resource Files on the developers site at: https://developer.nvmc.uscg.gov/ . At this point it is being provided for informational and planning purposes only and it is still subject to change.



Please note that while every effort is being made to ensure these updates are final as of this mailing, there exists the possibility for additional changes as needed or at the direction of the program office.  Any such changes or additions will be made available as soon as they are provided to or identified by the SANS team.  The SANS team will announce when the test web service and the test email are available.



The following is a list of the specific changes from Schema 3.2 to Schema 3.3:



Affected Fields:

NOTICE|NOTICE_DETAILS|VERSION

Change Details:

The only acceptable value for this field under Schema 3.3 will be "3.3" (not including the quotation marks)



Affected Fields:

NOTICE|VESSEL|OPERATOR, NOTICE|VESSEL|COFR_OPERATOR, NOTICE|VESSEL|CHARTERER

Change Details:

The pattern constraint for these fields has been changed in Schema 3.3 to allow additional special characters such as: ", &, +, '



Affected Fields:

NOTICE|VESSEL|LONGSHOREMAN_WORK_DECLARATION

Change Details:

The acceptable values of Yes|No under Schema 3.2 have been changed to NOT PROVIDED|Yes|No under Schema 3.3



Affected Fields:

NOTICE|CREW_LIST|CREW|LONGSHOREMAN_WORK_DECLARATION

Change Details:

The acceptable values of Yes|No under Schema 3.2 have been changed to NOT PROVIDED|Yes|No under Schema 3.3



Affected Fields:

NOTICE|NONCREW_LIST|NONCREW|NATIONALITY, NOTICE|CREW_LIST|CREW|NATIONALITY_CODE, NOTICE|CREW_LIST|CREW|COUNTRY_RESIDENCE, NOTICE|CREW_LIST|CREW|COUNTRY_RESIDENCE_CODE, NOTICE|NONCREW_LIST|NONCREW|EMBARK_COUNTRY, NOTICE|NONCREW_LIST|NONCREW|EMBARK_COUNTRY_CODE, NOTICE|NONCREW_LIST|NONCREW|EMBARK_DATE

Change Details:

The attribute of nillable="true" that was included in Schema 3.2 for these fields has been removed under Schema 3.3 as it was in conflict with the attribute minOccurs="1", which remains in place under Schema 3.3.


Return to All NewsReturn
      Disclaimer    Freedom of Information Act (FOIA) Get Software      Links     
NVMC 6.5.3.6 (Build 3) - Released 7 May 2020 - Please have your desktop resolution set to 1024x768 or higher.