Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    erikoskarwallin
    @erikoskarwallin
    (I'm using web version in Mac- working fine so far)
    Karl Hammar
    @hammar
    Am pasting the link to this chat in various places around the GitHub repos. Hopefully the channel will have more than two members at some point :-)
    harissecic
    @harissecic
    Hello guys, just found out about gitter channel for REC. Instead of spaming Karl via email I could move conversations over here.
    Joakim Eriksson
    @joakimeriksson
    The OS-X client seems to work fine!
    Karl Hammar
    @hammar
    Excellent. Windows client also works well. Actually seems more light-weigh than Slack by a fair amount..
    erikoskarwallin
    @erikoskarwallin
    Ios client seems ok so far
    Karl Hammar
    @hammar
    Excellent. I think we should initiate the move from the REC-internal Slack channel to here. There's very little private discussions on that channel anyway, and such discussions could be held in a private room here. @erikoskarwallin , @joakimeriksson : do we have consensus ons uch a move in the tech group? And is it in the mandate of the tech group to initiate this? (We'll have to check with Peter Hartlev as well of course)
    Peter Hartlev
    @PeteHart
    I’ve now joined Gitter and setup clients :-)
    Karl Hammar
    @hammar
    đź‘Ť
    Karl Hammar
    @hammar
    @PeteHart: i just merged your pull request for the Lantmäteriet branch. There is one un-annotated class that will need some documentation (EntranceType) before merging back into master. Let me know once you have those annotations in place and we can do the merge. Thanks for this!
    Peter Hartlev
    @PeteHart
    @hammar ok I’ll fix and let you know, note that we need to also think over the Apartment class, since we plan to have such as subclass for collection I think we need to remove it from here and have the annotations on the new subclass instead?
    Karl Hammar
    @hammar
    @PeteHart Good point. If we can get concensus in the community for a definition of an apartment as essentially just being a collection of rooms, then that model makes good sense. If, however, there are reasons to model Apartment as something other than Collection (my knowledge of the domain specifics is limited) we should perhaps postpone this until our meeting on January 29. That would postpone 3.2 though. Tricky choice.
    Peter Hartlev
    @PeteHart
    As to 3.2 timeline I personally feel we’d be good with a "first quarter” release, think we have numer of things to harmonize between Lease, Collection, Lantmäteriet, and likely more...
    With regards to Apartment, I suppose we should only have one subclass, irrespective of superclass, and i feel this is likely not from Lamntmäteriet since this will have a Swedish flavour to it
    As to Apartment being a collection of rooms it works for me, think the abstraction works, however, since its also a leasable object we need to think it over carefully with respect to the Lease module classes
    Peter Hartlev
    @PeteHart
    Uncertain if such discussions should take place in the GitHub issues or here at Gitter… guess the issues notes may end up here :-)
    Karl Hammar
    @hammar
    Good points @PeteHart . There is definitely need for a thorough discussion on the leasable/apartment concepts. I'm personally OK with taking such discussions both here and on GitHub, depending perhaps on the degree of specificity of the discussion.
    @/all We will run a workshop on the concepts and relations in the Leasable space (e.g., Apartments) and how to best model this in REC. 29 January, tentatively at Vasakronan in Stockholm. If you are interested in such discussions and think you have something to bring to the table, send me a note at karl.hammar@jonkoping.ai, and I'll send out a calendar invite with more details once we have them.
    Joakim Eriksson
    @joakimeriksson
    @hammar, will you also come for the Datalabs startworkshop? I see that this date is the day after.
    Peter Hartlev
    @PeteHart
    @hammar I suppose we park the Lantmäteriet module until after 29/1 since the lacking part regards the Lease structure (Apartment in particular)?
    @hammar note that i did a new pull request with missing annotations and alos i think i F’ed up and capitalized all labels, it appears we only capitalize on Classes (and that you did that)
    If you can confirm the cpaitalization schema for labels I update the file again and create a new pull request!?
    Karl Hammar
    @hammar
    @PeteHart You should have commit rights to the repo directly, so you can work in a branch there. No pull request needed.
    On capitalisation: we’re using initial uppercase for classes (both in IRIs and labels), and all lowercase (labels) and lower initial camelCase (IRIs) for properties.
    Peter Hartlev
    @PeteHart
    @hammar what about capitalization for named individuals - their labels and IRIs?
    Peter Hartlev
    @PeteHart
    @hammer just pushed updated Lantmäteri module, annotations fixed, on named individuals I’ve used PascalCase on IRI and lower case on labels
    Peter Hartlev
    @PeteHart
    @perkarlberg @hammar can either of you please share the Actuation description/document you refered to earlier
    Peter Hartlev
    @PeteHart
    @perkarlberg @hammar have my head down the actuation module, I’d assume that the URL of the actuation interface is to be a property in REC but cannot seem to find any href or similar? Or is it so that annotaiton owl:sameAs is to be used to refer to the actuation interface?
    Alternatively the href may be part of the key-value refs?
    on key-value definition, I see no value, only value data type, assume the hasValue data property is to be used?
    Peter Hartlev
    @PeteHart
    <gml:Point gml:id="p21" srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <gml:coordinates>45.67, 88.56</gml:coordinates>
    </gml:Point>
    Above is an example of a GML serialization of a geo point, to be correct “gml:" would have to be “expanded” to full IRI
    @hammar Is this what goes into asGML/GML Literal?
    Joakim Eriksson
    @joakimeriksson
    I have been discussing Azure digital twins with Yanzi (just a little) - https://github.com/Azure/IoTPlugandPlay/tree/master/DTDL - Did anyone see any schemas (RDF, etc) published for their digital twins APIs and data models?
    Peter Hartlev
    @PeteHart
    Nope, but didnt look either ;-) a fast browse through the DTDL link shows resemblance with the WoT Thing Description that HĂĄkan (@wotifi I believe) and I are deep into
    @joakimeriksson perhaps time for a touch base as we discussed last year :-)
    Karl Hammar
    @hammar
    @PeteHart sorry about the delay in responding.. holiday break :-) I'll make some threads on your questions shortly.
    Karl Hammar
    @hammar
    @perkarlberg I'm looking at RealEstateCore/rec#29 which I think was originated with you (correct me if I'm wrong). I think I may have misinterpreted when putting this in GitHub. Isn't it the range that you want broadened, rather than the domain -- i.e., a way of expressing that devices are mounted in a building or piece of real estate directly, not necessarily only in a building component?
    Karl Hammar
    @hammar
    So all, there's now a first draft of an Analytics ontology module, as we have worked on at two workshops at Vasakronan, see https://github.com/RealEstateCore/rec/tree/analytics. This is not yet fully documented with labels and comments, but I'll get around to that once we've had someone other than me look at the structure of the thing. How do we do QA on this? Preferably some of you with real analytics use cases could sit down with me in Stockholm January 28 or 29? Or an online conf call to test how we would use it in practice? Ping @PeteHart @perkarlberg @erikoskarwallin @joakimeriksson
    Also, note: the DataAnalysisConfiguration class is completely unspecified as of yet. It obviously needs some fleshing out in terms of the vocabulary we discussed at the last conference, possibly based on OpenTDSB
    Karl Hammar
    @hammar

    All: As previously announced, on January 29 I will be at Vasakronan (Mäster Samuelsgatan 56) in Stockholm, from 9-12, doing a REC development workshop. Initially the idea was to focus on improving the quality of the Lease module in REC, but looking at the roadmap for 3.2 and other pressing issues, we're going to reorient this workshop with a focus on:

    1) QA and evaluation of the Analysis module linked above (Does it work for your purposes/data? What needs to be extended/fixed before release? Any other ontologies we need to align it against?)

    2) REC API -- remaining open issues, evaluation, and design choices (I will spend the majority of the coming 2 weeks working on the API generator and related technologies).

    If you want to attend this workshop, ping me here or on email. I have confirmation from @PeteHart and @erikoskarwallin that they will attend, but everyone with an interest in REC development who can get to Stockholm is most welcome to attend.

    Karl Hammar
    @hammar
    Hey all. The OWL to OpenAPI Spec generator is now more-or-less feature complete. I'll be spending a day or two testing it out, clearing out some compiler warnings, etc., but I wouldn't mind others looking at it also. See https://github.com/hammar/owl2oas for the code, and https://github.com/hammar/owl2oas/blob/master/OWL2OAS/examples/rec-full-v3.1.yaml for an example of what is generated when I run it over the Full version of REC 3.1 (as available online)
    erikoskarwallin
    @erikoskarwallin
    Great news!
    Karl Hammar
    @hammar
    Of course, the generated OpenAPI spec is rather large/heavy (430+ KB) but the ontology isn't exactly small either. Feel free to test the file in the Swagger Editor at https://editor.swagger.io/
    Karl Hammar
    @hammar
    Hey all. There is now some documentation on OWL 2 Punning use in REC at https://github.com/RealEstateCore/rec/tree/master/doc
    This afternoon further documentation of design pattern use in REC will hopefully be added (or possibly later this week)
    Peter Hartlev
    @PeteHart
    I want to direct your attention to the API conversation/room where detailed information on the introduction of Hydra in the API (incl OpenAPI Spec) is shared
    This is particular important for practitioners developing a REC platform
    Peter Hartlev
    @PeteHart
    Introduction of Collection and Lantmäteriet modules in 3.2 requires some minor changes in the Lease module. I’ve documented a proposal with very little impact on the Lease module. See here https://docs.google.com/presentation/d/13BSPt1gnfovGj1pBV1el-Zk_UfOhwPv_Q9JchRb8WEk/edit?usp=sharing. Ambition is to discuss and decide in workshop next week (January 29). Comments and reflections are most welcome. Either here or direct in document with the comment tool.
    erikoskarwallin
    @erikoskarwallin
    good work!