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

Spec editing to-do list #56

Closed
cygri opened this issue Feb 20, 2013 · 8 comments
Closed

Spec editing to-do list #56

cygri opened this issue Feb 20, 2013 · 8 comments

Comments

@cygri
Copy link
Member

cygri commented Feb 20, 2013

@borsna
Copy link
Member

borsna commented Feb 22, 2013

I have created a script for generating documentation out of the turtle-file (converts it to rdf/xml and then applies a xslt)
I have only a windows build-script at the moment, bash-file coming soon.

Example of the output in in the documentation folder.
Online example of the rendered documentation can be found here: https://dl.dropbox.com/u/37711156/disco-spec-documentation/documentation/discovery.html

@boschthomas
Copy link
Member

Olof, good work!

I think Richard recommended LODE for the same purpose:
http://www.essepuntato.it/lode
Unfortunately, it doesn't work at the moment.

@borsna
Copy link
Member

borsna commented Feb 22, 2013

Thomas: thanks, i will have a look at LODE when its online again, in the meantime the xslt will work for the basic needs.
I looked at the 'rdfs:comment's in the model and i think we should use it primarily for describing the Class or property and not general information about using dcterms etc. I think the descriptions from the dublin core paper is a good start for explaining the terms we use.

@boschthomas
Copy link
Member

I agree.
Olof, you are modifying the rdfs:comments?

@borsna
Copy link
Member

borsna commented Feb 26, 2013

Thomas: i will replace them later this week with the descriptions used in the paper and write new ones for those missing. Will tell you when a review is needed.

@boschthomas
Copy link
Member

Olof, please use the defintions from the spec. I added the definitions from the DC paper.

@borsna
Copy link
Member

borsna commented Feb 26, 2013

Thomas: okay will pick them from there.

@boschthomas
Copy link
Member

already covered by other open issues

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

3 participants