NDR references NDR 5.INFO: IOexception during update file: file:/home/username/Dropbox/PDF_ARCHIVES/Responsibility/La%20nécessité%20d%20une%20nouvelle%20conception%20de%20la%20responsabilité%20au%20service%20de%20l%20en-commun-%20une%20approche%20à%20partir%20de%20champs%20spécifiques-%20genre,%20peuples%20autochtones,%20….pdfġ1:49:25 AM .LogUtils info Guidance has not yet been provided on metadata in JSON. Information that further qualifies primary data data about data. Each of these elements reference metadata IDs via their structures:metadata attribute.Ī data type for information that further qualifies primary data data about data. In the example below, a person is defined with two sub-properties: nc:PersonBirthDate and nc:PersonName. XML Instance exampleĪn element links to metadata by referencing each applicable metadata element’s ID ( structures:id) in inherited attribute structures:metadata. Other namespaces can define their own metadata elements and types and create references to them in NIEM release elements. Metadata types should not contain augmentation points. Elements can link to multiple metadata elements. There is no need to extend other metadata types in the model. Parent typeĪ metadata type must extend structures:MetadataType. For more specific metadata, a more descriptive name should be used, like PersonMetadataType. Metadata Types NameĪ metadata type should end with the representation term MetadataType.įor general metadata that may be applied to anything, the name MetadataType is sufficient. Use the attributes appinfo:appliesToElements and appinfo:appliesToTypes to limit the metadata element to one or more elements and/or types. For example, a metadata element constrained to type structures:AssociationType may be used by any association element. If a metadata element is constrained to a given type, then any element of that type or of a type that extends from that type may reference it. ApplicabilityĪ metadata element may be able to be used by any NIEM element or type, or it may be constrained to only certain ones.
TypeĪ metadata element must have a metadata type. For more specific metadata, a more descriptive name should be used, like PersonMetadata. Modeling guidance Metadata Elements NameĪ metadata element should end with the representation term Metadata.įor general metadata that may be applied to anything, the name Metadata is sufficient. Metadata on a higher level element, like nc:Person, may be considered to carry through to children elements, such as nc:PersonBirthDate, unless specifically overridden. It may not be necessary though to repeat the same references on each element in an instance. Metadata can be referenced from any element. The informational properties, like nc:EffectiveDate, have no special rules and are created and treated like any other property in the model. NIEM’s rules and guidance about metadata applies to those elements and types that act as the bundles, like element nc:Metadata and type nc:MetadataType. This simplifies the usage - an element references a metadata bundle once, rather than each of its contents individually. This means that if there are multiple elements that share the same metadata in an instance (for example, if they all come from the same database record that will have the same update date), then they can all link to the same metadata value(s) rather than duplicating the information.Ī metadata element in NIEM has a metadata type that bundles up one or more informational properties, such as nc:EffectiveDate and nc:LastUpdatedDate.
It might describe such things as who provided the content, and when it was last updated.īecause this is data that could potentially be provided about any and every property in the model (e.g., when the person name was last updated, when the address was last updated, when the vehicle tag was last updated, and so on), metadata should be defined separately from other types.
0 kommentar(er)
