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

Wrong NS links #265

Open
berezovskyi opened this issue Sep 12, 2019 · 10 comments
Open

Wrong NS links #265

berezovskyi opened this issue Sep 12, 2019 · 10 comments
Assignees

Comments

@berezovskyi
Copy link
Member

@berezovskyi berezovskyi commented Sep 12, 2019

Problems identified:

  • some folders have stray files (eg Core has core-vocab and core files)
  • some folders should not have been published (eg /config has no corresponding PSD)
  • some folders have unapproved vocabs in them (eg CM)

https://github.com/oslc-op/website-content-negotiation

https://github.com/oslc-op/website/tree/master/content/ns


TODOs

@berezovskyi

This comment has been minimized.

Copy link
Member Author

@berezovskyi berezovskyi commented Sep 12, 2019

The following files match the current NS folder and the archive:

b38c78a0cf5ddb9ee7370747285c888a90e23ed9  ./basicProfile/ldbp.rdf
a95ad96ee50e70552f2c09037405f3afe22f2bc2  ./cm/cm.rdf
6eb60dac7c98615b1f339ef14f68f36ead7bc680  ./ems/ems.rdf
8f68041afab51a2ce6acbb4ec929774f1b67f77f  ./qm/qm.rdf

The rest do not match. These are the differing files for the specs that were in the archive:

508dc70c88ceaf08a5816a336bd082b489f7175c  ./am/architecture-management-vocab.rdf
c99119aa823430dd7588477b620b32ce8802dc44  ./asset/asset-management-vocab.rdf
e03926db4c1b4e240e6618c18294a72df58993cc  ./rm/requirements-management-vocab.rdf
08475fab4c6d56e33ea8d8ce6609ce64e99ce60c  ./cm/change-mgt-vocab.rdf

Newly added (RDF/XML) files:

2db81dc4f955d38f53f903b38c9724594946cd97  ./auto/automation-vocab.rdf
895f0dd2df4e76acc0300bdc2e606746d4be87da  ./config/config-vocab.rdf
0e3b8e1d37d4a7066f8272d91ba3a31aa26c5413  ./core/core-vocab.rdf
3e515f188f08a1279c19488d164fc99b9c212b0a  ./core/core.rdf
5d081a82416ff90f3ab6ca32892466d517378ef9  ./perfmon/performance-monitoring-vocab.rdf

The only RDF/XML file in the specs repo is RM:

3eca6f0b11356c84706db3eb97ea5e7d2ac03ccf  ./rm/rm_2.0.rdf

SHA1 checksums were used.

cc @jamsden

@berezovskyi

This comment has been minimized.

Copy link
Member Author

@berezovskyi berezovskyi commented Sep 12, 2019

Okay, so the ./core/core.rdf mystery: it was used in the .htaccess file previously

@berezovskyi

This comment has been minimized.

Copy link
Member Author

@berezovskyi berezovskyi commented Sep 12, 2019

Now, AM:

$ cdiff -b am/architecture-management-vocab.rdf ../../misc/ns.old/am/am.rdf

$ rdfdiff am/architecture-management-vocab.rdf ../../misc/ns.old/am/am.rdf RDF/XML RDF/XML
am/architecture-management-vocab.rdf ../../misc/ns.old/am/am.rdf RDF/XML RDF/XML null null
models are equal

The old file will be restored to avoid confusion and cneg repo updated accordingly.

@berezovskyi

This comment has been minimized.

Copy link
Member Author

@berezovskyi berezovskyi commented Sep 12, 2019

Same for asset mgt:

└─[$] <git:(master)cdiff -b content/ns/am/architecture-management-vocab.rdf misc/ns.old/am/am.rdf
diff: content/ns/am/architecture-management-vocab.rdf: No such file or directory
└─[$] <git:(master)> rdfdiff content/ns/asset/asset-management-vocab.rdf misc/ns.old/asset/asset.rdf RDF/XML RDF/XML
content/ns/asset/asset-management-vocab.rdf misc/ns.old/asset/asset.rdf RDF/XML RDF/XML null null
models are equal
@berezovskyi

This comment has been minimized.

Copy link
Member Author

@berezovskyi berezovskyi commented Sep 14, 2019

  • Updated all XML files except for TRS (Turtle for Config).
  • Regenerated old Turtle/JSON-LD files with Jena 3.12
  • Generated N-Triples for all vocabs
@ndjc

This comment has been minimized.

Copy link
Member

@ndjc ndjc commented Sep 30, 2019

The vocabulary links from open-services.net/ns are still wrong. They now redirect to the specs, or to a page that in turn contains links only to the specifications, and not to the vocabularies.

For example, if I go to open-services.net/ns/rm, I get redirected to https://archive.open-services.net/bin/view/Main/RmSpecificationV2a8d9.html. That is not the vocabulary - indeed, it doesn't even have a link to the vocabulary. To find that, I have to manually click on the RM Home button on the breadcrumbs at the top of the page, from there follow the link to the new wiki, and then click on the link to the RM 2.0 vocab at https://archive.open-services.net/bin/view/Main/RmVocabulary.html#.

Similarly, if I just go to open-services.net/ns, I get a page of spec listings, with links that claim to be to the vocabularies, but in fact point to the shape tables in the specs (this is really a separate issue - the vocab links on that page https://open-services.net/specifications/vocabularies/ are all incorrect).

@berezovskyi

This comment has been minimized.

Copy link
Member Author

@berezovskyi berezovskyi commented Sep 30, 2019

@berezovskyi

This comment has been minimized.

Copy link
Member Author

@berezovskyi berezovskyi commented Sep 30, 2019

Will fix tomorrow at it requires redeploy of the content neg app

@berezovskyi

This comment has been minimized.

Copy link
Member Author

@berezovskyi berezovskyi commented Oct 3, 2019

@jamsden @ndjc please go over https://open-services.net/specifications/vocabularies/ and give me a set of actions to do.

@ndjc

This comment has been minimized.

Copy link
Member

@ndjc ndjc commented Feb 12, 2020

I've completed the initial verification of the RDF vocabulary pages at open-services.net, and I've found quite a few inconsistencies or errors that need to be addressed. Some will need discussion. See the attached note.
OSLC V2 Vocabulary Status.docx

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.