-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timestamp guidance and/or enforcement #11
Comments
I think that this is best handled by guidance in the documentation rather than schema enforcement, for reasons @bworrell mentions (patterning, regex, etc.) |
Just wanted to note that we'll want to coordinate this with several STIX tickets, notably: |
Agree that the timezone issue should be documentation on strongly suggested practice that it always be included in timestamps. |
I covered xs:date and xs:dateTime in #34. For uses of As for the other issues:
|
I agree with @johnwunder: I think the |
Why would @precision be invalid for patterns? @precision basically specifies how much of the DateTime typed field is relevant. You may want to say something similar in a pattern. For example, any File with a Created_Time occurring on 11/19/13. Technically you could do this by specifying a range of 11/19/13 00:00:00 to 11/19/13 23:59:59 but that seems kind of silly if we now have a @precision attribute to specify how much of the DateTime is relevant. Is there some issue that I am missing why we would want to discourage @precision in patterns? sean From: John Wunder <notifications@github.commailto:notifications@github.com> I covered xs:date and xs:dateTime in #34#34. For uses of cyboxCommon:DateTimeObjectPropertyType how about adding a precision attribute as I suggest in #34#34 and just re-use the cyboxCommon:DateTimePrecisionEnum that will be created? As for the other issues:
— |
… attribute Specifically, each of TimeObjectPropertyType, DateObjectPropertyType, and DateTimeObjectPropertyType had the following modifications applied: * Documentation explaining in more detail expected behavior for pattern comparisons * The addition of the precision attribute. This was accomplished by breaking the restriction out into a separate abstract type, and extending that type with the extra attribute. This is necessary because in XML schema the same complexType block cannot contain both a restriction and an enumeration In conjunction with commit fa7d54, this fixes #34
CybOX currently uses xs:dateTime and cyboxComon:DateTimeObjectPropertyType to store datetime information. DateTimeObjectPropertyType does not constrain values to xs:dateTime formats or enforce the use of timezone information, which is often essential when communicating cyber observable information.
Community members have identified the need to store more granular datetime information such as timezones information, which is not currently enforced by schema.
Pattern restricting the fields in schema may not be possible due to the CybOX patterning capability requirements (a regex does not conform to the xs:dateTime format), so we may just need to provide guidance on how best to store datetime information in both schema annotations and the specifications.
The text was updated successfully, but these errors were encountered: