Matches in LOV for { ?s <http://www.w3.org/2004/02/skos/core#historyNote> ?o. }
- ancestorOf historyNote B7677566e0be775abf7b0a72b9e9a564a.
- apprenticeTo historyNote B5009548c5acf30d33fdfa22ec159d96e.
- childOf historyNote B630f829345193d956afd3787335bc658.
- descendantOf historyNote B328349be4734a17f9127f98ca59451ec.
- descendantOf historyNote Bcae15cda0c2ada11e31e0b68b418725c.
- employedBy historyNote B3d56b88d0fdbfb4e3c0a8cbccf8eea49.
- employerOf historyNote B2516b2c66fa4df3f4a32ffaf6b7e1e73.
- grandchildOf historyNote B52c160df1a9c0972ea8fe3705da1ca13.
- grandparentOf historyNote B4a7223f93fdaf7bfd8cca82239b55587.
- knowsOf historyNote B775d8ce5267c775ffdec4f7cc6651c43.
- knowsOf historyNote Be9bc2d3c5782287905472a8245acd4fc.
- knowsOf historyNote Bff112681c9010eeb42eeadd942a7aad9.
- mentorOf historyNote B94430872f07e96e19724dd26fd33dd98.
- parentOf historyNote Bff5d7a5a670369eff0d5ccbfa84e2b19.
- participant historyNote B91b887f7861092ae57b0dc9c521b9b26.
- participantIn historyNote B4ea4f4e0e5da6ed4706456a9b59a4083.
- Wine historyNote B50088562c56f4bc08887023e2e24de3a.
- Wine historyNote B9bb52103a451f14aa69da7c41c8aead0.
- securityAlgorithms historyNote "Ontology extracted from the paper Security Ontology for Annotating Resources. [Kim et al. 2005] (See APPENDIX D. OWL Representations of the NRL Security Ontology) Security ontology to faciliate web service description and discovery.".
- Feature historyNote "Modified in version 3.1 : The cardinality constraints on feature code, feature class are relaxed on this class, and put on the specific subclass Geonames Feature. This class and attached properties can therefore be used for features not necessarily identified in the Geoanmes data base".
- geonamesID historyNote "Added in version 3.1".
- ontology historyNote "v2.1 : Relaxed domain constraints on several properties, replaced by Ontology Loose Coupling Annotations".
- ontology historyNote "v2.2 : Added spanish translations, provided by María Poveda Villalón".
- ontology historyNote "v2.21 : Added dutch translations plus 'interpreter' property suggested by Ronald Poell, along with minor corrections".
- ontology historyNote "v2.3 : Added :LanguageResource class, subclasses and properties. Added properties :tag :officialIn :fromCountry".
- ontology historyNote "v2.31 : Added more translations, language metadata, fixed typos plus cosmetic changes in the .ttl file".
- ontology historyNote "v2.32 : Added japanese translations, provided by Shuji Kamitsuna".
- ontology historyNote "v2.33 : Corrected minor typos, and added portuguese translations, provided by Mariana Curado Malta".
- ContentLocation historyNote "Creation / Maintenance Notes: A preservation repository should never refer to content that it does not control. Therefore, the PREMIS working group assumed that the repository will always assign the contentLocation, probably by program.".
- CreatingApplication historyNote "Creation / Maintenance Notes: If the object was created by the repository, assignment of creating application information should be straightforward. If the object was created outside the repository, it is possible this information could be supplied by the depositor. It might also be extracted from the file itself; the name of the creating application is often embedded within the file.".
- Dependency historyNote "Creation / Maintenance Notes: Recommended practice is for a repository to archive objects on which other objects depend. These may be sent by the submitter of the primary object, or they may in some cases be automatically obtained by the repository. For example, a markup file will often contain links to other objects it requires such as DTDs or XML Schema. If it does, these objects can often be identified by the link and downloaded by the repository.".
- Environment historyNote "Creation / Maintenance Notes: This information may be omitted when the repository is doing only bit-level preservation on the object. Rather than having each repository record this locally, it would be preferable to have a registry of environment information similar to proposed registries of format information. Repositories may choose to design mechanisms for inheritance, so that if the environment required for each file within a representation is identical to the environment recorded for the representation as a whole, it is not necessary to store this information in each file.".
- Fixity historyNote "Creation / Maintenance Notes: Automatically calculated and recorded by repository.".
- Format historyNote "Creation / Maintenance Notes: The format of a file or bitstream should be ascertained by the repository on ingest. Even if this information is provided by the submitter, directly in metadata or indirectly via the file name extension, recommended practice is to independently identify the format by parsing the file when possible. If the format cannot be identified at the time of ingest, it is valid to record that it is unknown, but the repository should subsequently make an effort to identify the format, even if manual intervention is required.".
- Hardware historyNote "Creation / Maintenance Notes: Hardware environment information can be very difficult to provide. Many different hardware environments may apply; there are a huge number of combinations of maker and type of CPU, memory, video drivers, and so on. Although at least one hardware environment should be recorded, it is not necessary to record them all and each repository will have to make its own decisions about which hardware environments to record. Because of the difficulty recording this information comprehensively, it would be optimal if central registries of environment information existed. In many cases the environment of a file object is directly associated with the format, making registry lookup by format feasible. In the absence of a global mechanism, repositories may be forced to develop their own local \"registries\" relating format to hwEnvironment.".
- Inhibitors historyNote "Creation / Maintenance Notes: Inhibitors are more likely to be present on an object ingested by the repository than applied by the repository itself. It is often not possible to tell that a file has been encrypted by parsing it; the file may appear to be ASCII text. Therefore, information about inhibitors should be supplied as metadata with submitted objects when possible.".
- PreservationLevel historyNote "Creation / Maintenance Notes: The preservation level may be assigned by the repository or requested by the depositor and submitted as metadata. The repository may also choose to record additional metadata indicating the context for the assignment of the preservation level.".
- SignificantProperties historyNote "Creation / Maintenance Notes: Significant properties may pertain to all objects of a certain class; for example, the repository can decide that for all PDF files, only the content need be preserved. In other cases, for example, for media art, the significant properties may be unique to each individual object. Where values are unique, they must be supplied by the submitter or provided by the curatorial staff of the repository.".
- Software historyNote "Creation / Maintenance Notes: If recording this explicitly, many different software environments may apply; for example, a particular object such as a PDF file may be viewable by several versions of several applications running under several operating systems and operating system versions. Although at least one software environment should be recorded, it is not necessary to record them all and each repository will have to make its own decisions about which software environments to record. Also, what appears to the user as a single rendering program can have many dependencies, including system utilities, runtime libraries, and so on, which each might have their own dependencies in turn. As with environment, metadata may be more efficiently managed in conjunction with a format registry either internal or external to a repository. In the absence of a global mechanism, repositories may be forced to develop their own local \"registries\" relating format to software environment.".
- hasCompositionLevel historyNote "Creation / Maintenance Notes: Composition level will generally be supplied by the repository, which should attempt to supply this value automatically. If the object was created by the repository, the creating routine knows the composition level and can supply this metadata. If the object is being ingested by the repository, repository programs will have to attempt to identify the composition level from the object itself or from externally supplied metadata.".
- hasPreservationLevelValue historyNote "Creation / Maintenance Notes: The preservation level may be assigned by the repository or requested by the depositor and submitted as metadata.".
- traffic historyNote "Ontology extracted from the paper Ontology Based Road Traffic Management. [Bermejo, A.J. et al. 2012]".
- 22-rdf-syntax-ns historyNote B5b8693e194dbf657100d7c3abb59cbca.
- 22-rdf-syntax-ns historyNote B759070d051bd597ae0b28673477cd726.
- 22-rdf-syntax-ns historyNote B7fe047849a2164187e11fed54819b85d.
- 22-rdf-syntax-ns historyNote Ba85a6a354426dada862b9e85b76d76a6.
- 22-rdf-syntax-ns historyNote Bdf564b68c8c82329db44adb20d5b27ea.
- 22-rdf-syntax-ns historyNote Be3bbb7be076795ffa40e7c2c82144f20.
- 22-rdf-syntax-ns historyNote Beae06443a96a058b19bf320e71ea29eb.
- eac-cpf.rdf historyNote B483fd7fe20b5c21da8bd1a0b0b38761d.
- eac-cpf.rdf historyNote B5fb02710d89d658c8fcd051736ef9596.
- eac-cpf.rdf historyNote Bbbf21320994c625cc3333623b61c254a.
- eac-cpf.rdf historyNote Bf49a6c3e681d91b736db18bdbfe76619.
- categoriaProfesional historyNote B432c508e0e84b9cfb418e7e7dd716008.
- categoriaProfesional historyNote B530772d1cb3e497146733d6bb24a0809.
- content historyNote "bibo:content has been deprecated; we recommend to use \"rdf:value\" for this purpose. Here is the rational behind this choice: http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#rdfvalue".
- code historyNote B5cf684b1b4214254475e80dac9c3c799.
- description historyNote B1a4a7e0a0006a7e48c0b3aa5a4eb948e.
- knowledgeGrouping historyNote B0d23a96ffd8b1bee134d3623daaed4da.
- knowledgeGrouping historyNote B79cbbacb9247c3b2bd0a57196a778a24.
- name historyNote B88cee85ee38189d9b972d5ff43355f68.
- name historyNote B9c52cd326f5ababb7f95e5f81ff19921.
- organizationalUnit historyNote B528159abac1d66e56af33d9833750e9e.
- organizationalUnit historyNote Bf307ca66126d5d5c8a4c61d7c153bd47.
- addition historyNote Bac252dd312dc0d4824a3c6e9b890dfa9.
- addition historyNote Bb60c97ff63ff5e29db1fc8a16b0e0882.
- precedingChangeSet historyNote Beeb52a7f0e074cf5a7e522cae24e646e.
- removal historyNote B3ffd259b36cb324ae9a929fcc58cb03e.
- removal historyNote Be4239149c44256b223c785b1bc484609.
- acquaintanceOf historyNote B7aab09a6a17ae8ea1e357689cfa30339.
- ambivalentOf historyNote Ba2ea264386746a822900506275ffbf77.
- ambivalentOf historyNote Bd62d466c39ef4a23d79215c06fd0a50b.
- antagonistOf historyNote B0c5e5d5b903ec7110ff4db6df823bc4d.
- closeFriendOf historyNote Ba13f6627ede845462a52c2142e9844a6.
- collaboratesWith historyNote Bb9188a09c6f5e9515f935a43a394ea33.
- colleagueOf historyNote Bcd5310a7c76219b9d50d42555a8c6433.
- enemyOf historyNote Bbfd97bf4331914d377f633b69a30512b.
- engagedTo historyNote Bb350f2a174da410239e9a7521e124efa.
- friendOf historyNote B0203d15453d7bf0fde88e743dd4bcad5.
- hasMet historyNote B1a3c499ef000ddc727524871423fa90a.
- influencedBy historyNote B846e73b7704c0310b7ca6eed7986b580.
- influencedBy historyNote Be3b8ff4a75480a08ab8128cfbc1e4b89.
- knowsByReputation historyNote Bdad2ddc6776e66f2beec98aac9dce4c7.
- knowsByReputation historyNote Bfbcb05f5901836fe31c72e67a2d129b6.
- knowsInPassing historyNote B90415b3033761579da62012839494e9e.
- lifePartnerOf historyNote B9680888594bbf1e011f22fb521fbfc1a.
- livesWith historyNote B4abaee5377bca08a562f4eb8d6d78cbd.
- lostContactWith historyNote B4da35e545d8d88bd8c15cea09f3a9759.
- neighborOf historyNote B5445f9759d19b5ffec086305069e00d7.
- neighborOf historyNote B9bfab0906d69eaa2dbbf999660133528.
- siblingOf historyNote B370d1a4028248352233ed7c100954c63.
- spouseOf historyNote B2d07ec8f2928c644dc549c0657c5c8d1.
- worksWith historyNote B32cee9415ebf64adf52880e9251dca90.
- worksWith historyNote B3709863ad54eb6ae9cbfc10c5b2415cb.
- wouldLikeToKnow historyNote Bc08d4ae0076aaeb5576916adb5984421.
- wouldLikeToKnow historyNote Bf7aea7a2ba8342f55234131786e25166.
- 0.7 historyNote B06bf073feeb1ad857bac09c2791401b2.
- 0.7 historyNote B61d68aa08e39628ba5e44ba5ff743bc0.
- 0.7 historyNote B95ac0d7ef084b88963c64c2848908ab1.
- 0.7 historyNote Bc1a20ebd0778fffa52e4ac3f770a6ba3.