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

Make gspo, graph and annotation terminology consistent #14

Open
fbaumgardt opened this issue Aug 29, 2016 · 0 comments
Open

Make gspo, graph and annotation terminology consistent #14

fbaumgardt opened this issue Aug 29, 2016 · 0 comments

Comments

@fbaumgardt
Copy link
Collaborator

fbaumgardt commented Aug 29, 2016

gspo stands for an {g:{ token:"", value:"" },s:{ token:"", value:"" },p:{ token:"", value:"" },o:{ token:"", value:"" }} SPARQL binding for quads. Currently it's sometimes used for a variant where the value is assigned directly to the g/s/p/o properties.

graph or body is the body of an oa:Annotation identified with the oa:hasBody relation. Currently it's being called graph, body or annotation, where annotation is supposed to have the meaning stated below and body is also used to refer to the HTML body of the entailing document.

annotation is supposed to be the full set of quads that make up an annotation, including the body and the metadata.

Moving to a consistent terminology throughout source code and documentation will improve readability.

@fbaumgardt fbaumgardt added this to the 0.1.0: refactored and mostly bug-free milestone Sep 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant