ISO5087-2:Bylaw

From City Data Model Project Collaboratory
Jump to navigation Jump to search


Pattern

This class has been associated with the following pattern:

Pattern:Bylaw Pattern

Subclass Of

Description

An English description of the definition (what distinguishes this sense of the term?).

The core concept of the Bylaw Ontology is Bylaw. Its properties decompose a Bylaw into conceptual relevant components that support linking with other city concepts, and enable efficient search. The following are a Bylaw’s properties: • schema:title: A short name for the Bylaw, to be used in other descriptions to refer to the Bylaw. • schema:legislationJurisdiction: identifies the city that enacted the Bylaw. The range is restricted to City. • schema:legislationIdentifier: a unique identifier for the bylaw. The range is a xsd:string. • schema:abstract: a brief statement of the bylaw’s purpose. The range is a xsd:string. • schema:keywords: keywords used to categorize the bylaw for search purposes. The range is zero of more xsd:string. • schema:jurisdiction: The City or CityDivision where the bylaw applies. The range is restricted to City or CityDivision. • schema:legislationType: Type of bylaw chosen from bylawMain, bylawAmending or bylawRevision. • schema:legislationLegalForce: Specifies whether the Bylaw is currently in force, not in force or partially in force. • hasDefinition: Words or phrases that are defined to have a specific meaning within the context of the Bylaw. The range is restricted to Definition. • impacts: who and/or what is impacted by the Bylaw. Restricted to Person, Organization, LandArea, City, CityDivision and/or Activities. • schema:legislationDate: Date which the Bylaw is officially adopted/signed by the legislationJurisdiction City or CityDivision. • schema:datePublished: Date the Bylaw is officially published. • dateInEffect: Date after which the Bylaw is in effect. • schema:expires: Date the Bylaw expires. • hasClause: Clauses that make up the body of the Bylaw. Restricted to Clause. • hasPenaltyClause: Clauses that specify penalties for not adhering to the Bylaw. • hasSeveranceClause: Clauses that specify that the bylaw remains valid if any portion of the bylaw is found to be invalid by a higher jurisdiction. • hasTransitionClause: Clauses that cover the period during which entities affected by the bylaw can do things to conform to the new conditions. • hasRepealClause: Clauses that specify all previous bylaws that deal with subjects that are addressed in the new bylaw must either be repealed or amended. • hasSchedule: Schedules that are attached to the Bylaw and are referenced by the Bylaw. A Schedule is part of the Bylaw.

Class Diagram Description

Required by Use Case(s)

(why is this specialized definition needed?)


CDM References

What other classes or properties reference this term?

Interface Specification References

This class has been associated with the following interface specification items:


Sources

Sources considered when developing the class:


Status

Pending Approval

Has Subclass(es)



Annotations

Annotation Value


Manchester Syntax Specification

Property Restriction Value
Schema:legislationJurisdiction exactly 1 (City or CityDivision)
Schema:legislationIdentifier exactly 1 xsd:string
Schema:abstract exactly 1 xsd:string
Schema:keywords only xsd:string
Schema:legislationType only [[{mainBylaw, amendingBylaw, revisionBylaw }]]
Schema:legislationLegalForce only [[{schema:InForce, schema:NotInForce, schema:PartiallyInForce}]]
HasDefinition only Definition
Impacts only (Person or Organization or LandArea or City or CityDivision or Activity)
Schema:legislationDate exactly 1 xsd:DateTime
Schema:datePublished exactly 1 xsd:DateTime
DateInEffect exactly 1 xsd:DateTime
Schema:expires exactly 1 xsd:DateTime
HasClause only Clause
HasPenaltyClause only Clause
HasSeveranceClause only Clause
HasTransitionClause only Clause
HasRepealClause only Clause
HasSchedule only Schedule


Supplementary Figures

Figure Caption