-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add function PROPERTY
as a synonym for PREDICATE
#178
Comments
I think this question can be asked more broadly. There have already been a few reports that I can classify as minor (those that do not break backward compatibility with SPARQL 1.1). One example was the proposal to add SHA3 functions. I think WG should decide where the boundary is for adding new functions to SPARQL 1.2 and what should be reported to sparql-dev as SEP. |
We need to consider the This issue is a little different though - it's for a synonym of an existing function, not adding a function.
|
I don't see a need for adding such a synonym for this function name (but I will also not fight against it if many here would like to see this added). Having both |
-1 from me as well. Offering multiple ways to achieve the same thing often adds more confusion than benefit IMO. |
URI and IRI were already being used interchangeably even back in SPARQL 1.0 days. The HTTP URL spec is UTF-8. We all use predicate/property interchangeably in common usage so, as I see it, it is already "out there". Given an open choice - which of |
I would prefer |
I'd be in favor of supporting both names. As @afs says, they are often used interchangeably. With the potential of rdf-star to bring more visibility and potential use from LPG communities, I think I think the existence of |
While I understand the argument for supporting both terms, I would caution against using
|
I also prefer |
"property" and "predicate" get used interchangeably.
Should we have a synonym
PROPERTY
forPREDICATE
?(The grammar currently has
PREDICATE
)c.f.
isURI
/isIRI
andURI
/IRI
The text was updated successfully, but these errors were encountered: