-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add schema browser to schemas.isotc211.org #8
Comments
Yes, we have talked about this before @ronaldtse. |
Sorry to have kept this hanging, we have been doing lots of enhancements on Geolexica lately. This issue is to make schema/resources browsable. This applies to these sites:
This shall come in a form of a plugin so it applies across the board. We will create a new task at https://github.com/ISO-TC211/jekyll-theme-isotc211/ to handle this. |
Moved under the schemas website repository, since the original request is about the schemas. This will be closed when ISO-TC211/jekyll-theme-isotc211#6 is done. |
Cool, thanks for handling this @strogonoff ! |
@ronaldtse are there some shared traits among formats of different schemas? E.g., 19115 and a few others (but not all of them) contain a “resources” subdirectory, which appears to provide some metadata. |
First (imperfect) pass is live at https://schemas.isotc211.org/, to be continued.
|
@strogonoff this is an awesome start! Please continue with the issues mentioned 👍 |
Is there any metadata associated with each schema? https://schemas.isotc211.org/schemas/ is a bit bare with only numeric IDs, showing a title or brief summary could help I think.
It’d be great if we could somehow glean it from schema files, but I doubt it. Perhaps with TC 211 participation we could extend schema format to include a metadata file?
… On 15 Aug 2019, at 9:31 AM, Ronald Tse ***@***.***> wrote:
@strogonoff this is an awesome start! Please continue with the issues mentioned 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@strogonoff the schemas are organized by ISO numbers, not sure if we could provide metadata for each. We could rely on Relaton to fetch the metadata of ISO documents, but they're still one step away from the schemas themselves. But yes, I suppose we could supply extra information in a metadata file? |
If there is a resource that can provide ISO/TC 211 schema metadata, given its ID, then sure plugin could query that resource during build.
Or I suppose the minimum metadata necessary to be bundled with schemas is a valid reference to an ISO document within each schema? Assuming each schema refers to a unique doc
… On 15 Aug 2019, at 6:17 PM, Ronald Tse ***@***.***> wrote:
@strogonoff the schemas are organized by ISO numbers, not sure if we could provide metadata for each. We could rely on Relaton to fetch the metadata of ISO documents, but they're still one step away from the schemas themselves.
But yes, I suppose we could supply extra information in a metadata file?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@PeterParslow forgot to let you know that the schema browser is now completed. If you go to this page: https://schemas.isotc211.org/schemas/ Click on any schema, and you will see the schema browser: Closing this issue now -- for feedback and improvement suggestions, please file new issues. Thanks! |
OK - I'll open a new issue: this allows us to browse, but not in the way @jetgeo or I described - i.e. use a web browser to dereference URIs built on the expected pattern, in the way I can at https://standards.iso.org. For example, I can't GET https://schemas.isotc211.org/schemas/19135/-2; I have to browse from the root, from https://schemas.isotc211.org/schemas/19135. |
@PeterParslow I see, you would like to still see the browser at: https://schemas.isotc211.org/schemas/19135/-2 . Correct? |
If so, we should be able to extend and handle that. |
That might solve it |
Looking good.
The default page at https://schemas.isotc211.org/ means I can no longer browse the available schemas, in the way I can at https://standards.iso.org/ittf/PubliclyAvailableStandards, which means I need to be well prepared before trying to find one.
Similarly, you can't browse to find parts or namespaces, e.g. https://schemas.isotc211.org/19110/ and https://schemas.isotc211.org/19110/fcc/ both give 404s.
For example, I just looked for 19139, forgetting it is -1 (even though I was the editor!) - and doesn't have a schema anyway.
Perhaps all this is deliberate, to ensure the schemas are only found by people coming from the (paid for) standards documents?
Also, the 404 isn't working "An Error Occurred While Attempting to Retrieve a Custom Error Document" 404.html
The text was updated successfully, but these errors were encountered: