> For the complete documentation index, see [llms.txt](https://docs.os.uk/osngd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/osngd/code-lists/code-lists-overview/nameddayvalue.md). # nameddayvalue This code list is used in association with the Named Day attribute which is present within the Restriction, Special Designation Area, Special Designation Line, and Special Designation Point Feature Types in the OS RAMI Collection. The code list describes specific days when a restriction may apply. | Label | Definition | | --------------- | ---------------------------------------------------------------------------- | | All Days | Applies to every day of the week. | | Friday | This is the day of Friday. | | Market Days | The day which a market is regularly held. | | Monday | This is the day of Monday. | | Public Holidays | A holiday established by law. | | Saturday | This is the day of Saturday. | | Sunday | This is the day of Sunday | | Thursday | This is the day of Thursday. | | Tuesday | This is the day of Tuesday. | | Wednesday | This is the day of Wednesday. | | Weekdays | A time interval which occurs during the working week, Monday to Friday | | Weekends | A time interval which occurs over the non-working days, Saturday and Sunday. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.os.uk/osngd/code-lists/code-lists-overview/nameddayvalue.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.