There are a few issues packed in here...at least...
1. the informational requirements for citations and what this means to be able to traverse the citation to get to the resource in the form you need it
2. interoperability across different citation systems
3. granularity (term vs vocabulary)
4. provenance - where did things come from.
There are multiple citation formats (bibtex etc...) - so i thinks its safe to say that no single approach is going to be ubiquitous, so registering transformations between the _set_ of formats is what is required for a system-of-systems
From the granularity perspective, citation for terms can be done in a system that requires URI dereferencing with a SKOS profile (without assuming this is the only way)
of course without URIs (explicit or implicit with namespace bindings) this will devolve into idiosyncratic solutions (or lack of solution) in every system
(note that the lack of support for sharing vocabularies in the wider architecture means that someone has to roll-their-own solution - but also note it has been isolated from other concerns and encapsulated in a reusable form)
_______________________________________________________
![](https://lh4.googleusercontent.com/G9sTs64BV0yilkQLDOgDnoOKyRoOwePYFdFBwJ4J4nhis-2NTsRa0cf7dQ0fqGIs4uscj7jdpLQPwpA8Gdiv9lgOXS6q4Yzht_TWfeUxd96dfEFqt3lEIVrbWI-foiU56MkVZLeW) | kind regards Rob Atkinson Lead Ontologist, Knowledge Architect at SURROUND Australia Pty Ltd | |
| | Enhancing Intelligence Within Organisations delivering evidence that connects decisions to outcomes
Copyrights: SURROUND Australia Pty Ltd is the copyright owner of all original content and attachments. All rights reserved. Confidentiality Notice: The contents of this e-mail are confidential to the ordinary user of the e-mail address to which it is addressed, and may also be privileged. If you are not the addressee of this e-mail, you may not copy, forward, disclose, or otherwise use it or any part of it or its attachments in any form whatsoever. If you have received this e-mail in error, please e-mail the sender by replying to this message. |
|
| |
|