LOV |

LOV

Matches in LOV for { ?s <http://www.w3.org/2004/02/skos/core#editorialNote> ?o. }

Showing items 1 to 83 of 83 with 100 items per page.

FeedOrEntry editorialNote "This class should probably be anonymous. It is really only used to make it easier to write the ontology, as it is helps regroup all the relations that are in common between a awol:Feed and an :Entry.".
TextContent editorialNote "Should awol:TextContent really be a sublcass of :Content ? If it is then all the properties that apply to text will also apply to :Content. If we want a :Content to be able to take properties such as :etag, this does not seem quite relevant to anything that is related to what should be the object of :title, :subtitle or :summary. Neither does :src really seem to be a relation that really makes sense there".
source editorialNote "This is indeed not really needed. But it is useful for explaining the relation between the source element in rfc 4287 and the awol:entry relation. It has educational value.".
term editorialNote "should specify that there is exactly one term".
title editorialNote "Reto argues that a Title should have any content attached to it. One should for example allow picture for people who can't read or audio titles for people who cannot write. This would of course make the semantics be a lot more lax that the rfc 4287 syntax allows. ".
1 editorialNote "Note that this assertion says only in <em xmlns=\"http://www.w3.org/1999/xhtml\" xmlns:acrt=\"http://privatealpha.com/ontology/certification/1#\" xmlns:bibo=\"http://purl.org/ontology/bibo/\" xmlns:dct=\"http://purl.org/dc/terms/\" xmlns:foaf=\"http://xmlns.com/foaf/0.1/\" xmlns:owl=\"http://www.w3.org/2002/07/owl#\" xmlns:rdf=\"http://www.w3.org/1999/02/22-rdf-syntax-ns#\" xmlns:rdfs=\"http://www.w3.org/2000/01/rdf-schema#\" xmlns:skos=\"http://www.w3.org/2004/02/skos/core#\" xmlns:vann=\"http://purl.org/vocab/vann/\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema#\">informal terms what the certification is, and what it allows me to do. This vocabulary is intended neither to describe the privileges granted by the certification, nor to describe the artifact that embodies the certification. It simply connects the subject of the certification to the issuing authority and their official serial number of the account.".
Agent editorialNote "BIBO assert that a dcterms:Agent is an equivalent class to foaf:Agent.\nThis means that all the individuals belonging to the foaf:Agent class\nalso belongs to the dcterms:Agent class. This way, dcterms:contributor\ncan be used on foaf:Person, foaf:Organization, foaf:Agent and foaf:Group.\nEven if this link is not done in neither the FOAF nor the DCTERMS ontologies this is a wide spread fact that is asserted by BIBO.".
Post editorialNote "This is a subclass of org:Organization by virtue of the fact that a post may have multiple holders at the same time, or over a period of time.".
Agent editorialNote "Entity properties: May hold or grant one or more rights. May carry out, authorize, or compel one or more events. May create or act upon one or more objects through an event or with respect to a rights statement.".
ApplicableDates editorialNote "Rationale Specific dates may apply to the particular rights statement.".
CreatingApplication editorialNote "Rationale: Information about the creating application, including the version of the application and the date the file was created, can be useful for problem solving purposes. For example, it is not uncommon for certain versions of software to be known for causing conversion errors or introducing artifacts. It is also useful to determine which rendering software is available for the digital object. For example, if you know that the Distiller program created the PDF file, you know it will be renderable with (among other programs) Adobe Reader.".
Environment editorialNote "Rationale: Environment is the means by which the user renders and interacts with content. Separation of digital content from its environmental context can result in the content becoming unusable.".
Event editorialNote "Entity properties: Must be related to one or more objects. Can be related to one or more agents. Links between entities may be recorded from either direction and need not be bi-directional.".
EventOutcomeDetail editorialNote "Rationale: An event outcome may be sufficiently complex that a coded description is not adequate to document it.".
Format editorialNote "Rationale: Many preservation activities depend on detailed knowledge about the format of the digital object. An accurate identification of format is essential. The identification provided, whether by name or pointer into a format registry, should be sufficient to associate the object with more detailed format information.".
FormatRegistry editorialNote "Rationale: If central format registries are available to the preservation repository, they may provide an excellent way of referencing detailed format information.".
Inhibitors editorialNote "Rationale: Format information may indicate whether a file is encrypted, but the nature of the encryption also must be recorded, as well as the access key.".
Object editorialNote "Entity properties: Can be associated with one or more rights statements. Can participate in one or more events. Links between entities may be recorded from either direction and need not be bi-directional.".
Object editorialNote "Entity types: Representation: A digital object instantiating or embodying an Intellectual Entity. A representation is the set of stored digital files and structural metadata needed to provide a complete and reasonable rendition of the Intellectual Entity. File: A named and ordered sequence of bytes that is known to an operating system. Bitstream: Contiguous or non-contiguous data within a file that has meaningful properties for preservation purposes.".
ObjectCharacteristics editorialNote "Rationale: There are some important technical properties that apply to objects of any format. Detailed definition of format-specific properties is outside the scope of this Data Dictionary, although such properties may be included within objectCharacteristicsExtension.".
PreservationLevel editorialNote "Rationale: Some preservation repositories will offer multiple preservation options depending on factors such as the value or uniqueness of the material, the \"preservability\" of the format, the amount the customer is willing to pay, etc. The context surrounding the choice of a particular preservation option for an object may also require further explanation.".
Signature editorialNote "Rationale: A repository may have a policy of generating digital signatures for files on ingest, or may have a need to store and later validate incoming digital signatures.".
SignificantProperties editorialNote "Rationale: Objects that have the same technical properties may still differ as to the properties that should be preserved for future presentation or use.".
Storage editorialNote "Rationale: It is necessary for a repository to associate the contentLocation with the storageMedium.".
TermOfGrant editorialNote "Rationale: The permission to preserve may be time bounded.".
TermOfRestriction editorialNote "Rationale: The current definition of termOfGrant is \"time period for the permissions granted.\" This allows for expressing information about the rights granted, but some repositories may need to express timebounded restrictions like embargoes. If this is applicable startDate for the beginning of the embargo and endDate for the end of the embargo should be recorded.".
hasAgent editorialNote "Rationale: Digital provenance requires often that relationships between agents and events are documented. The role of the associated agent may need to be documented. For this, a SKOS vocabulary can be used. The LOC will publish a vocabulary at http://id.loc.gov/, denoting the agent's role. These vocabulary will publish the concepts also as subproperties to the linkingAgent property, for denoting the role of the agent in the event or rightsstatement.".
hasCompositionLevel editorialNote "Rationale: A file or bitstream can be encoded with compression, encryption, etc., or bundled with other files or bitstreams into larger packages. Knowing the order in which these actions are taken is important if the original object or objects must be recovered.".
hasContentLocationType editorialNote "Rationale: To understand the meaning of the value it is necessary to know what location scheme is used.".
hasCopyrightJurisdiction editorialNote "Rationale: Copyright law can vary from country to country.".
hasDependencyName editorialNote "Rationale: It may not be self-evident from the dependencyIdentifier what the name of the object actually is.".
hasEnvironmentCharacteristic editorialNote "Rationale: If multiple environments are described, this element can help to distinguish among them.".
hasEventOutcome editorialNote "Rationale: A coded way of representing the outcome of an event may be useful for machine processing and reporting. If, for example, a fixity check fails, the event record provides both an actionable and a permanent record.".
hasEventOutcomeDetailNote editorialNote "Rationale: Additional information in textual form may be needed about the outcome of the event.".
hasEventType editorialNote "Rationale: Categorizing events will aid the preservation repository in machine processing of event information, particularly in reporting.".
hasIdentifierType editorialNote "Rationale: Identifier values cannot be assumed to be unique across domains. The combination of identifierType and identifierValue should ensure uniqueness.".
hasMessageDigest editorialNote "Rationale: This must be stored so that it can be compared in future fixity checks.".
hasObject editorialNote "Rationale: Digital provenance often requires that relationships between objects and events are documented. / Rights statements must be associated with the objects to which they pertain, either by linking from the rights statement to the object(s) or by linking from the object(s) to the rights statement. This provides the mechanism for the link from the rights statement to an object. For denoting the role of the object, when related to an event,one can extend this ontology be defining your own subproperties, such as those given by http://id.loc.gov/vocabulary/preservation/eventRelatedObjectRole.".
hasPreservationLevelRole editorialNote "Rationale: Repositories may assign preservationLevelValues in different contexts which must be differentiated, and may need to record more than one context.".
hasPreservationLevelValue editorialNote "Rationale: Some preservation repositories will offer multiple preservation options depending on factors such as the value or uniqueness of the material, the \"preservability\" of the format, the amount the customer is willing to pay, etc.".
hasRelatedObjectSequence editorialNote "Rationale: This semantic unit is particularly useful for structural relationships. In order to reconstruct a representation, it may be necessary to know the order of components with sibling or part-whole relationships. For example, to render a page-image book, it is necessary to know the order of files representing pages.".
hasRightsDocumentationRole editorialNote "Rationale: This information distinguishes the purpose of the supporting documentation especially when there are multiple documentation identifiers.".
hasSignatureEncoding editorialNote "Rationale: These values cannot be interpreted correctly if the encoding is unknown.".
hasSignatureMethod editorialNote "Rationale: The same algorithms must be used for signature validation.".
hasSignatureValidationRules editorialNote "Rationale: The repository should not assume that the procedure for validating any particular signature will be known many years in the future without documentation.".
hasSoftwareType editorialNote "Rationale: Several different layers of software can be required to support an object.".
hasStatuteJurisdiction editorialNote "Rationale: The connection between the object and the rights granted is based on jurisdiction.".
hasStorageMedium editorialNote "Rationale: The repository needs to know the medium on which an object is stored in order to know how and when to do media refreshment and media migration.".
identity editorialNote "\n It turns out that this relation is unintuitive to write out and to name.\n One should instead use cert:key\n ".
B3915bf75909dd8606db2182176c44a19 editorialNote "The label is language dependent and seems less important".
aggregates editorialNote "This relation is not visible in the rfc4287 xml. It is not clear that it is needed either, though it can help simplify queries. See also N3 rule that defines this precisely ".
generator editorialNote "The domain should really just be awol:Version. I don't see why Entries can't have an generator too (especially as atom:entry can be a top level content).".
icon editorialNote "The domain should really just be awol:Version. I don't see why Entries can't have an icon.".
label editorialNote "Should this be functional? Given the language sensitivity of the label".
logo editorialNote "The domain should really just be awol:Version. I don't see why Entries can't have a logo too.".
uri editorialNote "the uri with subject awol:Agent and :Generator are really the same relation".
xhtml editorialNote "Note that there is a tricky question concerning the xml div element. The xml:lang and xml:base elements are not in fact part of xhtml and it has been argued on the atom mailing list (28 June 2006) that the div is *not* part of the xhtml. We could have this be a special literal with the div, or we could remove the div and push the xml:lang and xml:base down (this would work only if there is one element beneath I suppose) or we would have to use the awol:lang and :base relations on the :Content object. ".
degree editorialNote "We are not defining, using an enumeration, the range of the bibo:degree to the defined list of bibo:ThesisDegree. We won't do it because we want people to be able to define new degress if needed by some special usecases. Creating such an enumeration would restrict this to happen.".
status editorialNote "We are not defining, using an enumeration, the range of the bibo:status to the defined list of bibo:DocumentStatus. We won't do it because we want people to be able to define new status if needed by some special usecases. Creating such an enumeration would restrict this to happen.".
CorporationSole editorialNote "This is a subclass of org:FormalOrganization by virtue of the fact that it has multiple members over a period of time, though by definition it only has one member at any one time.".
termsOfReference editorialNote "The range of gov:termsOfReference is kept deliberately open; it could be a literal string or a reference to a separate document as appropriate.".
represents editorialNote "No range set on this though for the House of Commons it will be a <http://data.ordnancesurvey.co.uk/ontology/admingeo/WestminsterConstituency>.".
hasAgentName editorialNote "Rationale: This semantic unit provides a more reader-friendly version of the agent identified by the agentIdentifier.".
hasAgentNote editorialNote "Rationale: Additional information may be needed to describe or disambiguate the agent.".
hasEnvironmentNote editorialNote "Rationale: There may be a need to give a textual description of the environment for additional explanation.".
hasEnvironmentPurpose editorialNote "Rationale: Different environments can support different uses of objects. For example, the environment needed to edit and modify a file can be quite different than the environment needed to render it.".
hasEventRelatedObject editorialNote "Rationale: Digital provenance often requires that relationships between objects and events are documented.".
hasFormatNote editorialNote "Rationale: Qualifying information may be needed to supplement format designation and registry information or record a status for identification.".
hasFormatRegistryRole editorialNote "Rationale: The same format may be defined in different registries for different purposes. For example, one registry may give detailed format specifications while another has profile information. If multiple registries are recorded, this semantic unit can be used to distinguish among them.".
hasFormatVersion editorialNote "Rationale: Many authority lists of format names are not granular enough to indicate version, for example, MIME Media types.".
hasHardwareOtherInformation editorialNote "Rationale: For hardware, the amount of computing resource needed (such as memory, storage, processor speed, etc.) may need to be documented. In addition, more detailed instructions may be needed to install and/or operate the hardware.".
hasMessageDigestOriginator editorialNote "Rationale: A preservation repository may ingest files that have had message digests calculated by the submitter; checking these ensures that the file as received is the same as the file as sent. The repository may also ingest files that do not have message digests, and so must calculate the initial value upon ingest. It can be useful to know who calculated the initial value of the message digest.".
hasOriginalName editorialNote "Rationale: The name used within the preservation repository may not be known outside of the repository. A depositor might need to request a file by its original name. Also, the repository may need to reconstruct internal links for dissemination.".
hasPreservationLevelDateAssigned editorialNote "Rationale: The preservationLevel applicable to an object is expected to be reviewed and changed over time, in response to changes in repository preservation requirements, policies, or capabilities relevant to the object. The date that the current preservationLevelValue was assigned aids review of decisions.".
hasPreservationLevelRationale editorialNote "Rationale: Application of a particular preservationLevelValue may require justification, especially if it differs from that usually applied according to repository policy.".
hasRightsGrantedNote editorialNote "Rationale: A textual description of the rights granted may be needed for additional explanation.".
hasRightsStatement editorialNote "Rationale: A repository may choose to link from a rights statement to an object or from an object to a rights statement or both.".
hasSigner editorialNote "Rationale: The signer might also be carried in the keyInformation, but it can be accessed more conveniently if recorded here.".
hasSignificantPropertiesType editorialNote "Rationale: Repositories may choose to describe significant properties based on a particular aspect or attribute of an object.".
hasSignificantPropertiesValue editorialNote "Rationale: Repositories may choose to describe significant properties based on a particular aspect or attribute of an object.".
hasSize editorialNote "Rationale: Size is useful for ensuring the correct number of bytes from storage have been retrieved and that an application has enough room to move or process files. It might also be used when billing for storage.".
hasStatuteInformationDeterminationDate editorialNote "Rationale: The permission in question may be the subject of some interpretation. These assessments are made within a specific context and at a specific time. At another time the context, and therefore the assessment, could change. For this reason it can be important to record the date of the decision.".
hex editorialNote " \n This relation should slowly be transited to just being a datatype.\n Being a datatype and a property is legal as explained here\n <a href=\"http://lists.w3.org/Archives/Public/semantic-web/2010Mar/0037.html\">on the semantic web mailing list in March 2010</a>. \n But it may be somewhat confusing, especially if it goes against a pattern - still to be set - by the xsd datatypes as the follow up email makes clear. \n ".