- From: Harshvardhan J. Pandit <me@harshp.com>
- Date: Tue, 5 Jan 2021 12:22:38 +0000
- To: "Railean, Alexander" <alexander.railean@informatik.uni-goettingen.de>, "public-dpvcg@w3.org" <public-dpvcg@w3.org>
The range for hasFrequency shouldn't be hard-set. So one could use enums (instances of a class are a better design pattern than strings IMO) or OWL-TIME or XSD or ints. Same for duration or location or other properties. While this makes reconciling different instance / data difficult because of data types, it does provide more flexibility to choose what to represent the data with. On 05/01/2021 12:16, Railean, Alexander wrote: > > Thus, the notation needs to be a bit more flexible to accommodate this case. > -- --- Harshvardhan J. Pandit, Ph.D Research Fellow ADAPT Centre, Trinity College Dublin https://harshp.com/
Received on Tuesday, 5 January 2021 12:25:10 UTC