Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Write a parser to fetch the semantic references of simple enough classes
See original GitHub issueI’m submitting a
- bug report.
- feature request.
Current Behaviour:
This is related to the discussion we had here https://docs.google.com/document/d/1J9PlcXUfu76lruJCb_1vKcQauL-J6H2wxZxqzdZO9dQ/edit
Expected Behaviour:
Every class/property needs to have a semantic reference. If it’s a complex object then define the object in vocab itself and provide semantic references to its properties else directly provide a semantic reference. Either way, semantic references need to be there.
It would be better if you write a parser that’ll try to find semantic references for properties from Schema.org and similar sources.
Do you want to work on this issue?
NO
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m not sure. Figure something out
yes , makes sense . Beautiful Soup should be good enough to do the job right ? I will search schema.org using the name given in OAS and use the first result if found . If not found will parse other semantic resources . Also the schema.org parser should be another module right ?