Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

should we sometimes be using FRBRname instead of FRBRnumber? #43

Open
goose-life opened this issue Jun 24, 2020 · 1 comment
Open

should we sometimes be using FRBRname instead of FRBRnumber? #43

goose-life opened this issue Jun 24, 2020 · 1 comment
Assignees

Comments

@goose-life
Copy link
Contributor

By-laws aren't always given numbers, so we use their titles for disambiguating them instead.

We might potentially use titles for judgments as well, depending on how reliably they are numbered.

This is correct according to https://docs.oasis-open.org/legaldocml/akn-nc/v1.0/os/akn-nc-v1.0-os.html#_Toc531692270, which says one should use "Number or title or other disambiguating feature of the Work" here.

However, it goes on to say "For an Akoma Ntoso XML representation, this value MUST correspond to the content of element or , respectively, in the metadata".

Do they mean that if a number isn't used, the element should be FRBRname, not FRBRnumber?

@longhotsummer
Copy link
Contributor

Yes, I think you're correct that we should probably use FRBRname when FRBRnumber isn't strictly a number. I'm not sure how we get cobalt to detect that, since something like 'cap17' is technically a number.

I'm not sure what "required when necessary for disambiguation, optional otherwise" at the end of that sentence in the docs means.

Also, the docs for FRBRnumber say "FRBRnumber is the metadata property containing a string or number for the number to be used in the work-level IRI of this document", so I've always interpreted this to mean that we can just use FRBRnumber for both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants