Ontologies Classes Object Properties Data Properties Annotation Properties Individuals Datatypes Clouds

Annotation Property: rdfs:comment

Usage (95)

  • 'Core Public Organization Vocabulary' rdfs:comment "The Core Public Organization Vocabulary (CPOV) is designed to support the exchange of basic information about individual public organizations." @en 
  • 'Foundation Event' rdfs:comment "Public organizations are formed and changed in response to events. The W3C ORG ontology captures this in its Change Event class but CPOV recognises the specific case of an organization's foundation as being sufficiently distinct to require a sub class of Change Event." @en 
  • 'Public Organization' rdfs:comment "Any organization that is defined as being part of the public sector by a legal framework at any level" 
  • 'Administrative Area' rdfs:comment "Formally defined as the set of skos:Concept in concept scheme eli:AdministrativeAreaTable" @en 
  • Format rdfs:comment "The physical embodiment of a legal expression, either on paper or in any electronic format (definition adapted from RDA).
    For example, any electronic or physical format of the legal expression (XML, TIFF, PDF, etc.) ; e.g. PDF version of act 3 of 2005. (adapted from Akoma Ntoso)"
    @en 
  • 'In force' rdfs:comment "Formally defined as the set of skos:Concept in concept scheme eli:InForceTable" @en 
  • Language rdfs:comment "Formally defined as the set of skos:Concept in concept scheme http://data.europa.eu/eli/ontology#language" @en 
  • 'Legal Expression' rdfs:comment "The intellectual realisation of a legal resource in the form of a "sequence of signs" (typically alpha-numeric characters in a legal context) (definition adapted from RDA)
    For example, any version of the legal resource whose content is specified and different from others for any reason: language, versions, etc.;

    Note that ELI ontology accommodates different point of view on what should be considered a new legal resource, or a new legal expression of the same resource. Typically, a consolidated version can be viewed, in the context of ELI, either as separate legal resource (linked to original version and previous consolidated version using corresponding ELI relations), or as a different legal expression of the same legal resource."
    @en 
  • 'Legal Resource' rdfs:comment "A distinct intellectual creation (i.e., the intellectual content). (definition adapted from RDA - Resource Description and Access, see http://www.rdaregistry.info/).
    For example, the abstract concept of the legal resource; e.g. "act 3 of 2005" (adapted from Akoma Ntoso)

    Legal resource can be linked together using properties defined in the model.
    A legal resource can represent a legal act or any component of a legal act, like an article.

    Note that ELI ontology accommodates different point of view on what should be considered a new legal resource, or a new legal expression of the same resource. Typically, a consolidated version can be viewed, in the context of ELI, either as separate legal resource (linked to original version and previous consolidated version using corresponding ELI relations), or as a different legal expression of the same legal resource."
    @en 
  • 'Legal value' rdfs:comment "Formally defined as the set of skos:Concept in concept scheme eli:LegalValueTable" @en 
  • 'Resource type' rdfs:comment "Formally defined as the set of skos:Concept in concept scheme eli:ResourceTypeTable" @en 
  • Version rdfs:comment "Formally defined as the set of skos:Concept in concept scheme eli:VersionTable" @en 
  • 'based on' rdfs:comment "inverse of "basis_for"" @en 
  • 'basis for' rdfs:comment "Legal resource (typically constitution, treaty or enabling act) that empowers the creation of another legal resource (secondary legislation)" @en 
  • 'changed by' rdfs:comment "Inverse of "changes"" @en 
  • changes rdfs:comment "Legal resource changing (amending or replacing) another legal resource This may be a direct change (textual or non-textual amendment) or a consequential or indirect change. Note, the property is to be used to express the existence of a change relationship between two acts rather than the existence of a consolidated version of the text that shows the result of the change. For consolidation relationships, use the "consolidates" and "consolidated_by" properties.

    Subclasses have been created following Akoma Ntoso definition [see http://docs.oasis-open.org/legaldocml/akn-core/v1.0/akn-core-v1.0-part1-vocabulary.html#_Toc397009791]"
    @en 
  • 'cited by' rdfs:comment "Inverse of "cites"" @en 
  • cites rdfs:comment "Citation in the text of the legislation. This may be at the legal resource or legal expression level, as required by the implementation context. This includes verbatim citation and citations in referrals." @en 
  • 'consolidated by' rdfs:comment "Inverse of "consolidates"" @en 
  • consolidates rdfs:comment "Link between a consolidated version, which is the product of an editorial process that revises the legislation to include changes made by other acts, and the original or previous consolidated version and the legislation making the change." @en 
  • 'date of the document' 'date of the document' 'date of the document' rdfs:comment "Date of adoption or signature (of the form yyyy-mm-dd)" @en 
  • 'date no longer in force' rdfs:comment "If the date is known, it is when the legal resource or legal expression is no longer in force (can be seen as the end date of a dc:valid range for this resource)" @en 
  • 'date of publication' 'date of publication' rdfs:comment "Date of publication of the official version of the legislation, in hard copy or online, depending on what the official publication is, and when it was published. Publication dates at the level of legal expressions can be separately asserted, using standard Dublin Core properties." @en 
  • description description rdfs:comment "An account of the resource (definition from Dubin Core), e.g a summary." @en 
  • embodies rdfs:comment "Relates a physical format to the legal expression embodied in that format (definition adapted from RDA). Inverse of "is_embodied_by"." @en 
  • 'first date of entry into force' rdfs:comment "The first date any part of the legal resource or legal expression came into force (can be seen as the start date of a dc:valid range for this resource)" @en 
  • format rdfs:comment "The file format, physical medium, or dimensions of the resource (definition from Dublin Core).
    Possible URIs values should be taken from http://www.iana.org/assignments/media-types (e.g. http://www.iana.org/assignments/media-types/application/xml), and can serve as a basis for content negotiation for the server to return the appropriate file based on the client preference."
    @en 
  • 'has part' rdfs:comment "inverse of "is_part_of"" @en 
  • 'local id' rdfs:comment "The unique identifier used in a local reference system to maintain backwards compatibility. For examples the CELEX at EU level, or the NOR in France." @en 
  • 'implemented by' rdfs:comment "Inverse of "implements".

    Note that this property is expressed on a legal resource, not on one of its language-specific legal expression."
    @en 
  • implements rdfs:comment "To be used for more general statements about the relationship between domestic and EU legislation, e.g. between consolidated versions of national implementing measures and consolidated versions of Directives.

    Note that this should point to the legal resource of the Directive itself, not to one of its language-specific legal expression."
    @en 
  • 'in force' rdfs:comment "A value indicating the legal force of a legal resource or a legal expression. A set of values is defined by ELI in the corresponding concept scheme. These values are :
    - in force
    - partially in force
    - not in force"
    @en 
  • 'is about' rdfs:comment "A subject for this legal resource. The use of Eurovoc (http://eurovoc.europa.eu) is encouraged to select values for this property. Member states are encouraged to align local values to Eurovoc." @en 
  • 'is embodied by' rdfs:comment "Relates a legal expression to a physical format of that expression (definition adapted from RDA). Inverse of "embodies"." @en 
  • 'is exemplified by' rdfs:comment "Link to a concrete file URL.
    Relates a format to a single exemplar or instance of that format (definition adapted from RDA). "
    @en 
  • 'is part of' rdfs:comment "A related resource in which the described resource is physically or logically included (definition from Dublin Core). Cover the case of legal resources included in an Official Journal and the case of legal resources grouping other legal resources across time." @en 
  • 'is realized by' rdfs:comment "Relates a legal resource to a legal expression of this resource in the form of a "sequence of signs" (typically alpha-numeric characters in a legal context). (definition adapted from RDA). Inverse of "realizes"." @en 
  • language language rdfs:comment "The language of an expression.

    EU Publications Office provides a list of languages at http://publications.europa.eu/mdr/authority/language. This list is large enough so that member states should not have to declare local values.

    Note that, if needed, a language can also be stated on a legal resource using the DublinCore "language" property."
    @en 
  • 'legal value' rdfs:comment "The legal value associated with a specific format of a resource. A set of values is defined by ELI in the corresponding concept scheme. These values are :
    - unofficial : no particular or special standing;
    - official : published by an organisation with the public task of making the information available (e.g. a consolidated version of a EU directive) ;
    - authoritative : the publisher gives some special status to the publication (e.g. "the Queens Printer" version of an Act of Parliament, or the OJ version of a EU Directive);
    - definitive : the text is conclusively what the law says, (e.g. the digitally signed version of an OJ)."
    @en 
  • licence rdfs:comment "A legal document giving official permission to do something with the resource (Definition from Dublin Core)" @en 
  • 'passed by' 'passed by' rdfs:comment "The agent that originally passed or made the law. The relationship between current and any former law making body should be represented in the description of the agent itself.

    Member states are encouraged to make their own list of Agents. EU Publications Office provides a list of corporate bodies at http://publications.europa.eu/mdr/authority/corporate-body."
    @en 
  • 'published in' rdfs:comment "Reference to the Official Journal or other publication in which the legal resource is published, identified by a suitable mechanism.
    Preferably to be expressed as a URI to a given resource, in the absence of such a URI as a descriptive string."
    @en 
  • publisher publisher rdfs:comment "An entity responsible for making the resource available (definition from Dublin Core)" @en 
  • publishes rdfs:comment "Inverse of "published_in".
    Note this property does not link a publisher with a resource, but rather a specific Format of a resource with a specific Format of another resource, indicating that the subject Format publishes the object Format."
    @en 
  • realizes realizes rdfs:comment "Relates a legal expression to the legal resource realised through that expression. (definition adapted from RDA). Inverse of "is_realized_by"." @en 
  • 'related to' rdfs:comment "Indicates a somehow related other document, not necessarily a legal resource. Note that citation links should use the cites property." @en 
  • 'relevant for' rdfs:comment "Refers to a place or an area associated with the resource. This covers the notions of jurisdiction, sovereignty, applicability or administrative area. The place identifier should be based on ISO3166-2. See: https://www.iso.org/obp/ui/#search.

    Member states are encouraged to make their own list of values in the corresponding concept scheme. EU Publications Office provides a list of places at http://publications.europa.eu/mdr/authority/place

    The group notes the limitations of what can be said with a single property; member states can refine this notion by declaring specific sub properties."
    @en 
  • 'responsibility of' rdfs:comment "An individual, organisational unit or organisation that has some kind of responsibility for the legislation." @en 
  • rights rdfs:comment "Information about rights held in and over the resource (definition from Dublin Core)" @en 
  • 'rights holder' rdfs:comment "A person or organization owning or managing rights over the resource (definition from Dublin Core)" @en 
  • title title rdfs:comment "The title, or name, of an expression.

    Note that, if needed, a title can also be stated on a legal resource using the Dublin Core "title" property."
    @en 
  • 'alternative title' rdfs:comment "An alternative title of the expression (if any).

    Note that, if needed, an alternative title can also be stated on a legal resource using the Dublin Core "alternative" property."
    @en 
  • 'short title' rdfs:comment "Established short title of the expression (if any)" @en 
  • 'transposed by' rdfs:comment "Inverse of "transposes".

    Note that this property is expressed on a legal resource, not on one of its language-specific legal expression."
    @en 
  • transposes rdfs:comment "To be used for precise statements of transposition, at act or article level, from the original version of a national implementing measure to the legal resource Directive as published in the EU Official Journal. Can be used for transposition tables, once EU Publication Office has introduced ELI support down to the article level.

    Note that this should point to the legal resource of the Directive itself, not to one of its language-specific legal expression."
    @en 
  • 'type document' 'type document' rdfs:comment "The type of a legal resource (e.g. "Directive", "Règlement grand ducal", "law", "règlement ministeriel", "draft proposition", "Parliamentary act", etc.).
    Member states are encouraged to make their own list of values in the corresponding concept scheme. EU Publications Office provides a list of values for EU resource types at http://publications.europa.eu/mdr/authority/resource-type"
    @en 
  • 'uri schema' rdfs:comment "Schema describing the URI of an ELI instance. ELI uses URI template specifications (IETF RFC 6570). Schemes should be associated with member states and will be published in a registry." @en 
  • version rdfs:comment "A skos concept scheme, could be locally defined? Group proposal is to start with an initial ELI scheme, that might include concepts of "Official Journal" "made" "consolidated" "proposed" "prospective"" @en 
  • 'version date' rdfs:comment "A date associated with the version." @en 
  • body rdfs:comment "The term body is taken by AkomaNtoso to express the content of an Act:

    The body is used for bills and acts and presents an explicit hierarchy of parts each part of which can be identified with a meaningful name (such as section, tome, etc.) and possibly provided with numbers and various types of headings."
     
  • Effect rdfs:comment "Any impact that one legislative provision may have on another. The most familiar type of effect is an amendment that changes the text of the affected legislation, but there are also types of effect that do not change the text, such as where a provision is said to be ‘modified’ or ‘applied’" 
  • SubjectDivision rdfs:comment "Classification of the greek law http://openlaw.e-themis.gov.gr/legislation-pilot/vocabulary.html" 
  • 'Subject Division Type List' rdfs:comment "Set of subject of a country juridiction" 
  • act rdfs:comment "An act is a subclass of Legal Resource which has a body" 
  • amendment rdfs:comment "An effect that changes the text of legislation which has an amendmentBody" 
  • article rdfs:comment "An article is a subclass of Legal Resource which may contain paragraphs and it is part of a chapter." 
  • baseAct rdfs:comment "A base act is a subclass of act" 
  • chapter rdfs:comment "A chapter is a subclass of Legal Resource which may contain articles and it is part of a part" 
  • consolidatedAct rdfs:comment "A consolidated act is a subclass of act" 
  • date_signature rdfs:comment "date of signature
    +
    date of published
    +
    date in which is in effect"
     
  • indent rdfs:comment "A indent is a subclass of Legal Resource which may contain subindents and it is part of a paragraph" 
  • officialGazette rdfs:comment "Used to represent an issue of an official publication body such as Official Gazette, Journal, Bulletin or Federal Register [AkomaNtoso http://docs.oasis-open.org/legaldocml/akn-core/v1.0/akn-core-v1.0-part1-vocabulary.html#_Toc348113723]" 
  • paragraph rdfs:comment "A paragraph is a subclass of Legal Resource which may contain indents and it is part of an article


    A paragraph can have 2 different uri schema (1 with the paragraph number only and 1 which includes a chapter number)

    Is a paragraph changing only a paragraph or another part of the document ?"
     
  • part rdfs:comment "A part is a subclass of Legal Resource which may contain chapters and it is part of an act

    there are 2 types of parts: verbal part (it has a word instead of index) and numerical part

    a section contains article and/or paragraphs"
     
  • passage rdfs:comment "A section is a subclass of Legal Resource and it is part of a subindent

    verses: verbal period between two dots. not numbered



    ASK definition of verses/section"
     
  • subindent rdfs:comment "A subindent is a subclass of Legal Resource which may contain sections and it is part of an indent" 
  • uri_schema uri_schema rdfs:comment "An uri schema class allows to define uri schema for each act component" 
  • 'has manifestation of expression' rdfs:comment "Relates an expression to a physical embodiment of an expression (RDA)." @en 
  • 'has work expressed' rdfs:comment "Relates an expression to the work realized through an expression (RDA)" @en 
  • 'has expression manifested' rdfs:comment "Relates a manifestation to an expression embodied in a manifestation (RDA)" @en 
  • 'alternative label' rdfs:comment "The range of skos:altLabel is the class of RDF plain literals." @en 
  • 'alternative label' rdfs:comment "skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties." @en 
  • 'has broader' rdfs:comment "Broader concepts are typically rendered as parents in a concept hierarchy (tree)." @en 
  • 'has exact match' rdfs:comment "skos:exactMatch is disjoint with each of the properties skos:broadMatch and skos:relatedMatch." @en 
  • 'hidden label' rdfs:comment "The range of skos:hiddenLabel is the class of RDF plain literals." @en 
  • 'hidden label' rdfs:comment "skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties." @en 
  • 'is in mapping relation with' rdfs:comment "These concept mapping relations mirror semantic relations, and the data model defined below is similar (with the exception of skos:exactMatch) to the data model defined for semantic relations. A distinct vocabulary is provided for concept mapping relations, to provide a convenient way to differentiate links within a concept scheme from links between concept schemes. However, this pattern of usage is not a formal requirement of the SKOS data model, and relies on informal definitions of best practice." @en 
  • 'has member list' rdfs:comment "For any resource, every item in the list given as the value of the
    skos:memberList property is also a value of the skos:member property."
    @en 
  • 'has narrower' rdfs:comment "Narrower concepts are typically rendered as children in a concept hierarchy (tree)." @en 
  • 'preferred label' rdfs:comment "A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag." @en 
  • 'preferred label' rdfs:comment "The range of skos:prefLabel is the class of RDF plain literals." @en 
  • 'preferred label' rdfs:comment "skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise
    disjoint properties."
    @en 
  • 'has related' rdfs:comment "skos:related is disjoint with skos:broaderTransitive" @en 
  • Homepage Homepage rdfs:comment "This property represents a website through which information about the Formal Organisation can be retrieved, the particular Formal Organisation can be contacted…." @en 
  • rdfs:comment "Transposition of the ELI metadata fieldsds into an OWL ontology.
    See the classes "LegalResource", "LegalExpression" and "Format" as entry points.

    ***** Notes *****

    - The ELI ontology reuses the property names from the Metalex ontology (http://www.metalex.eu/) to express the FRBR skeleton hierarchy : is_realized_by/realizes, is_embodied_by/embodies, is_exemplified_by. This wording is also the one used in the original FRBR specifications. However, the decision has been made _not_ to align to the Metalex class names (BibliographicWork, BibliographicExpression, BibliographicManifestation), because ELI is specifically about publishing legal metadata on the web, and not structuring legal content in any document.
    - Since published_in property has been made into a Literal, it is not possible to declare explicitely "publishes" as an inverse property.
    - first_date_entry_in_force and date_no_longer_in_force could be subproperties of dcterms:date
    - a class could be introduced for URI schemas to implement the URI schema registry



    ***** Version History *****

    * 1.0 *

    - added a set of values for the InForce table
    - added definitions to tables
    - minor fixes in definitions
    - added rdfs:seeAlso from properties to corresponding tables
    - cleaned the "whyThisIsNeeded" annotation

    * 0.6.1 *

    - fixed typos in definitions

    * 0.6 *

    - imported skos rather than redeclaring skos classes and properties
    - changed domain of in_force, first_date_entry_into_force, date_no_longer_in_force to [LegalResource or LegalExpression] instead of LegalResource
    - changed domain of language, title, title_short, title_alternative to LegalExpression instead of [LegalResource or LegalExpression]
    - reworked the tables : don't use country and resource type tables from MDR, but declare local tables.
    - integrated new definitions for all classes and properties

    * 0.5 *

    - Renamed "Interpretation" into "LegalExpression" (and modified comments accordingly)
    - Renamed the structural FRBR relations in accordance with Metalex ontology :
    - is_legal_resource_of becomes "is_relaized_by"
    - has_legalresource becomes "realizes"
    - is_interpretation_of becomes "is_embodied_by"
    - has_interpretation becomes "embodies"
    - file becomes "is_exemplified_by"
    - file has been made a subproperty of "has exemplar of manifestation" instead of "dc:hasPart"
    - relevant_for is no more considered mandatory. Deleted comment that stated "we are seeking a way to express that relevant_for must have at least one value for LegalResource or one of its LegalInterpretation".

    * 0.4.1 *

    - Added "publishes" property
    - Enriched the note on "transposes" and "transposed by" to indicate they must point to / be expressed on LegalResource"
    @en