See also: IRC log
http://htmlpreview.github.io/?https://github.com/w3c/hcls-fhir-rdf/blob/master/spec/index.html
oops! eric moved it already. he's getting the new link...
<ericP> http://w3c.github.io/hcls-fhir-rdf/spec/
eric: github's convention is that
a branch called 'gh-pages' will cause the HTML to be
rendered.
... I moved master to gh-pages.
... If you have outstanding commits you need to set your remote
to gh-pages
... And I set the default branch to gh-pages
list branches: https://github.com/w3c/hcls-fhir-rdf/branches
scribe: If you do not have outstanding edits, then you should be able to change your remote branch
dbooth: Or just wipe out the copy
on your local drive, and do a new 'git clone' of the
repository
... That should set up your default branch to be correct:
gh-pages
lloyd: Probably want separate pages for what the RDF versus what the OWL looks like. Should model the RDF part after other FHIR pages.
View the draft spec here: http://w3c.github.io/hcls-fhir-rdf/spec/
eric, raw xhtml link needs to be update also, to: https://github.com/w3c/hcls-fhir-rdf/blob/gh-pages/spec/index.html
"See spec/index.html"
GitHub repository -- See spec/index.html
lloyd: Content needs to xhtml
instead of html, and the content needs to be split between RDF
and OWL pieces.
... Some will care about RDF but not OWL.
... The header/footer are easy enough to add later as long as
we are consistent with heading levels, etc.
Here is a draft target, of what the RDF starting page should look like: https://hl7-fhir.github.io/rdf.html
lloyd: We'll modify the ref implementations to parse and produce RDF, and update the build process to convert all of the examples from XML to RDF and round-trip
tony: Add an RDF column?
lloyd: yes. When looking at a
particular resource, one change is adding the RDF column. Also
under each particular resource, there would be a section on RDF
for that resource.
... And on the downloads page, we would add a download for the
OWL schemas.
tony: So the build tooling will generate the OWL classes?
lloyd: Yes. Two possible ways to do that. 1. an XSLT that runs on the Structure Definition syntax. 2. Write it in Java and include it in the build process.
dbooth: Should we work the side-by-side doc into the form in https://hl7-fhir.github.io/rdf.html ?
lloyd: Yes. Breaking into
separate RDF and OWL pages.
... Right now there is a placeholder for ontology.html, that
would have the ontology description.
... If you look at the XML and JSON tabs it is extremely
generic, with a few examples. But the particular resources are
scattered through the spec, and auto-generated.
... The general principle is to be concise, because developers
don't like to read a lot.
tony: Page 1.18.3 is manually written?
lloyd: Yes, with a few things auto-inserted for header/footer, etc.
tony: One deliverable is 1.18.3
1.18.3: https://hl7-fhir.github.io/rdf.html
lloyd: the other is 1.25:
https://hl7-fhir.github.io/ontology.html
which is under Documentation
... warning: the section numbers may changes
dbooth: Our Deliverables are
listed here:
http://wiki.hl7.org/index.php?title=RDF_for_Semantic_Interoperability#Deliverables_and_Editors
... We need to split apart #1 to the RDF and OWL pages
... I have updated the deliverables list, to separately list
the RDF page and the ontology page:
http://wiki.hl7.org/index.php?title=RDF_for_Semantic_Interoperability#Deliverables_and_Editors
eric: In the resource definitions you have the logical table that comes from the structure def, and several tabs for XML, JSON and RDF, with invented languages for describing the data. I was thinking ShEx might be good there.
lloyd: The purpose of the XML and JSON views is to have somethign that looks like what an instance would look like, with some extra metadata embedded in a comment-y way, so that you can paste it into a document and quickly make a valid instance. We should think about what that syntax should look like.
eric: I prototyped that as ShEx so that we can see what it would look like
lloyd: We're really like to have xhtml with highlighting and all, so that we can see how it would look in the spec
<ericP> www.w3.org/2016/FHIR-tutorial/Constellations?shexc
dbooth: Maybe use Turtle annotated with ShEx expressions?
lloyd: Depends on how terse it can be. Want people to have a sense of what the Turtle will look like. The computability of the metadata is not a driver at all. If it is useful we could provide the ShEx representation as an alternative, just as we provide schematron.
dbooth: Could have hover-over that shows the ShEx snippets.
lloyd: Hover-over gives the
definitions.
... Want somethign quite readable for someone familiar with
Turtle, and it should require as little modifcation as possible
to produce valid Turtle after copy and paste.
<scribe> ACTION: dbooth to start separate RDF and Ontology docs on github [recorded in http://www.w3.org/2016/02/09-hcls-minutes.html#action01]
<trackbot> Created ACTION-49 - Start separate rdf and ontology docs on github [on David Booth - due 2016-02-16].
<scribe> CANCELED today.
Tony: Won't have enough ready by 5pm.
ADJOURNED
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: dbooth Inferring Scribes: dbooth Present: David_Booth Marc_T EricP Brian_Pech Tony_Mallia Thomas_Lukasik Rob_Hausam Harold_Solbrig Found Date: 09 Feb 2016 Guessing minutes URL: http://www.w3.org/2016/02/09-hcls-minutes.html People with action items: dbooth[End of scribe.perl diagnostic output]