-
**Update** : see extension v3 [below](https://github.com/schemaorg/schemaorg/issues/1156#issuecomment-259397260) (09 november 2016)
A **proposed extension to describe Legislation** within schema.or…
-
# Regulation Innovation SIG
## Date
Nov 16th 2021 - 12pm EST / 5pm GMT
## Meeting notices
- FINOS **Project leads** are responsible for observing the FINOS guidelines for [running project meetin…
-
The Code Editor will not display for rules that have sandwich text, because it is expecting an `eId` to be defined on the Akoma Ntoso element for the sandwich text. This is probably an error in how th…
-
Right now section 1.1. gets added to the Akoma Ntoso as `eId="sec_1"`, when it should be `eId="sec_1_1"`.
-
One way that we can make it easier to get Akoma Ntoso into the system is to allow the user to generate it using Slaw from laws.africa. The problem there is that the format of statutory text that Slaw …
-
For Blawx to be useful in the context of legislative drafting, the user needs to be able to edit not only the code, but also the law. That is going to pose two major problems. The first is that there …
-
Legislative text will often contain defaults and exceptions, and other parts and sub-parts that it is useful for testing purposes to be able to identify separately, inside an undivided paragraph of te…
-
Legal Documents should be possible to represent in s(CASP) in such a way as to be able to make references to their parts or pinpoint leaf nodes by name, for the purpose of giving the provenance of cer…
-
We need a way to style `la-akoma-ntoso` content differently based on the country, document type, etc. The FRBR URI has all this key information embedded into it. A user should be able to both add the …
-
To support improved re-use (in particular https://github.com/laws-africa/la-web-components/issues/30), we must move all styling into mixins.
Then, at the top level, we style `.akoma-ntoso` by inclu…