-
Issue gchq/event-logging-schema#86 : Change PermittedOrganisation to be unbounded within PermittedOrganisations.
-
Issue gchq/event-logging-schema#85 : Add In enumeration to TermConditionSimpleType to support the SQL IN condition.
-
Issue gchq/event-logging-schema#84 : Change Hash in BaseFileComplexType to be unbounded to allow multiple hashes for a file to be recorded.
-
Issue gchq/event-logging-schema#80 : Change Location.Floor from xs:integer to xs:string to allow for floors with names, e.g. Ground.
-
Issue gchq/event-logging-schema#75 : Add Changes element to Update to allow recording of a change where the before/after state is not known or is too large to record, e.g. adding a user to an long allow-list.
-
Issue gchq/event-logging-schema#62 : Add the Id attribute to AnyContentComplextType, e.g.
Meta/@Id. This is to distinguish between multiple sibling Meta elements. -
Issue gchq/event-logging-schema#67 : Add optional Outcome to EventDetail/Unknown to allow the outcome of the event to be recorded.
-
Issue gchq/event-logging-schema#74 : Add Date to EmailComnplexType.
-
Issue gchq/event-logging-schema#69 : Add optional unbounded Data element to the following elements or complex types: AntiMalwareThreatComplexType, Door, EventTimeComplexType, LocationComplexType, NetworkOutcomeComplexType and SystemComplexType.
-
Refactor element EventDetail.Unknown into UnknownComplexType. Doesn't impact validity of XML documents.
-
Issue gchq/event-logging-schema#76 : Add Data element to Permission to allow for non-enumerated permission types. Add Create, Delete and Use to PermissionAttributeSimpleType.